You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Avihaimar <av...@yahoo.com> on 2009/06/01 22:20:18 UTC
Maven repostiry for same projects,but different streams
Hey,
I have different streams for the same projects.
Each task effort has its own stream (all streams are child streams of the
integration stream).
I want to be able to run builds for each stream on the integration machine.
The problem is that the artifact names are the same , so the only possible i
think on it is to include the stream name in the artifact name, so when new
stream is created his name will be a parameter to the artifact name.
Another suggestions?
Thank you
--
View this message in context: http://www.nabble.com/Maven-repostiry-for-same-projects%2Cbut-different-streams-tp23821087p23821087.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven repostiry for same projects,but different streams
Posted by "Bracewell, Robert" <rb...@qualcomm.com>.
The use of classifiers may help out in this case.
The major Maven packaging plugins like jar, ear, and war allow the use of a classifier to be configured. For each of your streams if you pass in a property at build time -Dstream=<value> then you could set the classifier to this property and all your built artifacts would live side by side in the repo and each distinguished by the property.
--
Robert
-----Original Message-----
From: Avihaimar [mailto:avihaimar@yahoo.com]
Sent: Monday, June 01, 2009 1:20 PM
To: users@maven.apache.org
Subject: Maven repostiry for same projects,but different streams
Hey,
I have different streams for the same projects.
Each task effort has its own stream (all streams are child streams of the
integration stream).
I want to be able to run builds for each stream on the integration machine.
The problem is that the artifact names are the same , so the only possible i
think on it is to include the stream name in the artifact name, so when new
stream is created his name will be a parameter to the artifact name.
Another suggestions?
Thank you
--
View this message in context: http://www.nabble.com/Maven-repostiry-for-same-projects%2Cbut-different-streams-tp23821087p23821087.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
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: Maven repostiry for same projects,but different streams
Posted by "Vonnahme, Paul" <Vo...@principal.com>.
> I have different streams for the same projects.
> Each task effort has its own stream (all streams are child
> streams of the integration stream).
>
> I want to be able to run builds for each stream on the
> integration machine.
> The problem is that the artifact names are the same , so the
> only possible i think on it is to include the stream name in
> the artifact name, so when new stream is created his name
> will be a parameter to the artifact name.
> Another suggestions?
>
I'm currently evaluating Maven, and this is also an issue we would have to face in our environment. For each build we would pass in the stream name, such as 'mvn -Dbuild.stream=test1'. The big question is where to put the variable in the pom.
Option 1 - In the <groupId>:
<modelVersion>4.0.0</modelVersion>
<groupId>some.package.name.${build.stream}</groupId>
<artifactId>Utility_Jar</artifactId>
<packaging>jar</packaging>
<version>1.0-SNAPSHOT</version>
This is what I've been leaning toward since it provides the most separation.
Option 2 - In the <artifactId>:
<modelVersion>4.0.0</modelVersion>
<groupId>some.package.name</groupId>
<artifactId>Utility_Jar-${build.stream}</artifactId>
<packaging>jar</packaging>
<version>1.0-SNAPSHOT</version>
This is what Avihaimar is suggesting.
Option 3 - In the <version>:
<modelVersion>4.0.0</modelVersion>
<groupId>some.package.name</groupId>
<artifactId>Utility_Jar</artifactId>
<packaging>jar</packaging>
<version>1.0-${build.stream}-SNAPSHOT</version>
I think this is a valid build number, so this should work.
I'm completely new to maven and haven't finished "The Definitive Guide" yet, so maybe I'll come across the answer. If anyone out there has any advice, though, I'd be glad to hear it.
Thanks,
Paul
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.
While this communication may be used to promote or market a transaction
or an idea that is discussed in the publication, it is intended to provide
general information about the subject matter covered and is provided with
the understanding that The Principal is not rendering legal, accounting,
or tax advice. It is not a marketed opinion and may not be used to avoid
penalties under the Internal Revenue Code. You should consult with
appropriate counsel or other advisors on all matters pertaining to legal,
tax, or accounting obligations and requirements.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org