On 8/30/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> Yeah, we should do the same with the recently departed antlr plugin
> too. Move trunk to /retired/* (original tags would remain in the
> original place) would get my vote.
Sounds better than sandbox.
--
"Besides, manipulating elections is un
Yeah, we should do the same with the recently departed antlr plugin
too. Move trunk to /retired/* (original tags would remain in the
original place) would get my vote.
- Brett
On 30/08/2007, at 4:31 PM, Arnaud HERITIER wrote:
We can move it in the sandbox (just to keep it visible) ?
Or in
We can move it in the sandbox (just to keep it visible) ?
Or in a deprecated area ?
Arnaud
On 30/08/2007, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Its always gonna be in svn, so I'd just nuke it and if anyone wants
> to find the old stuff they can dig it up.
>
> --jason
>
>
> On Aug 29, 2007, at
+1
Please can we try exceptionally to note wait for a 72h vote ?
All corporate mirrors are now corrupted with those erroneous releases.
Arnaud
On 30/08/2007, Brett Porter <[EMAIL PROTECTED]> wrote:
> +1 again.
>
> This time I tested it with a clean local repository so I didn't pick
> up the prev
On 30/08/2007, at 3:32 PM, Jason van Zyl wrote:
On 29 Aug 07, at 10:06 PM 29 Aug 07, Wayne Fay wrote:
Does anyone else think this is a terrible idea? If we allow this
then there is no going back.
Yah, I'd love to hear it if anyone can pick holes in it, as I don't
want to steer down any bad
On 29 Aug 07, at 10:06 PM 29 Aug 07, Wayne Fay wrote:
Does anyone else think this is a terrible idea? If we allow this
then there is no going back.
Yah, I'd love to hear it if anyone can pick holes in it, as I don't
want to steer down any bad tracks repository wise either.
I'm not a huge fa
> > Does anyone else think this is a terrible idea? If we allow this
> > then there is no going back.
>
> Yah, I'd love to hear it if anyone can pick holes in it, as I don't
> want to steer down any bad tracks repository wise either.
I'm not a huge fan simply because I like the simplicity of "ever
On 30/08/2007, at 2:56 AM, Jason van Zyl wrote:
On 29 Aug 07, at 8:20 AM 29 Aug 07, Brett Porter wrote:
On 30/08/2007, at 1:11 AM, Jason van Zyl wrote:
Like with any other artifact (including if versions are split
across multiple repositories), it searches them all in sequence if
they
Its always gonna be in svn, so I'd just nuke it and if anyone wants
to find the old stuff they can dig it up.
--jason
On Aug 29, 2007, at 8:07 PM, Brett Porter wrote:
On 30/08/2007, at 3:01 AM, Jason van Zyl wrote:
You can fork the code, and change the groupId. People will use
yours, m
On 29 Aug 07, at 8:07 PM 29 Aug 07, Brett Porter wrote:
On 30/08/2007, at 3:01 AM, Jason van Zyl wrote:
You can fork the code, and change the groupId. People will use
yours, most likely, by virtue of you developing it, but we'll
leave the code here for anyone who wants to use it for what
On 30/08/2007, at 3:01 AM, Jason van Zyl wrote:
You can fork the code, and change the groupId. People will use
yours, most likely, by virtue of you developing it, but we'll leave
the code here for anyone who wants to use it for whatever they want
to use it for.
I don't expect there to b
Since alpha-6 was broken, but could have been downloaded, presumably
Carlos went up to alpha-7 to ensure everyone gets the right version.
As for why alpha-6 was broken, it appears an old version of the
release plugin that didn't fill in depMgmt correct was used and so it
stayed pinned to al
+1 again.
This time I tested it with a clean local repository so I didn't pick
up the previous version I tested. Yet another use case for local
repository segregation - I'll try and post that proposal today.
- Brett
On 30/08/2007, at 9:41 AM, Carlos Sanchez wrote:
Here we are again, seem
Thanks Jesse!
On 30/08/2007, at 11:26 AM, Jesse McConnell wrote:
and the maven zone is back up now..
cheerio!
jesse
On 8/29/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
fyi, I am pulling down the continuum instance on
maven.zones.apache.org in
order to update it to the latest beta ve
and the maven zone is back up now..
cheerio!
jesse
On 8/29/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
>
>
> fyi, I am pulling down the continuum instance on maven.zones.apache.org in
> order to update it to the latest beta version..
>
> I'll ping when I get it back up,
>
> jesse
>
> --
> jes
What happened with alpha-6?
On 29 Aug 07, at 4:13 PM 29 Aug 07, Carlos Sanchez wrote:
the release has been removed, a new alpha-7 is being voted on
On 8/30/07, Bill Dudney <[EMAIL PROTECTED]> wrote:
I had to edit my local copy of the plugin pom to look like this;
o
No response, so I'll try again.
What is the appropriate mechanism for mapping a plugin goal to custom
life cycle phase?
In particular to one of the phases used by the maven-release-plugin.
Is it possible in 2.0.7?
Is it being considered for 2.1?
William
-Original Message-
From: Willia
Here we are again, seems that alpha-6 was referencing alpha-5 jars
that I removed as it was improperly released,... well you know the
story now. I have removed both alpha-5 and alpha-6 and go for alpha-7.
The problems of the previous ones have been fixed, now just cross the
fingers not to make a ne
the release has been removed, a new alpha-7 is being voted on
On 8/30/07, Bill Dudney <[EMAIL PROTECTED]> wrote:
> I had to edit my local copy of the plugin pom to look like this;
>
>
>
>
> org.apache.maven.archetype
> maven-archetype-model
> 1.0-alpha-
I had to edit my local copy of the plugin pom to look like this;
org.apache.maven.archetype
maven-archetype-model
1.0-alpha-6
org.apache.maven.archetype
maven-archetype-core
1.0-alpha-6
org.apache.m
fyi, I am pulling down the continuum instance on maven.zones.apache.org in
order to update it to the latest beta version..
I'll ping when I get it back up,
jesse
--
jesse mcconnell
[EMAIL PROTECTED]
This is great news! Thanks Carlos.
I'll be sure to try it out when I do the next release...
Carlos Sanchez wrote:
I've fixed the problem with server settings, now you can specify the
id of source and target repos and it'll use the authentication info in
the settings
From the docs
The plugi
On 29 Aug 07, at 8:41 AM 29 Aug 07, Mark Hobson wrote:
On 29/08/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I would very much like to try and get both versions of Maven to use
it. If at all possibly we should try this and between you, myself,
Patrick and Ralph we can probably determine if t
I've fixed the problem with server settings, now you can specify the
id of source and target repos and it'll use the authentication info in
the settings
>From the docs
The plugin is used from the command line. In the following example we will
copy artifacts from a staging repository located at
On 29/08/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> I would very much like to try and get both versions of Maven to use
> it. If at all possibly we should try this and between you, myself,
> Patrick and Ralph we can probably determine if this is possible. If
> we decide we have to mimic bugs
On 28 Aug 07, at 6:14 PM 28 Aug 07, Tom Davies wrote:
Hi All,
One consequence of Cenqua's acquisition by Atlassian is that we now
have the resources to continue development of the Maven Clover
plugin ourselves. It will remain open source under the Apache
licence, and the source will be h
On 29 Aug 07, at 8:20 AM 29 Aug 07, Brett Porter wrote:
On 30/08/2007, at 1:11 AM, Jason van Zyl wrote:
Like with any other artifact (including if versions are split
across multiple repositories), it searches them all in sequence if
they aren't found in one.
This seems like a good pr
Okay, how about just upping the log level to warn for the time being?
At least we can then see where the potential circular deps are before
forcing failed builds upon people.
Mark
On 29/08/2007, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I'm ok with this so long as it would bring along a flag somewhe
On 30/08/2007, at 1:11 AM, Jason van Zyl wrote:
On 28 Aug 07, at 10:08 PM 28 Aug 07, Brett Porter wrote:
Where are we with this?
The thread went a bit off the rails for some other stuff, and the
only other suggestion I saw was:
On 23/08/2007, at 3:32 AM, Jason van Zyl wrote:
But the ca
On 29 Aug 07, at 6:53 AM 29 Aug 07, Mark Hobson wrote:
Hi Jason,
Apologies for the delayed reply - been a little busy of recent and
just catching up on my inbox. What's the plan here, to consolidate
maven-artifact between 2.0.x and 2.1.x? Sounds good to me. The work
I did on MNG-612 is bran
On 28 Aug 07, at 10:08 PM 28 Aug 07, Brett Porter wrote:
Where are we with this?
The thread went a bit off the rails for some other stuff, and the
only other suggestion I saw was:
On 23/08/2007, at 3:32 AM, Jason van Zyl wrote:
But the case that Atlassian wants solved would be very simple
I'm ok with this so long as it would bring along a flag somewhere
warn vs break or something, with default being
break, so we can still accomodate people that are using deps like
dom4j and jaxen.
Also, it would need to be well-documented so we can point all the
users@ people to the FAQ when they a
Pretty sure dom4j/jaxen still reference each other :(
- Brett
On 30/08/2007, at 12:00 AM, Mark Hobson wrote:
Hi there,
I've just encountered the silent disabling of circular dependencies in
a build whilst refactoring projects. Previously I've seen these
failing the build, as expected, but it
Hi there,
I've just encountered the silent disabling of circular dependencies in
a build whilst refactoring projects. Previously I've seen these
failing the build, as expected, but it appears that transitive
circular dependencies are merely logged as debug. See the comment in
DefaultArtifactColl
Hi Jason,
Apologies for the delayed reply - been a little busy of recent and
just catching up on my inbox. What's the plan here, to consolidate
maven-artifact between 2.0.x and 2.1.x? Sounds good to me. The work
I did on MNG-612 is branched off 2.0.x at the moment.
Let me know if I can help.
Hi
Maven expects the Source code in src/main/java , however RAD expects all the
ejb java files to be present in ejbModule.
Can I change the directory structure in Maven from src/main/java to
ejbModule? If yes, can anyone guide me on how can i do that?
Thanks and Regards
Hemant Ved
On 29/08/2007, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> thanks, I'm going to add this to the javadoc ;)
Sure thanks, I'll try to be less succinct in future :)
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional co
thanks, I'm going to add this to the javadoc ;)
On 8/29/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> On 21/08/2007, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > Why DependencyNode.getDepth was deprecated? it's still useful
>
> Sorry for the delayed reply - working my way though my inbox..
>
> It
On 21/08/2007, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> Why DependencyNode.getDepth was deprecated? it's still useful
Sorry for the delayed reply - working my way though my inbox..
It was deprecated with the introduction of node visitors and filters
since it can give misleading results. For e
On 29/08/2007, at 6:14 PM, Nigel Magnay wrote:
Which is great - it just felt like there was some disagreement between
whether it's actually a problem to be fixed :- "let's fix the local
repository" vs "Yes, I'm just saying separate processes should be
using
separate local repositories." which
Which is great - it just felt like there was some disagreement between
whether it's actually a problem to be fixed :- "let's fix the local
repository" vs "Yes, I'm just saying separate processes should be using
separate local repositories." which I didn't understand as I couldn't see
how a locally
41 matches
Mail list logo
