You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@tesla.io> on 2013/06/18 15:56:45 UTC

Maven 3.1.0-beta-1

Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I plan to cut the 3.1.0-beta-1 this weekend if there are no objections.

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

We know what we are, but know not what we may be.

  -- Shakespeare






Re: Maven 3.1.0-beta-1

Posted by Igor Fedorenko <ig...@ifedorenko.com>.
Are you able to provide standalone example project that demonstrates the
problem?

--
Regards,
Igor

On 2013-06-26 4:23 PM, Jörg Schaible wrote:
> Hi Jason,
>
> Jason van Zyl wrote:
>
>> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
>> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
>
> Apart from the reported bogus build with snapshots (MNG-5207) it seems M31
> has a major problem with PermGen space leakage.
>
> We have currently a build that contains 337 projects. With M221 I can build
> all of it in one run in ~11 minutes.
>
> With M305 the build runs faster, but I have to continue it two times with "-
> rf" option, because it runs out of PermGen space.
>
> With M31a the leakage is really worse. The build stops because of PermGen
> space 4 times, where I have to continue manually again.
>
> All plugins are locked down, so it has to be related with Maven core.
> MAVEN_OPTS is "-Xmx1g -XX:MaxPermSize=192m" and I am running "mvn clean
> install [-rf <name>]".
>
> Thanks,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Kristian Rosenvold <kr...@gmail.com>.
Oops. It appears the standard heap dump toosl don't really dump
permgen, so that's not going to get us anywhere.

I usually do this in jprofiler, maybe someone else has a suggestion :)

Kristian




2013/6/26 Kristian Rosenvold <kr...@gmail.com>:
> Funny in a sort of ironic way, permgen is noticeably better in 3.1 for
> my usecases :)
>
> The simplest way to get (my) attention to this issue is to create 2
> heap dumps of your maven process, one after "some time" and the other
> just before it runs out of permgen.
>
> ("some time" is supposed to be well into the execution so I can avoid
> tracking all the *correct* permgen usage that happens at the start of
> a maven build as it loads the plugins)
>
> You can send them to me via something like dropbox or other means that handles
> large files.
>
> Use jvisualvm or one of the other tools to get the heap dumps.
>
> Kristian
>
>
> 2013/6/26 Jörg Schaible <Jo...@scalaris.com>:
>> Hi Jason,
>>
>> Jason van Zyl wrote:
>>
>>> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
>>> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
>>
>> Apart from the reported bogus build with snapshots (MNG-5207) it seems M31
>> has a major problem with PermGen space leakage.
>>
>> We have currently a build that contains 337 projects. With M221 I can build
>> all of it in one run in ~11 minutes.
>>
>> With M305 the build runs faster, but I have to continue it two times with "-
>> rf" option, because it runs out of PermGen space.
>>
>> With M31a the leakage is really worse. The build stops because of PermGen
>> space 4 times, where I have to continue manually again.
>>
>> All plugins are locked down, so it has to be related with Maven core.
>> MAVEN_OPTS is "-Xmx1g -XX:MaxPermSize=192m" and I am running "mvn clean
>> install [-rf <name>]".
>>
>> Thanks,
>> Jörg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Kristian Rosenvold <kr...@gmail.com>.
Funny in a sort of ironic way, permgen is noticeably better in 3.1 for
my usecases :)

The simplest way to get (my) attention to this issue is to create 2
heap dumps of your maven process, one after "some time" and the other
just before it runs out of permgen.

("some time" is supposed to be well into the execution so I can avoid
tracking all the *correct* permgen usage that happens at the start of
a maven build as it loads the plugins)

You can send them to me via something like dropbox or other means that handles
large files.

Use jvisualvm or one of the other tools to get the heap dumps.

Kristian


2013/6/26 Jörg Schaible <Jo...@scalaris.com>:
> Hi Jason,
>
> Jason van Zyl wrote:
>
>> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
>> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
>
> Apart from the reported bogus build with snapshots (MNG-5207) it seems M31
> has a major problem with PermGen space leakage.
>
> We have currently a build that contains 337 projects. With M221 I can build
> all of it in one run in ~11 minutes.
>
> With M305 the build runs faster, but I have to continue it two times with "-
> rf" option, because it runs out of PermGen space.
>
> With M31a the leakage is really worse. The build stops because of PermGen
> space 4 times, where I have to continue manually again.
>
> All plugins are locked down, so it has to be related with Maven core.
> MAVEN_OPTS is "-Xmx1g -XX:MaxPermSize=192m" and I am running "mvn clean
> install [-rf <name>]".
>
> Thanks,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Jason van Zyl <ja...@tesla.io>.
It may be Maven or one of the plugins that changed as a result of updating the default plugins. I have a several very large builds and performance seems the same. I will set up the performance framework for the core[1], and I have a profiler for plugins that I will cleanup. I think it best to get the release out and many things will shake out and need to be fixed, and part of that should be enabling the performance tests to make sure that it doesn't slip.

[1]: https://github.com/tesla/maven-performance-tests
On Jun 30, 2013, at 3:21 PM, Dennis Lundberg <de...@gmail.com> wrote:

> Hi
> 
> I see this as well in our corporate aggregator POM that builds everything.
> This 124 module build succeeds with Maven 3.0.5, but fails with
> java.lang.OutOfMemoryError: PermGen space
> after 108 modules when using Maven 3.1.0-alpha-1.
> 
> Sorry but I can't share the project.
> Are there any free tools that I can use to provide a permgen dump?
> 
> 
> 
> On Wed, Jun 26, 2013 at 2:23 PM, Jörg Schaible
> <Jo...@scalaris.com>wrote:
> 
>> Hi Jason,
>> 
>> Jason van Zyl wrote:
>> 
>>> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
>>> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
>> 
>> Apart from the reported bogus build with snapshots (MNG-5207) it seems M31
>> has a major problem with PermGen space leakage.
>> 
>> We have currently a build that contains 337 projects. With M221 I can build
>> all of it in one run in ~11 minutes.
>> 
>> With M305 the build runs faster, but I have to continue it two times with
>> "-
>> rf" option, because it runs out of PermGen space.
>> 
>> With M31a the leakage is really worse. The build stops because of PermGen
>> space 4 times, where I have to continue manually again.
>> 
>> All plugins are locked down, so it has to be related with Maven core.
>> MAVEN_OPTS is "-Xmx1g -XX:MaxPermSize=192m" and I am running "mvn clean
>> install [-rf <name>]".
>> 
>> Thanks,
>> Jörg
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>> 
>> 
> 
> 
> -- 
> Dennis Lundberg

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

We all have problems. How we deal with them is a measure of our worth.

 -- Unknown







Re: Maven 3.1.0-beta-1

Posted by Dennis Lundberg <de...@gmail.com>.
Hi

I see this as well in our corporate aggregator POM that builds everything.
This 124 module build succeeds with Maven 3.0.5, but fails with
java.lang.OutOfMemoryError: PermGen space
after 108 modules when using Maven 3.1.0-alpha-1.

Sorry but I can't share the project.
Are there any free tools that I can use to provide a permgen dump?



On Wed, Jun 26, 2013 at 2:23 PM, Jörg Schaible
<Jo...@scalaris.com>wrote:

> Hi Jason,
>
> Jason van Zyl wrote:
>
> > Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
> > plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
>
> Apart from the reported bogus build with snapshots (MNG-5207) it seems M31
> has a major problem with PermGen space leakage.
>
> We have currently a build that contains 337 projects. With M221 I can build
> all of it in one run in ~11 minutes.
>
> With M305 the build runs faster, but I have to continue it two times with
> "-
> rf" option, because it runs out of PermGen space.
>
> With M31a the leakage is really worse. The build stops because of PermGen
> space 4 times, where I have to continue manually again.
>
> All plugins are locked down, so it has to be related with Maven core.
> MAVEN_OPTS is "-Xmx1g -XX:MaxPermSize=192m" and I am running "mvn clean
> install [-rf <name>]".
>
> Thanks,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
Dennis Lundberg

Re: Maven 3.1.0-beta-1

Posted by Jason van Zyl <ja...@tesla.io>.
I will resurrect the performance framework that Igor build long ago. I should be running it when major changes are made. I'll report back later this week. I need to find an old, crappy machine to run them on to gauge the difference accurately.

On Jun 26, 2013, at 8:23 AM, Jörg Schaible <jo...@scalaris.com> wrote:

> Hi Jason,
> 
> Jason van Zyl wrote:
> 
>> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
>> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
> 
> Apart from the reported bogus build with snapshots (MNG-5207) it seems M31 
> has a major problem with PermGen space leakage.
> 
> We have currently a build that contains 337 projects. With M221 I can build 
> all of it in one run in ~11 minutes.
> 
> With M305 the build runs faster, but I have to continue it two times with "-
> rf" option, because it runs out of PermGen space.
> 
> With M31a the leakage is really worse. The build stops because of PermGen 
> space 4 times, where I have to continue manually again.
> 
> All plugins are locked down, so it has to be related with Maven core. 
> MAVEN_OPTS is "-Xmx1g -XX:MaxPermSize=192m" and I am running "mvn clean 
> install [-rf <name>]".
> 
> Thanks,
> Jörg
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------







Re: Maven 3.1.0-beta-1

Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Jason,

Jason van Zyl wrote:

> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.

Apart from the reported bogus build with snapshots (MNG-5207) it seems M31 
has a major problem with PermGen space leakage.

We have currently a build that contains 337 projects. With M221 I can build 
all of it in one run in ~11 minutes.

With M305 the build runs faster, but I have to continue it two times with "-
rf" option, because it runs out of PermGen space.

With M31a the leakage is really worse. The build stops because of PermGen 
space 4 times, where I have to continue manually again.

All plugins are locked down, so it has to be related with Maven core. 
MAVEN_OPTS is "-Xmx1g -XX:MaxPermSize=192m" and I am running "mvn clean 
install [-rf <name>]".

Thanks,
Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Jason,

did you had a chance to take a second look, following my instructions in my 
first reply?

Thanks,
Jörg

Jason van Zyl wrote:

> I unpacked your example and ran your preparation script and it fails in
> 2.2.1 as well:
> 
> https://gist.github.com/jvanzyl/5824206
> 
> What's the overall usecase? You have a build with snapshots and you find
> you need to go back to a release so you lock down to a previous release
> and want to use that?
> 
> If you want to iteratively work on it together put it in a github repo.
> 
> On Jun 20, 2013, at 2:45 AM, Jörg Schaible <jo...@scalaris.com>
> wrote:
> 
>> Hi Jason,
>> 
>> Jason van Zyl wrote:
>> 
>>> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
>>> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
>> 
>> Since all versions of M30x fail in their core competence to make reliable
>> builds because it uses stale snapshots, it would be fine to have at least
>> a properly working M31x. What I am talking about? See MNG-5207! Reported
>> months ago, a proper IT test bit rots in JIRA and if you search through
>> the archives of this list for the issue, then you'll notice that it has
>> been reported more than once, with promises to look into it. And yes, I
>> have verified that M31a still fails.
>> 
>> - Jörg
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>> 
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> Three people can keep a secret provided two of them are dead.
> 
>  -- Benjamin Franklin



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Baptiste MATHUS <bm...@batmat.net>.
+1 on going 3.1.0.
At least, alphas is surely a too "frightening" name for many people to try
it.
Maybe RC would be more seen as already usable by a larger part of the
community, but not sure it's worth the effort/debate.


Cheers


2013/6/24 Sievers, Jan <ja...@sap.com>

> >Almost zero people have given feedback
>
> tycho has recently adapted to the changes in maven 3.1.0-alpha-1 with
> version 0.19.0-SNAPSHOT [1]
>
> All our ITs are passing with maven 3.1.0-alpha-1 and we didn't get tycho
> bugs reported w.r.t. maven 3.1.0-alpha-1
> Not sure how many people are using it though so you may be right that
> maven 3.1.x needs more advertising in order to to find the remaining issues.
>
> Regards,
> Jan
>
> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.19
>
> -----Original Message-----
> From: Jason van Zyl [mailto:jason@tesla.io]
> Sent: Sonntag, 23. Juni 2013 17:08
> To: Maven Developers List
> Subject: Re: Maven 3.1.0-beta-1
>
> I'm just going to cut the 3.1.0. Almost zero people have given feedback
> and I don't think anyone is going to look at this until it's released and
> then I think all sort of issues are going to surface and I will prepare to
> fix those. I believe there will be many issues but this process isn't going
> to find them.
>
> On Jun 22, 2013, at 7:20 AM, Vincent Latombe <vi...@gmail.com>
> wrote:
>
> > OK, thanks for the clarification.
> > Vincent
> >
> >
> > 2013/6/22 Jason van Zyl <ja...@tesla.io>:
> >>
> >> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <
> vincent.latombe@gmail.com> wrote:
> >>
> >>> Hello,
> >>>
> >>> I have a question about the alpha-1 release. I see that Aether has
> >>> been updated to 0.9.0 M2.
> >>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
> >>> Maven repository) is now implemented ?
> >>>
> >>
> >> No, it does not.
> >>
> >>> If this is the case, then IMHO this should be mentioned, even
> >>> highlighted in the release notes. I think this kind of improvement is
> >>> very expected for all people doing CI, as this would allow a major
> >>> speed up and reduce storage for local repositories in this kind of
> >>> environment.
> >>>
> >>> Cheers,
> >>>
> >>> Vincent
> >>>
> >>>
> >>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
> >>>>
> >>>> Hi Jason,
> >>>>
> >>>> first, thanks that you actually take your time to look into it!
> >>>>
> >>>> Jason van Zyl wrote:
> >>>>
> >>>>> I unpacked your example and ran your preparation script and it fails
> in
> >>>>> 2.2.1 as well:
> >>>>>
> >>>>> https://gist.github.com/jvanzyl/5824206
> >>>>
> >>>> The submodules are independent projects, you have to run "clean
> install".
> >>>> See the following session (I have modified the POMs of the children by
> >>>> adding a "<relativePath/>" element, the original example is now ~2
> years
> >>>> old):
> >>>>
> >>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
> >>>>
> >>>> Note, that after a successful run with M221, the build with M3x will
> no
> >>>> longer fail, but pack stale snapshots. To raise an error, you have to
> clean
> >>>> the repo from snapshots in <repohome>/bugs/maven.
> >>>>
> >>>>> What's the overall usecase? You have a build with snapshots and you
> find
> >>>>> you need to go back to a release so you lock down to a previous
> release
> >>>>> and want to use that?
> >>>>
> >>>> The final distribution of our product or projects typically consists
> of
> >>>> hundreds of artifacts, where most of them have individual release
> cycles. In
> >>>> the HEAD revision those are linked in a nested directory structure
> using
> >>>> "builder POMs" i.e. POMs that have only modules declared, but get
> never
> >>>> released themselves (like the POM in the root of the example). The
> versions
> >>>> of the individual artifact are managed in a shared parent POM. In
> HEAD those
> >>>> are typically all snapshot versions.
> >>>>
> >>>> This changes after a major release of the overall product, then all
> those
> >>>> versions become final, the shared parent is released first followed
> by all
> >>>> other artifacts in dependency order using this released parent. This
> works
> >>>> all fine.
> >>>>
> >>>> Now we get into maintenance mode of that major release. Due to the
> >>>> independence of the artifacts we have to branch only the affected
> projects
> >>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we
> develop bug
> >>>> fixes for JAR-C and JAR-S. This means we branch the shared parent,
> set JAR-C
> >>>> and JAR-S to snapshot and also the artifacts that will assemble those
> to two
> >>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the
> maintenance
> >>>> branch that contains those jars, the war and the distribution zip as
> module.
> >>>> Building this we should get a war that contains JAR-C and JAR-S as
> snapshot
> >>>> and all the others as release and the distribution contains the
> affected
> >>>> WAR-X as snapshot and all other stuff as released version - the
> perfect
> >>>> situation to test the fix.
> >>>>
> >>>> Unfortunately M3 fails here, because it is under some circumstance
> not able
> >>>> to calculate the proper build order (maybe it does no longer take
> attached
> >>>> snapshot artifacts into account ?!?) and will either pack a stale
> snapshot
> >>>> from the local repository or fail, because the snapshot is built at a
> later
> >>>> time.
> >>>>
> >>>>> If you want to iteratively work on it together put it in a github
> repo.
> >>>>
> >>>> If you bear with me, may day-to-day work is with svn only and my
> learning
> >>>> curve with git/github is still steep, e.g. I did not know about
> gists, so I
> >>>> already learned something new.
> >>>>
> >>>> Cheers and thanks for your time,
> >>>> Jörg
> >>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder & CTO, Sonatype
> >> Founder,  Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >>
> >> A party which is not afraid of letting culture,
> >> business, and welfare go to ruin completely can
> >> be omnipotent for a while.
> >>
> >>  -- Jakob Burckhardt
> >>
> >>
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> Three people can keep a secret provided two of them are dead.
>
>  -- Benjamin Franklin
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

RE: Maven 3.1.0-beta-1

Posted by "Sievers, Jan" <ja...@sap.com>.
>Almost zero people have given feedback 

tycho has recently adapted to the changes in maven 3.1.0-alpha-1 with version 0.19.0-SNAPSHOT [1]

All our ITs are passing with maven 3.1.0-alpha-1 and we didn't get tycho bugs reported w.r.t. maven 3.1.0-alpha-1
Not sure how many people are using it though so you may be right that maven 3.1.x needs more advertising in order to to find the remaining issues.

Regards,
Jan

[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.19 

-----Original Message-----
From: Jason van Zyl [mailto:jason@tesla.io] 
Sent: Sonntag, 23. Juni 2013 17:08
To: Maven Developers List
Subject: Re: Maven 3.1.0-beta-1

I'm just going to cut the 3.1.0. Almost zero people have given feedback and I don't think anyone is going to look at this until it's released and then I think all sort of issues are going to surface and I will prepare to fix those. I believe there will be many issues but this process isn't going to find them.

On Jun 22, 2013, at 7:20 AM, Vincent Latombe <vi...@gmail.com> wrote:

> OK, thanks for the clarification.
> Vincent
> 
> 
> 2013/6/22 Jason van Zyl <ja...@tesla.io>:
>> 
>> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <vi...@gmail.com> wrote:
>> 
>>> Hello,
>>> 
>>> I have a question about the alpha-1 release. I see that Aether has
>>> been updated to 0.9.0 M2.
>>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
>>> Maven repository) is now implemented ?
>>> 
>> 
>> No, it does not.
>> 
>>> If this is the case, then IMHO this should be mentioned, even
>>> highlighted in the release notes. I think this kind of improvement is
>>> very expected for all people doing CI, as this would allow a major
>>> speed up and reduce storage for local repositories in this kind of
>>> environment.
>>> 
>>> Cheers,
>>> 
>>> Vincent
>>> 
>>> 
>>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>>>> 
>>>> Hi Jason,
>>>> 
>>>> first, thanks that you actually take your time to look into it!
>>>> 
>>>> Jason van Zyl wrote:
>>>> 
>>>>> I unpacked your example and ran your preparation script and it fails in
>>>>> 2.2.1 as well:
>>>>> 
>>>>> https://gist.github.com/jvanzyl/5824206
>>>> 
>>>> The submodules are independent projects, you have to run "clean install".
>>>> See the following session (I have modified the POMs of the children by
>>>> adding a "<relativePath/>" element, the original example is now ~2 years
>>>> old):
>>>> 
>>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
>>>> 
>>>> Note, that after a successful run with M221, the build with M3x will no
>>>> longer fail, but pack stale snapshots. To raise an error, you have to clean
>>>> the repo from snapshots in <repohome>/bugs/maven.
>>>> 
>>>>> What's the overall usecase? You have a build with snapshots and you find
>>>>> you need to go back to a release so you lock down to a previous release
>>>>> and want to use that?
>>>> 
>>>> The final distribution of our product or projects typically consists of
>>>> hundreds of artifacts, where most of them have individual release cycles. In
>>>> the HEAD revision those are linked in a nested directory structure using
>>>> "builder POMs" i.e. POMs that have only modules declared, but get never
>>>> released themselves (like the POM in the root of the example). The versions
>>>> of the individual artifact are managed in a shared parent POM. In HEAD those
>>>> are typically all snapshot versions.
>>>> 
>>>> This changes after a major release of the overall product, then all those
>>>> versions become final, the shared parent is released first followed by all
>>>> other artifacts in dependency order using this released parent. This works
>>>> all fine.
>>>> 
>>>> Now we get into maintenance mode of that major release. Due to the
>>>> independence of the artifacts we have to branch only the affected projects
>>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we develop bug
>>>> fixes for JAR-C and JAR-S. This means we branch the shared parent, set JAR-C
>>>> and JAR-S to snapshot and also the artifacts that will assemble those to two
>>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the maintenance
>>>> branch that contains those jars, the war and the distribution zip as module.
>>>> Building this we should get a war that contains JAR-C and JAR-S as snapshot
>>>> and all the others as release and the distribution contains the affected
>>>> WAR-X as snapshot and all other stuff as released version - the perfect
>>>> situation to test the fix.
>>>> 
>>>> Unfortunately M3 fails here, because it is under some circumstance not able
>>>> to calculate the proper build order (maybe it does no longer take attached
>>>> snapshot artifacts into account ?!?) and will either pack a stale snapshot
>>>> from the local repository or fail, because the snapshot is built at a later
>>>> time.
>>>> 
>>>>> If you want to iteratively work on it together put it in a github repo.
>>>> 
>>>> If you bear with me, may day-to-day work is with svn only and my learning
>>>> curve with git/github is still steep, e.g. I did not know about gists, so I
>>>> already learned something new.
>>>> 
>>>> Cheers and thanks for your time,
>>>> Jörg
>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> A party which is not afraid of letting culture,
>> business, and welfare go to ruin completely can
>> be omnipotent for a while.
>> 
>>  -- Jakob Burckhardt
>> 
>> 
>> 
>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Three people can keep a secret provided two of them are dead.

 -- Benjamin Franklin






---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Jason van Zyl <ja...@tesla.io>.
Yes, just pointing out the current sisu/aether issues. All to be expected given the significant movement of projects to different organizations and the commensurate package changes. In Aether's case, significant API changes as well.

jvz

On 2013-06-23, at 11:38 AM, Stuart McCulloch <mc...@gmail.com> wrote:

> Actually the error in JENKINS-15935 is because MavenLoggerManager was removed in:
> 
>    https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=a23f7cfd10c04da702c7efb299cce6b3499c18ab
> 
> and the Jenkins maven-plugin depends on that class, hence the NCDFE.
> 
> Regarding event spy compatibility, Sisu M3 already provides preliminary support for the old API when "org.sonatype.sisu:sisu-inject:2.4.0" is also on the classpath and I'm working on improving the runtime compatibility wrt. launching from inside Hudson/Jenkins, so there will be a migration path going forwards.
> 
> --
> Cheers, Stuart
> 
> On 23 Jun 2013, at 18:49, Jason van Zyl wrote:
> 
>> The Jenkins and Hudson integration require changes with anything related to event spies that use Sisu or Aether specific classes. Existing versions of Hudson don't work either because of the event spy implementation requiring bits of Sisu in the sonatype space. 
>> 
>> This is expected. It's a major API change which is why I argued for calling it 4.0.0.
>> 
>> On Jun 23, 2013, at 9:17 AM, Dennis Lundberg <de...@gmail.com> wrote:
>> 
>>> Hi Jason
>>> 
>>> I've installed 3.1.0-alpha-1 into my local Jenkins 1.512 instance running
>>> on Windows. After that I tried a simple build and ran into an exception
>>> that others apparently had also seen:
>>> 
>>> https://issues.jenkins-ci.org/browse/JENKINS-15935
>>> 
>>> Is that a problem in the Maven Integration plugin for Jenkins?
>>> 
>>> 
>>> 
>>> On Sun, Jun 23, 2013 at 5:07 PM, Jason van Zyl <ja...@tesla.io> wrote:
>>> 
>>>> I'm just going to cut the 3.1.0. Almost zero people have given feedback
>>>> and I don't think anyone is going to look at this until it's released and
>>>> then I think all sort of issues are going to surface and I will prepare to
>>>> fix those. I believe there will be many issues but this process isn't going
>>>> to find them.
>>>> 
>>>> On Jun 22, 2013, at 7:20 AM, Vincent Latombe <vi...@gmail.com>
>>>> wrote:
>>>> 
>>>>> OK, thanks for the clarification.
>>>>> Vincent
>>>>> 
>>>>> 
>>>>> 2013/6/22 Jason van Zyl <ja...@tesla.io>:
>>>>>> 
>>>>>> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <
>>>> vincent.latombe@gmail.com> wrote:
>>>>>> 
>>>>>>> Hello,
>>>>>>> 
>>>>>>> I have a question about the alpha-1 release. I see that Aether has
>>>>>>> been updated to 0.9.0 M2.
>>>>>>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
>>>>>>> Maven repository) is now implemented ?
>>>>>> 
>>>>>> No, it does not.
>>>>>> 
>>>>>>> If this is the case, then IMHO this should be mentioned, even
>>>>>>> highlighted in the release notes. I think this kind of improvement is
>>>>>>> very expected for all people doing CI, as this would allow a major
>>>>>>> speed up and reduce storage for local repositories in this kind of
>>>>>>> environment.
>>>>>>> 
>>>>>>> Cheers,
>>>>>>> 
>>>>>>> Vincent
>>>>>>> 
>>>>>>> 
>>>>>>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>>>>>>>> 
>>>>>>>> Hi Jason,
>>>>>>>> 
>>>>>>>> first, thanks that you actually take your time to look into it!
>>>>>>>> 
>>>>>>>> Jason van Zyl wrote:
>>>>>>>> 
>>>>>>>>> I unpacked your example and ran your preparation script and it fails
>>>> in
>>>>>>>>> 2.2.1 as well:
>>>>>>>>> 
>>>>>>>>> https://gist.github.com/jvanzyl/5824206
>>>>>>>> 
>>>>>>>> The submodules are independent projects, you have to run "clean
>>>> install".
>>>>>>>> See the following session (I have modified the POMs of the children by
>>>>>>>> adding a "<relativePath/>" element, the original example is now ~2
>>>> years
>>>>>>>> old):
>>>>>>>> 
>>>>>>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
>>>>>>>> 
>>>>>>>> Note, that after a successful run with M221, the build with M3x will
>>>> no
>>>>>>>> longer fail, but pack stale snapshots. To raise an error, you have to
>>>> clean
>>>>>>>> the repo from snapshots in <repohome>/bugs/maven.
>>>>>>>> 
>>>>>>>>> What's the overall usecase? You have a build with snapshots and you
>>>> find
>>>>>>>>> you need to go back to a release so you lock down to a previous
>>>> release
>>>>>>>>> and want to use that?
>>>>>>>> 
>>>>>>>> The final distribution of our product or projects typically consists
>>>> of
>>>>>>>> hundreds of artifacts, where most of them have individual release
>>>> cycles. In
>>>>>>>> the HEAD revision those are linked in a nested directory structure
>>>> using
>>>>>>>> "builder POMs" i.e. POMs that have only modules declared, but get
>>>> never
>>>>>>>> released themselves (like the POM in the root of the example). The
>>>> versions
>>>>>>>> of the individual artifact are managed in a shared parent POM. In
>>>> HEAD those
>>>>>>>> are typically all snapshot versions.
>>>>>>>> 
>>>>>>>> This changes after a major release of the overall product, then all
>>>> those
>>>>>>>> versions become final, the shared parent is released first followed
>>>> by all
>>>>>>>> other artifacts in dependency order using this released parent. This
>>>> works
>>>>>>>> all fine.
>>>>>>>> 
>>>>>>>> Now we get into maintenance mode of that major release. Due to the
>>>>>>>> independence of the artifacts we have to branch only the affected
>>>> projects
>>>>>>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we
>>>> develop bug
>>>>>>>> fixes for JAR-C and JAR-S. This means we branch the shared parent,
>>>> set JAR-C
>>>>>>>> and JAR-S to snapshot and also the artifacts that will assemble those
>>>> to two
>>>>>>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the
>>>> maintenance
>>>>>>>> branch that contains those jars, the war and the distribution zip as
>>>> module.
>>>>>>>> Building this we should get a war that contains JAR-C and JAR-S as
>>>> snapshot
>>>>>>>> and all the others as release and the distribution contains the
>>>> affected
>>>>>>>> WAR-X as snapshot and all other stuff as released version - the
>>>> perfect
>>>>>>>> situation to test the fix.
>>>>>>>> 
>>>>>>>> Unfortunately M3 fails here, because it is under some circumstance
>>>> not able
>>>>>>>> to calculate the proper build order (maybe it does no longer take
>>>> attached
>>>>>>>> snapshot artifacts into account ?!?) and will either pack a stale
>>>> snapshot
>>>>>>>> from the local repository or fail, because the snapshot is built at a
>>>> later
>>>>>>>> time.
>>>>>>>> 
>>>>>>>>> If you want to iteratively work on it together put it in a github
>>>> repo.
>>>>>>>> 
>>>>>>>> If you bear with me, may day-to-day work is with svn only and my
>>>> learning
>>>>>>>> curve with git/github is still steep, e.g. I did not know about
>>>> gists, so I
>>>>>>>> already learned something new.
>>>>>>>> 
>>>>>>>> Cheers and thanks for your time,
>>>>>>>> Jörg
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>> 
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Jason
>>>>>> 
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder & CTO, Sonatype
>>>>>> Founder,  Apache Maven
>>>>>> http://twitter.com/jvanzyl
>>>>>> ---------------------------------------------------------
>>>>>> 
>>>>>> A party which is not afraid of letting culture,
>>>>>> business, and welfare go to ruin completely can
>>>>>> be omnipotent for a while.
>>>>>> 
>>>>>> -- Jakob Burckhardt
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>> 
>>>> Thanks,
>>>> 
>>>> Jason
>>>> 
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder & CTO, Sonatype
>>>> Founder,  Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>> 
>>>> Three people can keep a secret provided two of them are dead.
>>>> 
>>>> -- Benjamin Franklin
>>> 
>>> 
>>> -- 
>>> Dennis Lundberg
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> To do two things at once is to do neither.
>> 
>> -- Publilius Syrus, Roman slave, first century B.C.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Stuart McCulloch <mc...@gmail.com>.
Actually the error in JENKINS-15935 is because MavenLoggerManager was removed in:

	https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=a23f7cfd10c04da702c7efb299cce6b3499c18ab

and the Jenkins maven-plugin depends on that class, hence the NCDFE.

Regarding event spy compatibility, Sisu M3 already provides preliminary support for the old API when "org.sonatype.sisu:sisu-inject:2.4.0" is also on the classpath and I'm working on improving the runtime compatibility wrt. launching from inside Hudson/Jenkins, so there will be a migration path going forwards.

--
Cheers, Stuart

On 23 Jun 2013, at 18:49, Jason van Zyl wrote:

> The Jenkins and Hudson integration require changes with anything related to event spies that use Sisu or Aether specific classes. Existing versions of Hudson don't work either because of the event spy implementation requiring bits of Sisu in the sonatype space. 
> 
> This is expected. It's a major API change which is why I argued for calling it 4.0.0.
> 
> On Jun 23, 2013, at 9:17 AM, Dennis Lundberg <de...@gmail.com> wrote:
> 
>> Hi Jason
>> 
>> I've installed 3.1.0-alpha-1 into my local Jenkins 1.512 instance running
>> on Windows. After that I tried a simple build and ran into an exception
>> that others apparently had also seen:
>> 
>> https://issues.jenkins-ci.org/browse/JENKINS-15935
>> 
>> Is that a problem in the Maven Integration plugin for Jenkins?
>> 
>> 
>> 
>> On Sun, Jun 23, 2013 at 5:07 PM, Jason van Zyl <ja...@tesla.io> wrote:
>> 
>>> I'm just going to cut the 3.1.0. Almost zero people have given feedback
>>> and I don't think anyone is going to look at this until it's released and
>>> then I think all sort of issues are going to surface and I will prepare to
>>> fix those. I believe there will be many issues but this process isn't going
>>> to find them.
>>> 
>>> On Jun 22, 2013, at 7:20 AM, Vincent Latombe <vi...@gmail.com>
>>> wrote:
>>> 
>>>> OK, thanks for the clarification.
>>>> Vincent
>>>> 
>>>> 
>>>> 2013/6/22 Jason van Zyl <ja...@tesla.io>:
>>>>> 
>>>>> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <
>>> vincent.latombe@gmail.com> wrote:
>>>>> 
>>>>>> Hello,
>>>>>> 
>>>>>> I have a question about the alpha-1 release. I see that Aether has
>>>>>> been updated to 0.9.0 M2.
>>>>>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
>>>>>> Maven repository) is now implemented ?
>>>>>> 
>>>>> 
>>>>> No, it does not.
>>>>> 
>>>>>> If this is the case, then IMHO this should be mentioned, even
>>>>>> highlighted in the release notes. I think this kind of improvement is
>>>>>> very expected for all people doing CI, as this would allow a major
>>>>>> speed up and reduce storage for local repositories in this kind of
>>>>>> environment.
>>>>>> 
>>>>>> Cheers,
>>>>>> 
>>>>>> Vincent
>>>>>> 
>>>>>> 
>>>>>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>>>>>>> 
>>>>>>> Hi Jason,
>>>>>>> 
>>>>>>> first, thanks that you actually take your time to look into it!
>>>>>>> 
>>>>>>> Jason van Zyl wrote:
>>>>>>> 
>>>>>>>> I unpacked your example and ran your preparation script and it fails
>>> in
>>>>>>>> 2.2.1 as well:
>>>>>>>> 
>>>>>>>> https://gist.github.com/jvanzyl/5824206
>>>>>>> 
>>>>>>> The submodules are independent projects, you have to run "clean
>>> install".
>>>>>>> See the following session (I have modified the POMs of the children by
>>>>>>> adding a "<relativePath/>" element, the original example is now ~2
>>> years
>>>>>>> old):
>>>>>>> 
>>>>>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
>>>>>>> 
>>>>>>> Note, that after a successful run with M221, the build with M3x will
>>> no
>>>>>>> longer fail, but pack stale snapshots. To raise an error, you have to
>>> clean
>>>>>>> the repo from snapshots in <repohome>/bugs/maven.
>>>>>>> 
>>>>>>>> What's the overall usecase? You have a build with snapshots and you
>>> find
>>>>>>>> you need to go back to a release so you lock down to a previous
>>> release
>>>>>>>> and want to use that?
>>>>>>> 
>>>>>>> The final distribution of our product or projects typically consists
>>> of
>>>>>>> hundreds of artifacts, where most of them have individual release
>>> cycles. In
>>>>>>> the HEAD revision those are linked in a nested directory structure
>>> using
>>>>>>> "builder POMs" i.e. POMs that have only modules declared, but get
>>> never
>>>>>>> released themselves (like the POM in the root of the example). The
>>> versions
>>>>>>> of the individual artifact are managed in a shared parent POM. In
>>> HEAD those
>>>>>>> are typically all snapshot versions.
>>>>>>> 
>>>>>>> This changes after a major release of the overall product, then all
>>> those
>>>>>>> versions become final, the shared parent is released first followed
>>> by all
>>>>>>> other artifacts in dependency order using this released parent. This
>>> works
>>>>>>> all fine.
>>>>>>> 
>>>>>>> Now we get into maintenance mode of that major release. Due to the
>>>>>>> independence of the artifacts we have to branch only the affected
>>> projects
>>>>>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we
>>> develop bug
>>>>>>> fixes for JAR-C and JAR-S. This means we branch the shared parent,
>>> set JAR-C
>>>>>>> and JAR-S to snapshot and also the artifacts that will assemble those
>>> to two
>>>>>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the
>>> maintenance
>>>>>>> branch that contains those jars, the war and the distribution zip as
>>> module.
>>>>>>> Building this we should get a war that contains JAR-C and JAR-S as
>>> snapshot
>>>>>>> and all the others as release and the distribution contains the
>>> affected
>>>>>>> WAR-X as snapshot and all other stuff as released version - the
>>> perfect
>>>>>>> situation to test the fix.
>>>>>>> 
>>>>>>> Unfortunately M3 fails here, because it is under some circumstance
>>> not able
>>>>>>> to calculate the proper build order (maybe it does no longer take
>>> attached
>>>>>>> snapshot artifacts into account ?!?) and will either pack a stale
>>> snapshot
>>>>>>> from the local repository or fail, because the snapshot is built at a
>>> later
>>>>>>> time.
>>>>>>> 
>>>>>>>> If you want to iteratively work on it together put it in a github
>>> repo.
>>>>>>> 
>>>>>>> If you bear with me, may day-to-day work is with svn only and my
>>> learning
>>>>>>> curve with git/github is still steep, e.g. I did not know about
>>> gists, so I
>>>>>>> already learned something new.
>>>>>>> 
>>>>>>> Cheers and thanks for your time,
>>>>>>> Jörg
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>> 
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>> 
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Jason
>>>>> 
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder & CTO, Sonatype
>>>>> Founder,  Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>> 
>>>>> A party which is not afraid of letting culture,
>>>>> business, and welfare go to ruin completely can
>>>>> be omnipotent for a while.
>>>>> 
>>>>> -- Jakob Burckhardt
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>> 
>>> 
>>> Thanks,
>>> 
>>> Jason
>>> 
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder & CTO, Sonatype
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>> 
>>> Three people can keep a secret provided two of them are dead.
>>> 
>>> -- Benjamin Franklin
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> Dennis Lundberg
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> To do two things at once is to do neither.
> 
> -- Publilius Syrus, Roman slave, first century B.C.
> 
> 
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Jason van Zyl <ja...@tesla.io>.
The Jenkins and Hudson integration require changes with anything related to event spies that use Sisu or Aether specific classes. Existing versions of Hudson don't work either because of the event spy implementation requiring bits of Sisu in the sonatype space. 

This is expected. It's a major API change which is why I argued for calling it 4.0.0.

On Jun 23, 2013, at 9:17 AM, Dennis Lundberg <de...@gmail.com> wrote:

> Hi Jason
> 
> I've installed 3.1.0-alpha-1 into my local Jenkins 1.512 instance running
> on Windows. After that I tried a simple build and ran into an exception
> that others apparently had also seen:
> 
> https://issues.jenkins-ci.org/browse/JENKINS-15935
> 
> Is that a problem in the Maven Integration plugin for Jenkins?
> 
> 
> 
> On Sun, Jun 23, 2013 at 5:07 PM, Jason van Zyl <ja...@tesla.io> wrote:
> 
>> I'm just going to cut the 3.1.0. Almost zero people have given feedback
>> and I don't think anyone is going to look at this until it's released and
>> then I think all sort of issues are going to surface and I will prepare to
>> fix those. I believe there will be many issues but this process isn't going
>> to find them.
>> 
>> On Jun 22, 2013, at 7:20 AM, Vincent Latombe <vi...@gmail.com>
>> wrote:
>> 
>>> OK, thanks for the clarification.
>>> Vincent
>>> 
>>> 
>>> 2013/6/22 Jason van Zyl <ja...@tesla.io>:
>>>> 
>>>> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <
>> vincent.latombe@gmail.com> wrote:
>>>> 
>>>>> Hello,
>>>>> 
>>>>> I have a question about the alpha-1 release. I see that Aether has
>>>>> been updated to 0.9.0 M2.
>>>>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
>>>>> Maven repository) is now implemented ?
>>>>> 
>>>> 
>>>> No, it does not.
>>>> 
>>>>> If this is the case, then IMHO this should be mentioned, even
>>>>> highlighted in the release notes. I think this kind of improvement is
>>>>> very expected for all people doing CI, as this would allow a major
>>>>> speed up and reduce storage for local repositories in this kind of
>>>>> environment.
>>>>> 
>>>>> Cheers,
>>>>> 
>>>>> Vincent
>>>>> 
>>>>> 
>>>>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>>>>>> 
>>>>>> Hi Jason,
>>>>>> 
>>>>>> first, thanks that you actually take your time to look into it!
>>>>>> 
>>>>>> Jason van Zyl wrote:
>>>>>> 
>>>>>>> I unpacked your example and ran your preparation script and it fails
>> in
>>>>>>> 2.2.1 as well:
>>>>>>> 
>>>>>>> https://gist.github.com/jvanzyl/5824206
>>>>>> 
>>>>>> The submodules are independent projects, you have to run "clean
>> install".
>>>>>> See the following session (I have modified the POMs of the children by
>>>>>> adding a "<relativePath/>" element, the original example is now ~2
>> years
>>>>>> old):
>>>>>> 
>>>>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
>>>>>> 
>>>>>> Note, that after a successful run with M221, the build with M3x will
>> no
>>>>>> longer fail, but pack stale snapshots. To raise an error, you have to
>> clean
>>>>>> the repo from snapshots in <repohome>/bugs/maven.
>>>>>> 
>>>>>>> What's the overall usecase? You have a build with snapshots and you
>> find
>>>>>>> you need to go back to a release so you lock down to a previous
>> release
>>>>>>> and want to use that?
>>>>>> 
>>>>>> The final distribution of our product or projects typically consists
>> of
>>>>>> hundreds of artifacts, where most of them have individual release
>> cycles. In
>>>>>> the HEAD revision those are linked in a nested directory structure
>> using
>>>>>> "builder POMs" i.e. POMs that have only modules declared, but get
>> never
>>>>>> released themselves (like the POM in the root of the example). The
>> versions
>>>>>> of the individual artifact are managed in a shared parent POM. In
>> HEAD those
>>>>>> are typically all snapshot versions.
>>>>>> 
>>>>>> This changes after a major release of the overall product, then all
>> those
>>>>>> versions become final, the shared parent is released first followed
>> by all
>>>>>> other artifacts in dependency order using this released parent. This
>> works
>>>>>> all fine.
>>>>>> 
>>>>>> Now we get into maintenance mode of that major release. Due to the
>>>>>> independence of the artifacts we have to branch only the affected
>> projects
>>>>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we
>> develop bug
>>>>>> fixes for JAR-C and JAR-S. This means we branch the shared parent,
>> set JAR-C
>>>>>> and JAR-S to snapshot and also the artifacts that will assemble those
>> to two
>>>>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the
>> maintenance
>>>>>> branch that contains those jars, the war and the distribution zip as
>> module.
>>>>>> Building this we should get a war that contains JAR-C and JAR-S as
>> snapshot
>>>>>> and all the others as release and the distribution contains the
>> affected
>>>>>> WAR-X as snapshot and all other stuff as released version - the
>> perfect
>>>>>> situation to test the fix.
>>>>>> 
>>>>>> Unfortunately M3 fails here, because it is under some circumstance
>> not able
>>>>>> to calculate the proper build order (maybe it does no longer take
>> attached
>>>>>> snapshot artifacts into account ?!?) and will either pack a stale
>> snapshot
>>>>>> from the local repository or fail, because the snapshot is built at a
>> later
>>>>>> time.
>>>>>> 
>>>>>>> If you want to iteratively work on it together put it in a github
>> repo.
>>>>>> 
>>>>>> If you bear with me, may day-to-day work is with svn only and my
>> learning
>>>>>> curve with git/github is still steep, e.g. I did not know about
>> gists, so I
>>>>>> already learned something new.
>>>>>> 
>>>>>> Cheers and thanks for your time,
>>>>>> Jörg
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>> 
>>>> 
>>>> Thanks,
>>>> 
>>>> Jason
>>>> 
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder & CTO, Sonatype
>>>> Founder,  Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>> 
>>>> A party which is not afraid of letting culture,
>>>> business, and welfare go to ruin completely can
>>>> be omnipotent for a while.
>>>> 
>>>> -- Jakob Burckhardt
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> Three people can keep a secret provided two of them are dead.
>> 
>> -- Benjamin Franklin
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> -- 
> Dennis Lundberg

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

To do two things at once is to do neither.
 
 -- Publilius Syrus, Roman slave, first century B.C.






Re: Maven 3.1.0-beta-1

Posted by Dennis Lundberg <de...@gmail.com>.
Hi Jason

I've installed 3.1.0-alpha-1 into my local Jenkins 1.512 instance running
on Windows. After that I tried a simple build and ran into an exception
that others apparently had also seen:

https://issues.jenkins-ci.org/browse/JENKINS-15935

Is that a problem in the Maven Integration plugin for Jenkins?



On Sun, Jun 23, 2013 at 5:07 PM, Jason van Zyl <ja...@tesla.io> wrote:

> I'm just going to cut the 3.1.0. Almost zero people have given feedback
> and I don't think anyone is going to look at this until it's released and
> then I think all sort of issues are going to surface and I will prepare to
> fix those. I believe there will be many issues but this process isn't going
> to find them.
>
> On Jun 22, 2013, at 7:20 AM, Vincent Latombe <vi...@gmail.com>
> wrote:
>
> > OK, thanks for the clarification.
> > Vincent
> >
> >
> > 2013/6/22 Jason van Zyl <ja...@tesla.io>:
> >>
> >> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <
> vincent.latombe@gmail.com> wrote:
> >>
> >>> Hello,
> >>>
> >>> I have a question about the alpha-1 release. I see that Aether has
> >>> been updated to 0.9.0 M2.
> >>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
> >>> Maven repository) is now implemented ?
> >>>
> >>
> >> No, it does not.
> >>
> >>> If this is the case, then IMHO this should be mentioned, even
> >>> highlighted in the release notes. I think this kind of improvement is
> >>> very expected for all people doing CI, as this would allow a major
> >>> speed up and reduce storage for local repositories in this kind of
> >>> environment.
> >>>
> >>> Cheers,
> >>>
> >>> Vincent
> >>>
> >>>
> >>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
> >>>>
> >>>> Hi Jason,
> >>>>
> >>>> first, thanks that you actually take your time to look into it!
> >>>>
> >>>> Jason van Zyl wrote:
> >>>>
> >>>>> I unpacked your example and ran your preparation script and it fails
> in
> >>>>> 2.2.1 as well:
> >>>>>
> >>>>> https://gist.github.com/jvanzyl/5824206
> >>>>
> >>>> The submodules are independent projects, you have to run "clean
> install".
> >>>> See the following session (I have modified the POMs of the children by
> >>>> adding a "<relativePath/>" element, the original example is now ~2
> years
> >>>> old):
> >>>>
> >>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
> >>>>
> >>>> Note, that after a successful run with M221, the build with M3x will
> no
> >>>> longer fail, but pack stale snapshots. To raise an error, you have to
> clean
> >>>> the repo from snapshots in <repohome>/bugs/maven.
> >>>>
> >>>>> What's the overall usecase? You have a build with snapshots and you
> find
> >>>>> you need to go back to a release so you lock down to a previous
> release
> >>>>> and want to use that?
> >>>>
> >>>> The final distribution of our product or projects typically consists
> of
> >>>> hundreds of artifacts, where most of them have individual release
> cycles. In
> >>>> the HEAD revision those are linked in a nested directory structure
> using
> >>>> "builder POMs" i.e. POMs that have only modules declared, but get
> never
> >>>> released themselves (like the POM in the root of the example). The
> versions
> >>>> of the individual artifact are managed in a shared parent POM. In
> HEAD those
> >>>> are typically all snapshot versions.
> >>>>
> >>>> This changes after a major release of the overall product, then all
> those
> >>>> versions become final, the shared parent is released first followed
> by all
> >>>> other artifacts in dependency order using this released parent. This
> works
> >>>> all fine.
> >>>>
> >>>> Now we get into maintenance mode of that major release. Due to the
> >>>> independence of the artifacts we have to branch only the affected
> projects
> >>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we
> develop bug
> >>>> fixes for JAR-C and JAR-S. This means we branch the shared parent,
> set JAR-C
> >>>> and JAR-S to snapshot and also the artifacts that will assemble those
> to two
> >>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the
> maintenance
> >>>> branch that contains those jars, the war and the distribution zip as
> module.
> >>>> Building this we should get a war that contains JAR-C and JAR-S as
> snapshot
> >>>> and all the others as release and the distribution contains the
> affected
> >>>> WAR-X as snapshot and all other stuff as released version - the
> perfect
> >>>> situation to test the fix.
> >>>>
> >>>> Unfortunately M3 fails here, because it is under some circumstance
> not able
> >>>> to calculate the proper build order (maybe it does no longer take
> attached
> >>>> snapshot artifacts into account ?!?) and will either pack a stale
> snapshot
> >>>> from the local repository or fail, because the snapshot is built at a
> later
> >>>> time.
> >>>>
> >>>>> If you want to iteratively work on it together put it in a github
> repo.
> >>>>
> >>>> If you bear with me, may day-to-day work is with svn only and my
> learning
> >>>> curve with git/github is still steep, e.g. I did not know about
> gists, so I
> >>>> already learned something new.
> >>>>
> >>>> Cheers and thanks for your time,
> >>>> Jörg
> >>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder & CTO, Sonatype
> >> Founder,  Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >>
> >> A party which is not afraid of letting culture,
> >> business, and welfare go to ruin completely can
> >> be omnipotent for a while.
> >>
> >>  -- Jakob Burckhardt
> >>
> >>
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> Three people can keep a secret provided two of them are dead.
>
>  -- Benjamin Franklin
>
>
>
>
>
>


-- 
Dennis Lundberg

Re: Maven 3.1.0-beta-1

Posted by Jason van Zyl <ja...@tesla.io>.
I'm just going to cut the 3.1.0. Almost zero people have given feedback and I don't think anyone is going to look at this until it's released and then I think all sort of issues are going to surface and I will prepare to fix those. I believe there will be many issues but this process isn't going to find them.

On Jun 22, 2013, at 7:20 AM, Vincent Latombe <vi...@gmail.com> wrote:

> OK, thanks for the clarification.
> Vincent
> 
> 
> 2013/6/22 Jason van Zyl <ja...@tesla.io>:
>> 
>> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <vi...@gmail.com> wrote:
>> 
>>> Hello,
>>> 
>>> I have a question about the alpha-1 release. I see that Aether has
>>> been updated to 0.9.0 M2.
>>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
>>> Maven repository) is now implemented ?
>>> 
>> 
>> No, it does not.
>> 
>>> If this is the case, then IMHO this should be mentioned, even
>>> highlighted in the release notes. I think this kind of improvement is
>>> very expected for all people doing CI, as this would allow a major
>>> speed up and reduce storage for local repositories in this kind of
>>> environment.
>>> 
>>> Cheers,
>>> 
>>> Vincent
>>> 
>>> 
>>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>>>> 
>>>> Hi Jason,
>>>> 
>>>> first, thanks that you actually take your time to look into it!
>>>> 
>>>> Jason van Zyl wrote:
>>>> 
>>>>> I unpacked your example and ran your preparation script and it fails in
>>>>> 2.2.1 as well:
>>>>> 
>>>>> https://gist.github.com/jvanzyl/5824206
>>>> 
>>>> The submodules are independent projects, you have to run "clean install".
>>>> See the following session (I have modified the POMs of the children by
>>>> adding a "<relativePath/>" element, the original example is now ~2 years
>>>> old):
>>>> 
>>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
>>>> 
>>>> Note, that after a successful run with M221, the build with M3x will no
>>>> longer fail, but pack stale snapshots. To raise an error, you have to clean
>>>> the repo from snapshots in <repohome>/bugs/maven.
>>>> 
>>>>> What's the overall usecase? You have a build with snapshots and you find
>>>>> you need to go back to a release so you lock down to a previous release
>>>>> and want to use that?
>>>> 
>>>> The final distribution of our product or projects typically consists of
>>>> hundreds of artifacts, where most of them have individual release cycles. In
>>>> the HEAD revision those are linked in a nested directory structure using
>>>> "builder POMs" i.e. POMs that have only modules declared, but get never
>>>> released themselves (like the POM in the root of the example). The versions
>>>> of the individual artifact are managed in a shared parent POM. In HEAD those
>>>> are typically all snapshot versions.
>>>> 
>>>> This changes after a major release of the overall product, then all those
>>>> versions become final, the shared parent is released first followed by all
>>>> other artifacts in dependency order using this released parent. This works
>>>> all fine.
>>>> 
>>>> Now we get into maintenance mode of that major release. Due to the
>>>> independence of the artifacts we have to branch only the affected projects
>>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we develop bug
>>>> fixes for JAR-C and JAR-S. This means we branch the shared parent, set JAR-C
>>>> and JAR-S to snapshot and also the artifacts that will assemble those to two
>>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the maintenance
>>>> branch that contains those jars, the war and the distribution zip as module.
>>>> Building this we should get a war that contains JAR-C and JAR-S as snapshot
>>>> and all the others as release and the distribution contains the affected
>>>> WAR-X as snapshot and all other stuff as released version - the perfect
>>>> situation to test the fix.
>>>> 
>>>> Unfortunately M3 fails here, because it is under some circumstance not able
>>>> to calculate the proper build order (maybe it does no longer take attached
>>>> snapshot artifacts into account ?!?) and will either pack a stale snapshot
>>>> from the local repository or fail, because the snapshot is built at a later
>>>> time.
>>>> 
>>>>> If you want to iteratively work on it together put it in a github repo.
>>>> 
>>>> If you bear with me, may day-to-day work is with svn only and my learning
>>>> curve with git/github is still steep, e.g. I did not know about gists, so I
>>>> already learned something new.
>>>> 
>>>> Cheers and thanks for your time,
>>>> Jörg
>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder & CTO, Sonatype
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> A party which is not afraid of letting culture,
>> business, and welfare go to ruin completely can
>> be omnipotent for a while.
>> 
>>  -- Jakob Burckhardt
>> 
>> 
>> 
>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Three people can keep a secret provided two of them are dead.

 -- Benjamin Franklin






Re: Maven 3.1.0-beta-1

Posted by Vincent Latombe <vi...@gmail.com>.
OK, thanks for the clarification.
Vincent


2013/6/22 Jason van Zyl <ja...@tesla.io>:
>
> On Jun 21, 2013, at 11:48 PM, Vincent Latombe <vi...@gmail.com> wrote:
>
>> Hello,
>>
>> I have a question about the alpha-1 release. I see that Aether has
>> been updated to 0.9.0 M2.
>> Does it implies that issue MNG-2802 (Concurrent-safe access to local
>> Maven repository) is now implemented ?
>>
>
> No, it does not.
>
>> If this is the case, then IMHO this should be mentioned, even
>> highlighted in the release notes. I think this kind of improvement is
>> very expected for all people doing CI, as this would allow a major
>> speed up and reduce storage for local repositories in this kind of
>> environment.
>>
>> Cheers,
>>
>> Vincent
>>
>>
>> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>>>
>>> Hi Jason,
>>>
>>> first, thanks that you actually take your time to look into it!
>>>
>>> Jason van Zyl wrote:
>>>
>>>> I unpacked your example and ran your preparation script and it fails in
>>>> 2.2.1 as well:
>>>>
>>>> https://gist.github.com/jvanzyl/5824206
>>>
>>> The submodules are independent projects, you have to run "clean install".
>>> See the following session (I have modified the POMs of the children by
>>> adding a "<relativePath/>" element, the original example is now ~2 years
>>> old):
>>>
>>> https://gist.github.com/joehni/6aa8516bd5408144ec53
>>>
>>> Note, that after a successful run with M221, the build with M3x will no
>>> longer fail, but pack stale snapshots. To raise an error, you have to clean
>>> the repo from snapshots in <repohome>/bugs/maven.
>>>
>>>> What's the overall usecase? You have a build with snapshots and you find
>>>> you need to go back to a release so you lock down to a previous release
>>>> and want to use that?
>>>
>>> The final distribution of our product or projects typically consists of
>>> hundreds of artifacts, where most of them have individual release cycles. In
>>> the HEAD revision those are linked in a nested directory structure using
>>> "builder POMs" i.e. POMs that have only modules declared, but get never
>>> released themselves (like the POM in the root of the example). The versions
>>> of the individual artifact are managed in a shared parent POM. In HEAD those
>>> are typically all snapshot versions.
>>>
>>> This changes after a major release of the overall product, then all those
>>> versions become final, the shared parent is released first followed by all
>>> other artifacts in dependency order using this released parent. This works
>>> all fine.
>>>
>>> Now we get into maintenance mode of that major release. Due to the
>>> independence of the artifacts we have to branch only the affected projects
>>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we develop bug
>>> fixes for JAR-C and JAR-S. This means we branch the shared parent, set JAR-C
>>> and JAR-S to snapshot and also the artifacts that will assemble those to two
>>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the maintenance
>>> branch that contains those jars, the war and the distribution zip as module.
>>> Building this we should get a war that contains JAR-C and JAR-S as snapshot
>>> and all the others as release and the distribution contains the affected
>>> WAR-X as snapshot and all other stuff as released version - the perfect
>>> situation to test the fix.
>>>
>>> Unfortunately M3 fails here, because it is under some circumstance not able
>>> to calculate the proper build order (maybe it does no longer take attached
>>> snapshot artifacts into account ?!?) and will either pack a stale snapshot
>>> from the local repository or fail, because the snapshot is built at a later
>>> time.
>>>
>>>> If you want to iteratively work on it together put it in a github repo.
>>>
>>> If you bear with me, may day-to-day work is with svn only and my learning
>>> curve with git/github is still steep, e.g. I did not know about gists, so I
>>> already learned something new.
>>>
>>> Cheers and thanks for your time,
>>> Jörg
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> A party which is not afraid of letting culture,
> business, and welfare go to ruin completely can
> be omnipotent for a while.
>
>   -- Jakob Burckhardt
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Jason van Zyl <ja...@tesla.io>.
On Jun 21, 2013, at 11:48 PM, Vincent Latombe <vi...@gmail.com> wrote:

> Hello,
> 
> I have a question about the alpha-1 release. I see that Aether has
> been updated to 0.9.0 M2.
> Does it implies that issue MNG-2802 (Concurrent-safe access to local
> Maven repository) is now implemented ?
> 

No, it does not.

> If this is the case, then IMHO this should be mentioned, even
> highlighted in the release notes. I think this kind of improvement is
> very expected for all people doing CI, as this would allow a major
> speed up and reduce storage for local repositories in this kind of
> environment.
> 
> Cheers,
> 
> Vincent
> 
> 
> 2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>> 
>> Hi Jason,
>> 
>> first, thanks that you actually take your time to look into it!
>> 
>> Jason van Zyl wrote:
>> 
>>> I unpacked your example and ran your preparation script and it fails in
>>> 2.2.1 as well:
>>> 
>>> https://gist.github.com/jvanzyl/5824206
>> 
>> The submodules are independent projects, you have to run "clean install".
>> See the following session (I have modified the POMs of the children by
>> adding a "<relativePath/>" element, the original example is now ~2 years
>> old):
>> 
>> https://gist.github.com/joehni/6aa8516bd5408144ec53
>> 
>> Note, that after a successful run with M221, the build with M3x will no
>> longer fail, but pack stale snapshots. To raise an error, you have to clean
>> the repo from snapshots in <repohome>/bugs/maven.
>> 
>>> What's the overall usecase? You have a build with snapshots and you find
>>> you need to go back to a release so you lock down to a previous release
>>> and want to use that?
>> 
>> The final distribution of our product or projects typically consists of
>> hundreds of artifacts, where most of them have individual release cycles. In
>> the HEAD revision those are linked in a nested directory structure using
>> "builder POMs" i.e. POMs that have only modules declared, but get never
>> released themselves (like the POM in the root of the example). The versions
>> of the individual artifact are managed in a shared parent POM. In HEAD those
>> are typically all snapshot versions.
>> 
>> This changes after a major release of the overall product, then all those
>> versions become final, the shared parent is released first followed by all
>> other artifacts in dependency order using this released parent. This works
>> all fine.
>> 
>> Now we get into maintenance mode of that major release. Due to the
>> independence of the artifacts we have to branch only the affected projects
>> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we develop bug
>> fixes for JAR-C and JAR-S. This means we branch the shared parent, set JAR-C
>> and JAR-S to snapshot and also the artifacts that will assemble those to two
>> jars, say WAR-X and DIST-ZIP. Then we create a builder for the maintenance
>> branch that contains those jars, the war and the distribution zip as module.
>> Building this we should get a war that contains JAR-C and JAR-S as snapshot
>> and all the others as release and the distribution contains the affected
>> WAR-X as snapshot and all other stuff as released version - the perfect
>> situation to test the fix.
>> 
>> Unfortunately M3 fails here, because it is under some circumstance not able
>> to calculate the proper build order (maybe it does no longer take attached
>> snapshot artifacts into account ?!?) and will either pack a stale snapshot
>> from the local repository or fail, because the snapshot is built at a later
>> time.
>> 
>>> If you want to iteratively work on it together put it in a github repo.
>> 
>> If you bear with me, may day-to-day work is with svn only and my learning
>> curve with git/github is still steep, e.g. I did not know about gists, so I
>> already learned something new.
>> 
>> Cheers and thanks for your time,
>> Jörg
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.

  -- Jakob Burckhardt






Re: Maven 3.1.0-beta-1

Posted by Vincent Latombe <vi...@gmail.com>.
Hello,

I have a question about the alpha-1 release. I see that Aether has
been updated to 0.9.0 M2.
Does it implies that issue MNG-2802 (Concurrent-safe access to local
Maven repository) is now implemented ?

If this is the case, then IMHO this should be mentioned, even
highlighted in the release notes. I think this kind of improvement is
very expected for all people doing CI, as this would allow a major
speed up and reduce storage for local repositories in this kind of
environment.

Cheers,

Vincent


2013/6/21 Jörg Schaible <Jo...@scalaris.com>
>
> Hi Jason,
>
> first, thanks that you actually take your time to look into it!
>
> Jason van Zyl wrote:
>
> > I unpacked your example and ran your preparation script and it fails in
> > 2.2.1 as well:
> >
> > https://gist.github.com/jvanzyl/5824206
>
> The submodules are independent projects, you have to run "clean install".
> See the following session (I have modified the POMs of the children by
> adding a "<relativePath/>" element, the original example is now ~2 years
> old):
>
> https://gist.github.com/joehni/6aa8516bd5408144ec53
>
> Note, that after a successful run with M221, the build with M3x will no
> longer fail, but pack stale snapshots. To raise an error, you have to clean
> the repo from snapshots in <repohome>/bugs/maven.
>
> > What's the overall usecase? You have a build with snapshots and you find
> > you need to go back to a release so you lock down to a previous release
> > and want to use that?
>
> The final distribution of our product or projects typically consists of
> hundreds of artifacts, where most of them have individual release cycles. In
> the HEAD revision those are linked in a nested directory structure using
> "builder POMs" i.e. POMs that have only modules declared, but get never
> released themselves (like the POM in the root of the example). The versions
> of the individual artifact are managed in a shared parent POM. In HEAD those
> are typically all snapshot versions.
>
> This changes after a major release of the overall product, then all those
> versions become final, the shared parent is released first followed by all
> other artifacts in dependency order using this released parent. This works
> all fine.
>
> Now we get into maintenance mode of that major release. Due to the
> independence of the artifacts we have to branch only the affected projects
> in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we develop bug
> fixes for JAR-C and JAR-S. This means we branch the shared parent, set JAR-C
> and JAR-S to snapshot and also the artifacts that will assemble those to two
> jars, say WAR-X and DIST-ZIP. Then we create a builder for the maintenance
> branch that contains those jars, the war and the distribution zip as module.
> Building this we should get a war that contains JAR-C and JAR-S as snapshot
> and all the others as release and the distribution contains the affected
> WAR-X as snapshot and all other stuff as released version - the perfect
> situation to test the fix.
>
> Unfortunately M3 fails here, because it is under some circumstance not able
> to calculate the proper build order (maybe it does no longer take attached
> snapshot artifacts into account ?!?) and will either pack a stale snapshot
> from the local repository or fail, because the snapshot is built at a later
> time.
>
> > If you want to iteratively work on it together put it in a github repo.
>
> If you bear with me, may day-to-day work is with svn only and my learning
> curve with git/github is still steep, e.g. I did not know about gists, so I
> already learned something new.
>
> Cheers and thanks for your time,
> Jörg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Jason,

first, thanks that you actually take your time to look into it!

Jason van Zyl wrote:

> I unpacked your example and ran your preparation script and it fails in
> 2.2.1 as well:
> 
> https://gist.github.com/jvanzyl/5824206

The submodules are independent projects, you have to run "clean install". 
See the following session (I have modified the POMs of the children by 
adding a "<relativePath/>" element, the original example is now ~2 years 
old):

https://gist.github.com/joehni/6aa8516bd5408144ec53

Note, that after a successful run with M221, the build with M3x will no 
longer fail, but pack stale snapshots. To raise an error, you have to clean 
the repo from snapshots in <repohome>/bugs/maven.

> What's the overall usecase? You have a build with snapshots and you find
> you need to go back to a release so you lock down to a previous release
> and want to use that?

The final distribution of our product or projects typically consists of 
hundreds of artifacts, where most of them have individual release cycles. In 
the HEAD revision those are linked in a nested directory structure using 
"builder POMs" i.e. POMs that have only modules declared, but get never 
released themselves (like the POM in the root of the example). The versions 
of the individual artifact are managed in a shared parent POM. In HEAD those 
are typically all snapshot versions.

This changes after a major release of the overall product, then all those 
versions become final, the shared parent is released first followed by all 
other artifacts in dependency order using this released parent. This works 
all fine.

Now we get into maintenance mode of that major release. Due to the 
independence of the artifacts we have to branch only the affected projects 
in case of bugs. Say we have JAR artifacts JAR-A to JAR-Z and we develop bug 
fixes for JAR-C and JAR-S. This means we branch the shared parent, set JAR-C 
and JAR-S to snapshot and also the artifacts that will assemble those to two 
jars, say WAR-X and DIST-ZIP. Then we create a builder for the maintenance 
branch that contains those jars, the war and the distribution zip as module. 
Building this we should get a war that contains JAR-C and JAR-S as snapshot 
and all the others as release and the distribution contains the affected 
WAR-X as snapshot and all other stuff as released version - the perfect 
situation to test the fix.

Unfortunately M3 fails here, because it is under some circumstance not able 
to calculate the proper build order (maybe it does no longer take attached 
snapshot artifacts into account ?!?) and will either pack a stale snapshot 
from the local repository or fail, because the snapshot is built at a later 
time.

> If you want to iteratively work on it together put it in a github repo.

If you bear with me, may day-to-day work is with svn only and my learning 
curve with git/github is still steep, e.g. I did not know about gists, so I 
already learned something new.

Cheers and thanks for your time,
Jörg



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Jason van Zyl <ja...@tesla.io>.
I unpacked your example and ran your preparation script and it fails in 2.2.1 as well:

https://gist.github.com/jvanzyl/5824206

What's the overall usecase? You have a build with snapshots and you find you need to go back to a release so you lock down to a previous release and want to use that?

If you want to iteratively work on it together put it in a github repo.

On Jun 20, 2013, at 2:45 AM, Jörg Schaible <jo...@scalaris.com> wrote:

> Hi Jason,
> 
> Jason van Zyl wrote:
> 
>> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
>> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
> 
> Since all versions of M30x fail in their core competence to make reliable 
> builds because it uses stale snapshots, it would be fine to have at least a 
> properly working M31x. What I am talking about? See MNG-5207! Reported 
> months ago, a proper IT test bit rots in JIRA and if you search through the 
> archives of this list for the issue, then you'll notice that it has been 
> reported more than once, with promises to look into it. And yes, I have 
> verified that M31a still fails.
> 
> - Jörg
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

Three people can keep a secret provided two of them are dead.

 -- Benjamin Franklin






Re: Maven 3.1.0-beta-1

Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Jason,

Jason van Zyl wrote:

> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.

Since all versions of M30x fail in their core competence to make reliable 
builds because it uses stale snapshots, it would be fine to have at least a 
properly working M31x. What I am talking about? See MNG-5207! Reported 
months ago, a proper IT test bit rots in JIRA and if you search through the 
archives of this list for the issue, then you'll notice that it has been 
reported more than once, with promises to look into it. And yes, I have 
verified that M31a still fails.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Hervé BOUTEMY <he...@free.fr>.
yes, there doesn't seem to be much people reporting any issues.
Do we have any meaning of measuring the use of this new version?

I'm missing time at the moment to work on code.
But I'd like to work on little POM schema additions, like encoding 
configuration: the precise list of additions that can be made without creating 
incompatible changes to users of an artifact built with the new POM version is 
still to be defined

Regards,

Hervé

Le mardi 18 juin 2013 06:56:45 Jason van Zyl a écrit :
> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I plan
> to cut the 3.1.0-beta-1 this weekend if there are no objections.
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> We know what we are, but know not what we may be.
> 
>   -- Shakespeare

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven 3.1.0-beta-1

Posted by Arnaud Héritier <ah...@gmail.com>.
Is there an expert about the // build who could have a look at the last
comment provided by Dimitri :
http://jira.codehaus.org/browse/MNG-4996?focusedCommentId=326816&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-326816
I know him, he'll be happy to help us more to solve such issue but I don't
know who could mentor him

Cheers


On Tue, Jun 18, 2013 at 3:56 PM, Jason van Zyl <ja...@tesla.io> wrote:

> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> We know what we are, but know not what we may be.
>
>   -- Shakespeare
>
>
>
>
>
>


-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: Maven 3.1.0-beta-1

Posted by Mark Derricutt <ma...@talios.com>.
Jason van Zyl wrote:
> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
+1 - have been using it all week with no issues.

One thing I would love to see ( and I should really raise a JIRA for 
this ), when there are dependency range conflicts currently we get:

[ERROR] Failed to execute goal on project smx3.standardreports: Could 
not resolve dependencies for project 
smx3:smx3.standardreports:bundle:3.0.74-SNAPSHOT: Failed to collect 
dependencies for smx3:smx3.standardreports:jar:3.0.74-SNAPSHOT: Could 
not resolve version conflict among [smx3:smx3.spi:jar:[1.6.1,2.0.0), 
smx3:smx3.statistics:jar:[9.2.1,10.0.0) -> 
smx3:smx3.partyresource:jar:9.2.11-SNAPSHOT -> 
smx3:smx3.spi:jar:[2.0.0,3.0.0), smx3:smx3.api:jar:9.1.1 -> 
smx3:smx3.spi:jar:[1.3.9,2.0.0), smx3:smx3.reporting:jar:[9.2.1,10.0.0) 
-> smx3:smx3.mounting:jar:9.2.11-SNAPSHOT -> 
smx3:smx3.spi:jar:[2.0.0,3.0.0), smx3:smx3.reporting:jar:[9.2.1,10.0.0) 
-> smx3:smx3.entitysearch:jar:9.2.11-SNAPSHOT -> 
smx3:smx3.spi:jar:[2.0.0,3.0.0), smx3:smx3.schema:jar:9.2.3 -> 
smx3:smx3.spi:jar:[1.3.9,2.0.0)] -> [Help 1]

which is super super awesome and contains all the information one needs, 
only - it's kinda hard to read since its all on one line.

I find myself doing a simple search/replace on ,\s with ,\n which gives me:

[ERROR] Failed to execute goal on project smx3.standardreports: Could 
not resolve dependencies for project 
smx3:smx3.standardreports:bundle:3.0.74-SNAPSHOT: Failed to collect 
dependencies for smx3:smx3.standardreports:jar:3.0.74-SNAPSHOT: Could 
not resolve version conflict among [smx3:smx3.spi:jar:[1.6.1,2.0.0),
smx3:smx3.statistics:jar:[9.2.1,10.0.0) -> 
smx3:smx3.partyresource:jar:9.2.11-SNAPSHOT -> 
smx3:smx3.spi:jar:[2.0.0,3.0.0),
smx3:smx3.api:jar:9.1.1 -> smx3:smx3.spi:jar:[1.3.9,2.0.0),
smx3:smx3.reporting:jar:[9.2.1,10.0.0) -> 
smx3:smx3.mounting:jar:9.2.11-SNAPSHOT -> smx3:smx3.spi:jar:[2.0.0,3.0.0),
smx3:smx3.reporting:jar:[9.2.1,10.0.0) -> 
smx3:smx3.entitysearch:jar:9.2.11-SNAPSHOT -> 
smx3:smx3.spi:jar:[2.0.0,3.0.0),
smx3:smx3.schema:jar:9.2.3 -> smx3:smx3.spi:jar:[1.3.9,2.0.0)] -> [Help 1]

Which is SOOO much more readable having them on separate lines - some 
colorization in there would also rock.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org