Re: [POLL] Why are you not able to use the most recent maven release?
On Fri, Mar 7, 2008 at 5:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Some time after 2.0.5, Maven seems to have lost the ability to deal > with multiple repositories containing different versions of the same > plugin. > > For example: > * a 'third-party' repository with maven-whatever-plugin version 1.0 final > * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1 This was finally reproduced outside of my work environment (thanks, Marica!): http://jira.codehaus.org/browse/MNG-3560 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
>I'm responsible for the technical architecture of many projects at my >location. One project in particular (still in active development with >code released to production) will likely never upgrade past 2.0.4 >because of the changes to dependency resolution. Although these >changes are a good thing, problems will not show up in a build, but in >the runtime environment; the most problematic ones are class loading >issues with WebSphere, but occasionally I have had to deal with >"invalid class" errors because somehow commons-collections 2.0 made it >into the war when the project was compiled and tested against 3.2. We made a tool in the dependency plugin to help detect and correct these. Even if you aren't upgrading, you might want to run the tool as you might have problems you don't know about. I understood the problem enough to write the tool and was shocked how many issues I had in my own corp builds. >Anyway, I'm rambling. The project does not want to upgrade because >we would likely need to stop all work for at least two days for a >complete system test / regression test / fix pom cycle. After >spending many weeks overall resolving issues that were deemed to be >"maven brain damage" nobody wants the hassle. Not entirely try if you use the tool mentioned above. You will be able to fix your poms before moving over to the next version. That's how I did it with 60+ developer and 100s of modules. >I am having success at convincing newer projects to start out using >2.0.8; so I am wondering how to easily maintain two maven versions for >us developers on the technical architecture team -- is it as simple as >swapping out MAVEN_HOME? And path, yes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
I don't follow...what's the bug here? -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Saturday, March 15, 2008 4:57 PM To: [EMAIL PROTECTED] Cc: Maven Users List Subject: Re: [POLL] Why are you not able to use the most recent maven release? Jack this is a critical point in my 2.0.8 distro located at $M2_HOME/archetype/pom.xml I have this maven2.0 I have the following profile configuration.. http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 ...parentPoms etc.. maven2.0 commons-collections commons-collections 3.2 does this confirm your understanding ? Martin - Original Message - From: "Trevor Torrez" <[EMAIL PROTECTED]> To: "Maven Users List" Sent: Saturday, March 15, 2008 9:10 AM Subject: Re: [POLL] Why are you not able to use the most recent maven release? > I'm responsible for the technical architecture of many projects at my > location. One project in particular (still in active development with > code released to production) will likely never upgrade past 2.0.4 > because of the changes to dependency resolution. Although these > changes are a good thing, problems will not show up in a build, but in > the runtime environment; the most problematic ones are class loading > issues with WebSphere, but occasionally I have had to deal with > "invalid class" errors because somehow commons-collections 2.0 made it > into the war when the project was compiled and tested against 3.2. > > Anyway, I'm rambling. The project does not want to upgrade because > we would likely need to stop all work for at least two days for a > complete system test / regression test / fix pom cycle. After > spending many weeks overall resolving issues that were deemed to be > "maven brain damage" nobody wants the hassle. > > I am having success at convincing newer projects to start out using > 2.0.8; so I am wondering how to easily maintain two maven versions for > us developers on the technical architecture team -- is it as simple as > swapping out MAVEN_HOME? > > Thanks > > -trevor > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
Jack this is a critical point in my 2.0.8 distro located at $M2_HOME/archetype/pom.xml I have this maven2.0 I have the following profile configuration.. http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 ...parentPoms etc.. maven2.0 commons-collections commons-collections 3.2 does this confirm your understanding ? Martin - Original Message - From: "Trevor Torrez" <[EMAIL PROTECTED]> To: "Maven Users List" Sent: Saturday, March 15, 2008 9:10 AM Subject: Re: [POLL] Why are you not able to use the most recent maven release? > I'm responsible for the technical architecture of many projects at my > location. One project in particular (still in active development with > code released to production) will likely never upgrade past 2.0.4 > because of the changes to dependency resolution. Although these > changes are a good thing, problems will not show up in a build, but in > the runtime environment; the most problematic ones are class loading > issues with WebSphere, but occasionally I have had to deal with > "invalid class" errors because somehow commons-collections 2.0 made it > into the war when the project was compiled and tested against 3.2. > > Anyway, I'm rambling. The project does not want to upgrade because > we would likely need to stop all work for at least two days for a > complete system test / regression test / fix pom cycle. After > spending many weeks overall resolving issues that were deemed to be > "maven brain damage" nobody wants the hassle. > > I am having success at convincing newer projects to start out using > 2.0.8; so I am wondering how to easily maintain two maven versions for > us developers on the technical architecture team -- is it as simple as > swapping out MAVEN_HOME? > > Thanks > > -trevor > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
I'm responsible for the technical architecture of many projects at my location. One project in particular (still in active development with code released to production) will likely never upgrade past 2.0.4 because of the changes to dependency resolution. Although these changes are a good thing, problems will not show up in a build, but in the runtime environment; the most problematic ones are class loading issues with WebSphere, but occasionally I have had to deal with "invalid class" errors because somehow commons-collections 2.0 made it into the war when the project was compiled and tested against 3.2. Anyway, I'm rambling. The project does not want to upgrade because we would likely need to stop all work for at least two days for a complete system test / regression test / fix pom cycle. After spending many weeks overall resolving issues that were deemed to be "maven brain damage" nobody wants the hassle. I am having success at convincing newer projects to start out using 2.0.8; so I am wondering how to easily maintain two maven versions for us developers on the technical architecture team -- is it as simple as swapping out MAVEN_HOME? Thanks -trevor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
Hi! On Friday 07 March 2008 Brian E. Fox wrote: > If this is the case for you, please reply and state the version you're > using and why (preferably referring to a Jira). We will use this > information to prioritize issues for 2.0.10 and beyond. We are using maven 2.0.7. I wanted to upgrade to 2.0.8 some time ago but there were problems with the 2.3 surefire plugin at that time that are already resolved now. We currently do not have any issues with 2.0.7, that's why we didn't try to upgrade again. However, I just tested with 2.0.8 and a recent surefire plugin and the build works as expected. regards, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 signature.asc Description: This is a digitally signed message part.
Re: [POLL] Why are you not able to use the most recent maven release?
See http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins and the final post that started that page at http://www.nabble.com/forum/Permalink.jtp?root=7845254&post=7884079&page=y I can't find a JIRA, I would have thought I raised one... Oh well. I never found the time to re-investigate this. On Sat, Mar 8, 2008 at 11:39 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Wendy: What happens in this case? Does it grab the wrong one or just > die? Is there a Jira? > > > -Original Message- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Friday, March 07, 2008 7:22 PM > To: Maven Users List [del] > Some time after 2.0.5, Maven seems to have lost the ability to deal > with multiple repositories containing different versions of the same > plugin. > > For example: > * a 'third-party' repository with maven-whatever-plugin version 1.0 > final > * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1 > > I think someone brought this up on the dev list recently as a problem > when trying to test a staged plugin release-- it would be the same > situation, with the latest release of the plugin in the 'central' repo > and the staged one in some other repo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
>We're currently stuck on 2.0.4 but are starting to plan to upgrade to 2.0.9. >2.1 is not even on the radar yet. Good, be sure to check out your dependencies using the url I previously sent on this thread. 2.0.9 will have some important fixes / enhancements so it should be considered for upgrade. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
On 11/03/2008, Ken Liu <[EMAIL PROTECTED]> wrote: > Until I can figure out a way to get Continuum to > run with different Maven versions, we're stuck with the current one. If you are running Continuum 1.1 you can choose the Maven version to use per project or per group (as well as JDK, etc). If you have any follow up questions on this we can certainly help on [EMAIL PROTECTED] Cheers, Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
I'm sort of in the same boat, but for different reasons. The maven version is considered to be part of the configuration for each project, so projects are tied to whatever version of Maven was used at release time. Upgrades are considered to be changes to the build environment, which are out of scope in certain projects (small patch releases, for example). We play it safe in these cases because changes to Maven versions can cause build-related regressions. We also use Continuum as our CI environment, and Continuum is tied to whatever Maven version the Continuum unix account uses, which means that we are forced to use the same Maven version for all projects in Continuum. Upgrading the maven that Continuum uses forces all projects to upgrade Maven versions. Until I can figure out a way to get Continuum to run with different Maven versions, we're stuck with the current one. Either that, or I get the entire development team to upgrade simultaneously to a new Maven version. (Which might not really be such a big deal, IMO.) We're currently stuck on 2.0.4 but are starting to plan to upgrade to 2.0.9. 2.1 is not even on the radar yet. Ken On 3/7/08, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > We're currently stuck on 2.0.5 - the problem is getting an entire > organization to upgrade. Aside from the, "it works better" response, > typically, there needs to be a financial reason explaining why we are > asking everyone to stop what they are doing and upgrade. > > > > -Original Message- > From: Brian E. Fox [mailto:[EMAIL PROTECTED] > Sent: Friday, March 07, 2008 4:45 PM > To: Maven Users List > Subject: [POLL] Why are you not able to use the most recent maven > release? > > I get the sense that lots of people are using older versions of Maven > due to various regressions. As we get closer to 2.1 alpha, we need to > ensure that we identify the regressions across the 2.0 line so that we > can make sure they are fixed in 2.1 and so that users can upgrade to a > recent 2.0.x before trying out 2.1. > > > > If this is the case for you, please reply and state the version you're > using and why (preferably referring to a Jira). We will use this > information to prioritize issues for 2.0.10 and beyond. > > > > Thanks. > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [POLL] Why are you not able to use the most recent maven release?
2.0.7, with local patches. Because I've tried about 3 times to get someone to apply a fix for MNG-3284 (or tell me if the attached patch won't work because of something non-obvious), and it just never goes anywhere. :-/ On Fri, Mar 7, 2008 at 9:44 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > I get the sense that lots of people are using older versions of Maven > due to various regressions. As we get closer to 2.1 alpha, we need to > ensure that we identify the regressions across the 2.0 line so that we > can make sure they are fixed in 2.1 and so that users can upgrade to a > recent 2.0.x before trying out 2.1. > > > > If this is the case for you, please reply and state the version you're > using and why (preferably referring to a Jira). We will use this > information to prioritize issues for 2.0.10 and beyond. > > > > Thanks. > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
Brian E. Fox wrote: > I get the sense that lots of people are using older versions of Maven > due to various regressions. As we get closer to 2.1 alpha, we need to > ensure that we identify the regressions across the 2.0 line so that we > can make sure they are fixed in 2.1 and so that users can upgrade to a > recent 2.0.x before trying out 2.1. > > > > If this is the case for you, please reply and state the version you're > using and why (preferably referring to a Jira). We will use this > information to prioritize issues for 2.0.10 and beyond. M205: In use M206: Was totally broken for us (main issue was fixed for M207 though). M207+M208: Forgets dependencies under some obscure circumstances (MNG-3259, seems fixed now) M209 SNAPSHOT: Does work, looking forward to a RC. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
Please file a jira and attach your pom (better if you can make it reproducible) -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 9:05 PM To: Maven Users List Subject: Re: [POLL] Why are you not able to use the most recent maven release? here is a blocker with mvn 2.0.8 >mvn -e --debug install [DEBUG] xerces:xercesImpl:jar:2.8.1 [GC [DefNew: 3968K->0K(4032K), 0.0073060 secs] 34845K->31546K(262080K), 0.007430 0 secs] [INFO] Reloading plugin container for: org.apache.axis2:axis2-mar-maven-plugin. The plugin artifact has changed. [GC [DefNew: 3968K->0K(4032K), 0.0091788 secs] 35514K->32406K(262080K), 0.009302 3 secs] [INFO] Reloading plugin container for: org.apache.axis2:axis2-mar-maven-plugin. The plugin artifact has changed. [GC [DefNew: 3960K->0K(4032K), 0.0091827 secs] 36367K->33217K(262080K), 0.009303 7 secs] [INFO] Reloading plugin container for: org.apache.axis2:axis2-mar-maven-plugin. The plugin artifact has changed. [GC [DefNew: 3968K->0K(4032K), 0.0087908 secs] 37185K->34039K(262080K), 0.008909 8 secs] [GC [DefNew: 3968K->0K(4032K), 0.0044061 secs] 38007K->34357K(262080K), 0.004521 0 secs] [GC [DefNew: 3968K->0K(4032K), 0.0081681 secs] 38325K->35118K(262080K), 0.008291 0 secs] [DEBUG] Unable to find the lifecycle component in the extension org.codehaus.plexus.component.repository.exception.ComponentLookupExcept ion: Com ponent descriptor cannot be found in the component repository: org.apache.maven. artifact.handler.ArtifactHandlermar. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:312) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:440) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon tainer.java:390) at org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa ultPluginManager.java:1353) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH andlers(DefaultLifecycleExecutor.java:1181) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De faultLifecycleExecutor.java:178) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:141) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Reloading plugin container for: org.apache.axis2:axis2-mar-maven-plugin. The plugin artifact has changed. [GC [DefNew: 3968K->0K(4032K), 0.0068601 secs] 39086K->35756K(262080K), 0.006984 1 secs] [DEBUG] Unable to find the lifecycle component in the extension org.codehaus.plexus.component.repository.exception.ComponentLookupExcept ion: Com ponent descriptor cannot be found in the component repository: org.apache.maven. artifact.handler.ArtifactHandleraar. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:312) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:440) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon tainer.java:390) at org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa ultPluginManager.java:1353) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH andlers(DefaultLifecycleExecutor.java:1181) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De faultLifecycleExecutor.java:178) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:141) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Dele
Re: [POLL] Why are you not able to use the most recent maven release?
inWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] -
---
[INFO] Building Apache Axis 2.0 - Parent
[INFO]task-segment: [install]
[INFO] -
---
[DEBUG] Skipping disabled repository apache-snapshots
[DEBUG] maven-site-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
latest ve
rsion
org.apache.maven.plugins:maven-site-plugin:pom:LATEST
[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-site-plugi
n:pom:LATEST
[DEBUG] maven-site-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
release v
ersion
org.apache.maven.plugins:maven-site-plugin:pom:RELEASE
//maven-site-plugin is installed in localRepository located at
//${USERPROFILE}\.m2\repository\org\apache\maven\plugins\maven-site-plugin\1
7
//in that folder I see the 1.7 specific files
maven-site-plugin-1.7.jar
maven-site-plugin-1.7.pom
//contents of maven-metadata.xml
org.apache.maven.plugins
maven-site-plugin
1.7
1.7
1.7
20080114041911
//How come mvn 2.08 does'nt see my 1.7 maven-site-plugin and hunts for
LATEST RELEASE versions?
Thanks
M--
- Original Message -
From: "Brian E. Fox" <[EMAIL PROTECTED]>
To: "Maven Users List"
Sent: Friday, March 07, 2008 8:28 PM
Subject: RE: [POLL] Why are you not able to use the most recent maven
release?
I've been working through that list and I grabbed some of the serious
artifact/repo issues as well as the highest voted issues from all groups
for the .10 release. The plan most likely will be to fix the regressions
and the most popular issues for 2.0.x but it is unlikely that all of
those will get fixed; the edge cases and improvement issues will
probably get bumped to 2.1 at some point. The 2.0.x branch should start
to become very refined in scope of issues being fixed once 2.1 is
closing in. Naturally people will still use 2.0.x for sometime so we'll
be supporting it, but splitting the effort will only slow down the
overall progress. (typical release management stuff yada yada)
The moral is to vote for the issues you most want fixed, and call out
loudly regressions and blockers to updating as those are the priority.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Benedict
Sent: Friday, March 07, 2008 8:11 PM
To: Maven Users List
Subject: Re: [POLL] Why are you not able to use the most recent maven
release?
There are about 110 bugs slated in the "2.0.x" release category. As I
watch
2.0.9 and 2.0.10 develop, I notice that issues from "2.0.x" are not
touched.
My recommendation -- and hope -- is that someone could schedule a 2.0.11
and
2.0.12 based on 25 (swag) issues respectively from that big list. Those
are
the issues, it appears, that are long-standing and have been reported
early.
Paul
On Fri, Mar 7, 2008 at 6:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox
<[EMAIL PROTECTED]>
> wrote:
>
> > If this is the case for you, please reply and state the version
you're
> > using and why (preferably referring to a Jira). We will use this
> > information to prioritize issues for 2.0.10 and beyond.
>
> Some time after 2.0.5, Maven seems to have lost the ability to deal
> with multiple repositories containing different versions of the same
> plugin.
>
> For example:
> * a 'third-party' repository with maven-whatever-plugin version 1.0
final
> * a 'sandbox' repository with maven-whatever-plugin version
2.0-alpha-1
>
> I think someone brought this up on the dev list recently as a problem
> when trying to test a staged plugin release-- it would be the same
> situation, with the latest release of the plugin in the 'central' repo
> and the staged one in some other repo.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
I've been working through that list and I grabbed some of the serious artifact/repo issues as well as the highest voted issues from all groups for the .10 release. The plan most likely will be to fix the regressions and the most popular issues for 2.0.x but it is unlikely that all of those will get fixed; the edge cases and improvement issues will probably get bumped to 2.1 at some point. The 2.0.x branch should start to become very refined in scope of issues being fixed once 2.1 is closing in. Naturally people will still use 2.0.x for sometime so we'll be supporting it, but splitting the effort will only slow down the overall progress. (typical release management stuff yada yada) The moral is to vote for the issues you most want fixed, and call out loudly regressions and blockers to updating as those are the priority. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Benedict Sent: Friday, March 07, 2008 8:11 PM To: Maven Users List Subject: Re: [POLL] Why are you not able to use the most recent maven release? There are about 110 bugs slated in the "2.0.x" release category. As I watch 2.0.9 and 2.0.10 develop, I notice that issues from "2.0.x" are not touched. My recommendation -- and hope -- is that someone could schedule a 2.0.11 and 2.0.12 based on 25 (swag) issues respectively from that big list. Those are the issues, it appears, that are long-standing and have been reported early. Paul On Fri, Mar 7, 2008 at 6:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]> > wrote: > > > If this is the case for you, please reply and state the version you're > > using and why (preferably referring to a Jira). We will use this > > information to prioritize issues for 2.0.10 and beyond. > > Some time after 2.0.5, Maven seems to have lost the ability to deal > with multiple repositories containing different versions of the same > plugin. > > For example: > * a 'third-party' repository with maven-whatever-plugin version 1.0 final > * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1 > > I think someone brought this up on the dev list recently as a problem > when trying to test a staged plugin release-- it would be the same > situation, with the latest release of the plugin in the 'central' repo > and the staged one in some other repo. > > -- > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
It's the first I've heard but doesn't mean much. I have tested staged plugins recently (including your staged stage plugin) and didn't see anything. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 8:25 PM To: Maven Users List Subject: Re: [POLL] Why are you not able to use the most recent maven release? On Fri, Mar 7, 2008 at 6:09 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Wendy: What happens in this case? Does it grab the wrong one or just > die? Is there a Jira? Not sure if it's in JIRA, sorry. It does not just pick the wrong one, it dies with an error (and probably with corrupted local metadata.) I briefly tried to reproduce it at home at some point in the past, but wasn't able to (so I didn't open an issue.) It's possible that there's just something wrong in the repos at work, but whatever it is, 2.0.5 can deal with it and 2.0.7 can't. We do have a couple of patches on top of the 2.0.5/2.0.7 tags, so that's another possible culprit if no one else is seeing this. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
Yep, I did that - I personally have build our codeline with 2.0.5 - 8 and most recently, 2.1. The prab is when I upgrade myself and the build cluster, then when someone tries to build locally and they didn't upgrade and I get this angry horde with torches and pitchforks. -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 8:13 PM To: Maven Users List Subject: RE: [POLL] Why are you not able to use the most recent maven release? Ok that's fair. If it ain't broke, don't fix it. Have you tried your builds on newer versions to make sure it would work? There have been some differences between 2.0.5 & 2.0.6 that could require prep work (and you may discover issues you didn't know you had): http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari ng-dependencies.html -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 5:48 PM To: Maven Users List Subject: RE: [POLL] Why are you not able to use the most recent maven release? We're currently stuck on 2.0.5 - the problem is getting an entire organization to upgrade. Aside from the, "it works better" response, typically, there needs to be a financial reason explaining why we are asking everyone to stop what they are doing and upgrade. -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 4:45 PM To: Maven Users List Subject: [POLL] Why are you not able to use the most recent maven release? I get the sense that lots of people are using older versions of Maven due to various regressions. As we get closer to 2.1 alpha, we need to ensure that we identify the regressions across the 2.0 line so that we can make sure they are fixed in 2.1 and so that users can upgrade to a recent 2.0.x before trying out 2.1. If this is the case for you, please reply and state the version you're using and why (preferably referring to a Jira). We will use this information to prioritize issues for 2.0.10 and beyond. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
On Fri, Mar 7, 2008 at 6:09 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Wendy: What happens in this case? Does it grab the wrong one or just > die? Is there a Jira? Not sure if it's in JIRA, sorry. It does not just pick the wrong one, it dies with an error (and probably with corrupted local metadata.) I briefly tried to reproduce it at home at some point in the past, but wasn't able to (so I didn't open an issue.) It's possible that there's just something wrong in the repos at work, but whatever it is, 2.0.5 can deal with it and 2.0.7 can't. We do have a couple of patches on top of the 2.0.5/2.0.7 tags, so that's another possible culprit if no one else is seeing this. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
Ok that's fair. If it ain't broke, don't fix it. Have you tried your builds on newer versions to make sure it would work? There have been some differences between 2.0.5 & 2.0.6 that could require prep work (and you may discover issues you didn't know you had): http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari ng-dependencies.html -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 5:48 PM To: Maven Users List Subject: RE: [POLL] Why are you not able to use the most recent maven release? We're currently stuck on 2.0.5 - the problem is getting an entire organization to upgrade. Aside from the, "it works better" response, typically, there needs to be a financial reason explaining why we are asking everyone to stop what they are doing and upgrade. -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 4:45 PM To: Maven Users List Subject: [POLL] Why are you not able to use the most recent maven release? I get the sense that lots of people are using older versions of Maven due to various regressions. As we get closer to 2.1 alpha, we need to ensure that we identify the regressions across the 2.0 line so that we can make sure they are fixed in 2.1 and so that users can upgrade to a recent 2.0.x before trying out 2.1. If this is the case for you, please reply and state the version you're using and why (preferably referring to a Jira). We will use this information to prioritize issues for 2.0.10 and beyond. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
Wendy: What happens in this case? Does it grab the wrong one or just die? Is there a Jira? -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 7:22 PM To: Maven Users List Subject: Re: [POLL] Why are you not able to use the most recent maven release? On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > If this is the case for you, please reply and state the version you're > using and why (preferably referring to a Jira). We will use this > information to prioritize issues for 2.0.10 and beyond. Some time after 2.0.5, Maven seems to have lost the ability to deal with multiple repositories containing different versions of the same plugin. For example: * a 'third-party' repository with maven-whatever-plugin version 1.0 final * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1 I think someone brought this up on the dev list recently as a problem when trying to test a staged plugin release-- it would be the same situation, with the latest release of the plugin in the 'central' repo and the staged one in some other repo. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
There are about 110 bugs slated in the "2.0.x" release category. As I watch 2.0.9 and 2.0.10 develop, I notice that issues from "2.0.x" are not touched. My recommendation -- and hope -- is that someone could schedule a 2.0.11 and 2.0.12 based on 25 (swag) issues respectively from that big list. Those are the issues, it appears, that are long-standing and have been reported early. Paul On Fri, Mar 7, 2008 at 6:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]> > wrote: > > > If this is the case for you, please reply and state the version you're > > using and why (preferably referring to a Jira). We will use this > > information to prioritize issues for 2.0.10 and beyond. > > Some time after 2.0.5, Maven seems to have lost the ability to deal > with multiple repositories containing different versions of the same > plugin. > > For example: > * a 'third-party' repository with maven-whatever-plugin version 1.0 final > * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1 > > I think someone brought this up on the dev list recently as a problem > when trying to test a staged plugin release-- it would be the same > situation, with the latest release of the plugin in the 'central' repo > and the staged one in some other repo. > > -- > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [POLL] Why are you not able to use the most recent maven release?
On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > If this is the case for you, please reply and state the version you're > using and why (preferably referring to a Jira). We will use this > information to prioritize issues for 2.0.10 and beyond. Some time after 2.0.5, Maven seems to have lost the ability to deal with multiple repositories containing different versions of the same plugin. For example: * a 'third-party' repository with maven-whatever-plugin version 1.0 final * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1 I think someone brought this up on the dev list recently as a problem when trying to test a staged plugin release-- it would be the same situation, with the latest release of the plugin in the 'central' repo and the staged one in some other repo. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Why are you not able to use the most recent maven release?
On Sat, Mar 8, 2008 at 9:18 AM, EJ Ciramella <[EMAIL PROTECTED]> wrote: > We're currently stuck on 2.0.5 - the problem is getting an entire > organization to upgrade. Aside from the, "it works better" response, > typically, there needs to be a financial reason explaining why we are > asking everyone to stop what they are doing and upgrade. You should be ok to mix, as long as you dont get bitten by outstanding bugs. We moved to 2.0.7 to get the proxy:* stuff happening. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Why are you not able to use the most recent maven release?
We're currently stuck on 2.0.5 - the problem is getting an entire organization to upgrade. Aside from the, "it works better" response, typically, there needs to be a financial reason explaining why we are asking everyone to stop what they are doing and upgrade. -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 4:45 PM To: Maven Users List Subject: [POLL] Why are you not able to use the most recent maven release? I get the sense that lots of people are using older versions of Maven due to various regressions. As we get closer to 2.1 alpha, we need to ensure that we identify the regressions across the 2.0 line so that we can make sure they are fixed in 2.1 and so that users can upgrade to a recent 2.0.x before trying out 2.1. If this is the case for you, please reply and state the version you're using and why (preferably referring to a Jira). We will use this information to prioritize issues for 2.0.10 and beyond. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
