RE: [VOTE] Release Maven 2.0.5 (take 2)

[LAMY Olivier]

+1 (non binding).
Tested on all corporate production builds.

--
Olivier 

-Message d'origine-
De : Jason van Zyl [mailto:[EMAIL PROTECTED] 
Envoyé : lundi 12 février 2007 05:33
À : Maven Developers List
Objet : [VOTE] Release Maven 2.0.5 (take 2)

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: 
[EMAIL PROTECTED]


This e-mail, any attachments and the information contained therein ("this 
message") are confidential and intended solely for the use of the addressee(s). 
If you have received this message in error please send it back to the sender 
and delete it. Unauthorized publication, use, dissemination or disclosure of 
this message, either in whole or in part is strictly prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que  les informations 
contenues dans ce message ( ci après "le message" ), sont confidentiels et 
destinés exclusivement à l'usage de la  personne à laquelle ils sont adressés. 
Si vous avez reçu ce message par erreur, merci  de le renvoyer à son émetteur 
et de le détruire. Toutes diffusion, publication, totale ou partielle ou 
divulgation sous quelque forme que se soit non expressément autorisées de ce 
message, sont interdites.
-


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Arnaud HERITIER]

+1

Works fine on my projects

Arnaud

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Dan Tran]

Works on our builds with pde-maven-plugin, native-maven-plugin,
maven-dependency-plugin, and ofcourse java.

-D


On 2/13/07, Barrie Treloar <[EMAIL PROTECTED]> wrote:


+1 (I get a binding vote, yay)

Works on our project which includes an uber-archive of artifacts and
an eclipse pde build

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Barrie Treloar]

+1 (I get a binding vote, yay)

Works on our project which includes an uber-archive of artifacts and
an eclipse pde build

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Release Maven 2.0.5 (take 2)

[Brian E. Fox]

 
+1 works on my most complicated build, no problems.

>
> 2007/2/11, Jason van Zyl <[EMAIL PROTECTED]>:
> > Hi,
> >
> > The assemblies that people are interested in are staged here:
> >
> > http://people.apache.org/~jvanzyl/staging-repository/org/apache/mave
> > n/
> > maven-core/2.0.5/
> >
> > Here is the JIRA roadmap:
> >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?
> > reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> > order=DESC
> >
> > +1
> >
> > Thanks,
> >
> > Jason.
> >
> >
> > 
> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
jesse mcconnell
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jesse McConnell]

+1 \o/ woohoo!

On 2/13/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:

Our trunks build fine: +1

Thanks,

Vincent

2007/2/11, Jason van Zyl <[EMAIL PROTECTED]>:
> Hi,
>
> The assemblies that people are interested in are staged here:
>
> http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
> maven-core/2.0.5/
>
> Here is the JIRA roadmap:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> order=DESC
>
> +1
>
> Thanks,
>
> Jason.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
jesse mcconnell
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Vincent Siveton]

Our trunks build fine: +1

Thanks,

Vincent

2007/2/11, Jason van Zyl <[EMAIL PROTECTED]>:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason van Zyl]

On 13 Feb 07, at 9:41 AM 13 Feb 07, Trygve Laugstøl wrote:


Jason van Zyl wrote:

Hi,
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/maven-core/2.0.5/ Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


+1, my stuff builds.



Great, looks like we're out of the frying pan at least :-)

Jason.


--
Trygve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Trygve Laugstøl]

Jason van Zyl wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 


+1, my stuff builds.

--
Trygve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Release Maven 2.0.5 (take 2)

[Brian E. Fox]

Mostly windows, but also some flavors of linux (Fedora 6 and a custom
built kernel).

-Original Message-
From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 13, 2007 4:17 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.5 (take 2)

Hi Brian,

Strange, hey?... Which OS are you running Maven on? Because Stephen's
got
the same error as me on Fedore Core 6...

Fabrice.

On 2/13/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>
> Hi Fabrice,
> I'm doing exactly what you describe and from what I can see, the
latest
> 2.0.5 is working ok. I did find an issue in one of the early 2.0.5
> release candidates, but it was fixed. The method I use is attached to
> http://jira.codehaus.org/browse/MNG-2749.
>
> Thanks,
> Brian
>
> -Original Message-
> From: Fabrice Bellingard [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 12, 2007 10:02 AM
> To: Maven Developers List
> Subject: Re: [VOTE] Release Maven 2.0.5 (take 2)
>
> Hi Jason,
>
> The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader
problem
> loading a resource from a build extension Jar") still breaks my
> integrations
> with this last build of Maven... :-( As you tried the test project
> successfully, I don't understand what can be specific to my
environment
> .
> I've made a clean installation of Maven (no local repository and last
> build
> of 2.0.5), and still it breaks the test case I attached on JIRA.
>
> Is there someone here who develops Checkstyle custom Checks and
bundles
> them
> in a JAR (along with the configuration file) which is specified in the
> build
> extensions of another project? Or at least someone else who could test
> the
> case I described on JIRA? (with a clean installation)
>
> I may sound insisting on this, but the fact is that we have developed
> custom
> Checks in my company, and tens of projects are using them to generate
> the
> checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't
> be
> able to migrate to this new and awaited version of Maven. Which is sad
> because they're looking forward to using it...
>
> Apart from that, everything works fine. :-)
>
> Fabrice.
>
> On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > The assemblies that people are interested in are staged here:
> >
> >
>
http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
ttp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/>
> > maven-core/2.0.5/
> >
> > Here is the JIRA roadmap:
> >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa ?
> > reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> > order=DESC
> >
> > +1
> >
> > Thanks,
> >
> > Jason.
> >
> >
> >
-
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Stephen Duncan]

Actually, sorry for being misleading, but checkstyle as an extension
seems to work just fine for me.  However, I did notice that another
case where I was using a build extension is broken for me.  Again
sorry for the confusion.  I've created an issue for what I saw:
http://jira.codehaus.org/browse/MNG-2821

-Stephen

On 2/13/07, Fabrice Bellingard <[EMAIL PROTECTED]> wrote:

Hi Brian,

Strange, hey?... Which OS are you running Maven on? Because Stephen's got
the same error as me on Fedore Core 6...

Fabrice.

On 2/13/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>
> Hi Fabrice,
> I'm doing exactly what you describe and from what I can see, the latest
> 2.0.5 is working ok. I did find an issue in one of the early 2.0.5
> release candidates, but it was fixed. The method I use is attached to
> http://jira.codehaus.org/browse/MNG-2749.
>
> Thanks,
> Brian
>
> -Original Message-
> From: Fabrice Bellingard [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 12, 2007 10:02 AM
> To: Maven Developers List
> Subject: Re: [VOTE] Release Maven 2.0.5 (take 2)
>
> Hi Jason,
>
> The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader problem
> loading a resource from a build extension Jar") still breaks my
> integrations
> with this last build of Maven... :-( As you tried the test project
> successfully, I don't understand what can be specific to my environment
> .
> I've made a clean installation of Maven (no local repository and last
> build
> of 2.0.5), and still it breaks the test case I attached on JIRA.
>
> Is there someone here who develops Checkstyle custom Checks and bundles
> them
> in a JAR (along with the configuration file) which is specified in the
> build
> extensions of another project? Or at least someone else who could test
> the
> case I described on JIRA? (with a clean installation)
>
> I may sound insisting on this, but the fact is that we have developed
> custom
> Checks in my company, and tens of projects are using them to generate
> the
> checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't
> be
> able to migrate to this new and awaited version of Maven. Which is sad
> because they're looking forward to using it...
>
> Apart from that, everything works fine. :-)
>
> Fabrice.
>
> On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > The assemblies that people are interested in are staged here:
> >
> >
> http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ ttp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/>
> > maven-core/2.0.5/
> >
> > Here is the JIRA roadmap:
> >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa ?
> > reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> > order=DESC
> >
> > +1
> >
> > Thanks,
> >
> > Jason.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>




--
Stephen Duncan Jr
www.stephenduncanjr.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Fabrice Bellingard]

Hi Brian,

Strange, hey?... Which OS are you running Maven on? Because Stephen's got
the same error as me on Fedore Core 6...

Fabrice.

On 2/13/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:


Hi Fabrice,
I'm doing exactly what you describe and from what I can see, the latest
2.0.5 is working ok. I did find an issue in one of the early 2.0.5
release candidates, but it was fixed. The method I use is attached to
http://jira.codehaus.org/browse/MNG-2749.

Thanks,
Brian

-Original Message-
From: Fabrice Bellingard [mailto:[EMAIL PROTECTED]
Sent: Monday, February 12, 2007 10:02 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.5 (take 2)

Hi Jason,

The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader problem
loading a resource from a build extension Jar") still breaks my
integrations
with this last build of Maven... :-( As you tried the test project
successfully, I don't understand what can be specific to my environment
.
I've made a clean installation of Maven (no local repository and last
build
of 2.0.5), and still it breaks the test case I attached on JIRA.

Is there someone here who develops Checkstyle custom Checks and bundles
them
in a JAR (along with the configuration file) which is specified in the
build
extensions of another project? Or at least someone else who could test
the
case I described on JIRA? (with a clean installation)

I may sound insisting on this, but the fact is that we have developed
custom
Checks in my company, and tens of projects are using them to generate
the
checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't
be
able to migrate to this new and awaited version of Maven. Which is sad
because they're looking forward to using it...

Apart from that, everything works fine. :-)

Fabrice.

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> The assemblies that people are interested in are staged here:
>
>
http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
> maven-core/2.0.5/
>
> Here is the JIRA roadmap:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa ?
> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> order=DESC
>
> +1
>
> Thanks,
>
> Jason.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Fabrizio Giustina]

Works fine for me, +1

fabrizio

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Release Maven 2.0.5 (take 2)

[Brian E. Fox]

Hi Fabrice,
I'm doing exactly what you describe and from what I can see, the latest
2.0.5 is working ok. I did find an issue in one of the early 2.0.5
release candidates, but it was fixed. The method I use is attached to
http://jira.codehaus.org/browse/MNG-2749.

Thanks,
Brian

-Original Message-
From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 12, 2007 10:02 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.5 (take 2)

Hi Jason,

The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader problem
loading a resource from a build extension Jar") still breaks my
integrations
with this last build of Maven... :-( As you tried the test project
successfully, I don't understand what can be specific to my environment
.
I've made a clean installation of Maven (no local repository and last
build
of 2.0.5), and still it breaks the test case I attached on JIRA.

Is there someone here who develops Checkstyle custom Checks and bundles
them
in a JAR (along with the configuration file) which is specified in the
build
extensions of another project? Or at least someone else who could test
the
case I described on JIRA? (with a clean installation)

I may sound insisting on this, but the fact is that we have developed
custom
Checks in my company, and tens of projects are using them to generate
the
checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't
be
able to migrate to this new and awaited version of Maven. Which is sad
because they're looking forward to using it...

Apart from that, everything works fine. :-)

Fabrice.

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> The assemblies that people are interested in are staged here:
>
>
http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
> maven-core/2.0.5/
>
> Here is the JIRA roadmap:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa ?
> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> order=DESC
>
> +1
>
> Thanks,
>
> Jason.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Release Maven 2.0.5 (take 2)

[Brian E. Fox]

"Well, in any case it would be great to integrate the code of
http://jira.codehaus.org/browse/MNG-2676 into the dependencies plugin
and get a release. It is a great help to analyse and fix such situations
(here integrated into our internal info plugin)"

The current alpha-2 release is close to ready with just a couple of
issues. Anything major like this I'd like to put into alpha-3 so it
doesn't hold up the release.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Stephen Duncan]

Actually, using build extensions in ways that worked in Maven 2.0.4
now fail in 2.0.5 for me using Fedora Core 6.

- Stephen

On 2/12/07, Fabrice Bellingard <[EMAIL PROTECTED]> wrote:

Thanks for the hint, Dan, this actually works perfectly!
I wasn't aware of this way to specify the JAR. It would be worth updating
the documentation of the Checkstyle plugin. I will create a JIRA issue for
this.

FYI, Jason, yes, I've executed the test project on the bane of your
existence ;-)
  - Windows XP with Java 1.5.0_06
  - Windows 2k with Java 1.4.2_02
So even if this way of using the build extension is deprecated, I think this
remains a bug on Windows.

Anyways, everything works fine now.

So here is my (non-binding) +1 :-)
Fabrice.

On 2/12/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use
> that.   However, we don't put it in the extensions.   We put it as a
> direct
> dependency for the plugin:
> 
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 
>
>  org.apache.cxf
>  cxf-buildtools
>  . 
>
> 
> ..
> 
> and that works fine with 2.0.5.
>
>
> Dan
>




--
Stephen Duncan Jr
www.stephenduncanjr.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Fabrice Bellingard]

Thanks for the hint, Dan, this actually works perfectly!
I wasn't aware of this way to specify the JAR. It would be worth updating
the documentation of the Checkstyle plugin. I will create a JIRA issue for
this.

FYI, Jason, yes, I've executed the test project on the bane of your
existence ;-)
 - Windows XP with Java 1.5.0_06
 - Windows 2k with Java 1.4.2_02
So even if this way of using the build extension is deprecated, I think this
remains a bug on Windows.

Anyways, everything works fine now.

So here is my (non-binding) +1 :-)
Fabrice.

On 2/12/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:


Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use
that.   However, we don't put it in the extensions.   We put it as a
direct
dependency for the plugin:

org.apache.maven.plugins
maven-checkstyle-plugin

   
 org.apache.cxf
 cxf-buildtools
 . 
   

..

and that works fine with 2.0.5.


Dan

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Stephen Duncan]

Aha!  Apparently this was fixed in Maven 2.0.5, as I just tested and
it failed with 2.0.4, but worked when I tried it right afterward in
2.0.5.

Similarly, I have a project that uses the xfire-generator wsgen task,
and I had it defined as an extension.  This works with 2.0.4, but is
broken with 2.0.5.  However, changing it to a plugin dependency made
it work again.

Beyond this issue of extensions vs. plugin dependencies, the rest of
my build worked fine with Maven 2.0.5.

-Stephen

On 2/12/07, Stephen Duncan <[EMAIL PROTECTED]> wrote:

I've actually been telling people on the mailing list to use
extensions for jar with checkstyle configuration, rather than
plugin->dependencies.  The reason was that, in my testing at the time,
if you didn't already have that plugin dependency in your local repo,
it would not search for it in all your defined repos, it would only
look in central, and therefore break for other people.  At the time I
just assumed using extensions was the right mechanism, but if
plugin->dependencies is 'correct' then it should be verified that it
works correctly...

-Stephen

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> What Dan describes is probably more correct and we should document
> this because extensions are really something that executes where you
> really just want something on the classpath of the plugin. But as far
> as I can tell with the test that I checked in the extension works,
> but that should really be a deprecated form of use.
>
> jason.
>
> On 12 Feb 07, at 10:17 AM 12 Feb 07, Daniel Kulp wrote:
>
> >
> > Fabrice,
> >
> > On Monday 12 February 2007 10:02, Fabrice Bellingard wrote:
> >> The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader
> >> problem
> >> loading a resource from a build extension Jar") still breaks my
> >> integrations with this last build of Maven... :-( As you tried the
> >> test
> >> project successfully, I don't understand what can be specific to my
> >> environment . I've made a clean installation of Maven (no local
> >> repository
> >> and last build of 2.0.5), and still it breaks the test case I
> >> attached on
> >> JIRA.
> >>
> >> Is there someone here who develops Checkstyle custom Checks and
> >> bundles
> >> them in a JAR (along with the configuration file) which is
> >> specified in the
> >> build extensions of another project? Or at least someone else who
> >> could
> >> test the case I described on JIRA? (with a clean installation)
> >
> > Just FYI: we (CXF team) put our checkstyle rules into a jar bundle
> > and use
> > that.   However, we don't put it in the extensions.   We put it as
> > a direct
> > dependency for the plugin:
> > 
> > org.apache.maven.plugins
> > maven-checkstyle-plugin
> > 
> >
> >  org.apache.cxf
> >  cxf-buildtools
> >  . 
> >
> > 
> > ..
> > 
> > and that works fine with 2.0.5.
> >
> >
> > Dan
> >
> >
> >
> >>
> >> I may sound insisting on this, but the fact is that we have developed
> >> custom Checks in my company, and tens of projects are using them to
> >> generate the checkstyle report. As 2.0.5 currently breaks our
> >> builds, they
> >> wouldn't be able to migrate to this new and awaited version of
> >> Maven. Which
> >> is sad because they're looking forward to using it...
> >>
> >> Apart from that, everything works fine. :-)
> >>
> >> Fabrice.
> >>
> >> On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >>> Hi,
> >>>
> >>> The assemblies that people are interested in are staged here:
> >>>
> >>> http://people.apache.org/~jvanzyl/staging-repository/org/apache/
> >>> maven/ >>> tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/
> >>> maven/>
> >>> maven-core/2.0.5/
> >>>
> >>> Here is the JIRA roadmap:
> >>>
> >>> http://jira.codehaus.org/secure/IssueNavigator.jspa ?
> >>> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> >>> order=DESC
> >>>
> >>> +1
> >>>
> >>> Thanks,
> >>>
> >>> Jason.
> >>>
> >>>
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727C: 508-380-7194
> > [EMAIL PROTECTED]
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Stephen Duncan Jr
www.stephenduncanjr.com




--
Stephen Duncan Jr
www.stephenduncanjr.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Rahul Thakur]

+1

Rahul

Jason van Zyl wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Stephen Duncan]

I've actually been telling people on the mailing list to use
extensions for jar with checkstyle configuration, rather than
plugin->dependencies.  The reason was that, in my testing at the time,
if you didn't already have that plugin dependency in your local repo,
it would not search for it in all your defined repos, it would only
look in central, and therefore break for other people.  At the time I
just assumed using extensions was the right mechanism, but if
plugin->dependencies is 'correct' then it should be verified that it
works correctly...

-Stephen

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

What Dan describes is probably more correct and we should document
this because extensions are really something that executes where you
really just want something on the classpath of the plugin. But as far
as I can tell with the test that I checked in the extension works,
but that should really be a deprecated form of use.

jason.

On 12 Feb 07, at 10:17 AM 12 Feb 07, Daniel Kulp wrote:

>
> Fabrice,
>
> On Monday 12 February 2007 10:02, Fabrice Bellingard wrote:
>> The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader
>> problem
>> loading a resource from a build extension Jar") still breaks my
>> integrations with this last build of Maven... :-( As you tried the
>> test
>> project successfully, I don't understand what can be specific to my
>> environment . I've made a clean installation of Maven (no local
>> repository
>> and last build of 2.0.5), and still it breaks the test case I
>> attached on
>> JIRA.
>>
>> Is there someone here who develops Checkstyle custom Checks and
>> bundles
>> them in a JAR (along with the configuration file) which is
>> specified in the
>> build extensions of another project? Or at least someone else who
>> could
>> test the case I described on JIRA? (with a clean installation)
>
> Just FYI: we (CXF team) put our checkstyle rules into a jar bundle
> and use
> that.   However, we don't put it in the extensions.   We put it as
> a direct
> dependency for the plugin:
> 
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 
>
>  org.apache.cxf
>  cxf-buildtools
>  . 
>
> 
> ..
> 
> and that works fine with 2.0.5.
>
>
> Dan
>
>
>
>>
>> I may sound insisting on this, but the fact is that we have developed
>> custom Checks in my company, and tens of projects are using them to
>> generate the checkstyle report. As 2.0.5 currently breaks our
>> builds, they
>> wouldn't be able to migrate to this new and awaited version of
>> Maven. Which
>> is sad because they're looking forward to using it...
>>
>> Apart from that, everything works fine. :-)
>>
>> Fabrice.
>>
>> On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>> Hi,
>>>
>>> The assemblies that people are interested in are staged here:
>>>
>>> http://people.apache.org/~jvanzyl/staging-repository/org/apache/
>>> maven/>> tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/
>>> maven/>
>>> maven-core/2.0.5/
>>>
>>> Here is the JIRA roadmap:
>>>
>>> http://jira.codehaus.org/secure/IssueNavigator.jspa ?
>>> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
>>> order=DESC
>>>
>>> +1
>>>
>>> Thanks,
>>>
>>> Jason.
>>>
>>>
>>> 
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727C: 508-380-7194
> [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Stephen Duncan Jr
www.stephenduncanjr.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason van Zyl]

On 12 Feb 07, at 4:06 PM 12 Feb 07, Jorg Heymans wrote:


Jason van Zyl wrote:

Hi,
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/maven-core/2.0.5/


Excalibur builds fine with this release, no apparent probs spotted.



Cool, thanks for checking.

Jason.



Thanks,
Jorg


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jorg Heymans]

Jason van Zyl wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ 


Excalibur builds fine with this release, no apparent probs spotted.


Thanks,
Jorg


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Emmanuel Venisse]

+1

Emmanuel

Jason van Zyl a écrit :

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Joakim Erdfelt]

+1 (looking forward to it)

- Joakim

Jason van Zyl wrote:
> Hi,
>
> The assemblies that people are interested in are staged here:
>
> http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/
>
>
> Here is the JIRA roadmap:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC
>
>
> +1
>
> Thanks,
>
> Jason.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Tomasz Pik]

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC


Error code from mvn.bat is not returned correctly on windows,
solution described at continuum site is not working so maven-invoker-plugin
cannot be treat as reliable tool.
Steps to reproduce:
* checkout maven-antrun-plugin
* break one pom.xml files inside src/it/test_n directories
* run mvn install at project level
maven-invoker-plugin will report all tests as 'passed' but 'build.log'
file in directory with broken pom will contain errors.

Should I add it into JIRA?

Regards,
Tomek

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[John Casey]

+1 from me.

On 2/12/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:



+1 (non-binding)

Works for our builds.

Thanks!
Dan


On Sunday 11 February 2007 23:33, Jason van Zyl wrote:
> Hi,
>
> The assemblies that people are interested in are staged here:
>
> http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
> maven-core/2.0.5/
>
> Here is the JIRA roadmap:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> order=DESC
>
> +1
>
> Thanks,
>
> Jason.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Daniel Kulp]

+1 (non-binding)

Works for our builds.

Thanks!
Dan


On Sunday 11 February 2007 23:33, Jason van Zyl wrote:
> Hi,
>
> The assemblies that people are interested in are staged here:
>
> http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
> maven-core/2.0.5/
>
> Here is the JIRA roadmap:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> order=DESC
>
> +1
>
> Thanks,
>
> Jason.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason van Zyl]

What Dan describes is probably more correct and we should document  
this because extensions are really something that executes where you  
really just want something on the classpath of the plugin. But as far  
as I can tell with the test that I checked in the extension works,  
but that should really be a deprecated form of use.


jason.

On 12 Feb 07, at 10:17 AM 12 Feb 07, Daniel Kulp wrote:



Fabrice,

On Monday 12 February 2007 10:02, Fabrice Bellingard wrote:
The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader  
problem

loading a resource from a build extension Jar") still breaks my
integrations with this last build of Maven... :-( As you tried the  
test

project successfully, I don't understand what can be specific to my
environment . I've made a clean installation of Maven (no local  
repository
and last build of 2.0.5), and still it breaks the test case I  
attached on

JIRA.

Is there someone here who develops Checkstyle custom Checks and  
bundles
them in a JAR (along with the configuration file) which is  
specified in the
build extensions of another project? Or at least someone else who  
could

test the case I described on JIRA? (with a clean installation)


Just FYI: we (CXF team) put our checkstyle rules into a jar bundle  
and use
that.   However, we don't put it in the extensions.   We put it as  
a direct

dependency for the plugin:

org.apache.maven.plugins
maven-checkstyle-plugin

   
 org.apache.cxf
 cxf-buildtools
 . 
   

..

and that works fine with 2.0.5.


Dan





I may sound insisting on this, but the fact is that we have developed
custom Checks in my company, and tens of projects are using them to
generate the checkstyle report. As 2.0.5 currently breaks our  
builds, they
wouldn't be able to migrate to this new and awaited version of  
Maven. Which

is sad because they're looking forward to using it...

Apart from that, everything works fine. :-)

Fabrice.

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/ 
maven/>

maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa ?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


 
-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason van Zyl]

On 12 Feb 07, at 10:02 AM 12 Feb 07, Fabrice Bellingard wrote:


Hi Jason,

The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader  
problem
loading a resource from a build extension Jar") still breaks my  
integrations

with this last build of Maven... :-( As you tried the test project
successfully, I don't understand what can be specific to my  
environment .
I've made a clean installation of Maven (no local repository and  
last build

of 2.0.5), and still it breaks the test case I attached on JIRA.

Is there someone here who develops Checkstyle custom Checks and  
bundles them
in a JAR (along with the configuration file) which is specified in  
the build
extensions of another project? Or at least someone else who could  
test the

case I described on JIRA? (with a clean installation)

I may sound insisting on this, but the fact is that we have  
developed custom
Checks in my company, and tens of projects are using them to  
generate the
checkstyle report. As 2.0.5 currently breaks our builds, they  
wouldn't be

able to migrate to this new and awaited version of Maven. Which is sad
because they're looking forward to using it...



I checked your project in here:

http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/ 
core-integration-tests/src/test/resources/it0114- 
extensionThatProvidesResources/


And I just ran it with the 2.0.5 that I built and put in the staging  
repository:


http://rafb.net/p/humZR325.html

I'm on OS X with:

java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)

Are you on Windows? The bane of my existence?

Jason.


Apart from that, everything works fine. :-)

Fabrice.

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/

maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa ?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Daniel Kulp]

Fabrice,

On Monday 12 February 2007 10:02, Fabrice Bellingard wrote:
> The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader problem
> loading a resource from a build extension Jar") still breaks my
> integrations with this last build of Maven... :-( As you tried the test
> project successfully, I don't understand what can be specific to my
> environment . I've made a clean installation of Maven (no local repository
> and last build of 2.0.5), and still it breaks the test case I attached on
> JIRA.
>
> Is there someone here who develops Checkstyle custom Checks and bundles
> them in a JAR (along with the configuration file) which is specified in the
> build extensions of another project? Or at least someone else who could
> test the case I described on JIRA? (with a clean installation)

Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use 
that.   However, we don't put it in the extensions.   We put it as a direct 
dependency for the plugin:

org.apache.maven.plugins
maven-checkstyle-plugin

   
 org.apache.cxf
 cxf-buildtools
 . 
   

..

and that works fine with 2.0.5.


Dan



>
> I may sound insisting on this, but the fact is that we have developed
> custom Checks in my company, and tens of projects are using them to
> generate the checkstyle report. As 2.0.5 currently breaks our builds, they
> wouldn't be able to migrate to this new and awaited version of Maven. Which
> is sad because they're looking forward to using it...
>
> Apart from that, everything works fine. :-)
>
> Fabrice.
>
> On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > The assemblies that people are interested in are staged here:
> >
> > http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ >tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/>
> > maven-core/2.0.5/
> >
> > Here is the JIRA roadmap:
> >
> > http://jira.codehaus.org/secure/IssueNavigator.jspa ?
> > reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> > order=DESC
> >
> > +1
> >
> > Thanks,
> >
> > Jason.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason van Zyl]

On 12 Feb 07, at 3:24 AM 12 Feb 07, Jörg Schaible wrote:


Jason van Zyl wrote on Monday, February 12, 2007 7:12 AM:


On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote:


Are there release notes on the major changes or significant fixes
which we might need to adapt to and/or be able to remove local
build hacks?  The JIRA road map is kinda hard to scrape the relevant
details from.



The only thing in the list which may bite you is that the the
dependency resolution is more correct, at least in terms of what we
documented, in that the nearest version of a dependency will be
selected. This will affect if you are not specifying all dependencies
which you actually need to compile your project. Technically you
should always list the dependencies that your project actually needs
to compile, but we currently don't enforce that as Jorg noted. So if
you are relying on transitive deps to pick up your compile time
requirements you might have some issues. Specifically this:

http://jira.codehaus.org/browse/MNG-2794

The rest are bug fixes. There is only the one slight behavioral
change that I am aware off.


Well, in any case it would be great to integrate the code of http:// 
jira.codehaus.org/browse/MNG-2676 into the dependencies plugin and  
get a release. It is a great help to analyse and fix such  
situations (here integrated into our internal info plugin):




Here you can now help having access to the sandbox. And I think Mark  
has access too. The sandbox is going to be the first place that I  
look for integrating things. Pulling in Dan's work in the remote  
resources plugin was a snap. He had a working build with tests and  
notes, it was great. You want something like this integrated, if you  
put it in the sandbox and ping one of us you're chances of getting it  
integrate are very likely.


Jason.


 %< =

[INFO]  
-- 
--

[INFO] Building Commons Activation Project
[INFO]task-segment: [info:analyse]
[INFO]  
-- 
--

[INFO] Preparing info:analyse
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [info:analyse]
[INFO] Used declared dependencies:
[INFO]commons-io:commons-io:jar:1.3:compile
[INFO]com.company.commons:company-commons-test:jar:2.0.10:test
[INFO]proxytoys:proxytoys:jar:0.2.1:compile
[INFO]com.company.commons:company-commons-lang:jar:2.0.6:compile
[INFO]javax.activation:activation:jar:1.0.2:compile
[INFO] Used undeclared dependencies:
[INFO]jmock:jmock:jar:1.1.0:test
[INFO]junit:junit:jar:3.8.1:test
[INFO] Unused declared dependencies:
[INFO]None
[INFO]  
-- 
--

[INFO] BUILD SUCCESSFUL
[INFO]  
-- 
--

[INFO] Total time: 19 seconds
[INFO] Finished at: Mon Feb 12 09:21:38 CET 2007
[INFO] Final Memory: 6M/11M
[INFO]  
-- 
--


 %< =

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Fabrice Bellingard]

Hi Jason,

The issue http://jira.codehaus.org/browse/MNG-2795 ("Classloader problem
loading a resource from a build extension Jar") still breaks my integrations
with this last build of Maven... :-( As you tried the test project
successfully, I don't understand what can be specific to my environment .
I've made a clean installation of Maven (no local repository and last build
of 2.0.5), and still it breaks the test case I attached on JIRA.

Is there someone here who develops Checkstyle custom Checks and bundles them
in a JAR (along with the configuration file) which is specified in the build
extensions of another project? Or at least someone else who could test the
case I described on JIRA? (with a clean installation)

I may sound insisting on this, but the fact is that we have developed custom
Checks in my company, and tens of projects are using them to generate the
checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be
able to migrate to this new and awaited version of Maven. Which is sad
because they're looking forward to using it...

Apart from that, everything works fine. :-)

Fabrice.

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa ?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Stephane Nicoll]

+1 Our builds run fine.

Thanks,
Stéphane

On 2/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Reinhard Poetz]

Jason van Zyl wrote:

Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



+1


Cocoon trunk builds fine, here my non-binding +1

--
Reinhard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Release Maven 2.0.5 (take 2)

[Jörg Schaible]

Jason van Zyl wrote on Monday, February 12, 2007 7:12 AM:

> On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote:
> 
>> Are there release notes on the major changes or significant fixes
>> which we might need to adapt to and/or be able to remove local
>> build hacks?  The JIRA road map is kinda hard to scrape the relevant
>> details from. 
>> 
> 
> The only thing in the list which may bite you is that the the
> dependency resolution is more correct, at least in terms of what we
> documented, in that the nearest version of a dependency will be
> selected. This will affect if you are not specifying all dependencies
> which you actually need to compile your project. Technically you
> should always list the dependencies that your project actually needs
> to compile, but we currently don't enforce that as Jorg noted. So if
> you are relying on transitive deps to pick up your compile time
> requirements you might have some issues. Specifically this:
> 
> http://jira.codehaus.org/browse/MNG-2794
> 
> The rest are bug fixes. There is only the one slight behavioral
> change that I am aware off. 

Well, in any case it would be great to integrate the code of 
http://jira.codehaus.org/browse/MNG-2676 into the dependencies plugin and get a 
release. It is a great help to analyse and fix such situations (here integrated 
into our internal info plugin):

 %< =

[INFO] 

[INFO] Building Commons Activation Project
[INFO]task-segment: [info:analyse]
[INFO] 

[INFO] Preparing info:analyse
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [info:analyse]
[INFO] Used declared dependencies:
[INFO]commons-io:commons-io:jar:1.3:compile
[INFO]com.company.commons:company-commons-test:jar:2.0.10:test
[INFO]proxytoys:proxytoys:jar:0.2.1:compile
[INFO]com.company.commons:company-commons-lang:jar:2.0.6:compile
[INFO]javax.activation:activation:jar:1.0.2:compile
[INFO] Used undeclared dependencies:
[INFO]jmock:jmock:jar:1.1.0:test
[INFO]junit:junit:jar:3.8.1:test
[INFO] Unused declared dependencies:
[INFO]None
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 19 seconds
[INFO] Finished at: Mon Feb 12 09:21:38 CET 2007
[INFO] Final Memory: 6M/11M
[INFO] 

 %< =

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason Dillon]

Thanks for the info... seems to be okay so far, build works with  
2.0.4 and 2.0.5, will soon run the TCK on the 2.0.5 build to see if  
that shows any dependency related failures, but overall it looks good.


There are still a few big issues which we are working around in the G  
builds which I hope to see fixed in more frequent releases ;-)


Thanks,

--jason


On Feb 11, 2007, at 10:11 PM, Jason van Zyl wrote:



On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote:

Are there release notes on the major changes or significant fixes  
which we might need to adapt to and/or be able to remove local  
build hacks?  The JIRA road map is kinda hard to scrape the  
relevant details from.




The only thing in the list which may bite you is that the the  
dependency resolution is more correct, at least in terms of what we  
documented, in that the nearest version of a dependency will be  
selected. This will affect if you are not specifying all  
dependencies which you actually need to compile your project.  
Technically you should always list the dependencies that your  
project actually needs to compile, but we currently don't enforce  
that as Jorg noted. So if you are relying on transitive deps to  
pick up your compile time requirements you might have some issues.  
Specifically this:


http://jira.codehaus.org/browse/MNG-2794

The rest are bug fixes. There is only the one slight behavioral  
change that I am aware off.


Jason.


--jason


On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote:


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/maven-core/2.0.5/


Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


+1

Thanks,

Jason.


 
-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason van Zyl]

On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote:

Are there release notes on the major changes or significant fixes  
which we might need to adapt to and/or be able to remove local  
build hacks?  The JIRA road map is kinda hard to scrape the  
relevant details from.




The only thing in the list which may bite you is that the the  
dependency resolution is more correct, at least in terms of what we  
documented, in that the nearest version of a dependency will be  
selected. This will affect if you are not specifying all dependencies  
which you actually need to compile your project. Technically you  
should always list the dependencies that your project actually needs  
to compile, but we currently don't enforce that as Jorg noted. So if  
you are relying on transitive deps to pick up your compile time  
requirements you might have some issues. Specifically this:


http://jira.codehaus.org/browse/MNG-2794

The rest are bug fixes. There is only the one slight behavioral  
change that I am aware off.


Jason.


--jason


On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote:


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/maven-core/2.0.5/


Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason Dillon]

Seems to work fine for Geronimo trunk (2.0) and 1.2 builds...

+1

--jason


On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote:


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/maven-core/2.0.5/


Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5 (take 2)

[Jason Dillon]

Are there release notes on the major changes or significant fixes  
which we might need to adapt to and/or be able to remove local build  
hacks?  The JIRA road map is kinda hard to scrape the relevant  
details from.


--jason


On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote:


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/ 
maven/maven-core/2.0.5/


Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason Dillon]

What was the problem you found?

--jason


On Jan 17, 2007, at 7:12 AM, Jason van Zyl wrote:

We found a problem, so I'm rolling another release and will call a  
vote tomorrow.


Jason.

On 17 Jan 07, at 9:24 AM 17 Jan 07, Geoffrey De Smet wrote:


+1: no problems here

--
With kind regards,
Geoffrey De Smet

Jason van Zyl schreef:

Hi,
The entire release is staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/ Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC That's about it. Play around with it, if there are  
things wrong and I'll fix stuff. We haven't released in so long  
there very well may be some problems.
We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.

+1
Thanks,
Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Brett Porter]

Cool. We'll just need to tweak some fix for versions (simple bulk  
edit for anything fixed in 2.0.6/2.0.x).


On 18/01/2007, at 5:42 AM, Jason van Zyl wrote:



On 17 Jan 07, at 1:09 PM 17 Jan 07, Brett Porter wrote:

Will that include more recent changes to the branch? (My fix, and  
Kenney's fix?)




I'm going to roll it again completely so if it's there then yes.


On 18/01/2007, at 2:12 AM, Jason van Zyl wrote:

We found a problem, so I'm rolling another release and will call  
a vote tomorrow.


Jason.

On 17 Jan 07, at 9:24 AM 17 Jan 07, Geoffrey De Smet wrote:


+1: no problems here

--
With kind regards,
Geoffrey De Smet

Jason van Zyl schreef:

Hi,
The entire release is staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/ Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC That's about it. Play around with it, if there are  
things wrong and I'll fix stuff. We haven't released in so long  
there very well may be some problems.
We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.

+1
Thanks,
Jason.



--- 
--

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





 
-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 17 Jan 07, at 1:09 PM 17 Jan 07, Brett Porter wrote:

Will that include more recent changes to the branch? (My fix, and  
Kenney's fix?)




I'm going to roll it again completely so if it's there then yes.


On 18/01/2007, at 2:12 AM, Jason van Zyl wrote:

We found a problem, so I'm rolling another release and will call a  
vote tomorrow.


Jason.

On 17 Jan 07, at 9:24 AM 17 Jan 07, Geoffrey De Smet wrote:


+1: no problems here

--
With kind regards,
Geoffrey De Smet

Jason van Zyl schreef:

Hi,
The entire release is staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/ Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC That's about it. Play around with it, if there are  
things wrong and I'll fix stuff. We haven't released in so long  
there very well may be some problems.
We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.

+1
Thanks,
Jason.



 
-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Brett Porter]

Will that include more recent changes to the branch? (My fix, and  
Kenney's fix?)


On 18/01/2007, at 2:12 AM, Jason van Zyl wrote:

We found a problem, so I'm rolling another release and will call a  
vote tomorrow.


Jason.

On 17 Jan 07, at 9:24 AM 17 Jan 07, Geoffrey De Smet wrote:


+1: no problems here

--
With kind regards,
Geoffrey De Smet

Jason van Zyl schreef:

Hi,
The entire release is staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/ Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC That's about it. Play around with it, if there are  
things wrong and I'll fix stuff. We haven't released in so long  
there very well may be some problems.
We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.

+1
Thanks,
Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

We found a problem, so I'm rolling another release and will call a  
vote tomorrow.


Jason.

On 17 Jan 07, at 9:24 AM 17 Jan 07, Geoffrey De Smet wrote:


+1: no problems here

--
With kind regards,
Geoffrey De Smet

Jason van Zyl schreef:

Hi,
The entire release is staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/ Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC That's about it. Play around with it, if there are  
things wrong and I'll fix stuff. We haven't released in so long  
there very well may be some problems.
We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.

+1
Thanks,
Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Geoffrey De Smet]

+1: no problems here

--
With kind regards,
Geoffrey De Smet

Jason van Zyl schreef:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



That's about it. Play around with it, if there are things wrong and I'll 
fix stuff. We haven't released in so long there very well may be some 
problems.


We should probably let it sit until Tuesday as most folks won't try it 
out over the weekend.


+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Fabrice Bellingard]

On 1/15/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:



I myself have intentionally stayed away from artifact resolution on
the branch so do you have a test project I can use. I need to be able
to reproduce your problem and turn it into some form of test. So I
can see what's going on and so it doesn't regress again, if it is
indeed a regression.



I managed to reproduce the problem on a very simple project. I will send you
the ZIP in a few minutes. In the archive, you will find a project that has 3
dependecies:
 A -> D v2.1
 B -> D v3
 C (has no transitive dependency to D)
In the project, I call a class that exists in D v3 but not in D v2.1. If you
launch "mvn clean compile" with M2.0.4, the build is successful, but not
with M2.0.5.
And the most surprising: if you remove dependency C, then both builds
break...


That doesn't sound good though 2.0.4 and 2.0.5 both use the same

versions of classworlds and plexus so you're sure you have the same
version of the checkstyle plugin there?



Yes, I saw that both Maven 2.0.4 and 2.0.5 use the same version of
classworlds, that's why I don't really know what to think about it. But I
checked the log: the same version of the Checkstyle plugin is used in both
cases.
I will send you the log so that you can check.


Fabrice.

Re: [VOTE] Release Maven 2.0.5

[John Casey]

IIRC, the order in which dependencies are declared effectively becomes the
tie-breaker when two dependency versions are declared at the same depth...so
if:

A -> B, C
B -> D (v2)
C -> D (v3)

and A declares the following:


 
   [...]
   B
 
 
   [...]
   C
 


then Maven should choose D (v2) because B is declared first in the POM.

As I recall, that's how the change should function.

-john

On 1/15/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:


On 1/15/07, Fabrice Bellingard <[EMAIL PROTECTED]> wrote:

> The first is about dependency resolution. In the dependency tree of one
of
> my projects, I have 2 versions of the same lib at the same depth:
version
> 3.1 and 2.1.  With Maven 2.0.4, version 3.1 is selected for compiling
and
> testing, which is what I want. With Maven 2.0.5, version 2.1 is
selected,
> which breaks my unit tests because the code requires version 3.1 to run.
I'm
> not sure if this is a bug or not - maybe this resolution principle was
to be
> the default behaviour, but the fact is that there's a difference between
> 2.0.4 and 2.0.5. I've looked (quickly) into JIRA roadmap, but haven't
found
> any fixed issue related to that.

IIRC, Maven 2.0.4's behavior with two versions of the same dependency
at the same depth was undefined.  Now, it's supposed to be
predictable.

Can someone confirm?  (And explain how to predict what 2.0.5 will do
in this situation?)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Barrie Treloar]

On 1/16/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


On 15 Jan 07, at 8:56 AM 15 Jan 07, Max Bowsher wrote:

> Kenney Westerhof wrote:
>> tags cannot change, ever.
>
> The maven-2.0.5 tag already has been changed a bit since creation.
>

The only way we'll move toward having releases be perfect is to do
lots of them.


I would like to discuss this more, I've started another thread to do so.

See 
http://www.nabble.com/The-process-for-tags%2C-release-candidates%2C-final-releases--tf3017795s177.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

I revert the branch, apply the fix, redo the release and call for  
another vote.


Fabrice can you please check again on your builds and make sure it's  
not something with the checkstyle plugin.


Jason.


In the
On 15 Jan 07, at 11:40 AM 15 Jan 07, Jason van Zyl wrote:



On 15 Jan 07, at 11:19 AM 15 Jan 07, Kenney Westerhof wrote:


Hi,

I've fixed this bug a while back on trunk but haven't merged it to
the branch.

The cause is that for non-existing metadata files at the checked  
repositories,
no local metadata file is written. The 'daily' policy uses the  
timestamp for
that file to see if it should update again, which it always does  
since

the timestamp is 0 for non-existent files.

I've fixed this by creating a metadata file even if there's no  
metadata, but
I wanted to test more since it's different behaviour. The file is  
written without
a  tag (version is null), and there was an explicit unit  
test for that.

It all seems to work fine though.

I can merge this to trunk.



That would be great, then we can try Trygve's little test.  
Eventually we'll need a TimeSource that uses the system clock for  
runtime and a mock source for testing so we can make sure this  
doesn't happen again.


Jason.


-- Kenney

Trygve Laugstøl wrote:

Trygve Laugstøl wrote:

Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/


Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


That's about it. Play around with it, if there are things wrong  
and I'll fix stuff. We haven't released in so long there very  
well may be some problems.


We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.


I'm waiting until I've tried it out on my projects.
Testes and a serious bug was found. It seems that Maven tries to  
check for SNAPSHOT plugin updates on every run instead of the  
expected daily interval.
I've verified that it do check on every update by using truss  
(use strace on linux) on Solaris:

$ truss -t connect mvn -Dmaven.test.skip=true install
[INFO] Scanning for projects...
[INFO]  
 
 [INFO] Building Unnamed - no.java.monitor:monitor- 
core:jar:1.0-SNAPSHOT

[INFO]task-segment: [install]
[INFO]  
 
 [INFO] artifact org.apache.maven.plugins:maven-resources- 
plugin: checking for updates from codehaus-snapshots

/1: connect(8, 0xFFBFBAF4, 16, SOV_DEFAULT) = 0
/1: connect(7, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin:  
checking for updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin:  
checking for updates from codehaus-snapshots

/1: connect(9, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin:  
checking for updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-install-plugin:  
checking for updates from codehaus-snapshots

[INFO] [plexus:descriptor {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING]
Artifact junit:junit:jar:3.8.1:test retains local scope  
'test' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or  
remove the local scope.

So I'm -1 on this revision until this issue is resolved :'(
The issue was confirmed by other devs on IRC aswell.
--
Trygve
 
-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 15 Jan 07, at 11:19 AM 15 Jan 07, Kenney Westerhof wrote:


Hi,

I've fixed this bug a while back on trunk but haven't merged it to
the branch.

The cause is that for non-existing metadata files at the checked  
repositories,
no local metadata file is written. The 'daily' policy uses the  
timestamp for

that file to see if it should update again, which it always does since
the timestamp is 0 for non-existent files.

I've fixed this by creating a metadata file even if there's no  
metadata, but
I wanted to test more since it's different behaviour. The file is  
written without
a  tag (version is null), and there was an explicit unit  
test for that.

It all seems to work fine though.

I can merge this to trunk.



That would be great, then we can try Trygve's little test. Eventually  
we'll need a TimeSource that uses the system clock for runtime and a  
mock source for testing so we can make sure this doesn't happen again.


Jason.


-- Kenney

Trygve Laugstøl wrote:

Trygve Laugstøl wrote:

Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/


Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


That's about it. Play around with it, if there are things wrong  
and I'll fix stuff. We haven't released in so long there very  
well may be some problems.


We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.


I'm waiting until I've tried it out on my projects.
Testes and a serious bug was found. It seems that Maven tries to  
check for SNAPSHOT plugin updates on every run instead of the  
expected daily interval.
I've verified that it do check on every update by using truss (use  
strace on linux) on Solaris:

$ truss -t connect mvn -Dmaven.test.skip=true install
[INFO] Scanning for projects...
[INFO]  
- 
--- [INFO] Building Unnamed - no.java.monitor:monitor-core:jar: 
1.0-SNAPSHOT

[INFO]task-segment: [install]
[INFO]  
- 
--- [INFO] artifact org.apache.maven.plugins:maven-resources- 
plugin: checking for updates from codehaus-snapshots

/1: connect(8, 0xFFBFBAF4, 16, SOV_DEFAULT) = 0
/1: connect(7, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin:  
checking for updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin:  
checking for updates from codehaus-snapshots

/1: connect(9, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin:  
checking for updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-install-plugin:  
checking for updates from codehaus-snapshots

[INFO] [plexus:descriptor {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING]
Artifact junit:junit:jar:3.8.1:test retains local scope  
'test' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or  
remove the local scope.

So I'm -1 on this revision until this issue is resolved :'(
The issue was confirmed by other devs on IRC aswell.
--
Trygve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Kenney Westerhof]

Hi,

I've fixed this bug a while back on trunk but haven't merged it to
the branch.

The cause is that for non-existing metadata files at the checked repositories,
no local metadata file is written. The 'daily' policy uses the timestamp for
that file to see if it should update again, which it always does since
the timestamp is 0 for non-existent files.

I've fixed this by creating a metadata file even if there's no metadata, but
I wanted to test more since it's different behaviour. The file is written 
without
a  tag (version is null), and there was an explicit unit test for that.
It all seems to work fine though.

I can merge this to trunk.

-- Kenney

Trygve Laugstøl wrote:

Trygve Laugstøl wrote:

Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



That's about it. Play around with it, if there are things wrong and 
I'll fix stuff. We haven't released in so long there very well may be 
some problems.


We should probably let it sit until Tuesday as most folks won't try 
it out over the weekend.


I'm waiting until I've tried it out on my projects.


Testes and a serious bug was found. It seems that Maven tries to check 
for SNAPSHOT plugin updates on every run instead of the expected daily 
interval.


I've verified that it do check on every update by using truss (use 
strace on linux) on Solaris:


$ truss -t connect mvn -Dmaven.test.skip=true install
[INFO] Scanning for projects...
[INFO] 
 


[INFO] Building Unnamed - no.java.monitor:monitor-core:jar:1.0-SNAPSHOT
[INFO]task-segment: [install]
[INFO] 
 

[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: 
checking for updates from codehaus-snapshots

/1: connect(8, 0xFFBFBAF4, 16, SOV_DEFAULT) = 0
/1: connect(7, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking 
for updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking 
for updates from codehaus-snapshots

/1: connect(9, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking for 
updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking 
for updates from codehaus-snapshots

[INFO] [plexus:descriptor {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING]
Artifact junit:junit:jar:3.8.1:test retains local scope 'test' 
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove 
the local scope.


So I'm -1 on this revision until this issue is resolved :'(

The issue was confirmed by other devs on IRC aswell.

--
Trygve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Trygve Laugstøl]

Trygve Laugstøl wrote:

Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



That's about it. Play around with it, if there are things wrong and 
I'll fix stuff. We haven't released in so long there very well may be 
some problems.


We should probably let it sit until Tuesday as most folks won't try it 
out over the weekend.


I'm waiting until I've tried it out on my projects.


Testes and a serious bug was found. It seems that Maven tries to check 
for SNAPSHOT plugin updates on every run instead of the expected daily 
interval.


I've verified that it do check on every update by using truss (use 
strace on linux) on Solaris:


$ truss -t connect mvn -Dmaven.test.skip=true install
[INFO] Scanning for projects...
[INFO] 


[INFO] Building Unnamed - no.java.monitor:monitor-core:jar:1.0-SNAPSHOT
[INFO]task-segment: [install]
[INFO] 

[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: 
checking for updates from codehaus-snapshots

/1: connect(8, 0xFFBFBAF4, 16, SOV_DEFAULT) = 0
/1: connect(7, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking 
for updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking 
for updates from codehaus-snapshots

/1: connect(9, 0xFFBFBD98, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking for 
updates from codehaus-snapshots

/1: connect(7, 0xFFBFBD80, 16, SOV_DEFAULT) = 0
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking 
for updates from codehaus-snapshots

[INFO] [plexus:descriptor {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING]
Artifact junit:junit:jar:3.8.1:test retains local scope 'test' 
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or 
remove the local scope.


So I'm -1 on this revision until this issue is resolved :'(

The issue was confirmed by other devs on IRC aswell.

--
Trygve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Mike Perham]

+1

Tested against our build and appears to work identically to 2.0.4.

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Wendy Smoak]

On 1/15/07, Fabrice Bellingard <[EMAIL PROTECTED]> wrote:


The first is about dependency resolution. In the dependency tree of one of
my projects, I have 2 versions of the same lib at the same depth: version
3.1 and 2.1.  With Maven 2.0.4, version 3.1 is selected for compiling and
testing, which is what I want. With Maven 2.0.5, version 2.1 is selected,
which breaks my unit tests because the code requires version 3.1 to run. I'm
not sure if this is a bug or not - maybe this resolution principle was to be
the default behaviour, but the fact is that there's a difference between
2.0.4 and 2.0.5. I've looked (quickly) into JIRA roadmap, but haven't found
any fixed issue related to that.


IIRC, Maven 2.0.4's behavior with two versions of the same dependency
at the same depth was undefined.  Now, it's supposed to be
predictable.

Can someone confirm?  (And explain how to predict what 2.0.5 will do
in this situation?)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Vincent Siveton]

Hi,

+1 works fine for me

But I confirmed DOXIA-90 for 2.0.5. Is it a known issue on core?

Cheers,

Vincent

2007/1/12, Jason van Zyl <[EMAIL PROTECTED]>:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 15 Jan 07, at 8:56 AM 15 Jan 07, Max Bowsher wrote:


Kenney Westerhof wrote:

tags cannot change, ever.


The maven-2.0.5 tag already has been changed a bit since creation.



The only way we'll move toward having releases be perfect is to do  
lots of them.


The perpetual tension between burning publicly visible version  
numbers,
and retaining unique identity of versions strikes again.  
Unfortunately,

it's a problem without any obvious solution :-/ .



It's not a publicly visible, it's in a staging repository. A small  
addition of a build number (revision number) to the distribution will  
soon clearly separate versions.


We will get there very soon.

Jason.


Max.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 15 Jan 07, at 6:29 AM 15 Jan 07, Fabrice Bellingard wrote:


Hi Jason,

I've just tested Maven 2.0.5 on complex projects, and I've had 2  
problems

who broke the builds.

The first is about dependency resolution. In the dependency tree of  
one of
my projects, I have 2 versions of the same lib at the same depth:  
version
3.1 and 2.1. With Maven 2.0.4, version 3.1 is selected for  
compiling and
testing, which is what I want. With Maven 2.0.5, version 2.1 is  
selected,
which breaks my unit tests because the code requires version 3.1 to  
run. I'm
not sure if this is a bug or not - maybe this resolution principle  
was to be
the default behaviour, but the fact is that there's a difference  
between
2.0.4 and 2.0.5. I've looked (quickly) into JIRA roadmap, but  
haven't found

any fixed issue related to that.


I myself have intentionally stayed away from artifact resolution on  
the branch so do you have a test project I can use. I need to be able  
to reproduce your problem and turn it into some form of test. So I  
can see what's going on and so it doesn't regress again, if it is  
indeed a regression.




I had the second problem when executing the Checkstyle plugin  
(version 2.1).
So I dug a bit to see if this could be related to maven core or  
not, and

here is what I found.
I isolated the code that breaks the build in the checkstyle plugin: it
happens when the plugin tries to load my Checkstyle configuration  
file,

which is actually located in a JAR that is specified in the build
extensions. The code lies in the Locator#resolveLocation() method:

   *// Attempt a Resource.
* URL url =
*this*.getClass().getClassLoader().getResource( location );

This code returns null for the "url" variable, which in turns  
breaks the

plugin because it doesn't find any configuration file.
I haven't had the time to dig more into it, but I found the  
following issue

that might be related to this problem: "MNG-2228 : Classloader problem
loading jars from build extensions".
Brett and Carlos worked on it and fixed it, so maybe they could  
tell more

about it.




That doesn't sound good though 2.0.4 and 2.0.5 both use the same  
versions of classworlds and plexus so you're sure you have the same  
version of the checkstyle plugin there?


Apart from that, everything else works perfectly. Maybe some of us  
can tell

a bit more about those problems?

Cheers,
Fabrice.

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Max Bowsher]

Kenney Westerhof wrote:
> tags cannot change, ever.

The maven-2.0.5 tag already has been changed a bit since creation.

The perpetual tension between burning publicly visible version numbers,
and retaining unique identity of versions strikes again. Unfortunately,
it's a problem without any obvious solution :-/ .

Max.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 14 Jan 07, at 4:37 PM 14 Jan 07, Dennis Lundberg wrote:


Jason,

Would you consider upgrading the dependency on modello-maven-plugin  
in maven-model to alpha-13 (or alpha-14 if that is released) for  
this release? It would bring in a couple of nice features for the  
generated documentation. If not, I'll add it to JIRA for 2.0.6.


Also I found a couple of typos in maven.mdo that I fixed in trunk  
and the 2.0.x branch. Is it OK if I merge these into the 2.0.5 tag  
as well?




Add them to 2.0.6, I would prefer not re-rolling it unless there is a  
show stopper. We'll do a 2.0.6 pretty soon after this.


jason.


Jason van Zyl wrote:

Hi,
The entire release is staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-core/2.0.5/ Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC That's about it. Play around with it, if there are  
things wrong and I'll fix stuff. We haven't released in so long  
there very well may be some problems.
We should probably let it sit until Tuesday as most folks won't  
try it out over the weekend.

+1
Thanks,
Jason.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Emmanuel Venisse]

+1. It works fine for me.

Emmanuel

Jason van Zyl a écrit :

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



That's about it. Play around with it, if there are things wrong and I'll 
fix stuff. We haven't released in so long there very well may be some 
problems.


We should probably let it sit until Tuesday as most folks won't try it 
out over the weekend.


+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Kenney Westerhof]

Dennis Lundberg wrote:

Jason,

Would you consider upgrading the dependency on modello-maven-plugin in 
maven-model to alpha-13 (or alpha-14 if that is released) for this 
release? It would bring in a couple of nice features for the generated 
documentation. If not, I'll add it to JIRA for 2.0.6.


Also I found a couple of typos in maven.mdo that I fixed in trunk and 
the 2.0.x branch. Is it OK if I merge these into the 2.0.5 tag as well?




Hi,

tags cannot change, ever. In the best case a new release is cut, old tag
deleted, and a new one created. I think it depends on wheter the vote passes
if this could get into 2.0.5. The next release is planned pretty soon (1 to 2 
weeks),
so I think it's best to schedule those two issues for 2.0.6. 


-- Kenney


Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



That's about it. Play around with it, if there are things wrong and 
I'll fix stuff. We haven't released in so long there very well may be 
some problems.


We should probably let it sit until Tuesday as most folks won't try it 
out over the weekend.


+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Release Maven 2.0.5

[Brian E. Fox]

 
>I had the second problem when executing the Checkstyle plugin (version
2.1).
>So I dug a bit to see if this could be related to maven core or not,
and here is what I found.
>I isolated the code that breaks the build in the checkstyle plugin: it
happens when the plugin tries to load my Checkstyle configuration file,
which is actually >>located in a JAR that is specified in the build
extensions. The code lies in the Locator#resolveLocation() method:

That's curious because in a previous snapshot, I had the exact same
problem: http://jira.codehaus.org/browse/mng-2749 but it was fixed and I
verified my build with the previous snapshot as well as the release
artifact below. 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Fabrice Bellingard]

Hi Jason,

I've just tested Maven 2.0.5 on complex projects, and I've had 2 problems
who broke the builds.

The first is about dependency resolution. In the dependency tree of one of
my projects, I have 2 versions of the same lib at the same depth: version
3.1 and 2.1. With Maven 2.0.4, version 3.1 is selected for compiling and
testing, which is what I want. With Maven 2.0.5, version 2.1 is selected,
which breaks my unit tests because the code requires version 3.1 to run. I'm
not sure if this is a bug or not - maybe this resolution principle was to be
the default behaviour, but the fact is that there's a difference between
2.0.4 and 2.0.5. I've looked (quickly) into JIRA roadmap, but haven't found
any fixed issue related to that.

I had the second problem when executing the Checkstyle plugin (version 2.1).
So I dug a bit to see if this could be related to maven core or not, and
here is what I found.
I isolated the code that breaks the build in the checkstyle plugin: it
happens when the plugin tries to load my Checkstyle configuration file,
which is actually located in a JAR that is specified in the build
extensions. The code lies in the Locator#resolveLocation() method:

   *// Attempt a Resource.
* URL url =
*this*.getClass().getClassLoader().getResource( location );

This code returns null for the "url" variable, which in turns breaks the
plugin because it doesn't find any configuration file.
I haven't had the time to dig more into it, but I found the following issue
that might be related to this problem: "MNG-2228 : Classloader problem
loading jars from build extensions".
Brett and Carlos worked on it and fixed it, so maybe they could tell more
about it.


Apart from that, everything else works perfectly. Maybe some of us can tell
a bit more about those problems?

Cheers,
Fabrice.

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Dennis Lundberg]

Jason,

Would you consider upgrading the dependency on modello-maven-plugin in 
maven-model to alpha-13 (or alpha-14 if that is released) for this 
release? It would bring in a couple of nice features for the generated 
documentation. If not, I'll add it to JIRA for 2.0.6.


Also I found a couple of typos in maven.mdo that I fixed in trunk and 
the 2.0.x branch. Is it OK if I merge these into the 2.0.5 tag as well?


Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



That's about it. Play around with it, if there are things wrong and I'll 
fix stuff. We haven't released in so long there very well may be some 
problems.


We should probably let it sit until Tuesday as most folks won't try it 
out over the weekend.


+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Tom Huybrechts]

2) The repository copying only works using the file:/// when you're
on the same machine due to a bug in Wagon.


It should also work for http if you have the latest wagon api  Did you
try that ?

Tom

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason Dillon]

On Jan 13, 2007, at 2:40 PM, Jason van Zyl wrote:
1) From the top-level directory the GPG plugin didn't sign the  
assembly. That's my fault and need to fix that.
2) The repository copying only works using the file:/// when you're  
on the same machine due to a bug in Wagon.


Once those two things are ironed out and we publish the profile you  
should use then it will be ready for folks to try.



I would like to update the Geronimo
projects to use the new release support bits which have been added if
they are cooked enough.


There will be another round of releases and I'm preparing to fire  
out a 2.1-alpha-1 shortly so I will go through the whole thing  
again. Then a 2.0.6 release within the next couple weeks and after  
that the tools should be in good shape.


Awesome :-)

I will keep an eye out, though if you think its ready to go can you  
ping me or the Geronimo dev list with a heads up please?


 * * *

Are you guys still using the Continuum install on gbuild.org?

--jason



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 13 Jan 07, at 5:31 PM 13 Jan 07, Jason Dillon wrote:


+1, the Geronimo server/trunk builds just fine with 2.0.5.  I will
switch to this build and check out the other Geronimo project builds,
but I would guess that this bin will work fine for those too.

* * *

Did you use the new plugins to support staging for this release?


Yes, I used them.


Are
those ready for prime time?


Almost. I ran into two problems:

1) From the top-level directory the GPG plugin didn't sign the  
assembly. That's my fault and need to fix that.
2) The repository copying only works using the file:/// when you're  
on the same machine due to a bug in Wagon.


Once those two things are ironed out and we publish the profile you  
should use then it will be ready for folks to try.



I would like to update the Geronimo
projects to use the new release support bits which have been added if
they are cooked enough.


There will be another round of releases and I'm preparing to fire out  
a 2.1-alpha-1 shortly so I will go through the whole thing again.  
Then a 2.0.6 release within the next couple weeks and after that the  
tools should be in good shape.


Jason.



--jason


On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason Dillon]

+1, the Geronimo server/trunk builds just fine with 2.0.5.  I will
switch to this build and check out the other Geronimo project builds,
but I would guess that this bin will work fine for those too.

* * *

Did you use the new plugins to support staging for this release?  Are
those ready for prime time?  I would like to update the Geronimo
projects to use the new release support bits which have been added if
they are cooked enough.

--jason


On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Fabrizio Giustina]

+1

tested on a few complex projects, no regressions found.
fabrizio

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Trygve Laugstøl]

Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-core/2.0.5/ 



Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/order=DESC 



That's about it. Play around with it, if there are things wrong and I'll 
fix stuff. We haven't released in so long there very well may be some 
problems.


We should probably let it sit until Tuesday as most folks won't try it 
out over the weekend.


I'm waiting until I've tried it out on my projects.

--
Trygve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Stephane Nicoll]

+1

Stéphane

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Daniel Kulp]

Looks better.   Change my (non-binding) vote to +1.  :-)

Thanks!
Dan

On Friday 12 January 2007 16:55, Jason van Zyl wrote:
> On 12 Jan 07, at 12:30 PM 12 Jan 07, Daniel Kulp wrote:
> > Well,  I hate to do this cause I REALLY would like to see 2.0.5
> > out, but...
> >
> > -1, non-binding, but these are legal issues
> >
> > Issues:
> > 1) The NOTICE.TXT file in the root of the binary package only
> > mentions Apache
> > stuff.   However, I see a jsch jar, jtidy jar, and xml-apis jar that
> > certainly are not apache.  Plexus is codehaus, etc...   Thus, the
> > NOTICE file
> > definitely needs updating.
>
> xml-apis comes from xml-commons. I put notices in there for the rest.
>
> > 2) The scripts in bin have the old Apache copyright, not the new one.
>
> All fixed.
>
> > Sorry.  :-(
>
> No problem, in honor of your diligence we are naming our auditing
> tool after you :-)
>
> Should be all fixed now.
>
> Jason.
>
> > Dan
> >
> > On Friday 12 January 2007 11:45, Jason van Zyl wrote:
> >> Hi,
> >>
> >> The entire release is staged here:
> >>
> >> http://people.apache.org/~jvanzyl/maven-2.0.5/
> >>
> >> The assemblies that people are interested in are staged here:
> >>
> >> http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
> >> core/2.0.5/
> >>
> >> Here is the JIRA roadmap:
> >>
> >> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> >> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> >> order=DESC
> >>
> >> That's about it. Play around with it, if there are things wrong and
> >> I'll fix stuff. We haven't released in so long there very well may be
> >> some problems.
> >>
> >> We should probably let it sit until Tuesday as most folks won't try
> >> it out over the weekend.
> >>
> >> +1
> >>
> >> Thanks,
> >>
> >> Jason.
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727C: 508-380-7194
> > [EMAIL PROTECTED]
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 12 Jan 07, at 12:30 PM 12 Jan 07, Daniel Kulp wrote:



Well,  I hate to do this cause I REALLY would like to see 2.0.5  
out, but...


-1, non-binding, but these are legal issues

Issues:
1) The NOTICE.TXT file in the root of the binary package only  
mentions Apache

stuff.   However, I see a jsch jar, jtidy jar, and xml-apis jar that
certainly are not apache.  Plexus is codehaus, etc...   Thus, the  
NOTICE file

definitely needs updating.


xml-apis comes from xml-commons. I put notices in there for the rest.



2) The scripts in bin have the old Apache copyright, not the new one.



All fixed.


Sorry.  :-(


No problem, in honor of your diligence we are naming our auditing  
tool after you :-)


Should be all fixed now.

Jason.



Dan


On Friday 12 January 2007 11:45, Jason van Zyl wrote:

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Brett Porter]

This is a bug in the assembly plugin (or more specifically, the  
plexus-archiver).


- Brett

On 13/01/2007, at 8:18 AM, Tomasz Pik wrote:


On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


On 12 Jan 07, at 2:15 PM 12 Jan 07, Tomasz Pik wrote:

> On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
>> http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/ 
maven-

>> core/2.0.5/
>
> Can something be done with:
> tar: A lone zero block at 4174
>
> It's with tar 1.16 on windows/cygwin
>
> Not a bug but a little annoying warning.
>

Not going to happen for this release, but create an issue. Tell me
what it is and I'll assign it to 2.0.6.


here you are:
http://jira.codehaus.org/browse/MNG-2762

Regards,
Tomek

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Tomasz Pik]

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


On 12 Jan 07, at 2:15 PM 12 Jan 07, Tomasz Pik wrote:

> On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
>> http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
>> core/2.0.5/
>
> Can something be done with:
> tar: A lone zero block at 4174
>
> It's with tar 1.16 on windows/cygwin
>
> Not a bug but a little annoying warning.
>

Not going to happen for this release, but create an issue. Tell me
what it is and I'll assign it to 2.0.6.


here you are:
http://jira.codehaus.org/browse/MNG-2762

Regards,
Tomek

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Release Maven 2.0.5

[Brian E. Fox]

Verified previous snapshot and the assembly below both work fine on my
build.

+1 

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 12, 2007 11:45 AM
To: Maven Developers List
Subject: [VOTE] Release Maven 2.0.5

Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and I'll
fix stuff. We haven't released in so long there very well may be some
problems.

We should probably let it sit until Tuesday as most folks won't try it
out over the weekend.

+1

Thanks,

Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 12 Jan 07, at 3:57 PM 12 Jan 07, Jerome Lacoste wrote:


On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.



We're not in any particular rush.

Jason.


+1




The thing I am most scared of are regressions. I haven't tried the  
trunk for
a while. Not sure if I will have time to try it on all the projects  
I use m2

before Tuesday, but will try.

Will there be a 2.0.6 and if so, will the next release happen  
fast ? If not,
I'd suggest to leave more time for testing... Have waited so long  
that some

days more won't kill :)

J



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jason van Zyl]

On 12 Jan 07, at 2:15 PM 12 Jan 07, Tomasz Pik wrote:


On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/


Can something be done with:
tar: A lone zero block at 4174

It's with tar 1.16 on windows/cygwin

Not a bug but a little annoying warning.



Not going to happen for this release, but create an issue. Tell me  
what it is and I'll assign it to 2.0.6.


Jason.


Regards,
Tomek

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[jason . dillon]

This would be good... Many users are going to wonder if maven built assemblies 
are corrupt or not because of this. 

If not for 2.0.5 maybe 2.0.6 can quickly follow with some of these little 
details cleaned up?

--jason


  

-Original Message-
From: "Tomasz Pik" <[EMAIL PROTECTED]>
Date: Fri, 12 Jan 2007 20:15:17 
To:"Maven Developers List" 
Subject: Re: [VOTE] Release Maven 2.0.5

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:

> http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
> core/2.0.5/

Can something be done with:
tar: A lone zero block at 4174

It's with tar 1.16 on windows/cygwin

Not a bug but a little annoying warning.

Regards,
Tomek

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Jerome Lacoste]

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


Hi,

The entire release is staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC

That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.

We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.

+1




The thing I am most scared of are regressions. I haven't tried the trunk for
a while. Not sure if I will have time to try it on all the projects I use m2
before Tuesday, but will try.

Will there be a 2.0.6 and if so, will the next release happen fast ? If not,
I'd suggest to leave more time for testing... Have waited so long that some
days more won't kill :)

J

Re: [VOTE] Release Maven 2.0.5

[Tomasz Pik]

On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/


Can something be done with:
tar: A lone zero block at 4174

It's with tar 1.16 on windows/cygwin

Not a bug but a little annoying warning.

Regards,
Tomek

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Maven 2.0.5

[Daniel Kulp]

Well,  I hate to do this cause I REALLY would like to see 2.0.5 out, but...

-1, non-binding, but these are legal issues

Issues:
1) The NOTICE.TXT file in the root of the binary package only mentions Apache 
stuff.   However, I see a jsch jar, jtidy jar, and xml-apis jar that 
certainly are not apache.  Plexus is codehaus, etc...   Thus, the NOTICE file 
definitely needs updating.

2) The scripts in bin have the old Apache copyright, not the new one.

Sorry.  :-(

Dan


On Friday 12 January 2007 11:45, Jason van Zyl wrote:
> Hi,
>
> The entire release is staged here:
>
> http://people.apache.org/~jvanzyl/maven-2.0.5/
>
> The assemblies that people are interested in are staged here:
>
> http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
> core/2.0.5/
>
> Here is the JIRA roadmap:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> order=DESC
>
> That's about it. Play around with it, if there are things wrong and
> I'll fix stuff. We haven't released in so long there very well may be
> some problems.
>
> We should probably let it sit until Tuesday as most folks won't try
> it out over the weekend.
>
> +1
>
> Thanks,
>
> Jason.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]