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
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
woops, forgot to cc the group
-- Forwarded message --
From: Eric Redmond [EMAIL PROTECTED]
Date: Feb 28, 2007 11:53 AM
Subject: Re: [m2] POM Inheritance
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
There's not much more to say about it.
Create a pom.xml of packaging pom
Give
Will this work? I do not know.
Introduce a third pom (the data access pom) as a new module of the original
parent. The original parent pom remains unchanged except for the addition
of the new data access pom module. The new data access pom declares data
access dependencies. The data access
Will this work? I do not know.
Introduce a third pom (the data access pom) as a new module of the original
parent. The original parent pom remains unchanged except for the addition
of the new data access pom module. The new data access pom declares data
access dependencies. The data access
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
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:
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
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
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
Hi all,
I have this directory layout:
projects
parent-proj
pom.xml
sub-proj
pom.xml
In parent-proj/pom.xml I have defined
modules
module../sub-proj/module
/modules
In sub-proj/pom.xml I have defined
parent
...
: John Casey [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 05, 2005 3:01 AM
To: Maven Users List
Subject: Re: [m2] POM inheritance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright, this is the part where I print a complete retraction
of everything I just emailed
this up for the user docs.
Definitely need this clarification
jmp
-Original Message-
From: Peter van de Hoef [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 27, 2005 6:32 PM
To: Maven Users List
Subject: Re: [m2] POM inheritance
Hi John,
Thanks for your help. So pluginManagement
To: Maven Users List
Subject: Re: [m2] POM inheritance
Hi John,
Thanks for your help. So pluginManagement is used for
specifying plugin versions and configuration parameters,
whether they are used or not. This will be inherited by child
projects. The plugins section is just a list of plugins
, 2005 3:01 AM
To: Maven Users List
Subject: Re: [m2] POM inheritance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright, this is the part where I print a complete retraction
of everything I just emailed to the list... :)
Next time, I promise, I'll actually re-read the code and/or
do
] POM inheritance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright, this is the part where I print a complete retraction
of everything I just emailed to the list... :)
Next time, I promise, I'll actually re-read the code and/or
do some Right-Click - References - Project in Eclipse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll try to put together a test and fix whatever's causing this. Hate to
say this again, but would you mind submitting a JIRA issue for it? :)
That'll remind me.
Peter van de Hoef wrote:
Hi John,
Thanks for your help. So pluginManagement is used
That's all right, no problem. In that way I can add a small contribution to the
great work you are doing!
I will add some test files as attachment.
John Casey wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll try to put together a test and fix whatever's causing this. Hate to
say this
need this clarification
jmp
-Original Message-
From: Peter van de Hoef [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 27, 2005 6:32 PM
To: Maven Users List
Subject: Re: [m2] POM inheritance
Hi John,
Thanks for your help. So pluginManagement is used for
specifying plugin
-Original Message-
From: Peter van de Hoef [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 27, 2005 6:32 PM
To: Maven Users List
Subject: Re: [m2] POM inheritance
Hi John,
Thanks for your help. So pluginManagement is used for
specifying plugin versions and configuration parameters
PM
To: Maven Users List
Subject: Re: [m2] POM inheritance
Hi John,
Thanks for your help. So pluginManagement is used for
specifying plugin versions and configuration parameters,
whether they are used or not. This will be inherited by child
projects. The plugins section is just a list of plugins
To: Maven Users List
Subject: Re: [m2] POM inheritance
Hi John,
Thanks for your help. So pluginManagement is used for
specifying plugin versions and configuration parameters,
whether they are used or not. This will be inherited by child
projects. The plugins section is just a list of plugins
Hi all,
I have a question about which elements of the POM are inherited by
derived POM's.
In my parent POM I have a build section which specifies the source
directory and some parameters for the java compiler:
build
sourceDirectorysrc/sourceDirectory
plugins
plugin
Okay, I have added the issue: http://jira.codehaus.org/browse/MNG-357
Thanks for your time!
- Peter
John Casey wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's entirely possible that our inheritance mechanism isn't completely
right on this...can you please file a JIRA issue, and I'll look
On Tue, 2005-04-26 at 21:00 +0200, Peter van de Hoef wrote:
Hi all,
I have a question about which elements of the POM are inherited by
derived POM's.
The law on inheritance resides here:
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-
Thanks for your reply.
Now I see why the complete build section is inherited when it is
absent in the child:
*if* ( childBuild == *null* )
{
child.setBuild( parentBuild );
}
*else*
{
/// A lot of fields are inherited, except plugins
/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, I forgot all about the design decisions surrounding this... :)
Actually, our original decision was to disallow inheritance of any
plugin configuration, since plugin configuration can (and usually will)
modify the build lifecycle for that
AM
To: Maven Users List
Subject: Re: [m2] POM inheritance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, I forgot all about the design decisions surrounding this... :)
Actually, our original decision was to disallow inheritance
of any plugin configuration, since plugin
27, 2005 8:14 AM
To: Maven Users List
Subject: Re: [m2] POM inheritance
Sorry, I forgot all about the design decisions surrounding this... :)
Actually, our original decision was to disallow inheritance
of any plugin configuration, since plugin configuration can
(and usually will) modify
I actually am working on doco for the various management
features. I know this is vital, and it's not escaping in the
confusion. The documentation is coming, please bear with us.
This is still pre-beta software, after all...
Totally understood, hence the offer of help. I very much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've started writing a large-project management overview, and I'm queued
up on the managedDependencies doc (I have a blog entry waiting to go out
for when it's done ;)
Beyond that, pleased to have the help!
- -john
Brett Porter wrote:
Being
Tell me when we should take this off-list, but are:
# plugin management
# plugin configuration
safe areas to work? That is the basic topic we were
discussing.
Also what format should I work in?
Cheers,
jmp
--- John Casey [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think those are perfect places to start, and we're working in xdoc.
dunno if you're familiar with that from m1, but it's a modified version
of html with some shorthands for document layout...let me know if you
have questions.
Brett, any other
33 matches
Mail list logo
