Seems like this would fail on earlier versions as well?
On 18/03/2009, at 9:50 AM, Arnaud HERITIER wrote:
I reproduced it.The problem seems to be in jetty.
To reproduce : An empty local repo, JDK 1.4, maven 2.1.0-RC3
In archetype/pom.xml you change the maven-parent version to 11
(instead of
On 18/03/2009, at 9:51 AM, Jason van Zyl wrote:
On 17-Mar-09, at 10:10 AM, Brett Porter wrote:
On 18/03/2009, at 2:23 AM, Jason van Zyl wrote:
Why are you changing core code in the RC branch after we have
started the RC cycle?
Can we please leave the code alone in RCs and use the 2.1.x
� wrote:
Timothy Reilly wrote:
Hi Oleg,
I just worked with a company converting 130+ projects from Ant to Maven.
LATEST and RELEASE were invaluable.
I do think there needs to be more thought around when they're allowed. No
artifact's "release" pom should contain SNAPSHOT, LATEST or REL
too often
hence the itch that had me write versions-maven-plugin and the
update-parent goal
On 17/03/2009, Michael McCallum wrote:
> how often do you really change the enterprise pom though?
>
> On Wed, 18 Mar 2009 07:24:25 Timothy Reilly wrote:
>> Hi Oleg,
>>
>> I just worked with a company con
if the release wasn't done, you'll make many users happy doing it
Arnaud
On Tue, Mar 17, 2009 at 11:39 PM, Barrie Treloar wrote:
> How is this coming along?
> I think I am getting some more free time in the coming weeks to help if
> needed.
>
> --
On 17-Mar-09, at 10:10 AM, Brett Porter wrote:
On 18/03/2009, at 2:23 AM, Jason van Zyl wrote:
Why are you changing core code in the RC branch after we have
started the RC cycle?
Can we please leave the code alone in RCs and use the 2.1.x branch
for any non-regression related changes.
I reproduced it.The problem seems to be in jetty.
To reproduce : An empty local repo, JDK 1.4, maven 2.1.0-RC3
In archetype/pom.xml you change the maven-parent version to 11 (instead of
11-SNAPSHOT).
You launch a build
When you'll execute tests in "Building Maven Archetype Common" you'll have a
I'm trying to help the apache portals project set up some root poms.
They are currently using the apache pom version 5 which IIUC deploys
releases and snapshots to the apache nexus instance.
I googled but couldn't find any instructions on how to proceed with
this. I think it would be pret
On 17-Mar-09, at 10:17 AM, Henri Gomez wrote:
2009/3/17 Georgy Bolyuba :
There is a comment [1] by Igor on [2]:
> Henri, Tycho already discovers OSGi dependencies from bundle
manifest.
Does this mean that dependencies can be osgi-bundles? Where can one
find more information about it?
A
On 17-Mar-09, at 10:13 AM, Georgy Bolyuba wrote:
There is a comment [1] by Igor on [2]:
Henri, Tycho already discovers OSGi dependencies from bundle
manifest.
Does this mean that dependencies can be osgi-bundles? Where can one
find more information about it?
All I am able to find on Maven
I tried to build the archetype sub project with jdk 1.4 / 2.1.0 RC3I can try
to reproduce it. It seems its because I didn't have some SNAPSHOT
dependencies in my local repo.
On Tue, Mar 17, 2009 at 11:30 PM, John Casey wrote:
> Funny...I've been building these RC's using JDK 1.4 and Maven 2.0.1
How is this coming along?
I think I am getting some more free time in the coming weeks to help if needed.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Funny...I've been building these RC's using JDK 1.4 and Maven 2.0.10
(except RC1, which used 2.1.0-M1, IIRC)...I'll see whether I can
reproduce the error. Do you have any idea where your error came from?
-john
Arnaud HERITIER wrote:
It seems that we aren't checking for Java version used to la
It seems that we aren't checking for Java version used to launch maven
(>=1.5).I made the error to try to launch a build with the RC3 and Java 1.4
and received a method not found error. I quickly found my error but i'm not
sure everyone will think about this.
Perhaps it could save us time of users'
Timothy Reilly wrote:
> Hi Oleg,
>
> I just worked with a company converting 130+ projects from Ant to Maven.
> LATEST and RELEASE were invaluable.
>
> I do think there needs to be more thought around when they're allowed. No
> artifact's "release" pom should contain SNAPSHOT, LATEST or RELEAS
too often
hence the itch that had me write versions-maven-plugin and the
update-parent goal
On 17/03/2009, Michael McCallum wrote:
> how often do you really change the enterprise pom though?
>
> On Wed, 18 Mar 2009 07:24:25 Timothy Reilly wrote:
>> Hi Oleg,
>>
>> I just worked with a company con
how often do you really change the enterprise pom though?
On Wed, 18 Mar 2009 07:24:25 Timothy Reilly wrote:
> Hi Oleg,
>
> I just worked with a company converting 130+ projects from Ant to Maven.
> LATEST and RELEASE were invaluable.
>
> I do think there needs to be more thought around when
Passed tests on our projects.
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Monday, March 16, 2009 9:51 AM
To: Maven Developers List
Subject: [PLEASE TEST] Maven 2.1.0-RC3
Okay,
It looks like the last known bugs are resolved for 2.1.0. So, let's take
another
Timothy Reilly wrote:
Hi Oleg,
I just worked with a company converting 130+ projects from Ant to Maven. LATEST and RELEASE were invaluable.
I do think there needs to be more thought around when they're allowed. No artifact's "release" pom should contain SNAPSHOT, LATEST or RELEASE anywhere. T
Hi Oleg,
I just worked with a company converting 130+ projects from Ant to Maven. LATEST
and RELEASE were invaluable.
I do think there needs to be more thought around when they're allowed. No
artifact's "release" pom should contain SNAPSHOT, LATEST or RELEASE anywhere.
The later 2 should be
2009/3/17 Georgy Bolyuba :
> There is a comment [1] by Igor on [2]:
>
> > Henri, Tycho already discovers OSGi dependencies from bundle manifest.
>
> Does this mean that dependencies can be osgi-bundles? Where can one
> find more information about it?
>
> All I am able to find on Maven + OSGi is h
There is a comment [1] by Igor on [2]:
> Henri, Tycho already discovers OSGi dependencies from bundle manifest.
Does this mean that dependencies can be osgi-bundles? Where can one
find more information about it?
All I am able to find on Maven + OSGi is how to build osgi-bundle.
Thank you,
Ge
On 18/03/2009, at 2:23 AM, Jason van Zyl wrote:
Why are you changing core code in the RC branch after we have
started the RC cycle?
Can we please leave the code alone in RCs and use the 2.1.x branch
for any non-regression related changes.
See the concurrent threads - the change you quote
I posted a short blog on the subject [http://tinyurl.com/c7m8qv], and in
addition to that - I argue that LATEST and RELEASE are bad. What do you
think?
Extract:
Let me first be clear about virtual versions as a whole: they are an
excellent source of hard-to-find build erro
On 16-Mar-09, at 5:06 PM, Stephen Connolly wrote:
Yeah, I got that, but will it be interpolated...
No. The raw model.
at present by using MXpp3 I can get the raw model.
project.getOriginalModel() gives a kind-of interpolated without
property
evaluation
project.getModel() gives the fin
Why are you changing core code in the RC branch after we have started
the RC cycle?
Can we please leave the code alone in RCs and use the 2.1.x branch for
any non-regression related changes.
On 17-Mar-09, at 4:39 AM, br...@apache.org wrote:
Author: brett
Date: Tue Mar 17 11:39:18 2009
New
Hi Developers
I would like to add some features to org.codehaus.plexus.util.FileUtils
Can I write them using Generics ?
/Anders
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
nice catch. I looked at that plugin descriptor, but missed the different
version...I was looking more for bad xml.
-john
Benjamin Bentmann wrote:
Chris Handy wrote:
I am having an issue where the inclusion of a plugin using maven 2.0.9
works
fine but in maven 2.1.0-RC3 it complains saying it
Hello,
It is the first time I use this mailing list, I just hope it is the right one.
I am facing a transitive dependency management issue since yesterday. I have
checked all the documentation on the Maven web site and found my answer
(http://maven.apache.org/guides/introduction/introduction-to
I've made both these changes - thanks Benjamin!
- Brett
On 17/03/2009, at 9:20 PM, Brett Porter wrote:
On 17/03/2009, at 9:10 PM, Benjamin Bentmann wrote:
For the sake of reduced heap consumption, how about unregistering
the validator right after createChildContainer() returns such that
I'm creating some in-house archectypes.
I've got some questions :
- I need to add extra parameters, ie -DappId and got it resolved in
the generated pom.xml
I do :
mvn archetype:generate -DarchetypeGroupId=org.mycorp.archetypes
-DarchetypeArtifactId=myapp -DarchetypeVersion=1.0-SNAPSHOT
-DgroupI
I'm having issues with releasing (but this is not specific to 2.1.0-RC3
and is reproducible on 2.0.10).
(http://jira.codehaus.org/browse/MRELEASE-406) but I am not sure if it
is a fault in core or the release plug-in.
Basically a forked maven process doesn't inherit env vars.
D:\workspaces\svn_a
On 17/03/2009, at 9:10 PM, Benjamin Bentmann wrote:
For the sake of reduced heap consumption, how about unregistering
the validator right after createChildContainer() returns such that
the validator can be garbage collected?
Imagine a plugin A which depends on another plugin artifact B,
Hi Brett,
Author: brett
Date: Tue Mar 17 02:28:26 2009
New Revision: 755086
URL: http://svn.apache.org/viewvc?rev=755086&view=rev
Log:
[MNG-4091] Validate the plugin descriptors and improve error reporting when
mismatched with artifact
Modified:
maven/components/branches/maven-2.1.0-RC/maven
Works fine for me.
Good job!
- Message d'origine
De : John Casey
À : Maven Developers List
Envoyé le : Lundi, 16 Mars 2009, 17h51mn 16s
Objet : [PLEASE TEST] Maven 2.1.0-RC3
Okay,
It looks like the last known bugs are resolved for 2.1.0. So, let's take
another look things with RC
35 matches
Mail list logo
