In this case, we have something like this:
// < parent
//
// < children
//
Without putting <artifactId>R1.0</artifactId(and then changing
it for every release) in the parent pom, what should these be?
I'm still confused about the relationships here, but will running from
the top level allow me to release a single child module, or will it
attempt them all?
I like the thought of having the scm entry in the parent pom, and
nothing in the children (and running the release plugin from the top
level) but don't want to release modules just because they are there
(and have no changes since last release).
Message
From: Mike Perham [mailto:Mike.Perham (AT) webifysolutions (DOT) com]
Sent: Wednesday, June 14, 2006 4:49 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
Yes, you need to release all three. If you have a parent project with A
B and C as child modules, you can release the parent and it will
recursively release A B and C also at the same time.
If you put it in the parent and release everything at once, it should
just work. If you want to release the children separately, it will use
a hueristic to determine the SCM location based on the parent's SCM
config. It appends the artifactId to the parent SCM config. If the
child's directory name is not equal to artifactId, you will get a
"Unable to submit" error from Perforce. The solution is to put a <scm>
block in each child also if you have this problem.
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Wednesday, June 14, 2006 3:44 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
Got it - yeah, I was editing a pom in a different branch (DH!).
I have the following dependency chain
C depends on B depends on A. The only real application here is C.
In order to release C, I need to release B and A also?
And my other question earlier was, where is this scm setup supposed to
be, the parent level or child level?
Message
From: Mike Perham [mailto:Mike.Perham (AT) webifysolutions (DOT) com]
Sent: Wednesday, June 14, 2006 4:31 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
You need something like this in your PM.
<scm>
<connection></
connection
<developerConnection>
/parent</d
eveloperConnection>
</scm
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Wednesday, June 14, 2006 3:02 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
I tried that:
E:\work\up-svcs-test\rel\R1.5\cryptoServer>mvn
-Dmaven.test.skip=true release:prepare
@172.22.144.63:1666://d
[INF] Scanning for projects
[INF] Searching repository for plugin with prefix: 'release'.
[INF]
[INF] Building Crypto Server
[INF] task-segment: [release:prepare] (aggregator-style)
[INF]
[INF] [release:prepare]
[INF]
[ERRR] BUILD FAILURE
[INF]
[INF] Missing required setting: scm connection or
developerConnection must be specified.
[INF]
[INF] For more information, run Maven with the -e switch [INF]
[INF] Total time: 2 seconds
[INF] Finished at: Wed Jun 14 16:00:06 EDT 2006 [INF] Final
Memory: 4M/8M [INF]
Message
From: Alexandre Poitras [mailto:alexandre.poitras (AT) gmail (DOT) com]
Sent: Wednesday, June 14, 2006 3:09 PM
To: Maven Users List
Subject: Re: integration builds and version numbers
Just pass it on the command line. You should check the plugin page.
Tons of information like the goal names and their properties :
6/14/06, EJ Ciramella <ejciramella (AT) upromise (DOT) comwrote:
Does anyone know if mvn, when using the perforce scm
config, will pull
the users password from an environment variable?
Mike, did you try that before you left this person logged in?
Message
From: Mike Perham [mailto:Mike.Perham (AT) webifysolutions (DOT) com]
Sent: Wednesday, June 14, 2006 12:12 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
The perforce provider does not handle passwords; it is
assumed that
you
are already logged in. We have a special build user who is only
allowed
to log in from the build server and whose login never expires.
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Wednesday, June 14, 2006 9:54 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
I'm talking about passwords to perforce
Message
From: Roald Bankras [mailto:roald (AT) jteam (DOT) nl]
Sent: Wednesday, June 14, 2006 10:55 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
The website mentioned by Kieran Brady shows how you can
store the
scm passwords.
Roald Bankras
Software Engineer
JTeam b.v.
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Wednesday, June 14, 2006 4:40 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
- got the pdf, but I'm confused. Does this release
plugin need
to be configured at the parent or child pom level? What
if our scm
tool of choose (perforce) requires passwords?
Message
From: Roald Bankras [mailto:roald (AT) jteam (DOT) nl]
Sent: Wednesday, June 14, 2006 10:26 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
In chapter 7 of the 'better builds with maven' book
(downloadable
from
www.mergere.com) there is a description on how to use
the release
plugin.
The plugin website can be found at
Roald Bankras
Software Engineer
JTeam b.v.
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Wednesday, June 14, 2006 4:14 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
I tried both mvn release and mvn release:release -
neither exists.
What is the correct goal?
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Wednesday, June 14, 2006 9:51 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
Where is this documented? I'd like to read more about this.
Message
From: Roald Bankras [mailto:roald (AT) jteam (DOT) nl]
Sent: Wednesday, June 14, 2006 3:16 AM
To: Maven Users List
Subject: RE: integration builds and version numbers
Updating the version numbers in the pom files can be done
by calling
the release goal.
Roald Bankras
Software Engineer
JTeam b.v.
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Monday, June 12, 2006 11:30 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
Someone must be using CC + M2, no?
Message
From: EJ Ciramella [mailto:ejciramella (AT) upromise (DOT) com]
Sent: Monday, June 12, 2006 8:01 AM
To: Maven Users List
Subject: integration builds and version numbers
How are people updating their pom.xml files with
version numbers
from say cruisecontrol?
We have two types of codelines (in perforce) here, project and
release lines. Everything starts out life as a project
then over
time one (or
more) projects can be integrated to a release line.
I'm curious, we're forcefully editing (with the ant replace
task) some templated version.html files to reflect what
version was
built. Do I need to be doing this to the pom.xml files also?
When something is getting built from a project branch,
the build
number looks like this:
X.<projectbranchname>.<buildnumber>
So:
8.P000001.1
In the maven world, all the project branches would look
like this:
<version>X.X-SNAPSHT</version
So in the above case -
<version>8.0-P000001-SNAPSHT</version>
And when that goes to release
<version>8.0.X</version>
Where X is a build number.
This has a problem though - I'll have to remember the
dependency
order to build and make sure that module "C" gets built
before "B"
which is built before "A" (or the replace at least
happens in that
order).
So what are people doing for this? Manually updating
before every
build? I _really_ don't want to have to go back to that
>
>
>
To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
>
>
>
>