-surefire-plugin .. (from super-pom) 2.17
I have no idea why it tells me that the super-pom defines 2.17, is this the
expected behavior? In the debug output the versions look better.
Greetings
Bernd
PS: I tested it with the following pom, settings file, empty local repo and
Hi Team,
I am getting following Exception, I don't understand why it's all of sudden
looking for
*super-pom-1.0.0.0-site_en.xml*<http://mavenrepo.mitchell.com/repo/com/mitchell/maven/apd/super-pom/1.0.0.0/super-pom-1.0.0.0-site_en.xml>
from
Artifactory. When i execute MA
Don't call this a "super pom"! It's a parent (pom). There is only ONE
Super-POM and it's part of Maven Core. Calling some other artifact a
super-pom will only confuse people.
/Anders
On Thu, Mar 29, 2012 at 02:47, Daivish Shah wrote:
> Hi,
>
> I am trying to
On Thu, Mar 29, 2012 at 11:17 AM, Daivish Shah wrote:
> Hi,
>
> I am trying to use the super POM in my all of the project and seems like
> PluginManagement doesn't work like this way.
>
> Super-Pom Project
>
> pom.xml
>
>
>
>
>
>
>
> or
Hi,
I am trying to use the super POM in my all of the project and seems like
PluginManagement doesn't work like this way.
Super-Pom Project
pom.xml
org.apache.maven.plugins
maven-javadoc-plugin
2.8.1
Using Super POM in my other project as followed.
pom.xml
com.
(and OS!) used in the enforcer rules, and setting these does
> make sure your build is reproducible.
Sounds like you want Enforcer to work like:
if version of plugin not in this pom, or a parent etc
and
maven version locked down
and
jdk version is locked down
and
maven super pom specifies vers
Comments inline.
Regards,
/James
>>2009/12/9 Nord, James :
>> I'm having a really strange error in Maven 2.2.1 and the enforcer plugin.
>>
>> Basically it appears as though the super pom is missing version definitions
>> for the following even thou
2009/12/9 Nord, James :
> I'm having a really strange error in Maven 2.2.1 and the enforcer plugin.
>
> Basically it appears as though the super pom is missing version definitions
> for the following even though they should be present according to the web
> documentati
Hi all,
I'm having a really strange error in Maven 2.2.1 and the enforcer plugin.
Basically it appears as though the super pom is missing version definitions for
the following even though they should be present according to the web
documentation (and performing a help:effective-pom shows
nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26674107.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
2.3
--
View this message in context:
http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26662106.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e
org.apache.maven.plugins
maven-resources-plugin
2.3
--
View this message in context:
http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26662106.html
Sent from the
Keith,
> Which version is reported by "mvn help:describe -Dplugin="?
My guess is that it is from , not
Paul
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.
ssage in context:
http://old.nabble.com/Plugin-version-in-SUPER-POM-simply-ignored%2C-with-trivial-pom.xml-tp26661071p26661657.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
espite 2.3 being specified
> in the super pom.
>
>
> My entire pom is this:
>
>
> 4.0.0
> com.redshiftsoft
> redshift-pom
> pom
> 1.0.0-SNAPSHOT
>
>
>
> mvn help:describe -Dplugin=resources
>
> Reports version 2.4.1
>
> HOW
maven-resources-plugin resolves to version 2.4.1 despite 2.3 being specified
in the super pom.
My entire pom is this:
4.0.0
com.redshiftsoft
redshift-pom
pom
1.0.0-SNAPSHOT
mvn help:describe -Dplugin=resources
Reports version 2.4.1
HOWEVER,
mvn help:effective-pom
This is absolutely intentional. The best practice is for you to
control your own versions. Yes the super pom introduces a bit of
stability, but at the cost of complacency. If you rely on the defaults
in the super pom it means in a year when you build with a different
version of maven, you have a
On Fri, 05 Jun 2009 14:12:50 -0500, dkowis wrote:
> Say I've got a super pom with a defined SCM section like so:
>
> scm:git:git://server/repos/${artifactId}.git
>
>
> Well in the child pom, it's taking the super pom's name and appending /
> child pom
Say I've got a super pom with a defined SCM section like so:
scm:git:git://server/repos/${artifactId}.git
Well in the child pom, it's taking the super pom's name and appending /
child pom's name.
Like so:
scm:git:git://server/repos/Super/Child.git
That's not what I w
Oh, BTW, when I do a maven clean, it removes the target/classes
folder. That is where maven is supposed to compile the classes. Do I
have to separately compile within Eclipse, or can maven do the compile
also?
On Feb 21, 2009, at 1:12 PM, Rusty Wright wrote:
John, go to sonatype.com and
Thanks,
I'm getting those printed out so I can read a bit more leisurely. I
finally copied the pom.xml to the directory above the various eclipse
projects and it seems to find them now. I keep getting errors now
about some of the tools ( plugins ) not finding VM software, and not
being
John, go to sonatype.com and look at their book;
http://www.sonatype.com/documentation/books
I was able to figure it out from that and they're good at exhorting you to use
best practices.
Another good online book is
http://www.exist.com/better-build-maven
John Wooten wrote:
Thanks,
I thi
Thanks,
I think the problem is not understand the life cycle of a maven build
and how these things relate.
So, as I understand it, you create a master pom, no modules, but
default information. Then mvn install it to put it into a
repository. It should be a "pop" package, though.
Then
On Sat, Feb 21, 2009 at 6:48 AM, John Wooten wrote:
> I have the following file structure:
>
> /Deep6MasterPOM
>pom.xml
> /Foundation
>pom.xml
>
> I have a local maven repository in ~woo/.m2/repository, of course.
>
> I'm trying to put a few common things into the Deep6MasterPOM li
">
4.0.0
com.areteq
Deep6MasterPOM
pom
../Foundation
0.0.1-SNAPSHOT
Deep6MasterPOM
http://maven.apache.org
This project provides a Super POM with the JDepend
plugin specified
Feb-20-2009
Mantis
http://localhost/~woo/mantis
Hi,
You could find a multimodule configuration for resources files (xml, txt
...) in the checkstyle plugin documentation.
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
This tips is to create a new maven module (jar) that will contains all your
resources
Hi,
i have a multimodule setup...
Now i have the following question:
I use a plugin (maven-license-plugin) in my parent pom and do the
configuration of it there as well. The configuration of it are in a
folder of this parent module
Parent
+--- Module A
+--- Module B
+--- confi
Hi all,
I would like to activate profile which is placed in super pom for using
it in child project.
The reason:
I would like to use common properties but depends on profile in many
child projects.
Sample situation:
- super pom:
myGroupId
superLevel
pom
...
mainDevProperties
e are ready to use JDK 1.5 by inheritance from a super POM. I'm
> having no luck, hence this post. I'm new to maven (thanks to this forum
> for telling me maven defaults to jdk 1.3) so super POMs are a little
> unfamiliar to me, from searching this forum I'm told that creat
You need to specify this pom as a element in your child
pom...simply adding it in the parent directory doesn't magically do it
for you ;-) Also, super-pom is normally reserved to mean the pom
included in the maven core...the true super pom. A more appropriate term
is a corporate pom for a
computer. Thank you.
-Original Message-
From: mikeottinger [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 24, 2008 4:06 PM
To: users@maven.apache.org
Subject: Adding maven-compiler-plugin to super POM
Hello, I'm trying to come up with a way such that new maven projects I
creat
Hello, I'm trying to come up with a way such that new maven projects I create
are ready to use JDK 1.5 by inheritance from a super POM. I'm having no
luck, hence this post. I'm new to maven (thanks to this forum for telling me
maven defaults to jdk 1.3) so super POMs are a little u
Here is what learned about my problem:
* It is certainly possible to have a child pom (extension) have a
different version that its parent pom (base) - (good!)
* My problem was due to use of variable ${pom.parent.version} within
dependencyManagement section. Apparently the variab
If this is not possible then whats is the best way to avoid duplication
of conetnt between base.pom and extension.pom?
Also please see a typo fix inline below...
Farrukh Najmi wrote:
Dear Colleagues,
I have two separate projects "base" and "extension".
Each project is really a multi-project
Dear Colleagues,
I have two separate projects "base" and "extension".
Each project is really a multi-project inheritance hierarchy.
Finally extension pom is a sub pom of base pom.
The pom inheritance is as follows:
base
base-sub1
base-sub2
extension
extension-sub1
extens
example?
Thanks
M-
- Original Message -
From: "Marcelo Alcantara" <[EMAIL PROTECTED]>
To: "Maven Users List"
Sent: Friday, February 15, 2008 3:24 PM
Subject: Re: Super POM location
> Ok! Thanks everybody for the promply respose!
>
> Regards,
>
>
Ok! Thanks everybody for the promply respose!
Regards,
Marcelo
On Fri, Feb 15, 2008 at 3:05 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> As already mentioned, there is a super pom (in the Maven jar itself),
> but you shoudn't be editing it. Instead you should make a top level
&g
As already mentioned, there is a super pom (in the Maven jar itself),
but you shoudn't be editing it. Instead you should make a top level
corporate pom and have all projects inherit from it (set as parent).
Wayne
On 2/15/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Ok, I'
35
To: Maven Users List
Subject: Re: Super POM location
actually, it does exist. if you look in the maven uber jar it's under
org.apache.maven.project
On Fri, Feb 15, 2008 at 10:30 AM, <[EMAIL PROTECTED]> wrote:
> I think the "super-pom" is the name for the concept of defaul
actually, it does exist. if you look in the maven uber jar it's under
org.apache.maven.project
On Fri, Feb 15, 2008 at 10:30 AM, <[EMAIL PROTECTED]> wrote:
> I think the "super-pom" is the name for the concept of default settings and
> there is no actual super pom.
&
Hi,
I searched a lot in the Internet but could not find this answer.
Where is the super pom located?
I have configurations that are for all projects that I wanted to setup in
it.
Thanks in advance.
--
Marcelo Alcantara
Senior Developer/Architect
I think the "super-pom" is the name for the concept of default settings and
there is no actual super pom.
The normal solution for your problem would be to create a corporate/company pom
and let all projects add it as their parent.
Hth,
Nick S.
-Original Message-
Fro
This is deep down in the maven-release code, so no, you don't have to adjust it.
Why are you using relativePath? If you remove it and do a mvn install the super
pom is copied to your local repository and found from there.
With regards,
Nick Stolwijk
-Original Message-
From: jav
g( 0, tagPath.length() - 1 );
}
>
.Where are placed this lines? in a maven-configuration fike?
.i must modify this..or is only the way that maven work with paths?
>Which will throw an exception if your trunkPath or tagPath is empty.
Is possible, that the tags in each sub-project are wrong?
g
Subject: FATAL ERROR on release:prepare with a super-pom
Hi folks,
I'm trying to do a mv nrelease:prepare from a super-pom that have a lsit of
proyects i want to release to the same version..
All was runing fine,asking the new version, the SCM TAG ..but just af
Hi folks,
I'm trying to do a mv nrelease:prepare from a super-pom that have a lsit of
proyects i want to release to the same version..
All was runing fine,asking the new version, the SCM TAG ..but just after
this i have a "FATAL ERROR" : java.lang.ArrayIndexOutOfBoundsE
Hello,
I would like to separate the reporting section for all of our projects
in a common configuration file or pom to keep the projects pom as simple
as possible.
I already created a hierarchy of poms (java-pom, maven-plugin-pom and so
on) for the different project types to externalize common s
gt; > On 3/22/07, Aravindhan Damodharan <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I'm using Maven 2.0.5 for dependency management in my Ant script.
> The
> > > ant script is a generic script which can be used to build multiple
> > >
API's which we have
planned
> to
> > manage using an internal central repository. So I created a Parent
POM
> > file for all the dependency API's in the central repository and a
> child
> > POM for each project to be built. The Child POM will have only the
> &g
oject to be built. The Child POM will have only the
> > dependencies required for a particular project.
> >
> > Now though I have Parent POM and a internal repository configured
> while
> > execution Maven tries to fetch certain missing pieces from the
> > http:
t; Now though I have Parent POM and a internal repository configured
while
> execution Maven tries to fetch certain missing pieces from the
> http://repo1.maven.org/maven2/. I learnt that this repository is
> configured in the Super POM and will be inherited by all the POM
files.
>
rent POM and a internal repository configured
while
> execution Maven tries to fetch certain missing pieces from the
> http://repo1.maven.org/maven2/. I learnt that this repository is
> configured in the Super POM and will be inherited by all the POM
files.
> I need to disable this
ttp://repo1.maven.org/maven2/. I learnt that this repository is
configured in the Super POM and will be inherited by all the POM files.
I need to disable this feature so that Maven should only refer to the
internal repository. I tried to get information through internet but I
wasn't able to get it.
certain missing pieces from the
http://repo1.maven.org/maven2/. I learnt that this repository is
configured in the Super POM and will be inherited by all the POM files.
I need to disable this feature so that Maven should only refer to the
internal repository. I tried to get information through intern
Hi all !!!
I would like to add the information about and
in somewhere in order to be common to all projects.
I know that is a super pom used by maven, but how can I customize that pom?
(where is it?).
Besides, does not get inherited, is
there a way to define that info in some other
We have a company super pom with no modules. Just common dependencies, java
compile version, etc.
It is included in all of our projects as parent.
However when I run mvn clean package on my project pom I get a warning in phase
site:attach-descriptor
saying that the parent pom does not exist
st be curious about the matter.
>>
>> a cup of Java, cheers!
>> Sha Jiang
>>
>>
>> Wayne Fay wrote:
>>>
>>> I wrote this email a long, long time ago. ;-)
>>>
>>> Since then, I have found out that there certainly is a re
n your own local project pom.xml file.
> Of course, I don't modify the POM.
> I just be curious about the matter.
>
> a cup of Java, cheers!
> Sha Jiang
>
>
> Wayne Fay wrote:
>>
>> I wrote this email a long, long time ago. ;-)
>>
>> Sinc
I just be curious about the matter.
a cup of Java, cheers!
Sha Jiang
Wayne Fay wrote:
>
> I wrote this email a long, long time ago. ;-)
>
> Since then, I have found out that there certainly is a real "super
> pom" which is in one of the Maven jars... forget which one, but
I wrote this email a long, long time ago. ;-)
Since then, I have found out that there certainly is a real "super
pom" which is in one of the Maven jars... forget which one, but you
can find it if you search the Maven jars. But you shouldn't extract
the file, edit, and add it
Hi Wayne,
I really don't understand your words.
If Super POM doesn't exist in my machine as a real and independent file,
then it may be built by source codes as a concept.
Does it means that if the concept of Super POM is changed, then the source
of Maven would be changed, too?
I cann
e.org
Subject: super pom filter
I have a pom that has a couple of modules, I would like to post a site
directly to my baseDir or more accurately my top most pom's directory. I
tried something like this in my top most pom:
test.site
Test Website
file:${baseDir
context:
http://www.nabble.com/super-pom-filter-tf2217708.html#a6142939
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Can Clover read your license file from the classpath ?
Then you could deploy your (jarred) license to your maven repo and add
it as a dependency to the clover plugin. See the checkstyle plugin
docs [1] for more information - it allows you to do a similar thing
with checkstyle configurations.
Tom
Could you just symlink the license file around to the various directories?
On 8/16/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
Set up Apache on your box and point it to the top root directory. Then
its always "online" and you're obviously "connected" to the server, so
you can use a URL to the file.
Set up Apache on your box and point it to the top root directory. Then
its always "online" and you're obviously "connected" to the server, so
you can use a URL to the file.
Wayne
On 8/16/06, Ingo Düppe <[EMAIL PROTECTED]> wrote:
This is not really a good solution, because then you have to be al
This is not really a good solution, because then you have to be always
online and must have contact to the server.
No other solution?
Regards,
Ingo
Emmanuel Venisse schrieb:
No you can't.
It would be better to use an url to reference your clover license file.
Emmanuel
No you can't.
It would be better to use an url to reference your clover license file.
Emmanuel
Ingo Düppe a écrit :
Hello,
is it possible in a multi module project to reference a directory in an
absolute manner of the super pom?
Independent of the current position I like to refere
Hello,
is it possible in a multi module project to reference a directory in an
absolute manner of the super pom?
Independent of the current position I like to reference a directory from
the top root directory of myproject.
For instance I have following project structure:
myproject
ost.com.au> cc:
Subject: RE:
Super Pom
Thanks Stephen,
Sending to maven users list for future reference.
Thanks
Lakshman
> -Original Message-
> From: Stephen Duncan [mailto:[EMAIL PROTECTED]
> Sent: Friday, 28 July 2006 12:09 PM
> To: Lakshman Srilakshmanan
> Subject: Re: Super Pom
>
> Yes. That "
Hi Stephen,
Thanks for your suggestion, I was coming to the same conclusion.
What puzzled me was the manual "Better Builds with Maven" pg 24, where they
refer to a "Super POM" that is implicitly inherited by all pom's. I guess this
is buried deep in the maven code so
ubject: RE: Super Pom
Hi Emmanuel,
Thanks for your reply.
The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html
describes how to include a customised checkstyle within a POM.
I need to know the location of the super POM itself, if one exists.
Thanks
Lakshman
>
You can choose to make a "super-pom" that all your projects inherit
from to provide common configuration.
- Stephen
On 7/26/06, Lakshman Srilakshmanan
<[EMAIL PROTECTED]> wrote:
Hi Emmanuel,
Thanks for your reply.
The http://maven.apache.org/plugins/maven-checkstyle-plugi
Hi Emmanuel,
Thanks for your reply.
The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html
describes how to include a customised checkstyle within a POM.
I need to know the location of the super POM itself, if one exists.
Thanks
Lakshman
> -Original Mess
appropriate place would be to include it in the super pom.
Unfortunately I don't seem to be able to find it. Could you please
direct me to where it is located.
Thanks
Lakshman
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Hi All,
I have used maven 1.x for a couple of years now and am in the process of
migrating to maven 2.x
I need to set some configuration globally (eg customised checkstyle). I
find the appropriate place would be to include it in the super pom.
Unfortunately I don't seem to be able to fi
The super POM is internal to Maven. I honestly don't know for certain if the
superPOM is a seperate file, or a conceptual thing, but I believe it is the
former, and this is probably it:
http://svn.apache.org/repos/asf/maven/components/trunk/maven-project/src/main/resources/org/apache/
No problem...
Are these two configured/setup/located differently?
-Original Message-
From: Eric Redmond [mailto:[EMAIL PROTECTED]
Sent: 10 July 2006 17:12
To: Maven Users List
Subject: Re: Super POM
Also, as an aside (sorry, I'm a stickler for correct terms!), there is a
diffe
Also, as an aside (sorry, I'm a stickler for correct terms!), there is a
difference between a super POM and a parent POM. The SuperPOM is the global
default for the whole Maven POM structure, and conceptually, the POM from
which all POMs inherit. A parent is just any POM that is interited
Hey Everyone,
Done it - Really appreaciate the help!
Kind regards,
--
Viz
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
ben short
Sent: 10 July 2006 14:19
To: Maven Users List
Subject: Re: Super POM
Viz
Heres one I have setup...
http
.org/browse/MNG-2308
The super-Pom should also be found vi parent-entries if it is one dir up or the
relativePath
entry is specified.
regards, carsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-m
Hi Arnuad,
When I create the new project for the super pom what archetypeArtefactId
should I use?
Kind regards,
--
Viz
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: 10 July 2006 14:12
To: Maven Users List
Subject: Re: Super POM
sorry, in the local repo it&#
element
module1
module2
Im still new to maven 2 also but i hope this gives you some ideas.
Ben
On 7/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi All,
I'm new to Maven and am struggling to create a super pom. I am involved in
a project which
There was a Bug that is fixed in 2.0.5 (I'm waiting for the public release, to
try it out :-) ):
http://jira.codehaus.org/browse/MNG-2308
The super-Pom should also be found vi parent-entries if it is one dir up or the
relativePath
entry is specified.
regards, carsten
On 10 Jul 2006 at
perPOM directory
Arnaud
On 7/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
> I'm new to Maven and am struggling to create a super pom. I am involved
> in
> a project which has a number of sub projects and would like to have a
> super
> pom
The parent POM must be deployed in your local repository to allow yours
subprojects to find it.
You just have to do :
mvn deploy
in the superPOM directory
Arnaud
On 7/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi All,
I'm new to Maven and am struggling to create a super
Hi All,
I'm new to Maven and am struggling to create a super pom. I am involved in
a project which has a number of sub projects and would like to have a super
pom for the general configs, which are inherited by the sub projects. The
problem is that I can create a super pom by hand, but w
Here is a god example of a organisational super pom
http://maven.sateh.com/repository/org/apache/apache/2/
I have created one for my compnay that contains the following...
internal-released
scp://192.168.6.194/var/mvn/internal-released
You confuse multi-modules project and super pom. A super pom doesn't
need to declare any modules. It is an independant project which has
its own version and distributed in your internal repository so that
any project can download whenever it needs it.
It should fix your problems.
On 6/
Dhananjay Nene wrote:
Although the question wasn't addressed to me, I have run into some
problems (hence the question in the first place) so just adding my 2c.
If the super pom modeled as a top level module (ie. each project
declares it as a parent), I get into a lot of issues when usin
What factors/bases should be taken into account when thinking to create
super POM or not? Create parent -> child model or not, especially if the
components also used in another different projects?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Car
t place) so just adding my 2c.
If the super pom modeled as a top level module (ie. each project
declares it as a parent), I get into a lot of issues when using the
release plugin for the individuaal projects (You can just try it out to
see what I mean). One of the issues I also get into is th
: Maven Users List
Subject: Re: How to implement an organisational super pom ?
Although the question wasn't addressed to me, I have run into some
problems (hence the question in the first place) so just adding my 2c.
If the super pom modeled as a top level module (ie. each project
declares
Although the question wasn't addressed to me, I have run into some
problems (hence the question in the first place) so just adding my 2c.
If the super pom modeled as a top level module (ie. each project
declares it as a parent), I get into a lot of issues when using the
release plugin fo
Nathan
What kind of problems did you ran into? I'm currently working on a super pom
for my company, but haven't seen any problems yet.
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: Beyer,Nathan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 20, 2006 1
s to generate POMs
in a certain fashion. For common "automated build" stuff use profile
settings for the build user.
-Nathan
-Original Message-
From: Dhananjay Nene [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 1:34 PM
To: Maven Users List
Subject: How to implement an o
assign a version to the common pom, and the release
management workflow tries to checkout a project corresponding to top
level pom which obviously fails in my case. How can I implement a common
pom (like the maven super pom) so that the common pom is used only for
inheritance, and each pom which
On 6/13/06, Stefan Hübner <[EMAIL PROTECTED]> wrote:
Hi Kenney,
2006/6/13, Kenney Westerhof <[EMAIL PROTECTED]>:
> On Mon, 12 Jun 2006, Stephen Duncan wrote:
>
>
Another advantage, more of convenience, of differ between parent and
aggregating pom: you can have the parent pom at the same level as
Hi Stephen,
2006/6/13, Stephen Duncan <[EMAIL PROTECTED]>:
I personally do more as you do.
I have team-wide "super-POMs" I have a primary one that has basic
url, issue management, etc. type settings. Then I have a "core" POM
with common dependencyManagment section to encourage use of the same
1 - 100 of 108 matches
Mail list logo
