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 c
+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=11214&version=1915
> 0&styleName=Html[1]
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secu
+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 t
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.
http://maven.ap
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,
>
Hi,
We solved 10 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=18491
There are still a couple of issues left in JIRA:
https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MENFORCER+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=
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 3.0.4,
y-p version), this cache should be avoided but I tried and it didn't
> 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,
>
>>>>> willing to help fix this up, but I;m not following the logic of a
>>>>> release. Feel free to explain why I'm confused.
>>>>
>>>> I'll do more diagnosis later today.
>>>>
>>>>>
>>>>>
&g
other
> side of the planet where they have some rules about internet less fun than
> here.
>
> Arnaud
>
> On Mon, Oct 22, 2012 at 9:39 PM, Paul Gier wrote:
>
>> After this change, I'm still seeing the same failures on Jenkins, but
>> not seeing them locally :(
&
> 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 wrote:
>
>> I have now split out the manual purge option into a separate mojo, and
>> added
e ok with Maven 2 but not Maven 3 on Jenkins.
>
> Arnaud
>
> On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier 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 wi
éritier wrote:
>
>> no problem, 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
week
>
> Cheers,
>
> Arnaud
>
> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier 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!
>&g
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 wrote:
>
>
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 i
+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
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 projec
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
Hi,
We solved 5 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=17443
There are still a couple of issues left in JIRA:
https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MENFORCER+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=h
+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=11138&version=17354
>
>
> There are still plenty of issues left in JIRA:
>
> http://jira.codehaus.org/secure/Iss
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 t
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!
--
tors.
> [INFO]
>
>
> And that builds the site correctly for me.
>
> Were you following the instructions for generating the site:
> http://maven.apache.org/developers/release/maven-shared-release.html#Staging_the_latest_documentation
>
> or did you do mvn site:site in p
entirely 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
d for shadefire [2], so I
think these changes were at least somwhat intentional.
[1]http://svn.apache.org/viewvc?view=revision&revision=1144298
[2]http://svn.apache.org/viewvc?view=revision&revision=1136849
On 09/26/2011 05:26 PM, Paul Gier wrote:
> Hi,
>
> We solved 8 issues:
>
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=17431
There are still lots of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated
e heard a lot of complaints from others when their build starts
downloading stuff from some seemingly random location on the internet.
http://jira.codehaus.org/browse/MNG-3056
>
> On Mon, Aug 1, 2011 at 3:58 PM, Paul Gier wrote:
>> Using a project local settings allows you to use the re
Objet : Re: [DISCUSS] Project local setting.xml
>>
>> 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 wrote:
>>> I'd like to di
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 t
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
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 th
t; I'm not sure Maven can 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
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
ca
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'
work ok for us. 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, 201
entral... This could
>> break people's builds.
>>
>> /Anders
>>
>> On Mon, Jun 20, 2011 at 19:00, Paul Gier
>> wrote:
>>
>>> It seems that the artifacts were moved to a different
>> location:
>>> https://issues.sonatype.org/
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].
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/
[2]http
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 comm
in mvn3.
>
> LieGrue,
> strub
>
> --- On Fri, 5/27/11, John Casey wrote:
>
>> From: John Casey
>> Subject: Re: Handling of unrecognised version qualifiers
>> To: "Maven Developers List"
>> Date: Friday, May 27, 2011, 4:31 PM
>>
>
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 curr
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 proje
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
Hi,
This is a minor enhancement/bug fix release.
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11131&styleName=Html&version=16083
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&status=1
S
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]https://github.com/jbossas
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 sa
+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/ol
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 poten
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=revision&revision=1032452
On 11/05/2010 03:01 AM, Matthias Wessendorf wrote:
> Hi,
>
> I noticed that our (MyFaces) huds
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!
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 proj
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
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"
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&version=16742
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11125&status=1
Staging repo:
https://repository.apache.org/content/repositori
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=1004461&view=rev
>> Log:
>> [MANTRUN-155] Set encoding for generated Ant build. Patch from Anders
>> Hammar with so
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 p
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
+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/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 rele
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 loc
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&#
Hi,
We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&version=16504
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11125&status=1
Staging repo:
https://repository.apache.org/content/repositori
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 ho
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 r
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=16024&styleName=Html&projectId=11533
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNav
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 p
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
Hi,
We solved 14 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&version=14641
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11125&status=1
Staging repo:
https://repository.apache.org/content/repositor
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=11125&version=14641
>
> There are still a couple of issue
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:
>>>
>>&
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 )
> {
> ma
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&version=14641
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11125&status=1
Staging repo:
https://repository.apache.org/content/repositor
> postpone them ?
>
>
> 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 is
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 kn
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=943900&view=rev
>> Log:
>> [SUREFIRE-598] Removing classpath elements should come after the
>> classes/test-classes config so that they are n
those 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, P
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 con
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 n
Brian Fox wrote:
> 2010/4/27 Arnaud Héritier :
>> 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 point of vi
om the page you pointed.
>>>>>> There are several annoying things about settings from my
>>>>> point of view
>>>>>> but we won't be able to change before a 3.x :
>>>>>> - We cannot use properties in mirror url (if we want to
>>&
t;> Software Factory Manager
>>>> eXo platform - http://www.exoplatform.com
>>>> ---
>>>> http://www.aheritier.net
>>>>
>>>>
>>>> On Tue, Apr 27, 2010 at 2:16 AM, Brian Fox
>>> wrote:
>>>>> I assume y
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
at into the default settings.xml commented 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:
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 orde
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!
[1]http://cwiki.apache.org/
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 op
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
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 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 i
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
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. The
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 An
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:
http://jir
Brett Porter wrote:
On 21/11/2009, at 8:53 AM, Wendy Smoak wrote:
On Fri, Nov 20, 2009 at 2:46 PM, Michael 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 here, there is a
+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.
T
Stephen Connolly wrote:
2009/10/16 Peter Janes
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 thank
you.
For dependencies, use
Brian Fox wrote:
On Fri, Oct 2, 2009 at 5:57 AM, Paul Gier wrote:
Why would everyone need to use both repos? If the legacy repository is done
correctly, the vast majority of users would never need to hit it, or even
know about it at all.
Note that this idea is different than creating a new
1 - 100 of 251 matches
Mail list logo
