classes which is
there inside in the maven-parent project.
2) can we able to create two war/jar(child and parent project separately)
files by running the child maven project only.please help me out ..
--
View this message in context:
http://www.nabble.com/Project-Inheritance-in-Maven
On Tue, Dec 23, 2008 at 8:36 AM, arun_rocky
arunkumarave...@cognizant.com wrote:
1) I have created a parent maven project and i called the pom.xml file in
child maven project.
by using the parent/parent. its working fine. but i cant able to
retrieve the user-created classes of parent maven
-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 24, 2008 4:09 PM
To: Maven Users List
Subject: Re: assembly plugin and project inheritance
Copy requires that the artifact must be in the local repository or in a
remote repository.
The copy dependencies allows
Copy requires that the artifact must be in the local repository or in a
remote repository.
The copy dependencies allows for the artifact to come from the reactor, so
you don't have to install the artifact into your local repository.
The copy dependencies can be set to only copy one dependency.
If you do something like
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
*includeTypesassembly-descriptor**includeTypes*
...**
Thank you very much for your help, I can now have many projects generate
the right assembly with just one assembly descriptor and without
requiring to check out multiple projects (and having them at the right
position in the directory structure).
I don't understand your suggestion to use
You could attach the common descriptor as a build artifact one module, and
then use the dependency plugin to pull it down to each child module.
i.e.
Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a
classifier of, e.g. assembly-descriptor.
Now when you run mvn install or mvn
Thanks Stephen,
trying to follow the path you describe I added the following to the
parent-pom:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuild-helper-maven-plugin/artifactId
executions
execution
The version I posted doesn't work as the child-projects can't perform
the attach-artifact attached to the package phase.
I've now extracted the dist configuration and the attachment of it to a
separate project[1]. Having done this I also attached the copy and the
assembly goals to the compile
there are two sets of goals in the maven dependency plugin.
the first set are copy and unpack. you specify the artifacts inside
the plugin configuration. these are not the set you want. the set you
want are copy-dependencies (or something like that I am on my iPod so
you will have to check) with
Hello
I'm having many projects that share some dependencies and that should be
packaged the same way. So I wanted to have a parent project configuring
the maven-assembly-plugin.
I did this with the following in the parent pom:
plugin
artifactIdmaven-assembly-plugin/artifactId
Hi,
I do have a question regarding referencing the parent pom of a multi module project as
described in chapter 3 of Better Builds With Maven.
If a project consists of multiple modules (e.g.: api, core, model, ..), these modules reside in sub-directories of a top level directory. Each module
On 4/10/07, DI Kurt Edegger [EMAIL PROTECTED] wrote:
Hi,
I do have a question regarding referencing the parent pom of a multi module project as
described in chapter 3 of Better Builds With Maven.
If a project consists of multiple modules (e.g.: api, core, model, ..), these
modules reside in
Hi,
thank you Jerome for your fast response!
I'll check out that plugin.
Take care, Kurt
Jerome Lacoste schrieb:
On 4/10/07, DI Kurt Edegger [EMAIL PROTECTED] wrote:
Hi,
I do have a question regarding referencing the parent pom of a multi
module project as described in chapter 3 of Better
Hi,
I have a POM which is both a parent and a multi-module. When I build from
this POM I would like the plugins to be executed for the modules and not the
parent POM i.e. how can I supress the execution for the current POM but
still inherit the properties?
Aidan
: Project inheritance
Hi,
I have a POM which is both a parent and a multi-module. When I build from
this POM I would like the plugins to be executed for the modules and not the
parent POM i.e. how can I supress the execution for the current POM but
still inherit the properties?
Aidan
Hi,
A long time ago, this question was posted, but I can't find the answer
(if there was one?)
My primary goal is to create a WAR (don't need an EAR) that depends on
another WAR project...essentially extending that original project. I
want to include all the JSPs, etc from the parent WAR.
Hello all - I'm having a bit of trouble with three layers of pom files.
If I have:
pom.xml - pom.xml - pom.xml
what _should_ the parent tags look like?
In the top most one, I have:
groupIdlty/groupId
artifactIdapp/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
In the
Hello David,
Do you have inside a module A and s module B parent defined?
Something like this:
parent
groupIdyour parent groupid/groupId
artifactIdyour parent artifact id /artifactId
versionyour parent version/version
/parent
Taavi
Davis Ford wrote:
Hi, I have a parent pom.xml
yes, that is the way it is currently set up
On 5/17/06, Taavi Sildeberg [EMAIL PROTECTED] wrote:
Hello David,
Do you have inside a module A and s module B parent defined?
Something like this:
parent
groupIdyour parent groupid/groupId
artifactIdyour parent artifact id /artifactId
Hi, I have a parent pom.xml project in C:\someplace\pom.xml that has
modulemoduleA/module
modulemoduleB/module
Then I have
C:\someplace\moduleA\pom.xml
C:\someplace\moduleB\pom.xml
If I execute:
C:\someplace\mvn clean
C:\someplace\mvn compile
C:\someplace\mvn test
That works great for
21 matches
Mail list logo
