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.. <project xmlns="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";> <modelVersion>4.0.0</modelVersion> ...parentPoms etc.. <profiles> <profile> <id>maven2.0</id //which contains the dependency.. <dependency> <groupId>commons-collections</groupId> <artifactId>commons-collections</artifactId> <version>3.2</version> </dependency> does this confirm your understanding ? Martin ----- Original Message ----- From: "Trevor Torrez" <[EMAIL PROTECTED]> To: "Maven Users List" <[email protected]> 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]
