Is there a best practices for using the extend tag in the POM?
My structure is something like:
holder-dir
Project1
project.xml
Project2
project.xml
Project3
project.xml
Some things are common between the projects (by convention, not by
using the extend). I wo
I like adding a pom to my Maven installation directory, share it in SCM and
then all projects can extend from the pom added to Maven by referering to it
as
${maven.home}/project.xml
I like to refer to this pom added to Maven as the program-level pom. Each
project extends the program-level pom
On 8/9/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> I like adding a pom to my Maven installation directory, share it in SCM and
> then all projects can extend from the pom added to Maven by referering to it
> as
> ${maven.home}/project.xml
> I like to refer to this pom added to Maven as t
Is there any way for dependency:copy-dependencies and
dependency:unpack-dependencies to consider parents (and all ancestors)
as dependencies?
Alternately, is there a way to automatically/implicitly add the parent
the parent as a dependency? I tried adding:
...
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith
Bonawitz
Sent: Thursday, May 08, 2008 12:06 PM
To: Maven Users List
Subject: dependency:copy-dependencies and parent projects
Is there any way for dependency:copy-dependencies and
dependency:unpack-dependencies to consider parents (and all ancestors
Hi,
I'm using a configuration with two base projects; BaseJava and BaseEJB
(extends BaseJava). I have configured the maven-site-plugin in the BaseJava
like this:
[BaseJava/pom.xml]:
.
.
org.apache.maven.plugins
maven-site
hi all,
i have a project with this structure
|_WebWorkMain
| WebWorkBackend
| WebWorkWebApp
in WebWorkBackend i have hibernate code (mappings generated via xdoclet
etc)..
WebWorkMain is the parent project, which has been laid out like that for
Eclipse.
whenever i
