The current maven release behaviour seems to force me to release a
sub-project and increment its version number even if there is no code
change done whatsover for the project.
I have a parent project (say A) with child projects (say B and C). The
pom for A lists B and C as modules. Let us
Sorry - I made a mistake - the scenario documented below should've read :
If I change only files in the project C (and make no changes whatsoever
to any files in B).
Dhananjay Nene wrote:
The current maven release behaviour seems to force me to release a
sub-project and increment its version
pom to
each of its modules. The simplest way to get the bahavior you want is to
create two projects: a multi-module, containing B and C as modules, and a
parent from which they may inherit.
Eric
On 11/22/06, Dhananjay Nene [EMAIL PROTECTED] wrote:
Sorry - I made a mistake - the scenario
and pluginManagement, but that only
goes so far.
My suggestion is to standardize things via archetypes to generate POMs
in a certain fashion. For common automated build stuff use profile
settings for the build user.
-Nathan
-Original Message-
From: Dhananjay Nene [mailto:[EMAIL PROTECTED]
Sent: Monday
I need to implement a common pom which can be inherited by a large
number of projects. However the common pom does not reflect a top level
module and does not have any sources or artifacts (since it is used only
for inheritance). My attempts so far lead me to believe that maven
requires me to
I have a set of modules and each module has its own independent
repository. As an example top level module A contains modules B and C.
When I attempt to execute mvn scm:checkout on A it tries to checkout
files for A (and I assume subsequently it would try to do the same for
B and C). However
I am using maven 2.0.4 and have been trying to do a release:prepare. I
have attempted to work through a number of options but am having trouble
connecting to my CVS repository for release:prepare (Note: scm:checkout
works just fine - the settings are identical for connection and
My pom.xml has been configured to checkout the project
${basedir}/target/checkout/source (I have configured the
checkoutDirectory for maven-scm-plugin). However release:prepare
continuously fails since the cvs update command does not contain the
directory where the project is checked out. The
-release-plugin/perform-mojo.html
-D
On 6/12/06, Dhananjay Nene [EMAIL PROTECTED] wrote:
My pom.xml has been configured to checkout the project
${basedir}/target/checkout/source (I have configured the
checkoutDirectory for maven-scm-plugin). However release:prepare
continuously fails since the cvs
/06, Dhananjay Nene [EMAIL PROTECTED] wrote:
release:prepare is attempting an update. My assumption is that the same
is for ensuring that the source has not changed and thus it will need
need to know exactly where the source has been checked out earlier. Not
sure if I have made a mistake
Thanks to maven 2 beta 2 I am now able to get a text output of the test
case execution status. Any way I can get the same generated in html /
xml format ?
Dhananjay
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
I am unable to figure out why when I run m2 with a test target the
tests are executed with a nearly empty classpath. I have setup all my
dependencies with the appropriate compile or test scope but these
are are not being reflected in the classpath during execution. e.g. I
added the following to
Duh!! thats embarassing. The classpath is being set correctly. Thanks.
Kenney Westerhof wrote:
On Mon, 26 Sep 2005, Dhananjay Nene wrote:
There's nothing wrong here. The system property java.class.path is
the classpath for the JVM, i.e. the CLASSPATH environment variable
when you start
13 matches
Mail list logo
