Hi Todd,
I´m actually using the maven-release-plugin with Base ClearCase, but with
some (known) limitations:
- i could only release modules within a tree, not a flat directory
hierarchy
- i could only release modules at the main branch; releasing at a branch
is not possible due to the configspec generaration - you need to release
per hand
- i could only release modules one can load with a simple load rule;
defining multiple load rules in the <scm> section is not expected.
For bootstrapping (mvn scm:bootstrap ) my configuration looks like:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<configuration>
<goals>install</goals>
<checkoutDirectory>c:\LocalViewsMaven\${artifactId}-${version}</checkoutDirectory>
</configuration>
</plugin>
For releasing afterwards (mvn release:prepare, mvn release:perform), my
configuration looks like
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<!-- sonst kann selbst bei SNAPSHOT-plugins nichts
released werden -->
<allowTimestampedSnapshots>true</allowTimestampedSnapshots>
<workingDirectory>c:\LocalViewsRelease\${artifactId}-${version}</workingDirectory>
<!-- sonst funktioniert der MultiModule build im Release
nicht -->
<preparationGoals>clean install</preparationGoals>
</configuration>
</plugin>
Doing so, there were two Snapshot Views being created:
C:\LocalViewsMaven\myproject-1.0-SNAPSHOT (mvn scm:bootstrap)
C:\LocalViewsRelease\myproject-1.1-SNAPSHOT (mvn release:perform)
As you can see, the name of the "Release Snapshot view" is bad - it better
would be C:\LocalViewsRelease\myproject-1.0 but I dont know how to do
that.
After releasing your project you than have to delete those created
Snapshot Views, because otherwise you would run into problems, when trying
to release it the next time:
C:\LocalViewsMaven\myproject-1.1-SNAPSHOT (mvn scm:bootstrap)
C:\LocalViewsRelease\myproject-1.2-SNAPSHOT (mvn release:perform)
=> a snapshot view with "myproject-1.1-SNAPSHOT" already exists (name of
the release snapshot view from the last release phase)
have fun,
Torsten
Todd Farrell <[EMAIL PROTECTED]>
30.07.2008 04:40
An
[EMAIL PROTECTED]
Kopie
Thema
Re: Experience in maven-release-plugin using ClearCase SCM
Hi Torsten,
I've been trying to get the maven-release-plugin working with ClearCase
and came across this message:
http://www.mail-archive.com/[email protected]/msg79519.html
Wanted to find out if you'd had any luck solving this problem - I get a
similar error trying to do release:perform.
Cheers,
Todd
Todd Farrell
Application Developer
Link Market Services Limited
* Level 12, 680 George Street, Sydney NSW 2000
: Email: [EMAIL PROTECTED]
( Ph: +61 2 8280 7498 ( Fax: +61 2 9287 0305
ý Please consider the environment before printing this email
Visit http://www.linkmarketservices.com.au/ to find out about the services
we offer our clients and their investors..
*************************************************************************************************
DISCLAIMER:
This email (which includes any attachments or links to other websites) is
intended solely for the named addressee. It is confidential and may
contain legally privileged information. Delivery to any person other than
the named addressee does not waive privilege or confidentiality. If you
have received this email in error, let us know by reply email, delete it
from your system and destroy any copies. This email is also subject to
copyright. You must not reproduce or distribute it without our consent.
We believe that information contained in this email is correct but we give
no warranty as to its accuracy or completeness. It is provided as general
information only and does not take into account your particular
circumstances. It does not purport to be investment advice and you must
not act in reliance on it unless we expressly authorise you to do so. You
should consult an independent financial or legal adviser to assist you in
forming your own opinion on the information. To the extent permitted by
law, we disclaim all liability (including liability for negligence) for
direct or indirect loss or damage suffered by any recipient acting in
reliance on this email.
This email may contain information or links to websites prepared by people
who are not our employees or representatives. Such information will be
identified as the product of an independent third party. It is provided
for your interest and convenience only. We have not independently verified
(and to the extent permitted by law disclaim all liability for) its
accuracy or completeness and it does not constitute our recommendation or
opinion.
Emails may be interfered with, may contain computer viruses or other
defects and may not be successfully replicated on other systems. It is
the responsibility of the recipient to verify the integrity and
authenticity of this email and to ensure that any attachments are scanned
for viruses.
*************************************************************************************************
