Hi,
just an suggestion for a potential fix to
http://jira.codehaus.org/browse/MCOMPILER-80
as maven 2.0.9 fixes the plugin version in super POM, we can consider that
- if maven 2.0.9 + is detected - any version of maven compiler 2.0.2 (the
one set in super-pom) has been set by the user. In such
Arnaud HERITIER wrote:
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them waiting
all our releases for several weeks.
I don't really understand why fixing a project to produce a proper
source bundle
nicolas de loof wrote:
So my idea would be to (pseudo-code) :
if ( mavenSession.getVersion() 2.0.9 source == null)
{
source = 1.5;
}
IMHO, making a default value a function of both the plugin version and
the Maven version introduces unnecessary complexity to the code and
confusion
On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Arnaud HERITIER wrote:
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them
waiting
all our releases for several
Just to bring the thread back up in light of the recent discussions of
plugin releases:
John has taken over the assembly release that contains the fix I put in for
the ASF stuff. I've been travelling a lot the past two weeks and haven't
progressed much on the poms. Tomorrow or monday I should have
2009/6/4 Brian Fox bri...@infinity.nu:
On Thu, Jun 4, 2009 at 9:44 AM, nicolas de loof nico...@apache.org wrote:
Hi,
just an suggestion for a potential fix to
http://jira.codehaus.org/browse/MCOMPILER-80
as maven 2.0.9 fixes the plugin version in super POM, we can consider that
- if maven
Hi everyone,
If you recall, not too long ago I posted a link to the Maven wiki
outlining my plan to revamp the version-expression transformation for
pom.xml files, which was added to Maven in 2.1.0.
After spending quite a bit of time on this issue - more than I'm
comfortable admitting, I
On Fri, Jun 5, 2009 at 7:13 AM, Brian Fox bri...@infinity.nu wrote:
On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Arnaud HERITIER wrote:
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't
On Jun 4, 2009, at 4:19 PM, John Casey wrote:
Hi everyone,
If you recall, not too long ago I posted a link to the Maven wiki
outlining my plan to revamp the version-expression transformation
for pom.xml files, which was added to Maven in 2.1.0.
After spending quite a bit of time on this
I thought we needed to have a fix in the assembly plugin to be able to
release with ASF rules.If we can do it with just some local changes in our
pom, we have to do it.
However I agree with Barry and we cannot loose too many time to do the
release.
Is there someone who can help us to setup the
Seriously just use the assembly plugin to zip up the source folder,
excluding target. There are several examples in the related threads.
On Thu, Jun 4, 2009 at 5:04 PM, Arnaud HERITIER aherit...@gmail.com wrote:
I thought we needed to have a fix in the assembly plugin to be able to
release
Issue Subscription
Filter: Design Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Right, so do we agree to upgrade default-value to 1.5 in a new 2.1 branch of
the compiler plugin (with required warnings in release note) ?
2009/6/5 Olivier Lamy ol...@apache.org
2009/6/4 Brian Fox bri...@infinity.nu:
On Thu, Jun 4, 2009 at 9:44 AM, nicolas de loof nico...@apache.org
wrote:
My understanding of the problems that are being had with the assembly stuff
is around releasing multi-module projects (e.g. surefire, enforcer). If all
you are releasing is a single module (e.g. maven-eclipse-plugin), then
assembly does exactly what you want right now.
The issue that John and
14 matches
Mail list logo
