pom of release plugin is already updated. You must build it.
Emmanuel
dan tran a écrit :
the current release plugin uses maven-scm alpha2. so you will need to
fetch maven-release plugin, fix its pom to use maven-scm beta2 snapshot
( for now)
-D
On 11/23/05, *Wim Deblauwe* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
What problems does ClearCase show? It should work fine on a machine
with no clearcase.
regards,
Wim
2005/11/24, Mike Perham <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
[INFO]
----------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
----------------------------------------------------------------------------
[INFO] Maven SCM ..............................................
SUCCESS [0.328s]
[INFO] Maven SCM API ..........................................
SUCCESS [2.125s]
[INFO] Maven SCM Managers .....................................
SUCCESS [ 0.016s]
[INFO] Maven SCM Manager for Plexus ...........................
SUCCESS [0.171s]
[INFO] Maven SCM Test .........................................
SUCCESS [0.094s]
[INFO] Maven SCM Providers ....................................
SUCCESS [ 0.000s]
[INFO] Maven SCM Perforce Provider ............................
SUCCESS [1.219s]
[INFO] Maven SCM Local Provider ...............................
SUCCESS [0.766s]
[INFO] Maven SCM Subversion Provider ..........................
SUCCESS [ 26.376s]
[INFO] Maven SCM Client .......................................
SUCCESS [0.093s]
[INFO] Maven SCM Plugin .......................................
SUCCESS [0.922s]
[INFO]
----------------------------------------------------------------------------
[INFO]
----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
----------------------------------------------------------------------------
Dan, I have compiled it numerous times now. :-) Am I missing
something else? As a sidenote, I removed starteam, clearcase
and cvs cause they all have build or test problems on my machine
for some reason.
------------------------------------------------------------------------
*From:* dan tran [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>]
*Sent:* Wednesday, November 23, 2005 8:00 PM
*To:* scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
*Subject:* Re: 'No such provider: perforce'
best to checkout maven-scm source and build
-D
On 11/23/05, *Mike Perham* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Yes. I just noticed that at runtime mvn is using
1.0-alpha-2. The version I am working on is
1.0-beta-1-SNAPSHOT. How do I tell mvn to use my version?
I tried 'mvn -U -up release:prepare' but it continues to use
a2 instead of my newer snapshot.
mike
------------------------------------------------------------------------
*From:* dan tran [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>]
*Sent:* Wednesday, November 23, 2005 7:48 PM
*To:* scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
*Subject:* Re: 'No such provider: perforce'
Take a look at other provider's components.xml. Do you have
one yet?
-Dan
On 11/23/05, *Mike Perham* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
How do I get the DefaultScmManager to see my new
Perforce provider?
mike
