> > Stupid me, this is my fault. I simply haven't noticed that I did not use the
> > secured URL but used the read-only URL.
> >
> > Sorry for the noise!
>
> Its not noise, someone else is bound to make the same mistake,
> especially if they are new committer and may have old read only
> repositor
> Stupid me, this is my fault. I simply haven't noticed that I did not use the
> secured URL but used the read-only URL.
>
> Sorry for the noise!
Its not noise, someone else is bound to make the same mistake,
especially if they are new committer and may have old read only
repositories checked out
Am 2013-05-21 03:17, schrieb Olivier Lamy:
Strange.
You are listed here http://people.apache.org/committer-index.html#michaelo
And with correct Karma.
I checked in ldap and you are in the group:
olamy@minotaur:~$ list_unix_group.pl maven | grep michaelo
michaelo
Are you sure about your password
Strange.
You are listed here http://people.apache.org/committer-index.html#michaelo
And with correct Karma.
I checked in ldap and you are in the group:
olamy@minotaur:~$ list_unix_group.pl maven | grep michaelo
michaelo
Are you sure about your password ? Can you log here https://id.apache.org ?
2
thank you for the patch
moved to MPOM-43 [1]
and applied in Maven parent pom [2]
Regards,
Hervé
[1] https://issues.apache.org/jira/browse/MPOM-43
[2] http://maven.apache.org/pom/maven/
Le lundi 20 mai 2013 15:26:48 Baptiste MATHUS a écrit :
> Fwiw: http://jira.codehaus.org/browse/MNG-5481
>
I should actually add that depMgmt actually happens at TWO levels in a
graph:
1. the top-level that enforces versions/scope/exclusions for the whole graph
2. the direct project (or parent) that declares the dependency to be managed
This makes sense, if you think about it: if you leave a versio
On 05/16/2013 05:42 PM, Jörg Hohwiller wrote:
is there already some slight inital draft or idea for a strategy how maven x.y
could deal with jigsaw?
I wrote up a very preliminary sketch about a year ago [1] but have not worked on it since then, and whatever worked then may or may not work with
Hi folks,
it seems like I do not have full access to the Maven directory in the
Subversion repository.
See
commit -m "REOPENED - issue MSKINS-72: Add copyright notice position
option" D:/Projekte/maven-fluido-skin-trunk/src/site/apt/index.apt.vm
D:/Projekte/maven-fluido-skin-trunk/src/main/r
This is something I've seen in the wild in the past couple of weeks,
too. I had to mock it up and see it for myself before I believed the user.
Personally, option A makes the most sense to me. The reason is in
Geoffrey's third slide...I would expect MyProject to simply append the
dependency gr
Fwiw: http://jira.codehaus.org/browse/MNG-5481
Cheers
2013/5/15 Kristian Rosenvold
> You'll need to attach the patch somewhere that does not mangle patches,
> like the mailing list does :)
>
>
>
> Kristian
>
>
> 2013/5/15 Baptiste MATHUS
>
> > Well, I cannot do it myself since I'm not a commi
I don't undesrtand the last failure:
- it works on my machine
- ArtifactNotFoundException: Could not find artifact
org.apache.maven.skins:maven-default-skin:jar:1.0 in central
(file:target/null), but it is available in the local repository [1]
If someone knows what's happenning...
Regards,
Her
11 matches
Mail list logo