I got a strange behaviour :
rollback the release, then i do :
macbook-pro-de-raphael-pieroni:archetype raphaelpieroni$ svn st
macbook-pro-de-raphael-pieroni:archetype raphaelpieroni$ svn up
svn: No such revision 764991
macbook-pro-de-raphael-pieroni:archetype raphaelpieroni$ svn up
At revision 764
Still fails even with subversion 1.5.0
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/raphaelpieroni/Projects/archetype &&
svn --non-interactive commit --file /tmp/maven-scm-966248461.commit
--targets /tmp/maven-scm-20952-targets
[INFO] Working directory: /Users/raphael
Setting the plugin version in pluginmanagement didn't work
I have a wrong version of svn it seems
svn --version
svn, version 1.5.6 (r36142)
I try downgrading to 1.5.0
2009/4/14 Olivier Lamy
> Or you update maven-release-plugin version to 2.0-beta-9 .
>
>
> 2009/4/14 Arnaud HERITIER :
> > Or y
Or you update maven-release-plugin version to 2.0-beta-9 .
2009/4/14 Arnaud HERITIER :
> Or you have to use SVN 1.5.0 or 1.6.0 bianires. No 1.5.x.
> Arnaud
>
> On Tue, Apr 14, 2009 at 11:33 PM, Brian Fox wrote:
>
>> Raphaël Piéroni wrote:
>>
>>> Hi folks,
>>>
>>> I try to prepare the release of
Or you have to use SVN 1.5.0 or 1.6.0 bianires. No 1.5.x.
Arnaud
On Tue, Apr 14, 2009 at 11:33 PM, Brian Fox wrote:
> Raphaël Piéroni wrote:
>
>> Hi folks,
>>
>> I try to prepare the release of the next version of the archetype plugin,
>> but i fail.
>> The release plugin tell me it can't create
Raphaël Piéroni wrote:
Hi folks,
I try to prepare the release of the next version of the archetype plugin,
but i fail.
The release plugin tell me it can't create the tag.
I run mvn release:prepare -DdryRun=true without any problem,
but when i remove the dryRun, i got this exception :
[INFO] Ch
Hi folks,
I try to prepare the release of the next version of the archetype plugin,
but i fail.
The release plugin tell me it can't create the tag.
I run mvn release:prepare -DdryRun=true without any problem,
but when i remove the dryRun, i got this exception :
[INFO] Checking in modified POMs..
Martijn Dashorst wrote:
I think this is a great idea. You could even put the new apache wide
repository and staging area in the release profile. Would make doing a
release a snap IMO.
That part is already in Apache-5 ;-)
---
I think this is a great idea. You could even put the new apache wide
repository and staging area in the release profile. Would make doing a
release a snap IMO.
Martijn
On Tue, Apr 14, 2009 at 9:18 PM, Brian Fox wrote:
> We currently have some expectations about what artifacts are created for
> a
I think it is a fine idea and would serve as a good example of best
practices for other organizations to follow...
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Tue, Apr 14, 2009 at 14:18, Brian Fox wrote:
> We currently have some expectations about what artifacts are created for
> ap
We currently have some expectations about what artifacts are created for
apache builds, such as javadocs and source jars, and specifically
artifact signatures. Currently each project must configure the current
release profile in their own top level pom. This raises the bar of entry
for new proj
Albrecht Militzer wrote:
My maven settings contain my proxy. Since it downloaded some artifacts
before reaching this error, I believe it is setup correctly.
Could you tell me how I can get access to this plugin?
Adding http://repository.apache.org/snapshots/ as a
should do, see [0] for deta
The Maven team is pleased to announce the release of the Maven Patch
Plugin, version 1.1
This plugin is used to apply patches to source files. See the plugin's
site for more details:
http://maven.apache.org/plugins/maven-patch-plugin/
To use the updated plugin in your projects, you need to sp
+1
Benjamin Bentmann wrote:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&styleName=Html&version=14831
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&status=1
Staging re
+1
-Lukas
Benjamin Bentmann wrote:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&styleName=Html&version=14831
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&status=1
Hello,
I am trying to build maven following these instructions:
http://maven.apache.org/guides/development/guide-building-m2.html
The svn checkout completes without error.
Calling maven install results in this:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Apache Maven
[
+1
Vincent
2009/4/13 Benjamin Bentmann :
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&styleName=Html&version=14831
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&st
17 matches
Mail list logo