Another possible solution would be to change the dependency versions in
the pom before deployment to the repository. So when you build
yourproject the pom is updated, maybe in the target directory, to
reflect the dependency versions that were used during the build, and the
imported depMgmt pom
+1
It seems to work fine for me
On 05/14/2013 05:22 PM, Hervé BOUTEMY wrote:
Hi,
We solved 12 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214version=1915
0styleName=Html[1]
There are still a couple of issues left in JIRA:
+1 it looks ok to me.
On 03/11/2013 11:44 AM, John Casey wrote:
Bump...
Has this vote failed, then, or are we saying that all the +1's from the
previous round of voting should be counted here? There is new code in
this vote, so I'm not 100% sure that's a good idea.
I can complete the
Hi,
The vote has passed with the following result :
+1 (binding): Paul Gier, Stephen Connolly, Olivier Lamy, Hervé Boutemy,
Robert Scholte
+1 (non binding): Tony Chemit, Mirko Friedenhagen
I will promote the artifacts to the central repo.
On 11/28/2012 06:26 PM, Paul Gier wrote:
Hi,
We
The Maven team is pleased to announce the release of the Maven Enforcer
Plugin, version 1.2
The enforcer plugin provides goals to control certain environmental
constraints such as Maven version, JDK version and OS family along with
many more standard rules and user created rules.
Hi,
We solved 10 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=18491
There are still a couple of issues left in JIRA:
I realized that I didn't remove the separate manual purge mojo after
merging this feature back in to the main purge mojo. So I will remove
this extra mojo now, and hopefully the release can be re-tagged/staged.
Also, I created MNG-5366 to describe the dependency resolution problem
in Maven
free to explain why I'm confused.
I'll do more diagnosis later today.
Arnaud
On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY
herve.bout...@free.fr
wrote:
Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
I did some more testing, and the tests only seem to fail using
Maven
3.0.4
change anything
but this time, this would be a Maven core bug :)
WDYT?
Regards,
Hervé
Le mercredi 24 octobre 2012 08:56:32 Paul Gier a écrit :
Hi Arnaud,
I should have some time today to try out the shared dependency tree API,
if it doesn't work in Maven 3.0.4 with that, then I'm
, you're doing the harder work :-)
I'll launch the release process today.
I hope to not have too many glitches as I didn't do that for a (too) long
time..
Arnaud
On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier pg...@redhat.com wrote:
Ok, I'm done working on the purge-local-repositories goal
.
Arnaud
On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier pg...@redhat.com wrote:
Sorry about that, looks like two of them are failing on Jenkins also.
I'm not sure why I don't see the failures locally, I tested with Maven
2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
On 10/22
:
As discussed on IRC for now I don't see a better solution.
Someone else has a feedback or some ideas ?
Arnaud
On Mon, Oct 22, 2012 at 6:21 PM, Paul Gier pg...@redhat.com wrote:
I have now split out the manual purge option into a separate mojo, and
added the requiresDependencyResolution
less fun than
here.
Arnaud
On Mon, Oct 22, 2012 at 9:39 PM, Paul Gier pg...@redhat.com wrote:
After this change, I'm still seeing the same failures on Jenkins, but
not seeing them locally :(
I may try the DependencyGraphBuilder as Hervé suggested, but it will
probably take another day
On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier pg...@redhat.com wrote:
Hi Arnaud,
Can you hold off one more day? I have a couple of fixes I want to get
in, and I want to do a bit more testing.
Thanks!
On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
ok thx.
I'll do the release tomorrow
Hi Arnaud,
Can you hold off one more day? I have a couple of fixes I want to get
in, and I want to do a bit more testing.
Thanks!
On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
ok thx.
I'll do the release tomorrow
Arnaud
On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte
+1, and I'm willing to volunteer if you still need more people.
On 09/05/2012 06:04 AM, Olivier Lamy wrote:
Hi,
This vote is to decide moving our source tree currently located in one
svn repository to git (multiple git repositories).
First, we need to have at least 3 volunteers to help on
On 09/11/2012 07:13 AM, Kristian Rosenvold wrote:
But GIT sucks a bit when it comes to projects like maven-shared and
maven-plugins which get released in portions. We already explained that with
long words and we might have found a compromise which doesn't hurt too
badly. But still it has
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, John Casey, Robert Scholte, Hervé Boutemy
+1 (non binding): Mirko Friedenhagen, Tony Chemit
I will promote the artifacts to the central repo.
On 05/08/2012 10:46 PM, Paul Gier wrote:
Hi,
We solved 5 issues
The Maven team is pleased to announce the release of the Maven Enforcer,
version 1.1
This plugin provides various configurable validation rules for Maven builds.
http://maven.apache.org/enforcer/
http://maven.apache.org/plugins/maven-enforcer-plugin/
You should specify the version in your
Hi,
We solved 5 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=17443
There are still a couple of issues left in JIRA:
+1
The new javadoc plugin works fine for me.
On 01/17/2012 02:18 PM, John Casey wrote:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=17354
There are still plenty of issues left in JIRA:
Hi,
The vote has passed with the following result:
+1 (binding): Kristian Rosenvold, Olivier Lamy, Emmanuel Venisse, Herve
Boutemy, Vincent Siveton
+1 (non binding): Tony Chemit, Tamás Cservenák
I will continue the release process.
Thanks!
The Maven team is pleased to announce the release of the Maven Surefire,
version 2.10
This release includes the maven-surefire-plugin, which executes the
unit tests of an application, the maven-surefire-report-plugin, which
parses surefire/failsafe test results and renders them to DOXIA
creating
for shadefire [2], so I
think these changes were at least somwhat intentional.
[1]http://svn.apache.org/viewvc?view=revisionrevision=1144298
[2]http://svn.apache.org/viewvc?view=revisionrevision=1136849
On 09/26/2011 05:26 PM, Paul Gier wrote:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure
private artifact in
the surefire build, basically a shaded previous version of surefire to
run the tests for surefire itself.
Stephen did the site work and I'm sure he can tell us what's up ;)
Kristian
ti., 27.09.2011 kl. 09.12 -0500, skrev Paul Gier:
I noticed some possible problems
artifact in
the surefire build, basically a shaded previous version of surefire to
run the tests for surefire itself.
Stephen did the site work and I'm sure he can tell us what's up ;)
Kristian
ti., 27.09.2011 kl. 09.12 -0500, skrev Paul Gier:
I noticed some possible problems in the staged
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17431
There are still lots of issues left in JIRA:
I'd like to discuss the possibility of Maven automatically looking for a
project specific settings.xml file [1]. The main use case for this is
to eliminate, or at least reduce, the need to add repositories to the
poms. A setting.xml file could simply be added into scm into the root
directory of
hasn't that been the purpose of profiles.xml files back in 2.x before
it was removed for 3.x?
Milos
On Mon, Aug 1, 2011 at 9:00 PM, Paul Gier pg...@redhat.com wrote:
I'd like to discuss the possibility of Maven automatically looking for
a
project specific settings.xml file [1
location on the internet.
http://jira.codehaus.org/browse/MNG-3056
On Mon, Aug 1, 2011 at 3:58 PM, Paul Gier pg...@redhat.com wrote:
Using a project local settings allows you to use the repo during build,
but still have a clean pom in the repo when you release. We've
experienced a lot
settings.xml can include pluginManagement in a profile? I thought you
could only include a few things like repos and properties, at least
that's what the docs say.
http://maven.apache.org/ref/3.0.3/maven-settings/settings.html
On 07/25/2011 06:43 AM, Benson Margulies wrote:
I don't know about
Hi Everyone,
The current behaviour of Maven for a multi-module project is that the
module path will automatically be appended to the end of the scm fields
(connection, url, etc). This has always seemed like a bug to me since
it not what you would want for a real multi-module project. The only
reliably fill in an intelligent value for SCM
information, if it's missing from a POM. That leaves a pretty tedious
state of affairs, though.
On 7/14/11 10:57 AM, Paul Gier wrote:
Hi Everyone,
The current behaviour of Maven for a multi-module project is that the
module path will automatically
of a large multi-module project. For now, I'm getting around
this by just using my own properties instead of the main scm fields.
On 07/14/2011 10:13 AM, Paul Gier wrote:
I think inheriting it unchanged is fine for most multi-module projects,
even using SVN. Thinking in terms of the JBoss AS build
Welcome Robert!
On 07/06/2011 02:40 PM, Mark Struberg wrote:
Hi Maven folks!
The Apache Maven PMC is glad to welcome Robert Scholte as new Apache Maven
Committer!
Most of us know Robert already from his dedicated work on lots of Maven
plugins over at codehaus-mojo, so I guess I don't
. Maybe we should have a similar setup with central?
On 06/22/2011 05:12 PM, Anders Hammar wrote:
Yes, as I said, artifacts at central should never change as it will break
people's builds. I thought that was the policy.
/Anders
On Wed, Jun 22, 2011 at 19:56, Paul Gier pg...@redhat.com wrote
20, 2011 at 19:00, Paul Gier pg...@redhat.com
wrote:
It seems that the artifacts were moved to a different
location:
https://issues.sonatype.org/browse/MVNCENTRAL-71
On 06/20/2011 10:41 AM, Paul Gier wrote:
The artifacts for javax.servlet:jstl:1.2 seem to
have disappeared from
central [1
The artifacts for javax.servlet:jstl:1.2 seem to have disappeared from
central [1]. They still appear in the Sonatype search [2]. Does anyone
know what happened to these files? Were they removed because of a bad
license or something?
[1]http://repo1.maven.org/maven2/javax/servlet/jstl/
It seems that the artifacts were moved to a different location:
https://issues.sonatype.org/browse/MVNCENTRAL-71
On 06/20/2011 10:41 AM, Paul Gier wrote:
The artifacts for javax.servlet:jstl:1.2 seem to have disappeared from
central [1]. They still appear in the Sonatype search [2]. Does
On 05/27/2011 11:02 AM, Paul Gier wrote:
Maven 3 currently treats unrecognised version qualifiers as newer
releases than the GA release. For example:
1.0 is older than 1.0-xyz
It also looks like this was reversed at some point, since there is a
test case commented out on line 117
Maven 3 currently treats unrecognised version qualifiers as newer
releases than the GA release. For example:
1.0 is older than 1.0-xyz
It also looks like this was reversed at some point, since there is a
test case commented out on line 117 that expects the opposite behaviour
[1]. So is the
jdca...@commonjava.org
Subject: Re: Handling of unrecognised version qualifiers
To: Maven Developers List dev@maven.apache.org
Date: Friday, May 27, 2011, 4:31 PM
On 5/27/11 12:02 PM, Paul Gier wrote:
Maven 3 currently treats unrecognised version
qualifiers as newer
releases than the GA
Hi,
The vote has passed with the following result:
+1 (binding): Emmanuel Venisse, Lukas Theussl, Olivier Lamy, Stephen
Connolly, Kristian Rosenvold, Hervé Boutemy
+1 (non-binding): Tony Chemit
I will promote the artifacts to the central repo.
Thanks
On 05/09/2011 03:59 PM, Paul Gier wrote
The Maven team is pleased to announce the release of the Maven Deploy
Plugin, version 2.6
This plugin allows artifacts to be deployed to a Maven repository. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-deploy-plugin/
You should specify the version in your
Hi,
This is a minor enhancement/bug fix release.
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11131styleName=Htmlversion=16083
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11131status=1
There seems to be a regression in the jboss as build [1]. Not sure what
the cause is, but the new Maven RC seems to have a problem during
execution of our custom surefire impl. I created a jira issue [2] to
track this and attached the relevant part of the build log.
+1
On 01/26/2011 12:30 AM, Olivier Lamy wrote:
Hello,
I propose Evgeny Mandrikov as a new committer.
He as done a lot of patches for Maven SCM, he is a Mojo and Sonar
contributor @codehaus.
Vote is open for 72H.
Here my +1.
Thanks,
--
Olivier Lamy
http://twitter.com/olamy
I would even go further and say that if it's not a vote, a +1 or I
agree by themselves don't really add to the conversation. In general,
no response means either I agree or I don't care enough to respond,
so do what you want. If a proposal or discussion item is put forward,
it's normally safe to
Works for me building JBoss AS and some other projects.
On 01/05/2011 03:20 PM, Benjamin Bentmann wrote:
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential
I also ran into this problem. I updated the enforcer to refer to
maven-parent version 18-SNAPSHOT until maven-parent version 17 is released.
http://svn.apache.org/viewvc?view=revisionrevision=1032452
On 11/05/2010 03:01 AM, Matthias Wessendorf wrote:
Hi,
I noticed that our (MyFaces) hudson
I noticed that many of the org/bouncycastle POMs do not have the
appropriate checksums in central [1]. What's the appropriate way to
handle this? Does anyone have a script that can genarate the missing ones?
http://repo2.maven.org/maven2/org/bouncycastle/bcprov-jdk15/1.43/
Thanks!
On 10/09/2010 11:05 AM, Benjamin Bentmann wrote:
Paul Gier wrote:
Staging site:
http://maven.apache.org/plugins/maven-antrun-plugin-1.6/
Hm, both this staged site and the one from the 1.5 release are missing
the menu Project Documentation in the left nav bar of the index page.
This menu
Hi,
The vote has passed with the following result:
+1 (binding): Paul Gier, Vincent Siveton, Olivier Lamy, Benjamin
Bentmann, Hervé Boutemy
I will promote the artifacts to the central repository and continue with
the release.
On 10/07/2010 03:32 PM, Paul Gier wrote:
Hi,
We solved 4 issues
The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.6
This plugin provides the ability to run Ant tasks in a Maven build. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125version=16742
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11125status=1
Staging repo:
On 10/04/2010 05:45 PM, Benjamin Bentmann wrote:
Hi Paul,
Author: pgier
Date: Mon Oct 4 22:22:30 2010
New Revision: 1004461
URL: http://svn.apache.org/viewvc?rev=1004461view=rev
Log:
[MANTRUN-155] Set encoding for generated Ant build. Patch from Anders
Hammar with some minor changes.
Hi,
The vote has passed with the following result:
+1 (binding): Paul Gier, Arnaud Héritier, Benjamin Bentmann, Emmanuel
Venisse
I will promote the artifacts to the central repository and continue with
the release.
On 09/14/2010 01:19 PM, Paul Gier wrote:
Hi,
We solved 9 issues:
http
The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.5
This plugin allows Ant tasks to be run within a Maven build. See the
plugin's site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your project's
+1
Seems to work fine for me.
On 09/15/2010 03:34 PM, Benjamin Bentmann wrote:
Hi,
in preparation for the release of Apache Maven 3.0, the Maven team is
seeking your help to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test
On 09/14/2010 05:03 PM, Benjamin Bentmann wrote:
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-023/
Staging site:
http://maven.apache.org/plugins/maven-antrun-plugin-1.5/
+1, although it's unfortunate that the example POM snippets on the site
On 09/15/2010 12:37 PM, Benjamin Bentmann wrote:
Paul Gier wrote:
I will try to do a 1.5.1 release next week with the site updates.
Well, I won't stop you from going all fancy and do another release just
for a site update. But if you just tweaked your local copy before
deploying the 1.5
On 09/15/2010 12:49 PM, Paul Gier wrote:
On 09/15/2010 12:37 PM, Benjamin Bentmann wrote:
Paul Gier wrote:
I will try to do a 1.5.1 release next week with the site updates.
Well, I won't stop you from going all fancy and do another release just
for a site update. But if you just tweaked
Hi,
We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125version=16504
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11125status=1
Staging repo:
Sorry, for the late response. I'm running into a few issues building
the JBoss App server with beta-3. I'm currently trying to narrow down
the issues enough to create small test projects/test cases.
The issues seem to be related to very specific edge cases, so I don't
think they are things to
I'd like to get out the next release of surefire and related
plugins/components, and just wanted to check on the status of the
remaining open issues.
Stephen, is the refactoring work from SUREFIRE-592 in a stable state?
The remaining issues look like they can be pushed to a future release.
In our multi-module project (JBoss AS) we have a module that doesn't
have any main sources. It just has test sources and surefire runs these
tests. This module uses jar packaging so that we get the test phases
of the lifecycle. This means that an empty main jar is created and
deployed to the
Seems to work ok for me.
+1
On 07/19/2010 03:50 PM, Hervé BOUTEMY wrote:
Hi,
We solved 14 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=16024styleName=HtmlprojectId=11533
There are still a couple of issues left in JIRA:
Hi,
The vote has passed with the following results:
+1 (binding): Paul Gier, Arnaud Héritier, Benjamin Bentmann
+1 (non-binding): Stephen Connolly, Paul Merlin
I will promote the artifacts to the central repository and continue with the
release.
Paul Gier wrote:
Hi,
We solved 14 issues
The Maven team is pleased to announce the release of the Maven Antrun Plugin,
version 1.4
This plugin allows Ant tasks to be run inside a Maven build. See the plugin's
site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your project's
Benjamin Bentmann wrote:
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-013/
-1
The implementation for MANTRUN-100 has two flaws:
if ( classifier == null )
{
mavenProject.setFile( file );
}
else
{
ArtifactHandler
You're right, I will cancel and restart the vote.
Arnaud Héritier wrote:
I think you should have restart another vote.
+1 for it.
On May 25, 2010, at 6:46 PM, Paul Gier wrote:
Benjamin Bentmann wrote:
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories
Due to the issues Bejamin found, I restarted the release process, so this vote
is canceled.
Paul Gier wrote:
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125version=14641
There are still a couple of issues left in JIRA:
http://jira.codehaus.org
Hi,
We solved 14 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125version=14641
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11125status=1
Staging repo:
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125version=14641
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11125status=1
Staging repo:
?
On May 19, 2010, at 7:27 PM, Paul Gier wrote:
Yeah, I agree we should just change the pom version to 1.4-SNAPSHOT, and
probably remove 1.3.1 from jira. I made some significant changes so that's
why
I started putting issues in the 1.4 bucket.
Arnaud Héritier wrote:
yes and we should update
Yeah, I agree we should just change the pom version to 1.4-SNAPSHOT, and
probably remove 1.3.1 from jira. I made some significant changes so that's why
I started putting issues in the 1.4 bucket.
Arnaud Héritier wrote:
yes and we should update the pom.
I'll wait paul's feedback about it to
Benjamin Bentmann wrote:
Hi Paul,
Author: pgier
Date: Thu May 13 14:39:11 2010
New Revision: 943900
URL: http://svn.apache.org/viewvc?rev=943900view=rev
Log:
[SUREFIRE-598] Removing classpath elements should come after the
classes/test-classes config so that they are not re-added to the
Benjamin Bentmann wrote:
Hi,
considering the recent fixes to checksums for stuff in central, I was
wondering what's the overall state of (existing) checksums on central
these days?
Assuming checksums are correct where present, this should put us in a
good position to introduce a new
Jason van Zyl wrote:
On May 3, 2010, at 12:10 PM, Benjamin Bentmann wrote:
Hi,
somehow related to my previous question about the checksums, what are our
chances to automatically detect and fix bad maven-metadata.xml's deployed to
Central like seen in [0]?
While the content of the
would not
affect builds.
Brian Fox wrote:
Possibly if we introduce a pom that has the exact internal model maven
generates when it can't find one. This could cause some issues for
people who have their own versions of those poms.
On Mon, May 3, 2010 at 2:05 PM, Paul Gier pg...@redhat.com wrote
out? I
think this would solve the main visibility problem without affecting
runtime.
[1]
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html#ex-maven-nexus-simple
On Mon, Apr 26, 2010 at 6:41 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Paul Gier
Benjamin Bentmann wrote:
Paul Gier wrote:
Would there be any problems if the central repo definition was moved
out of the
Maven internals and into the default settings.xml [1]?
I assume you refer to the global settings file shipped inside the Maven
installation directory. The one issue I
-simple
On Mon, Apr 26, 2010 at 6:41 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Paul Gier wrote:
Would there be any problems if the central repo definition was
moved out of the Maven internals and into the default
settings.xml
[1]?
I assume you refer to the global settings file
out? I
think this would solve the main visibility problem without
affecting
runtime.
[1]
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single
-
group.html#ex-maven-nexus-simple
On Mon, Apr 26, 2010 at 6:41 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Paul Gier
Brian Fox wrote:
2010/4/27 Arnaud Héritier aherit...@gmail.com:
It could be better but far from perfect. Few users are reading this file and
are using it to create their own.
I think they are often copying it from the page you pointed.
There are several annoying things about settings from my
Hi Everyone,
The current behaviour in Maven is that the central repository is built into the
code, and it's there unless you hack your settings.xml to disable it. This can
be a bit confusing when trying to configure your settings for a repository
manager. And it's not immediately clear what
Hi Everyone,
I put a proposal on the wiki about improving integration with Ant [1]. The idea
is to gradually merge the Ant tasks and the antrun plugin so that they use the
same API, but I'm not sure how practical it is at this point. Any feedback is
appreciated!
It seems that the copyFileIfModified implementation should be changed. Since
currently it only checks if the source timestamp is newer. Maybe this should be
changed to check for the timestamps not equal (and maybe size not equal also)
instead of just a newer timestamp. That would allow the
The Maven team is pleased to announce the release of the Maven Ant Tasks,
version 2.1.0
The Maven Ant Tasks allow several features of Maven to be used in an Ant build.
This includes dependency management, reading and writing pom files, and
deployment to a Maven repository. More information
CC to the PMC list.
Paul Gier wrote:
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Hervé Boutemy
+1 (non-binding): Paul Gier, Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Paul
The Maven Ant Tasks 2.1.0 have been released.
Can this be added to the next board report please?
Thanks!
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Hervé Boutemy
+1 (non-binding): Paul Gier, Stephen Connolly
I will promote the artifacts to the central repository and continue with the
release.
Paul Gier wrote:
Hi,
I believe it's time
, or use the apache proxy to view the updated one before the refresh.
Benjamin Bentmann wrote:
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-033/
+1
Staging site (need to sync):
http://maven.apache.org/ant-tasks-2.1.0/
Some minor things
Hi,
I believe it's time for the next release of the Maven Ant Tasks. This release
has several enhancements and bug fixes and the dependencies on the core maven
libraries have been updated to version 2.2.1.
I also created a download page as part of the Ant tasks site. This will allow
the
I wonder if we really need a full vote for every alpha. Especially if this is
going to happen every two weeks. Why not just vote for a 2 week alpha release
schedule and then don't do another vote until it's time for beta 1?
Benjamin Bentmann wrote:
Hi,
We solved some more issues:
Brett Porter wrote:
On 21/11/2009, at 8:53 AM, Wendy Smoak wrote:
On Fri, Nov 20, 2009 at 2:46 PM, Michael sg...@gmx.net wrote:
Brian Fox schrieb:
oh wait oh wait, but i've got 15 things.
Which are?
He's kidding. :) It seems like every time someone tries to release
something around
+1
I tested it on a few projects and in general it seems to be working well.
I ran into a problem resolving local snapshots with classifiers after I had just
installed them which appears to be related to an existing problem ni 2.x [1].
But I had trouble reliably reproducing the without messing
I really think it should not be allowed, since it makes the builds less
predictable/reproduceable/secure. Most people I've talked to think it's a bug
when they first see it happening because they are trying to figure out why Maven
is downloading files from a random location on the Internet.
Stephen Connolly wrote:
2009/10/16 Peter Janes maven.apache@peterjanes.ca
On 15/10/09 05:45 AM, Stephen Connolly wrote:
These are very dangerous versions to suggest use of.
...but there *are* use cases for them.
When your use case results in a completely unpredictable build... no
growing up ;-)
-Stephen
Sent from my [rhymes with tryPod] ;-)
On 1 Oct 2009, at 18:39, Paul Gier pg...@redhat.com wrote:
What about creating a new legacy repository for deprecated artifacts?
Stuff that we don't want in the main repository could be moved to a
new legacy repo. This way we
1 - 100 of 246 matches
Mail list logo
