On 2 Apr 07, at 2:03 PM 2 Apr 07, Emmanuel Venisse wrote:
Joakim Erdfelt a écrit :
Jason van Zyl wrote:
On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
Should this include the
Joakim Erdfelt a écrit :
Jason van Zyl wrote:
On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
Should this include the full change log like previous releases?
I added a pointer to
Jason van Zyl wrote:
>
> On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
>
>> On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>> On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
>>> > Should this include the full change log like previous releases?
>>>
>>> I added a pointer to the roa
On 4/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
So when they reference bad information in the site you're going to go
back and edit it to make it correct again?
Huh? I want the release notes to be static. Not to change if
something changes in JIRA, and not to disappear (404) if JIRA gets
On 2 Apr 07, at 1:01 PM 2 Apr 07, Wendy Smoak wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
> Should this include the full change log like previous releases?
I added a pointer to the roadmap, I don't think we need to entirely
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
> Should this include the full change log like previous releases?
I added a pointer to the roadmap, I don't think we need to entirely
replicate the list produced by JIRA. But users should be
releases with 2.0.6, but I don't really see where this would
come from.
Help would be appreciated.
Thanks folks!
Denis.
> -Message d'origine-
> De : Jason van Zyl [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 2 avril 2007 15:22
> À : Maven Developers List
> Objet
Jörg Schaible wrote:
> Another regression problem: XDoclet plugin is completly broken. The
> plugin itself was problematic anyway, since it depends on the
> o.a.m.p:maven-anrun-plugin:1.0 (as jar dependency!!!) that prevented the
> version 1.1 from antrun-plugin to work properly already with earlie
Another regression problem: XDoclet plugin is completly broken. The plugin
itself was problematic anyway, since it depends on the
o.a.m.p:maven-anrun-plugin:1.0 (as jar dependency!!!) that prevented the
version 1.1 from antrun-plugin to work properly already with earlier Maven
versions (MOJO-64
age d'origine-
> De : Jason van Zyl [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 2 avril 2007 15:22
> À : Maven Developers List
> Objet : Re: Regression: (was: [ANN] Maven 2.0.6 Released)
>
>
> On 2 Apr 07, at 8:46 AM 2 Apr 07, Jörg Schaible wrote:
>
> >
>
On 2 Apr 07, at 8:46 AM 2 Apr 07, Jörg Schaible wrote:
A dependencyManagement section overwrites the scope of the
currently built artifact (MNG-2919) ... :-/
Assigned to 2.0.7, but it's biting you to work around the transitive
compile scope effect. I'll make an IT with your sample or y
A dependencyManagement section overwrites the scope of the currently built
artifact (MNG-2919) ... :-/
Heads-up: 2.0.6 is listed in JIRA still as unreleased ... ;-)
Jason van Zyl wrote on Sunday, April 01, 2007 3:01 PM:
> The Apache Maven team would like to announce the availability of
> Maven
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
The Apache Maven team would like to announce the availability of
Maven 2.0.6. We have closed out 22 issues for this release and the
upgrade from 2.0.5 should be pain free. We corrected a major flaw in
the artifact resolution mechanism and we can
Congrats and thanks to all the people working on it! Especially MGN-1577 ...
- Jörg
Jason van Zyl wrote on Sunday, April 01, 2007 3:01 PM:
> The Apache Maven team would like to announce the availability of
> Maven 2.0.6. We have closed out 22 issues for this release and the
> upgrade from 2.0.5
On 1 Apr 07, at 12:14 PM 1 Apr 07, Gregory Kick wrote:
Thanks for the release. Just thought that I'd point out that the main
maven.apache.org page still says 2.0.5.
Fixed, thanks.
On 4/1/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Thanks!
On 01/04/2007, at 11:25 PM, Jason van Zyl wrote:
Thanks for the release. Just thought that I'd point out that the main
maven.apache.org page still says 2.0.5.
On 4/1/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Thanks!
On 01/04/2007, at 11:25 PM, Jason van Zyl wrote:
>
> On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
>
>>
>> On 01/04/
Thanks!
On 01/04/2007, at 11:25 PM, Jason van Zyl wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like p
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like previous releases?
Forgot to mention I updated that and de
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like previous releases?
I added a pointer to the roadmap, I don
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like previous releases?
Thanks,
Brett
-
To unsubscrib
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
The Apache Maven team would like to announce the availability of
Maven 2.0.6. We have closed out 22 issues for this release and the
upgrade from 2.0.5 should be pain free. We corrected a major flaw in
the artifact resolution mechanism and we can
The Apache Maven team would like to announce the availability of
Maven 2.0.6. We have closed out 22 issues for this release and the
upgrade from 2.0.5 should be pain free. We corrected a major flaw in
the artifact resolution mechanism and we cannot find any problems but
information about th
22 matches
Mail list logo
