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
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,
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;
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
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
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
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
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
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
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
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.
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=7845254post=7884079page=y
I can't find a JIRA, I would have thought I raised one... Oh well.
I never found the time to re-investigate
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
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:
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
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
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
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
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):
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
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
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:
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
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
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
25 matches
Mail list logo
