Release Plugin: How to specify next version
I am trying to find a way to specify the next version to be used by the maven release plugin on the command line. Basically, I have a project that is currently at version 1.0.9-SNAPSHOT and would like the next release to be 1.1.0-SNAPSHOT after the 1.0.9 version is released. I saw another thread (http://www.nabble.com/batch-release-of-a-set-of-projects-without-using-the-default-versioning-scheme-td11067663s177.html#a11067663) that outlined how to do this using the release.properties file, but I was wondering if there is a way to do this on the command line. Any help would be greatly appreciated. Thanks, John -- View this message in context: http://www.nabble.com/Release-Plugin%3A-How-to-specify-next-version-tp15835733s177p15835733.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is the Best practice for generating variations of an artifacts?
Wouldn't this still result in different artifacts for different environments?
If so, this is what I want to avoid. I would like my artifacts to be
environment agnostic. If you are building a single artifact, perhaps you
could explain how this works.
Thanks,
John
Antony Stubbs wrote:
Even better - you can do away with the system property requirement if you
use Maven Filtering with spring. That way you can set the parameters at
build time, and not have to depend on a system parameter existing.
e.g. you use maven filtering to replace ${dev} inside your spring xml
files with the parameters value during build, instead of spring having to
resolve it.
jp4 wrote:
I have found a solution that works well for me. I use spring in
conjuction with a bootstrap variable called env. When I start my
container in development env=dev in production it's env=prod. I then use
spring to resolve properties based on the environment. For example, a
property file would look like this
url.dev=http://dev.foo.com
url.qa=http://qa.foo.com
url.prod=http://www.foo.com
I then inject this property into a spring bean with something like this
bean id=test class=
property name=urlvalue${url.${env}}/value/property
/bean
This allows all of my deployable artifacts to be environment agnostic,
the same war, ear, etc can be deployed to any environment as long as the
System Property is set on the container.
In addition, this solution has the added benefit of simplifying unit test
cases as well. If you don't use spring, then this probably isn't right
for you. If you are interested I can provide sample code, etc.
Jo Vandermeeren wrote:
Hi Vincent,
I use filtering with profiles (option 1) and rebuild the entire project
when
I need another configuration.
This is far from ideal..
Perhaps you could keep your runtime configuration in a separate module
and
include the one you need as a dependency by activating a profile?
I like your idea with the classifier approach..
Cheers
Jo
On 3/16/07, Vincent Massol [EMAIL PROTECTED] wrote:
Hi,
I've never found a good answer to this use case so far so I'm curious
about how others have implemented it.
Imagine a project that generates a WAR. This WAR contains a config
file (say in WEB-INF/classes) that configures connection parameters
for the database.
Now imagine that your project wants to support several databases and
you want the ability to build for a given database.
I see 2 options:
Option 1
---
* Use filtering
* Use profiles to set the values for the different databases
Issues:
* In order to differentiate the generate WAR file name you'll need to
use finalName but the value set there won't be used for install/
deploy which means that the WAR files users will see will always be
the same.
Idea for future:
* It would be nice if Maven had a classifier element under
project so that it would be possible to generate an artifact with a
classifier.
Option 2
---
* Create one module per database, under a parent module
* Create profiles in the parent module to conditionally include the
module to be built
Issues:
* Very heavy (one module per database) especially when the only
difference between the generated artifacts is only 3 lines in a
config file
* Need a way to share common configuration between the modules, in
order to prevent duplication. For example if the config files only
contains 3 lines that are different for each database and there are
100 lines in total, you don't want to duplicate the 97 lines in as
many modules as you have databases
What do people do? Is there some plan to support this use case in a
better fashion in the future?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/What-is-the-Best-practice-for-generating-variations-of-an-artifacts--tf3414040s177.html#a11963274
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Disable javadoc during site
I was wondering if there is an easy way to skip javadoc generation while invoking mvn clean deploy site site:deploy I have a project with a tremendous amount of javadoc. Generation of site docs takes forever, I want the other reports, but javadoc isn't cruical. Thanks, jp4 -- View this message in context: http://www.nabble.com/Disable-javadoc-during-site-tf4126698s177.html#a11735442 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disable javadoc during site
Wendy, Thanks, I neglected to check the parent pom file that all of my project parents inherit from. I commented out the javadoc plugin section. Thanks, John Wendy Smoak-3 wrote: On 7/22/07, jp4 [EMAIL PROTECTED] wrote: I was wondering if there is an easy way to skip javadoc generation while invoking mvn clean deploy site site:deploy mvn clean deploy site-deploy (Unrelated to your question, but this will do more or less the same thing-- site-deploy is the last phase in the 'site' lifecycle.) I have a project with a tremendous amount of javadoc. Generation of site docs takes forever, I want the other reports, but javadoc isn't cruical. Remove the javadoc plugin from the reporting section? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Disable-javadoc-during-site-tf4126698s177.html#a11736440 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Install Deploy an artifact generated with Assembly Plugin
Tim, That was exactly what I was looking for. Thanks! John Tim Kettler wrote: John, you can attach the jar file with the attach:artifact goal from build-helper-maven-plugin [1] over at the mojo project. -Tim [1] http://mojo.codehaus.org/build-helper-maven-plugin/ jp4 schrieb: I use the assembly plugin to create an executable jar file that contains all of it's dependencies. The file name is foo-1.0-SNAPSHOT-jar-with-dependencies.jar. I would like to be able to install this artifact locally and/or deploy to a remote repository. How can I do this? I have included the assembly plugin configuration below if that helps. plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId executions execution phasepackage/phase configuration descriptors descriptorjar-with-dependencies.xml/descriptor /descriptors workDirectorytarget/assembly/work/workDirectory archive manifestFilesrc/main/resources/META-INF/MANIFEST.MF/manifestFile /archive /configuration goalsgoalassembly/goal/goals /execution /executions /plugin /plugins Thanks, jp4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Install---Deploy-an-artifact-generated-with-Assembly-Plugin-tf3960408s177.html#a11254277 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Install Deploy an artifact generated with Assembly Plugin
I use the assembly plugin to create an executable jar file that contains all of it's dependencies. The file name is foo-1.0-SNAPSHOT-jar-with-dependencies.jar. I would like to be able to install this artifact locally and/or deploy to a remote repository. How can I do this? I have included the assembly plugin configuration below if that helps. plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId executions execution phasepackage/phase configuration descriptors descriptorjar-with-dependencies.xml/descriptor /descriptors workDirectorytarget/assembly/work/workDirectory archive manifestFilesrc/main/resources/META-INF/MANIFEST.MF/manifestFile /archive /configuration goalsgoalassembly/goal/goals /execution /executions /plugin /plugins Thanks, jp4 -- View this message in context: http://www.nabble.com/Install---Deploy-an-artifact-generated-with-Assembly-Plugin-tf3960408s177.html#a11238491 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Filtering Changes Jira Report By Version
I was wondering if it's possible to configure the changes plugin to pull only the jira issues that were assigned to the current version of my project. For example, if my project version is 1.1, I would like to see only issues that were assigned to version 1.1 in the changes jira report. Thanks, jp4 -- View this message in context: http://www.nabble.com/Filtering-Changes-Jira-Report-By-Version-tf3719358s177.html#a10406319 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is the Best practice for generating variations of an artifacts?
I have found a solution that works well for me. I use spring in conjuction
with a bootstrap variable called env. When I start my container in
development env=dev in production it's env=prod. I then use spring to
resolve properties based on the environment. For example, a property file
would look like this
url.dev=http://dev.foo.com
url.qa=http://qa.foo.com
url.prod=http://www.foo.com
I then inject this property into a spring bean with something like this
bean id=test class=
property name=urlvalue${url.${env}}/value/property
/bean
This allows all of my deployable artifacts to be environment agnostic, the
same war, ear, etc can be deployed to any environment as long as the System
Property is set on the container.
In addition, this solution has the added benefit of simplifying unit test
cases as well. If you don't use spring, then this probably isn't right for
you. If you are interested I can provide sample code, etc.
Jo Vandermeeren wrote:
Hi Vincent,
I use filtering with profiles (option 1) and rebuild the entire project
when
I need another configuration.
This is far from ideal..
Perhaps you could keep your runtime configuration in a separate module and
include the one you need as a dependency by activating a profile?
I like your idea with the classifier approach..
Cheers
Jo
On 3/16/07, Vincent Massol [EMAIL PROTECTED] wrote:
Hi,
I've never found a good answer to this use case so far so I'm curious
about how others have implemented it.
Imagine a project that generates a WAR. This WAR contains a config
file (say in WEB-INF/classes) that configures connection parameters
for the database.
Now imagine that your project wants to support several databases and
you want the ability to build for a given database.
I see 2 options:
Option 1
---
* Use filtering
* Use profiles to set the values for the different databases
Issues:
* In order to differentiate the generate WAR file name you'll need to
use finalName but the value set there won't be used for install/
deploy which means that the WAR files users will see will always be
the same.
Idea for future:
* It would be nice if Maven had a classifier element under
project so that it would be possible to generate an artifact with a
classifier.
Option 2
---
* Create one module per database, under a parent module
* Create profiles in the parent module to conditionally include the
module to be built
Issues:
* Very heavy (one module per database) especially when the only
difference between the generated artifacts is only 3 lines in a
config file
* Need a way to share common configuration between the modules, in
order to prevent duplication. For example if the config files only
contains 3 lines that are different for each database and there are
100 lines in total, you don't want to duplicate the 97 lines in as
many modules as you have databases
What do people do? Is there some plan to support this use case in a
better fashion in the future?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/What-is-the-Best-practice-for-generating-variations-of-an-artifacts--tf3414040s177.html#a10200077
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Versioning Site Documentation
I would like to know how to version my site documentation. I have a nightly build that I use for generating snapshots and promoting them to our internal maven repo along with deploying site docs to apache. In addition, when I create a release of a particular artifact I generate site documentation as well. I was wondering if there is a way to deploy the site documentation to two different locations so that it is versioned properly... For example, http://www.foo.com/project1/1.0-SNAPSHOT http://www.foo.com/project1/1.1/ It's ok to overwrite the nightly site docs, but I want to make sure that the release versions are not overwritten. Right now, they are both writing to the same location, which is not optimal. Any ideas? Thanks, jp4 -- View this message in context: http://www.nabble.com/Versioning-Site-Documentation-tf3648383s177.html#a10190677 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Versioning Site Documentation
Wendy,
I tried what you suggested, but it appears as though none of the child
modules for the parent projects are linked properly. It creates directories
/project-parent-1.1-SNAPSHOT/project-parent/
/project-moduleA-1.1-SNAPSHOT/project-parent/moduleA
/project-moduleB-1.1-SNAPSHOT/project-parent/moduleB
The problems is that links from
/project-parent-1.1-SNAPSHOT/project-parent/index.html are referring to
modules with relative links like this
/project-parent-1.1-SNAPSHOT/project-parent/moduleA/index.html
But the modules directories are at the same level as the parent... Any
ideas?
Thanks,
jp4
Wendy Smoak-3 wrote:
On 4/25/07, jp4 [EMAIL PROTECTED] wrote:
I was wondering if there is a way to deploy the site documentation to two
different locations so that it is versioned properly...
For example,
http://www.foo.com/project1/1.0-SNAPSHOT
http://www.foo.com/project1/1.1/
Try using ${version} in your distributionManagement site url.
There's an example of something similar in the maven plugins parent pom:
http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml
(look at the stagingSiteURL).
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Versioning-Site-Documentation-tf3648383s177.html#a10191124
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
POM for common libraries
I have a project (common-data-access) of type pom that is used to group a set
of common libraries for reuse. In this case, I group all libraries that I
need for a data access project. In each data access project in include
common-data-access as typepom/type. I have encountered two issues and I
was hoping someone could help me. First, it appears as though artifacts
that are defined as scopeprovide/scope in common-data-access are not
recognized by projects that include common-data-access. The oracle jar file
is one example. In addition, it appears as though dependencies with a test
scope are also not recognized by projects that include common-data-access.
Below is my pom.xml, am I doing something wrong here?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdcom.foo/groupId
artifactIdcommon-maven-build/artifactId
version8.1-SNAPSHOT/version
/parent
groupIdcom.foo/groupId
artifactIdcommon-data-access/artifactId
version8.1-SNAPSHOT/version
name${artifactId}/name
packagingpom/packaging
dependencies
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate/artifactId
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring/artifactId
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdoracle_jdbc/artifactId
scopeprovided/scope
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-spring-util/artifactId
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-configuration/artifactId
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-abstract-unit-tests/artifactId
typetest-jar/type
scopetest/scope
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
scopetest/scope
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-configuration/artifactId
scopetest/scope
typetest-jar/type
/dependency
/dependencies
/project
--
View this message in context:
http://www.nabble.com/POM-for-common-libraries-tf3607983s177.html#a10080824
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM for common libraries
Wayne,
Thanks for the reply. What you have described makes sense. I guess I am
just looking for a way to avoid including the same test and provided scoped
dependencies in multiple projects that follow essentially the same design
patterns.
Thanks,
jp4
Wayne Fay wrote:
What you're describing actually makes the most sense to me vs what
you're expecting...
Test scope means: when I am testing this particular artifact, I need
to include these dependencies in the classpath. But you're not testing
this artifact -- you're simply including it as a dependency of another
artifact -- so why in the world would those test scoped artifacts come
in? If you need these dependencies to test this other
artifact/project, then it must attach them itself. (aka, test scope is
not transitive)
Provide scope means: I need these artifacts to properly build and
use/run the code in this project, but I know these artifacts will be
provided by the environment I'll be executing in. When you bring this
dependency into another project, suddenly that new project is the
environment and so it must ensure that dependency is available in
the classpath (through provide or compile scope, as appropriate).
(aka, provide scope is not transitive)
I think that what you're seeing is exactly how it should work, and
your expectations are simply invalid. But I'm happy to be proven wrong
or continue this discussion.
Wayne
On 4/19/07, jp4 [EMAIL PROTECTED] wrote:
I have a project (common-data-access) of type pom that is used to group a
set
of common libraries for reuse. In this case, I group all libraries that
I
need for a data access project. In each data access project in include
common-data-access as typepom/type. I have encountered two issues
and I
was hoping someone could help me. First, it appears as though artifacts
that are defined as scopeprovide/scope in common-data-access are not
recognized by projects that include common-data-access. The oracle jar
file
is one example. In addition, it appears as though dependencies with a
test
scope are also not recognized by projects that include
common-data-access.
Below is my pom.xml, am I doing something wrong here?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdcom.foo/groupId
artifactIdcommon-maven-build/artifactId
version8.1-SNAPSHOT/version
/parent
groupIdcom.foo/groupId
artifactIdcommon-data-access/artifactId
version8.1-SNAPSHOT/version
name${artifactId}/name
packagingpom/packaging
dependencies
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate/artifactId
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring/artifactId
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdoracle_jdbc/artifactId
scopeprovided/scope
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-spring-util/artifactId
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-configuration/artifactId
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-abstract-unit-tests/artifactId
typetest-jar/type
scopetest/scope
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
scopetest/scope
/dependency
dependency
groupIdcom.foo/groupId
artifactIdcommon-configuration/artifactId
scopetest/scope
typetest-jar/type
/dependency
/dependencies
/project
--
View this message in context:
http://www.nabble.com/POM-for-common-libraries-tf3607983s177.html#a10080824
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/POM-for-common-libraries-tf3607983s177.html#a10082195
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] POM Inheritance
This is exactly what I was looking for. I didn't realize that you could include a typepom/type as a dependency. This makes things much cleaner. Thanks again, jp4 Eric Redmond wrote: Abstract it? I don't understand. The JDBC pom is just a seperate project. Like this: JDBC POM: project ... artifactIdmy-jdbc-project/artifactId packagingpom/packaging dependencies ... add jdbc dependencies here, like mysql jdbc, or sqlserver jdbc ... /dependencies /project Then, in your project that needs to use the jdbc drivers: dependencies dependency groupId.../groupId artifactIdmy-jdbc-project/artifactId version.../version typepom/type /dependency On 2/28/07, jp4 [EMAIL PROTECTED] wrote: So how to you use this abstract jdbc pom file? Do you include it as a dependency in your data access modules?Do you use it as the parent of your data access modules? jp4 Eric Redmond wrote: Yeah, I do this quite a lot - for example, to abstract jdbc implementations across and organization - all jars required go into a pom project called jdbc. If you need to make an orthogonal change, just change jdbc's dependency list. Eric On 2/28/07, Thierry Lach [EMAIL PROTECTED] wrote: Is it possible to declare a pom as a dependency, so that its dependencies would be inherited? If that doesn't work, them maybe it should be added as an enhancement. On 2/27/07, jp4 [EMAIL PROTECTED] wrote: I wonder if it would make sense to create a project of type jar that does nothing more than declare common dependencies like spring and hibernate. This way, by including a common data access jar file, all other data access modules would transitively include the spring and hibernate jars. Any thoughts our ideas would be greatly appreciated. jp4 jp4 wrote: I have been doing some reading and it looks like the pluginManagement section will allow me to achieve part of what I want to do with reusing plugin configurations. jp4 jp4 wrote: I have posted about this question several times before but haven't received many responses. I am hoping that someone has done or knows how to accomplish the following. Basically, I have several multi module projects. Each project defines a parent pom.xml file which contains a list of modules as well as the project's version id (all children use the parent.version). In addition, if necessary, it defines any common dependencies for it's modules. I have several projects that follow this pattern, most of which produce a deployable webapp and consist of webapp, model, data access, and service modules. For the most part, the data access modules usually share common configuration such as spring and hibernate dependencies and perhaps some common plugins. So, in the case of a data access module, I would like it's parent to be the projects' parent pom.xml file, but I would also like it to be able to inherit data access configurations from a different pom.xml file. I know that you can create an inheritance chain, but in this case, I really don't want the project's parent pom.xml file to inherit from a data access pom.xml for obvious reasons. The solution may be that I have to redefine the spring and hibernate dependencies as well as plugins in each data access project. I can do that, but I wanted to explore a more elegant solution before resorting to that. Any help would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/POM-Inheritance-tf3304518s177.html#a9196345 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Eric Redmond http://codehaus.org/~eredmond -- View this message in context: http://www.nabble.com/POM-Inheritance-tf3304518s177.html#a9226529 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Eric Redmond http://codehaus.org/~eredmond -- View this message in context: http://www.nabble.com/POM-Inheritance-tf3304518s177.html#a9234650 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
POM Inheritance
I have posted about this question several times before but haven't received many responses. I am hoping that someone has done or knows how to accomplish the following. Basically, I have several multi module projects. Each project defines a parent pom.xml file which contains a list of modules as well as the project's version id (all children use the parent.version). In addition, if necessary, it defines any common dependencies for it's modules. I have several projects that follow this pattern, most of which produce a deployable webapp and consist of webapp, model, data access, and service modules. For the most part, the data access modules usually share common configuration such as spring and hibernate dependencies and perhaps some common plugins. So, in the case of a data access module, I would like it's parent to be the projects' parent pom.xml file, but I would also like it to be able to inherit data access configurations from a different pom.xml file. I know that you can create an inheritance chain, but in this case, I really don't want the project's parent pom.xml file to inherit from a data access pom.xml for obvious reasons. The solution may be that I have to redefine the spring and hibernate dependencies as well as plugins in each data access project. I can do that, but I wanted to explore a more elegant solution before resorting to that. Any help would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/POM-Inheritance-tf3304518s177.html#a9192076 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] POM Inheritance
I have been doing some reading and it looks like the pluginManagement section will allow me to achieve part of what I want to do with reusing plugin configurations. jp4 jp4 wrote: I have posted about this question several times before but haven't received many responses. I am hoping that someone has done or knows how to accomplish the following. Basically, I have several multi module projects. Each project defines a parent pom.xml file which contains a list of modules as well as the project's version id (all children use the parent.version). In addition, if necessary, it defines any common dependencies for it's modules. I have several projects that follow this pattern, most of which produce a deployable webapp and consist of webapp, model, data access, and service modules. For the most part, the data access modules usually share common configuration such as spring and hibernate dependencies and perhaps some common plugins. So, in the case of a data access module, I would like it's parent to be the projects' parent pom.xml file, but I would also like it to be able to inherit data access configurations from a different pom.xml file. I know that you can create an inheritance chain, but in this case, I really don't want the project's parent pom.xml file to inherit from a data access pom.xml for obvious reasons. The solution may be that I have to redefine the spring and hibernate dependencies as well as plugins in each data access project. I can do that, but I wanted to explore a more elegant solution before resorting to that. Any help would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/POM-Inheritance-tf3304518s177.html#a9196293 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] POM Inheritance
I wonder if it would make sense to create a project of type jar that does nothing more than declare common dependencies like spring and hibernate. This way, by including a common data access jar file, all other data access modules would transitively include the spring and hibernate jars. Any thoughts our ideas would be greatly appreciated. jp4 jp4 wrote: I have been doing some reading and it looks like the pluginManagement section will allow me to achieve part of what I want to do with reusing plugin configurations. jp4 jp4 wrote: I have posted about this question several times before but haven't received many responses. I am hoping that someone has done or knows how to accomplish the following. Basically, I have several multi module projects. Each project defines a parent pom.xml file which contains a list of modules as well as the project's version id (all children use the parent.version). In addition, if necessary, it defines any common dependencies for it's modules. I have several projects that follow this pattern, most of which produce a deployable webapp and consist of webapp, model, data access, and service modules. For the most part, the data access modules usually share common configuration such as spring and hibernate dependencies and perhaps some common plugins. So, in the case of a data access module, I would like it's parent to be the projects' parent pom.xml file, but I would also like it to be able to inherit data access configurations from a different pom.xml file. I know that you can create an inheritance chain, but in this case, I really don't want the project's parent pom.xml file to inherit from a data access pom.xml for obvious reasons. The solution may be that I have to redefine the spring and hibernate dependencies as well as plugins in each data access project. I can do that, but I wanted to explore a more elegant solution before resorting to that. Any help would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/POM-Inheritance-tf3304518s177.html#a9196345 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] POM Inheritance
I still haven't found a good solution for this and I was hoping to spark some
discussion with a follow up post.
jp4 wrote:
I was wondering if there is any way to achieve multiple pom inheritance
with maven. I have created several pom abstractions (i.e. data access
which includes dependencies for hibernate, spring, etc... webapp which
includes dependencies for struts, etc) for convenience as most of my data
access projects follow the same pattern using hibernate and spring. I
don't want to have to redefine these dependencies in each of my data
access projects.
Now here is where the problem comes in, I have a multi-module projectA
that has a model, data access, webapp projects. In addition, I have a
multi-module projectB that has a model, data access, webapp project. I
would like to have all modules in projectA have the same version so that I
can refer to version for projectA as ${project.version} in my model, data
access, and webapp. The problem that I have is that I want projectA's
data access project to inherit from both the data access pom as well as
the projectA pom. Is there any way to do this? Or is there a different
approach to achieve the desired results?
Thanks,
jp4
--
View this message in context:
http://www.nabble.com/POM-Inheritance-tf3164691s177.html#a9107889
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
POM Inheritance
I was wondering if there is any way to achieve multiple pom inheritance with
maven. I have created several pom abstractions (i.e. data access which
includes dependencies for hibernate, spring, etc... webapp which includes
dependencies for struts, etc) for convenience as most of my data access
projects follow the same pattern using hibernate and spring. I don't want
to have to redefine these dependencies in each of my data access projects.
Now here is where the problem comes in, I have a multi-module projectA that
has a model, data access, webapp projects. In addition, I have a
multi-module projectB that has a model, data access, webapp project. I
would like to have all modules in projectA have the same version so that I
can refer to version for projectA as ${project.version} in my model, data
access, and webapp. The problem that I have is that I want projectA's data
access project to inherit from both the data access pom as well as the
projectA pom. Is there any way to do this? Or is there a different
approach to achieve the desired results?
Thanks,
jp4
--
View this message in context:
http://www.nabble.com/POM-Inheritance-tf3164691s177.html#a8779117
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Parent pom file usage
I am looking for some advice on how to properly structure my build. I have a multi-project build with several layers of pom abstraction, the ultimate parent being maven-build project. The maven-build pom.xml resides in root directory where all of my subprojects reside. Currently, the maven-build project builds 5 modules, each of those modules building 1 or more modules. In addition, I have defined a dependencyManagement section, common plugins like clover, javadoc, surefire, etc. The problem that I am having is when I add something new to the dependencyManagement section of maven-build (i.e commons-logging-1.0.jar) and to a project that uses that dependency my build fails because the version is specificed in the project that uses it. If I comment out the modules in the maven-build pom.xml and do a clean install, the uncomment them it works. Basically what is happening is that the maven-build pom.xml is not in the local repo until it has been build (and all modules are built). I am thinking that the best way to deal with this is to put a profile tag around the modules section in the maven-build pom.xml file but I am not sure if this is the best way to approach things. It is kinda of a chicken and egg scenario. I want the power of inheriting dependencies from dependencyManagement as well as plugin configurations, but I have to have a better way to deal with updates to the maven-build pom.xml file. Any suggestions would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/Parent-pom-file-usage-tf3149151s177.html#a8730361 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Are clovered files supposed to be deployed to the remote repo?
The first question I have is whether or not clovered artifacts are supposed to be deployed to the remote repo when running mvn clean install deploy? I do not see these clovered artifacts being deployed and wonder if they should be. The reason I ask this is because I am running into a anomoly with my build. I run my build locally and it pulls clovered dependencies from the local repo. When I run it on our build server with the same exact configuration, it attempts to find the clovered artifacts from our development repository instead of the local repo? As a result, the build fails since clovered files are not deployed to the development repo. Any insight would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/Are-clovered-files-supposed-to-be-deployed-to-the-remote-repo--tf3143783s177.html#a8714082 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Site Documentation in a Multi Project
I have a fairly large maven build with approx 30-40 different projects grouped into different submodules. My layout is as follows. pom.xml (includes modules common, app1, app2, etc... no plugins define, just lists build order) ---common --pom.xml (type=pom, build projects in common) --maven-build (type=pom, defines all common plugins and dependencyManagement) -pom.xml --proj2 -pom.xml --proj2 -pom.xml ---app1 --pom.xml (type=pom, build projects in app1) --app1-proj1 -pom.xml --app1-proj2 -pom.xml etc The problem that I am having is that site documentation created in the root directory (where the main pom.xml resides) does not have any links to modules (common, app1, app2, etc). In addition, aggregation plugins like javadoc, clover, etc don't seem to be aggregating at the main pom level. I had this working a while back when I was running all modules from the maven-build projects, but I had to remove modules from there because of ciruclar dependency issues. In any event, I would like to have a main pom.xml that does nothing more than list the modules that need to be built. In addition, I would like the site documentation to be fully integrated so that I can easily navigate to sub modules and view aggregated reports. Any help would be greatly appreciated. Thanks, jp4 -- View this message in context: http://www.nabble.com/Site-Documentation-in-a-Multi-Project-tf3065703s177.html#a8526690 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clearing out local repository during nightly builds
My solution wasn't elegant, but I had to make it simple.
I created a clean project which was the first module listed in the main
pom.xml. The clean project pom.xml looked something like this... It runs an
ant script to do the delete. Hope this helps.
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.foo.common/groupId
artifactIdcommon-clean/artifactId
version1.0-SNAPSHOT/version
name${artifactId}/name
packagingpom/packaging
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idclean/id
phaseclean/phase
configuration
tasks
property name=user.home
value=${user.home}/
property name=m2.repo
value=${user.home}/.m2/repository/
property name=foo.repo.dir
value=${m2.repo}/com/foo/
echoi4commerce dir =
${foo.repo.dir}/echo
delete dir=${foo.repo.dir}/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
distributionManagement
site
idrepository/id
urlscp://gondor/var/www/html/mavenSite//url
/site
repository
idrepository/id
urlscp://gondor/var/www/html/maven/url
/repository
/distributionManagement
/project
Thierry Lach-2 wrote:
OK I've also been waiting for an answer on this. Anyone know?
On 1/15/07, jp4 [EMAIL PROTECTED] wrote:
Recently I have had some issues with version management where we upgrade
a
particular artifact to a new version, but some how, not all projects
reference the new version. I have tried to mitigate this by making use
of
the dependencyManagement section which works nicely.
I would still however, like to clean out the local repository (only a
certain directory com/foo) so that I don't encounter this problem in the
future. My problem now is that I have a pom.xml that builds all of my
modules. In addition, this pom uses the antrun plugin to remove the
directory from the local repo. This works fine if I do a mvn clean then
a
mvn install, but if I do a mvn clean install, the last thing that happens
is
the delete. Is there any way to have this run before any of the modules
are
built?
Thanks,
jp4
--
View this message in context:
http://www.nabble.com/Clearing-out-local-repository-during-nightly-builds-tf3015348s177.html#a8373630
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Clearing-out-local-repository-during-nightly-builds-tf3015348s177.html#a8432680
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Multi Project Module Order
I am having an issue with the order in which modules are built. I have explicitly specified in the main pom.xml file that the clean project (which deletes a portion of the local repo) should be built first. However, maven has decided to build the clean project second, which causes problems because it deletes the artifact that was built first from the local repo. Is there any way to explicitly set the order for modules to be built? Or is there any easy way to call an ant script to delete a portion of the local repo (like my clean project is doing) before the other modules are built? Thanks, jp4 -- View this message in context: http://www.nabble.com/Multi-Project-Module-Order-tf3021371s177.html#a8391433 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Clearing out local repository during nightly builds
Recently I have had some issues with version management where we upgrade a particular artifact to a new version, but some how, not all projects reference the new version. I have tried to mitigate this by making use of the dependencyManagement section which works nicely. I would still however, like to clean out the local repository (only a certain directory com/foo) so that I don't encounter this problem in the future. My problem now is that I have a pom.xml that builds all of my modules. In addition, this pom uses the antrun plugin to remove the directory from the local repo. This works fine if I do a mvn clean then a mvn install, but if I do a mvn clean install, the last thing that happens is the delete. Is there any way to have this run before any of the modules are built? Thanks, jp4 -- View this message in context: http://www.nabble.com/Clearing-out-local-repository-during-nightly-builds-tf3015348s177.html#a8373630 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can you compile test cases without running them
I would like to be able to compile my test cases without actually running them. I use maven.test.skip=true but that seems to prevent not only the test execution but the test compilation. Is there a way to compile without running test cases. I would prefer not to mess with the pom files, but do it via the command line like -Dmaven.test.skip=true. Thanks, jp4 -- View this message in context: http://www.nabble.com/Can-you-compile-test-cases-without-running-them-tf3016005s177.html#a8375655 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can you compile test cases without running them
I just ran mvn clean install -Dtest=foo where foo is not a valid test and this seems to do what I want. If anyone has a cleaner way, please let me know. jp4 wrote: I would like to be able to compile my test cases without actually running them. I use maven.test.skip=true but that seems to prevent not only the test execution but the test compilation. Is there a way to compile without running test cases. I would prefer not to mess with the pom files, but do it via the command line like -Dmaven.test.skip=true. Thanks, jp4 -- View this message in context: http://www.nabble.com/Can-you-compile-test-cases-without-running-them-tf3016005s177.html#a8375759 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven, clover and the Axis2 aar plugin
I am wondering if anyone has attempted to create an instrumented aar file using clover? I am attempting to deploy my webservices inside an application server container using cargo so that I can get some code coverage stats. Basically, my problem is that when I use the maven2 aar plugin, the foo-1.0.aar file is installed into the local repository but the foo-1.0-clover.aar file is not. I can see when it is installing the foo-1.0-clover.aar file it is writing it to foo-1.0.aar in the repository, which is subsequently overwritten with the non-instrumented foo-1.0.aar file. I am curious if anyone has had the same issue, and if so how did you resolve it? Like I said before, all of the artifacts are built properly see below, but the foo-1.0-clover.aar isn't installed in the repository properly. target/foo-1.0.aar target/clover/foo-1.0-clover.aar Thanks, jp4 -- View this message in context: http://www.nabble.com/Maven%2C-clover-and-the-Axis2-aar-plugin-tf2891510s177.html#a8078091 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deploying clover instrumented war using cargo
I am trying to deploy a clover instrumented war file using cargo. I am able to deploy the file but when I run integration tests against it, clover writes to the target/clover/clover.db.XZ file. I believe unit test cases write to the target/clover/clover.db file. My question is how do i merge the unit test case files with the ones that run in container? thanks, jp4 -- View this message in context: http://www.nabble.com/Deploying-clover-instrumented-war-using-cargo-tf2644958s177.html#a7383666 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using Cargo and Cobertura to get in container code coverage
I have been using cargo to deploy my application and run integration tests against the application in container. Now I would like to have cargo deploy a war file that contains classes instrumented by cobertura. In addition, I would like to be able to merge the results of the unit and integration tests. Has anyone done this successfully, if so can you please share your pom file? thanks, jp4 -- View this message in context: http://www.nabble.com/Using-Cargo-and-Cobertura-to-get-in-container-code-coverage-tf2639446s177.html#a7367963 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn site running test cases twice
I removed the coberatura plugin and unit test cases run only once... Here is what I have in my pom build section plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId executions execution goals goalclean/goal /goals /execution /executions /plugin reporting section plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId /plugin Any ideas? Looks like the test cases get run during instrumentation? Thanks, jp4 Wendy Smoak-3 wrote: On 11/3/06, jp4 [EMAIL PROTECTED] wrote: I am using the surefire report plugin as well as coberatura, javadoc and checkstyle.. When I do a mvn site it runs my test cases twice. Does it happen if you remove the Cobertura plugin? We use surefire, javadoc and checkstyle in the Struts build, and the tests don't run twice. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/mvn-site-running-test-cases-twice-tf2571386s177.html#a7225137 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn site running test cases twice
This seems like a big issue since our nightly builds usually run all of our unit and container test cases. If we have to run the tests twice, it will almost double the build time which is already several hours. Is there any way to instrument without invoking the test cases? It seems like you would want to clean, compile, instrument, test, install create site docs. Has anyone found a workaround? Thanks, jp4 Wendy Smoak-3 wrote: On 11/7/06, jp4 [EMAIL PROTECTED] wrote: I removed the coberatura plugin and unit test cases run only once... Here is what I have in my pom ... Any ideas? Looks like the test cases get run during instrumentation? I think it's normal based on Maven's current design. The tests are run once during the 'test' phase, then in order to produce the coverage report, the tests have to be re-run on the instrumented code. Take a look at this post from Vincent which talks about a similar issue with the Clover plugin: http://www.nabble.com/-M2--My-tests-are-launched-3-times-%21-t2190279s177.html#a6075779 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/mvn-site-running-test-cases-twice-tf2571386s177.html#a7226443 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Continue Build and Site Generation on Junit failure
I am interested in what you did. We use CC as well. Any info you can provide would be greatly appreciated. This is very important as we have a huge codebase and would like to identify all errors every night (NOT JUST THE FIRST ONE!) Thanks, jp4 Jon SlinnHawkins wrote: TestFailureIgnore will then result in a build success. When infact the tests failed, so the build needs to be failed. I had exeactly the same issue. We are using CruiseControl for our Continuous Integration system. Unfortunately I had to modify the CC code. It was only a minor change but it has enable us to execute maven 3 times as part of the same build, if any of the 3 runs fail the build will continue until all 3 are finshed and THEN report a build failure. FYI - 1 - Checkout source and cleanup folders 2 - Maven deploy (inculding unit and functional testing) 3 - Build the site. If you are using CC i will try and find the peice of code i changed. It was a very simple change. Cheers Jon Alexandre Russel [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Continue-Build-and-Site-Generation-on-Junit-failure-tf2553508s177.html#a7226861 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where can I get the nightly Maven2 build?
I don't know if the fix was specific to a plugin or to maven itself... I have another post with no replies http://www.nabble.com/mvn-site-running-test-cases-twice-tf2571386s177.html I think the fix may be in the way maven plugins communicate, not necessarily in a particular plugin... But I am not sure. Thanks, jp4 Wendy Smoak-3 wrote: On 11/3/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 11/3/06, jp4 [EMAIL PROTECTED] wrote: I was hoping to get a nightly build so that I can see if my unit test cases will run twice when I run mvn site. I am hoping it's fixed in the new version, but I haven't been able to find a link to the nightly builds. Snapshots are published here: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/ On second thought, if you're trying to test a fix for the site plugin, that won't help. See: http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html It looks like the most recent snapshot for the site plugin was published in late May. http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-site-plugin/ When was the fix you're looking for committed? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Where-can-I-get-the-nightly-Maven2-build--tf2571186s177.html#a7174004 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven equivalent of ant depend optional task
I have been searching for the Maven2 equivalent of the ant depend task but I can't seem to find it. Can someone help me out with a link? -- View this message in context: http://www.nabble.com/Maven-equivalent-of-ant-%3Cdepend%3E-optional-task-tf2568454s177.html#a7159353 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mechanism to import common depdencies into your pom files?
I have a client with many different maven projects. I am trying to figure out a way to manage the versions of common libraries across these projects without duplicating the version number in each project. For example, commons-lang-1.1.jar is used in 50 projects. I know that I can use a parent pom file to do this, but I don't want all of my projects to include everything in the parent pom. Is there a way to import or include a dependency in your pom... So for example, define a file with common-lang dependency and include that in all pom files that need to reference it? Thanks, jp4 -- View this message in context: http://www.nabble.com/Mechanism-to-import-common-depdencies-into-your-pom-files--tf2568584s177.html#a7159759 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven equivalent of ant depend optional task
The depend task is used to determine java class file dependencies From
the ant docs...
The depend task works by determining which classes are out of date with
respect to their source and then removing the class files of any other
classes which depend on the out-of-date classes.
For example, if you have Foo.java and Bar.java... Initially, BAR = BAR...
The first compilation prints BAR in both A B If you change BAR = FOO
and recompile it only compiles Bar.java... As a result Foo prints BAR and
Bar prints FOO... You can get around this with clean, but for big projects,
clean takes too long.
public class Foo {
public static void main(String[] args) {
System.out.println(Bar.BAR);
}
}
public class Bar {
public static final String BAR = FOO;
public static void main(String[] args) {
System.out.println(BAR);
}
}
Wendy Smoak-3 wrote:
On 11/3/06, jp4 [EMAIL PROTECTED] wrote:
I have been searching for the Maven2 equivalent of the ant depend task
but
I can't seem to find it. Can someone help me out with a link?
Everything in Maven centers around the build lifecycle.
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
Because of that, tasks don't 'depend' on other tasks, instead they are
bound to different phases of the lifecycle.
What are you trying to get Maven to do?
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Maven-equivalent-of-ant-%3Cdepend%3E-optional-task-tf2568454s177.html#a7159988
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mechanism to import common depdencies into your pom files?
Exactly what I was looking for and it works quite well! Thanks, jp4 Wendy Smoak-3 wrote: On 11/3/06, jp4 [EMAIL PROTECTED] wrote: I have a client with many different maven projects. I am trying to figure out a way to manage the versions of common libraries across these projects without duplicating the version number in each project. This is typically done with dependencyManagement. You specify version numbers there, then just declare the groupId and artifactId in the module that needs it. (There have been some issues with dependency management and transitive dependencies, so check JIRA or the list archives if it doesn't seem to be working right.) For example, commons-lang-1.1.jar is used in 50 projects. I know that I can use a parent pom file to do this, but I don't want all of my projects to include everything in the parent pom. Is there a way to import or include a dependency in your pom... So for example, define a file with common-lang dependency and include that in all pom files that need to reference it? To inherit it without ever declaring it again, just put it in dependencies in a top-level pom. Many organizations have a 'master pom' (with no modules) that the various [project]-parent poms inherit from. If you do this, be sure the dependencies are *really* common to all projects. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Mechanism-to-import-common-depdencies-into-your-pom-files--tf2568584s177.html#a7160595 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 project type for a standalone utility
I have used the maven assembly plugin before to build an executable jar file that contains all of the necessary runtime libraries. In order to run the app all you have to do is type java -jar foo.jar arg1 arg2... If this sounds like something you want, I can post the pom.xml jp4 David Jackman wrote: I have a Java project that I want to build using Maven 2. This particular project doesn't really produce a jar as its main artifact, but instead needs to produce a zip file containing all of the runtime dependencies along with a batch file that users use to run the utility. Before I try to create a new plugin that will build this kind of project, I'm wondering if anyone out there has already built this kind of thing and what you used to build it. Thanks, ..David.. -- View this message in context: http://www.nabble.com/M2-project-type-for-a-standalone-utility-tf2569649s177.html#a7163227 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Where can I get the nightly Maven2 build?
I was hoping to get a nightly build so that I can see if my unit test cases will run twice when I run mvn site. I am hoping it's fixed in the new version, but I haven't been able to find a link to the nightly builds. Thanks, jp4 -- View this message in context: http://www.nabble.com/Where-can-I-get-the-nightly-Maven2-build--tf2571186s177.html#a7167649 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn site running test cases twice
I am using the surefire report plugin as well as coberatura, javadoc and checkstyle.. When I do a mvn site it runs my test cases twice. I have read other threads on this issue, but I haven't seen a definitive resolution... Is there one? We have a done of tests that get run nightly and now I know why the build takes so long. Any feedback would be greatly appreciated. jp4 -- View this message in context: http://www.nabble.com/mvn-site-running-test-cases-twice-tf2571386s177.html#a7168325 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Method for synching Devlopment Repository to Remote Repository
The client that I am currently working for has a very strict process for approving the use of open source software and third party libraries. As a result, we basically have to allow access to only a single repository which a few developers have access to upload libraries and sync to other repositories. The hope is that developers won't be able to just add a new dependency to their project if the dependency isn't installed on the development repository. I am curious if anyone has run into this, and if so, how did you approach the problem? In addition, is it possible to override the SUPER POM? Thanks, jp4 -- View this message in context: http://www.nabble.com/Method-for-synching-Devlopment-Repository-to-Remote-Repository-tf2548291s177.html#a7102345 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Need Local Repository variable for ant script
Does anyone know if there is a variable which contains the location of the local repository. I am working with jibx and in order to create my jibx binding classes, I have to extract classes from a jar file located in the repository at compile time. I am using an ant script to do this and it works with a hard-coded location, but I need a better solution. Is there a way to get a specific dependency location to an ant script... For example, could I specify this jar file as a dependency and pass it's location to the ant script? jp4 -- View this message in context: http://www.nabble.com/Need-Local-Repository-variable-for-ant-script-tf2300661.html#a6393855 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need Local Repository variable for ant script
I am getting closer, only problem is that variable has some extraneous characters in it... Looks like this [local] - file:///home/jpfeifer/.m2/repository Eric Redmond wrote: Yes you could, assuming you're executing your ant script within Maven (with antrun, or as a plugin); You can find the repository location via the localRepository property. Eric On 9/19/06, jp4 [EMAIL PROTECTED] wrote: Does anyone know if there is a variable which contains the location of the local repository. I am working with jibx and in order to create my jibx binding classes, I have to extract classes from a jar file located in the repository at compile time. I am using an ant script to do this and it works with a hard-coded location, but I need a better solution. Is there a way to get a specific dependency location to an ant script... For example, could I specify this jar file as a dependency and pass it's location to the ant script? jp4 -- View this message in context: http://www.nabble.com/Need-Local-Repository-variable-for-ant-script-tf2300661.html#a6393855 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Eric Redmond http://codehaus.org/~eredmond -- View this message in context: http://www.nabble.com/Need-Local-Repository-variable-for-ant-script-tf2300661.html#a6394445 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Locally Patched Maven War Plugin
I have patched the Maven War Plugin locally and installed it into my local repository with mvn install. I bumped the version from 2.0.1 to 2.0.2. It works fine when installed in the local repository, but when I upload to the development repository, other developers can't seem to get it to work. When they run a mvn -U install they get the following. I am hoping that someone can help me understand what maven is trying to do here. Which checksums is it comparing? Can I disable the central repo from the Super POM? [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-surefire-plugin:maven-plugin:2.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates from devrepo [DEBUG] Skipping disabled repository codehaus-snapshots [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '867df7ba2a0c81782ac0fb14db5ccda5f85f5d42'; remote = '3009ca8b79c340cc83543ea789f57b1ee0128cb6' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '867df7ba2a0c81782ac0fb14db5ccda5f85f5d42'; remote = '3009ca8b79c340cc83543ea789f57b1ee0128cb6' - IGNORING [DEBUG] maven-war-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-war-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-war-plugin:pom:LATEST [DEBUG] maven-war-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-war-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-war-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-war-plugin' does not exist or no valid version could be found -- View this message in context: http://www.nabble.com/Locally-Patched-Maven-War-Plugin-tf2277436.html#a6324861 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Modified WAR Plugin
How do you refer to the new plugin in your pom.xml file? I thought that a project of packaging typewar/type will automatically use the default war plugin... How did you override this behavior? jp4 Max Cooper wrote: My project was using a modified version of the war plugin for a while. I decided that the best solution was to make the plugin another module in our project. This solution seemed easier than managing a release process for the modified plugin separately, or requiring team members to do something unusual like installing it themselves. We have since removed the plugin from our file tree because the released version now does what we need. It all went pretty smoothly. You might find that making the modified plugin just another module in your project to be the best solution. -Max jp4 wrote: I recently modified the maven-war-plugin source to accomodate some changes that I needed to support axis2. I submitted this code for inclusion into the next version of the plugin, but until that time I need to distribute the plugin to everyone on my development team. I can install it into the local repository and it works fine, but if I try to upload it to our development repository (internally) I can't seem to get the plugin to update. I have included the development repository in the settings.xml and have tried using 2.0.1-SNAPSHOT as well as 2.0.2 versions. I seem to get the same problem listed below. Can I disable the Super POM plugin repo? Having each developer install the plugin locally isn't really an option so I have to be able to distribute this via our development repository. I have also tried using the explicit plugin version in our root POM file and I get the same error. Any help would be greatly appreciated. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates from devrepo [DEBUG] Skipping disabled repository codehaus-snapshots [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '867df7ba2a0c81782ac0fb14db5ccda5f85f5d42'; remote = '3009ca8b79c340cc83543ea789f57b1ee0128cb6' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '867df7ba2a0c81782ac0fb14db5ccda5f85f5d42'; remote = '3009ca8b79c340cc83543ea789f57b1ee0128cb6' - IGNORING [DEBUG] maven-war-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-war-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-war-plugin:pom:LATEST [DEBUG] maven-war-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-war-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-war-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-war-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-war-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1011) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:453) Thanks, JP4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Modified-WAR-Plugin-tf2268007.html#a6305302 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Modified WAR Plugin
I recently modified the maven-war-plugin source to accomodate some changes that I needed to support axis2. I submitted this code for inclusion into the next version of the plugin, but until that time I need to distribute the plugin to everyone on my development team. I can install it into the local repository and it works fine, but if I try to upload it to our development repository (internally) I can't seem to get the plugin to update. I have included the development repository in the settings.xml and have tried using 2.0.1-SNAPSHOT as well as 2.0.2 versions. I seem to get the same problem listed below. Can I disable the Super POM plugin repo? Having each developer install the plugin locally isn't really an issue, so I have to be able to distribute this via our development repository. I have also tried using the explicit plugin version in our root POM file and I get the same error. Any help would be greatly appreciated. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates from devrepo [DEBUG] Skipping disabled repository codehaus-snapshots [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates from central [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '867df7ba2a0c81782ac0fb14db5ccda5f85f5d42'; remote = '3009ca8b79c340cc83543ea789f57b1ee0128cb6' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '867df7ba2a0c81782ac0fb14db5ccda5f85f5d42'; remote = '3009ca8b79c340cc83543ea789f57b1ee0128cb6' - IGNORING [DEBUG] maven-war-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-war-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-war-plugin:pom:LATEST [DEBUG] maven-war-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-war-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-war-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-war-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-war-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1011) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:453) Thanks, JP4 -- View this message in context: http://www.nabble.com/Modified-WAR-Plugin-tf2268007.html#a6294602 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
