+1
2008/11/26 Arnaud HERITIER <[EMAIL PROTECTED]>
> Hi team,
>
> We upgraded several plugins and updated some settings since version 9.
> In the logic to release often I propose to release the version 10.
> Changes are :
>
> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?view=diff&
+1
On 11/25/08 6:43 PM, "Arnaud HERITIER" <[EMAIL PROTECTED]> wrote:
> Hi team,
>
> We upgraded several plugins and updated some settings since version 9.
> In the logic to release often I propose to release the version 10.
> Changes are :
> http://svn.apache.org/viewvc/maven/pom/trunk/ma
Hi team,
We upgraded several plugins and updated some settings since version 9.
In the logic to release often I propose to release the version 10.
Changes are :
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?view=diff&r1=693260&r2=720642&diff_format=h
The pom is staged at:
http
it's nor so simple when you add repo1 into the mix. you would need to
separate repositories by model version (again) or using repo1 would
become a crapshoot (oh look spring have a new version, my version
range will pick that up... but now it won't build because of a pom
parse error. this bu
Or they'll against burn maven ...
Arnaud
On Wed, Nov 26, 2008 at 12:08 AM, Paul Benedict <[EMAIL PROTECTED]>wrote:
> Arnaud, that is why I said let the free market decide. Why should we
> care if someone only wants to adopt a 4.0+ format? If their adoption
> doesn't happen because not enough use
Arnaud, that is why I said let the free market decide. Why should we
care if someone only wants to adopt a 4.0+ format? If their adoption
doesn't happen because not enough users have it, it's incentive for
them to make a better decision.
Paul
On Tue, Nov 25, 2008 at 4:59 PM, Arnaud HERITIER <[EMA
Thus when spring, hibernate, whatever will decide to publish their poms in a
4.0.0+ format projects which will want to use those new version will have to
upgrade maven too. I think that in many corporate environment their managers
will just say ... no (too risky, expensive, ..). And those framework
I just don't see the big deal with forcing users to upgrade Maven if
they want to use a newer POM version. It will be up to the publishers
to decide whether they want 4.0, 4.1, or both formats in the
repository. Let the free market decide what should be supported.
Paul
---
Barrie Treloar wrote:
On Wed, Nov 26, 2008 at 2:49 AM, Benjamin Bentmann
<[EMAIL PROTECTED]> wrote:
+request.setLocalRepositoryPath( new File(
"/Users/jvanzyl/.m2/repository" ) );
This path might be troublesome for others...
Hahahaha.
Only for those that aren't jason clones :)
Hm,
On Wed, Nov 26, 2008 at 2:49 AM, Benjamin Bentmann
<[EMAIL PROTECTED]> wrote:
>> +request.setLocalRepositoryPath( new File(
>> "/Users/jvanzyl/.m2/repository" ) );
>
> This path might be troublesome for others...
Hahahaha.
Only for those that aren't jason clones :)
---
jvanzyl wrote:
Author: jvanzyl
Date: Tue Nov 25 08:13:29 2008
New Revision: 720525
URL: http://svn.apache.org/viewvc?rev=720525&view=rev
Log:
o adding missing model extensions i added
Added:
maven/components/trunk/maven-core/src/main/java/org/apache/maven/listeners/DefaultMavenModelEventP
Ok. I keep the plugin and the manager together but I use everywhere the
version of the plugin.
Arnaud
On Tue, Nov 25, 2008 at 12:42 AM, Jason van Zyl <[EMAIL PROTECTED]>wrote:
> On 24-Nov-08, at 1:04 PM, Arnaud HERITIER wrote:
>
> Why didn't we store the maven-release-manager under shared and t
CI.sonatype.org is mostly deprecated now except for tycho and m2e.
Everything else is live on the grid (grid.sonatype.org/ci) but the
notifications weren't turned on yet. We can do that today now that the
builds are working.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
I didn't look to which list it was send. I thought it was a mail to
the user mailing list. (Where it should belong. :) )
Just close the issue.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Tue, Nov 25, 2008 at 3:52 PM, Nick Stolwijk <[EMA
> However all these artifacts are only really needed when releasing, ie when
> calling the deploy phase.
If you change this to:
> However all these artifacts are only really needed when releasing, ie when
> calling the release plugin.
The release plugin uses a release profile, thus you can bin
jvanzyl wrote:
Author: jvanzyl
Date: Mon Nov 24 23:11:35 2008
New Revision: 720432
URL: http://svn.apache.org/viewvc?rev=720432&view=rev
Log:
o primarily refactoring in part for the preparation making room for mercury and
processing events from maven-shared-model
o add plexus component descrip
Hi Thierry,
you'll probably have more help in the dev list.
cheers
Arnaud
On Wed, Nov 19, 2008 at 1:33 PM, Thierry Boileau <
[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I would like to know if there is an official documentation about the format
> of the maven repositories, especially (and alm
The Maven team is pleased to announce the release of the Maven Changes
Plugin, version 2.1.
http://maven.apache.org/plugins/maven-changes-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-changes-plugin
2.1
Release Notes - Maven 2
I agree, I would like to have this supported easily in repository managers.
It's already available in Nexus Pro, and I'll think it'll be available in
archiva in few monthes (I just opened the issue :
http://jira.codehaus.org/browse/MRM-1021).
In the meantime, I'll try to develop this feature. I th
19 matches
Mail list logo
