You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Todd Thiessen <th...@nortel.com> on 2009/04/02 23:50:14 UTC
Using release plugin to build scm project
I made a change to the scm project to fix a bug that was bugging me.
Built the 1.3-SNAPSHOT version of the latest SCM plugin, tested it, and
it works fine.
Now I want to do a formal release of my own personalized version of the
project.
The release:prepare fails because of missing dependencies between
modules. The only solution I know of is to add the install goal to the
preperationGoals configuration. But I am sure Oliver didn't have to do
this when he cut the latest release of this project not too long ago (or
maybe he did ;-)).
I just don't know what it is about the release plugin which causes it to
fail. Individuals on this list have made clear claims that you should
NOT have to do an install when you have module dependencies. Any
thoughts or discussion here would be very much appreciated.
The build fails on the maven-scm-plugin project (which is a module of
the scm project itself. Here is a snippet.
[INFO] [INFO]
------------------------------------------------------------------
------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
------------------------------------------------------------------
------
[INFO] [INFO] Failed to resolve artifact.
[INFO]
[INFO] Missing:
[INFO] ----------
[INFO] 1)
org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nortel-1
[INFO] Path to dependency:
[INFO] 1)
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-no
rtel-1
[INFO] 2)
org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nor
tel-1
[INFO]
[INFO] ----------
[INFO] 1 required artifact is missing.
[INFO]
[INFO] for artifact:
[INFO]
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-nortel-1
[INFO]
[INFO] from the specified remote repositories:
[INFO] nexus (http://nexus.norforge.nortel.com/content/groups/public)
---
Todd Thiessen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Using release plugin to build scm project
Posted by "David C. Hicks" <dh...@i-hicks.org>.
Check the archives over the last month and you'll find plenty of
discussion on this subject. :-)
My own solution was to set my preparationGoals="clean install"
Todd Thiessen wrote:
> I made a change to the scm project to fix a bug that was bugging me.
> Built the 1.3-SNAPSHOT version of the latest SCM plugin, tested it, and
> it works fine.
>
> Now I want to do a formal release of my own personalized version of the
> project.
>
> The release:prepare fails because of missing dependencies between
> modules. The only solution I know of is to add the install goal to the
> preperationGoals configuration. But I am sure Oliver didn't have to do
> this when he cut the latest release of this project not too long ago (or
> maybe he did ;-)).
>
> I just don't know what it is about the release plugin which causes it to
> fail. Individuals on this list have made clear claims that you should
> NOT have to do an install when you have module dependencies. Any
> thoughts or discussion here would be very much appreciated.
>
> The build fails on the maven-scm-plugin project (which is a module of
> the scm project itself. Here is a snippet.
>
> [INFO] [INFO]
> ------------------------------------------------------------------
> ------
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
> ------------------------------------------------------------------
> ------
> [INFO] [INFO] Failed to resolve artifact.
> [INFO]
> [INFO] Missing:
> [INFO] ----------
> [INFO] 1)
> org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nortel-1
> [INFO] Path to dependency:
> [INFO] 1)
> org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-no
> rtel-1
> [INFO] 2)
> org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nor
> tel-1
> [INFO]
> [INFO] ----------
> [INFO] 1 required artifact is missing.
> [INFO]
> [INFO] for artifact:
> [INFO]
> org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-nortel-1
> [INFO]
> [INFO] from the specified remote repositories:
> [INFO] nexus (http://nexus.norforge.nortel.com/content/groups/public)
>
> ---
> Todd Thiessen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Using release plugin to build scm project
Posted by Todd Thiessen <th...@nortel.com>.
> He did :-) with the cli parameters.
hehe. Thanks for the response Oliver. This at least tells me that their
isn't something wrong with what I am doing.
There still seems to be a disconnect, however, regarding when an install
is required. Ah well. I guess do what works for now.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Using release plugin to build scm project
Posted by Olivier Lamy <ol...@apache.org>.
2009/4/2 Todd Thiessen <th...@nortel.com>:
> I made a change to the scm project to fix a bug that was bugging me.
> Built the 1.3-SNAPSHOT version of the latest SCM plugin, tested it, and
> it works fine.
>
> Now I want to do a formal release of my own personalized version of the
> project.
>
> The release:prepare fails because of missing dependencies between
> modules. The only solution I know of is to add the install goal to the
> preperationGoals configuration. But I am sure Oliver didn't have to do
> this when he cut the latest release of this project not too long ago (or
> maybe he did ;-)).
He did :-) with the cli parameters.
>
> I just don't know what it is about the release plugin which causes it to
> fail. Individuals on this list have made clear claims that you should
> NOT have to do an install when you have module dependencies. Any
> thoughts or discussion here would be very much appreciated.
>
> The build fails on the maven-scm-plugin project (which is a module of
> the scm project itself. Here is a snippet.
>
> [INFO] [INFO]
> ------------------------------------------------------------------
> ------
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
> ------------------------------------------------------------------
> ------
> [INFO] [INFO] Failed to resolve artifact.
> [INFO]
> [INFO] Missing:
> [INFO] ----------
> [INFO] 1)
> org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nortel-1
> [INFO] Path to dependency:
> [INFO] 1)
> org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-no
> rtel-1
> [INFO] 2)
> org.apache.maven.scm:maven-scm-providers-standard:pom:1.3-nor
> tel-1
> [INFO]
> [INFO] ----------
> [INFO] 1 required artifact is missing.
> [INFO]
> [INFO] for artifact:
> [INFO]
> org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.3-nortel-1
> [INFO]
> [INFO] from the specified remote repositories:
> [INFO] nexus (http://nexus.norforge.nortel.com/content/groups/public)
>
> ---
> Todd Thiessen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org