This only imports Spring Boot dependencyManagement, and it looks like the
thread starter would also like access to the plugins configured by
spring-boot-parent. He’d have to duplicate Spring Boot's plugin configuration
in his own project.
Nils.
> Op 5 dec 2023, om 15:11 heeft Francois Marot
For the record, Spring Boot has no hard requirement of using a 'parent'
pom. It is just a bit simpler and in most of the examples online.
But you can simply set the scope import in your dependencyManagement. This
works.
org.springframework.boot
spring-boot-dependencies
Howdy,
For importing plugins there was even some PoC like this:
https://github.com/apache/maven/pull/1190
Also, planned for maven4 to (or already is, Guillaume?) support mixins.
HTH
T
On Tue, Dec 5, 2023 at 12:51 PM Bernd Eckenfels
wrote:
> Hello,
>
> I think that’s a long-standing
Hello,
I think that’s a long-standing restriction of mavens Pom-model, not sure it can
easily be solved. Spring boot (and other frameworks) did not make the situation
easier with their parent requirement (but then again there is not much
alternatives).
>From my experience it seems a good idea
In my current project i'm working we already have a parent POM that I
should be inheriting from, but when trying to integrate the spring boot I
come into an issue that I should inherit their super pom instead of using
our own. For dependencies its pretty simple - you use the import scope, but
what
havior between inheritance and -dtest with
surefire
Howdy,
unrelated to your question, and unsure if this is intentional from your
side, but Maven user properties (like the "test" is) on CLI should be set
using "-Dtest=foo" (uppercase letter D) and not "-dte
Hello,
I actually used -Dtest=foo. Sorry for the confusion.
Kim
On Wed, Feb 22, 2023 at 12:19 PM Tamás Cservenák
wrote:
> Howdy,
>
> unrelated to your question, and unsure if this is intentional from your
> side, but Maven user properties (like the "test" is) on CLI should be set
> using
Howdy,
unrelated to your question, and unsure if this is intentional from your
side, but Maven user properties (like the "test" is) on CLI should be set
using "-Dtest=foo" (uppercase letter D) and not "-dtest=foo" as you wrote.
HTH
T
On Wed, Feb 22, 2023 at 5:43 PM DJ Kim wrote:
> Hi there,
>
Hi there,
Yesterday I posted a question about -dtest.
To give a bit more of a context. I have a child class that extends parent,
and I would only like to run -dtest=childclass#MethodinheritedfromParent.
Unfortunately, the surefire executed all the test cases inherited from
parent (unexpected
Subject: Re: Parent pom plugin inheritance
The plugins you've listed are default plugins included in maven
configuration. Whether you declare them or not, they will get included
regardless, though not always with the version you'll want. It's not
necessary to reference the elements in management
nt pom inheritance.
> When I first set things up, I put the common plugins in the parent pom under
> the plugingManagement tags and things are working fine (with no plugins in
> the child poms)
>
> But in my research of all things maven I came across a few learnings that say
&g
I am new to Maven and doing a lot of learning about Parent pom inheritance.
When I first set things up, I put the common plugins in the parent pom under
the plugingManagement tags and things are working fine (with no plugins in the
child poms)
But in my research of all things maven I came
> Is it because the oci-java-sdk is 2 hops from my pom and the jackson-bom
is 3 hops?
Yes, my experience tells that the distance from your pom matters.
> Is there anything I can do to control this such that the versions defined
in my parent "win"?
No, I think you can only import jackson-bom of
I'm quite interested in this conversation as in my experience the process
of producing & consuming BOMs is still misunderstood.
Regarding 3rd party dependencies in a BOM, I've seen 2 main usages of BOMs.
- library BOM: defines *only* those modules belonging to the same
multi-project. Examples:
Actually, I'd say those BOMs probably shouldn't declare jackson. The
project's dependencies should be enough, and you explicitly declare the
version you need/want to use.
In the case of the OCI BOM, it seems quite clear that it mistakenly
inherits dependency management from it's parent POM: most
Not sure the behavior in your particular case is exactly documented. but it
is sure that the depth in the dependency tree and order at the same level
plays a role.
You can find some hints inside an Andres Almiray blog post:
http://andresalmiray.com/maven-dependencies-pop-quiz-results/
One
Hi,
I have the following structure in my pom:
My pom <- import oci-java-sdk-bom <- parent = ocj-java-sdk
^
|
parent = spring-boot-starter-parent
^
|
parent = spring-boot-dependencies <- import jackson-bom
Both jackson-bom and oci-java-sdk have a dependency management section and
declare
I have just started understanding maven.I was curious how to decide whether
our element in child pom will override the parent pom detail or just get
added along with the parent pom inherited elements in child pom.
Let us take an example to understand :
For example, each dependency is uniquely
to work in multi-module sites using
inheritance as described here
(https://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html).
Here (https://maven.apache.org/plugins/maven-site-plugin/migrate.html)
it is stated that interpolation is now done after inheritance and new
early
Hi!
I'm having trouble to understand how maven site descriptor interpolation
is designed to work in multi-module sites using inheritance as described
here
(https://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html).
Here (https://maven.apache.org/plugins/maven-site-plugin
juin 2014 14:52:12 Benson Margulies a écrit :
What do you think of an element in site.xml that turns off all
inheritance? The case I'm dealing with is a project that wants to
inherit build stuff from a parent but not site stuff. I'll tackle this
if you think it's reasonable.
On Sat, Jun
/doxia-sitetools/doxia-decoration-model/decorat
ion.html
tell me if you need help
Regards,
Hervé
Le samedi 14 juin 2014 14:52:12 Benson Margulies a écrit :
What do you think of an element in site.xml that turns off all
inheritance? The case I'm dealing with is a project that wants
14:52:12 Benson Margulies a écrit :
What do you think of an element in site.xml that turns off all
inheritance? The case I'm dealing with is a project that wants to
inherit build stuff from a parent but not site stuff. I'll tackle this
if you think it's reasonable.
On Sat, Jun 14, 2014
inheritance? The case I'm dealing with is a project that wants to
inherit build stuff from a parent but not site stuff. I'll tackle this
if you think it's reasonable.
On Sat, Jun 14, 2014 at 12:58 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
you can't inherit nothing with what has beed coded
I think it could go in the site plugin doc; I'm willing to do some writing.
Even after reading the JIRA, I don't know how to express, I don't
want to inherit any breadcrumbs at all all.
On Fri, Jun 13, 2014 at 2:04 AM, Hervé BOUTEMY herve.bout...@free.fr wrote:
true that there isn't much doc on
you can't inherit nothing with what has beed coded in MSITE-582: the top
breadcrumb will always be there
if you really need to drop absolutely everything, we need a new feature
notice there are a lot of new features in maven-site-plugin 3.4-SNAPSHOT,
waiting for a release (with Doxia, Doxia
What do you think of an element in site.xml that turns off all
inheritance? The case I'm dealing with is a project that wants to
inherit build stuff from a parent but not site stuff. I'll tackle this
if you think it's reasonable.
On Sat, Jun 14, 2014 at 12:58 PM, Hervé BOUTEMY herve.bout
that turns off all
inheritance? The case I'm dealing with is a project that wants to
inherit build stuff from a parent but not site stuff. I'll tackle this
if you think it's reasonable.
On Sat, Jun 14, 2014 at 12:58 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
you can't inherit nothing with what
true that there isn't much doc on this
any idea on how/where to document this site.xml inheritence is welcome
Regards,
Hervé
Le jeudi 12 juin 2014 09:14:06 Andreas Sewe a écrit :
Hi,
that wasn't possible during my time of activity, not sure if anything
changed since:
Hi,
that wasn't possible during my time of activity, not sure if anything
changed since:
http://mail-archives.apache.org/mod_mbox/maven-users/201104.mbox/%3c4da464c8.2060...@apache.org%3E
yes, https://jira.codehaus.org/browse/MSITE-582 got fixed and I have
used the fix successfully in one of
Is there a way to reset the breadcrumbs and not inherit them from a parent/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
that wasn't possible during my time of activity, not sure if anything
changed since:
http://mail-archives.apache.org/mod_mbox/maven-users/201104.mbox/%3c4da464c8.2060...@apache.org%3E
Cheers,
-Lukas
Am 12.06.2014 04:52, schrieb Benson Margulies:
Is there a way to reset the breadcrumbs and
Hi there,
Met an interesting question recently about plugin inheritance and hope you
could give me some feedback :)
At first, I define two maven java doc plugin inside the reporting tag and used
to generate different type of javadoc, one for standard javadoc and for
customize one.
Later, I
At first, I define two maven java doc plugin inside the reporting tag and
used to generate
different type of javadoc, one for standard javadoc and for customize one.
FYI: I don't use much of the reporting functionality in Maven, just the basics.
Later, I want to move those two javadoc plug
Hi Wayne,
Thanks, will try today.
Br,
Tim
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: den 24 februari 2014 23:11
To: Maven Users List
Subject: Re: Rule for maven plugin inheritance
At first, I define two maven java doc plugin inside the reporting tag
, scm, mailing lists, and so on),
only really make sense for the project as a whole. Is there any way to avoid
creating them for all of the sub-projects without a separate site.xml for each
project? I tried disabling inheritance, but all that did was cause all of the
subproject sites to revert
are
guaranteed to fail - unless someone overrides many plugin versions and
configuration).
Regards,
/James
[1] http://maven.apache.org/pom.html#Inheritance
[2] http://jira.codehaus.org/browse/MNG-2423
It is strange from one PoV but not so strange from another. The docs should
probably be fixed. And if we ever do get a chance to rev up the model
version, we should probably split it into one pre-req for inheritance and a
separate one for consuming as a dependency and a final one (corresponding
...@gmail.com]
Sent: 14 March 2013 12:12
To: Maven Users List
Subject: Re: prerequisites pom inheritance
It is strange from one PoV but not so strange from another. The docs should
probably be fixed. And if we ever do get a chance to rev up the model
version, we should probably split it into one
Hello,
I try to port an existing ANT based build system to Maven.
I set in my root POM (A) the org.codehaus.mojo:properties-maven-plugin
to read all required properties from an existing property file.
That works fine. But when I create a new Maven module (B) where I set
its parent to be A, it
. But when I create a new Maven module (B) where I set
its parent to be A, and this is a module of A, it complains that does
not find the property file.
Does exist the property inheritance in Maven?
Thoughts?
Graf László
Property inheritance works for properties you put into the properties
section of a parent pom.
The m-build-helper-p creates properties dynamically *after* maven already
executed pom parsing and property inheritance. I. e.: inheriting dynamic
properties does not work.
HTH
Ansgar
Am 07.02.2013 21
Am 07.02.2013 21:49 schrieb Ansgar Konermann
ansgar.konerm...@googlemail.com:
Property inheritance works for properties you put into the properties
section of a parent pom.
The m-build-helper-p
s/build-helper/properties/
creates properties dynamically *after* maven already executed pom
Please take a couple of minutes to read my answer to a very similar
question on stack overflow
http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072
It should hopefully make things a little clearer
-Stephen
On Thursday, 7 February 2013,
Hello,
I am trying to invoke a single goal before another (ant-based) Mojo
executes.
Due to http://jira.codehaus.org/browse/MNG-5405 I cannot just do
exeecutiongoalfoo:bar/goal/execution in the mojo.xml for the plugin.
So instead, I've defined a lifecycle.xml, with only one goal in it.
This
i was trying to extend a parent-defined profile in a child module, and then
found out its impossible (see a much ebtter description i found here -
http://www.dashbay.com/2011/03/maven-profile-inheritance/)
my question is will this ever be supported?
funny that a tool which has build code re-use
Hi there,
I've seen this topic debated many times, and still haven't figured
everything out. I was recently confused by the handling and
inheritance of urls in Maven. I think I got most of it, when it comes
to project.url.
Now, when it comes to deploying a site, I'm baffled. Up to
maven-site
Grégory Joseph wrote:
Hi there,
I've seen this topic debated many times, and still haven't figured
everything out. I was recently confused by the handling and
inheritance of urls in Maven. I think I got most of it, when it comes
to project.url.
Now, when it comes to deploying a site
Hi Lukas,
On 2 July 2012 13:18, Lukas Theussl ltheu...@apache.org wrote:
Grégory Joseph wrote:
It kind of sounds like MSITE-600 to me, so I'm unsure if/how the issue
was fixed. Example:
* Corporate parent pom defines this site deployment url:
prot://foo/${artifactId}/${version} -- it works
Just tried staging, and indeed, the paths in that case are correct* -
but again, I'm assuming that's because the normalization is done and
supported by my local FS ?
-g
* with the strange bug that https://nexus.domain.org/xyz; was
converted to targetstaging/http/s.domain.org/xyz ...
On 2 July
Grégory Joseph wrote:
Just tried staging, and indeed, the paths in that case are correct* -
but again, I'm assuming that's because the normalization is done and
supported by my local FS ?
IIRC normalization is done by the wagon you are using for the deploy, so
it's outside the realm of the
On 2 July 2012 14:38, Lukas Theussl ltheu...@apache.org wrote:
Grégory Joseph wrote:
Just tried staging, and indeed, the paths in that case are correct* -
I take it back. Staging was fine… with 2.1.1.
With 3.1 I get this, for example for last module of the multi-module build
[INFO] Pushing
that only
*one* parent POM is likely to be not enough for my purpose.
As pointed out by Curtis and Laird, my problem seems to boil down to a lack of
multi-inheritance and/or include mechanism.
By the way, bravo guys, you used the exact words I was trying not to hear. More
seriously, I didn't start
one set of configuration.
Hope this is a better explanation.
Then, about your proposals:
1. Inheritance does not necessarily follow aggregation.
That's right, I didn't think about aggregator POMs. Actually if properties
defined in an aggregator POM are accessible in the sub-modules
, inherit from one set of distribution management information, and
from one set of configuration.
Hope this is a better explanation.
Then, about your proposals:
1. Inheritance does not necessarily follow aggregation.
That's right, I didn't think about aggregator POMs. Actually if properties
inheritance in POMs—or
else a non-inheritance-based include mechanism. AFAIK, Maven does not have
either of those capabilities.
Just like in Java, which is also single-inheritance only, it can be
difficult or impossible to avoid code duplication in certain complex cases.
But in my experience it is fairly
(or whatever)
and you don't want to keep specifying those plugins over and over and over
again for your various JPA projects. Just an example.
You can repeat this as many levels deep as you want.
Finally at the end of the inheritance stack here you would have a project
pom.xml that would inherit from one
start wondering if I'm not asking maven more than it can manage.
Not the first time I struggle with its poor inheritance capabilities and the
lack of an include feature (heard about mixins, but seems it won't be there
before a long time).
Thanks in advance to all people who will reach the end
.
So this is not working either.
Now, I start wondering if I'm not asking maven more than it can manage.
Not the first time I struggle with its poor inheritance capabilities and the lack of an
include feature (heard about mixins, but seems it won't be there before a
long time).
Thanks in advance
Hello Ron,
I'm not sure I understand what you meant...
My problem is all about the POMs, that is, how can I share pieces of
configuration (i.e pieces of POM file) between bundles, the main problems being
that I have not a single inheritance chain (because of project specific
deployment
My problem is all about the POMs, that is, how can I share pieces of
configuration (i.e pieces of POM file) between bundles, the main problems
being that I have not a single inheritance chain (because of project specific
deployment properties and target specific configuration).
I'm not sure
Hello all,
I have a project with a parent pom and child modules. Configuration
properties are kept in a build.properties file and an overriding
custom.build.properties. The properties-maven-plugin is defined in the
parent pom to load these properties, and the plugin is inherited by the
child
are off the reservation there already.
That plugin is against the Maven design, at least as far as property
inheritance is concerned, only bugs in Maven 2 may have let you away
with that for now.
parent pom to load these properties, and the plugin is inherited by the
child poms. Property
the reservation there already.
That plugin is against the Maven design, at least as far as property
inheritance is concerned, only bugs in Maven 2 may have let you away
with that for now.
parent pom to load these properties, and the plugin is inherited by the
child poms. Property substitution based
the Maven design, at least as far as property
inheritance is concerned, only bugs in Maven 2 may have let you away
with that for now.
parent pom to load these properties, and the plugin is inherited by the
child poms. Property substitution based on these files is used directly
in
the parent
[This mainly applies to the project-info-reports plugin]
The reporting/plugins/plugin entries support the inherited element;
if set to false, child projects don't inherit the plugin settings,
i.e. the parent can disinherit the child.
Is the reverse also possible, i.e. given a parent pom, can a
no, the child can override, that's all
see MNG-2807 for the same about CI management, or MNG-3124 for mailing lists
there is an inheritance configuration pattern to find then apply on many
elements of the pom.
If you have an idea about something easyto understand from a user
perspective
On 10 September 2011 15:39, Hervé BOUTEMY herve.bout...@free.fr wrote:
no, the child can override, that's all
Don't understand what you mean by that.
see MNG-2807 for the same about CI management, or MNG-3124 for mailing lists
there is an inheritance configuration pattern to find then apply
Hello,
I am not sure whether to choose inheritance or aggregation or both for my
maven project.
I have a domain module which contains entity classes. I have a service
module which contains spring services and daos and finally I have a web
module .
Can anyone provide guidelines please?
Regards
You most likely would like a parent project (inheritance) where you define
and control common stuff, like plugin configuration. Then you also most
likely want to an aggregating project to simplify build. Both could be
combined in the same Maven project.
/Anders
On Mon, Jul 18, 2011 at 18:52
thanks Anders. that's what I am going to do.
2011/7/18 Anders Hammar and...@hammar.net
You most likely would like a parent project (inheritance) where you define
and control common stuff, like plugin configuration. Then you also most
likely want to an aggregating project to simplify build
Hello everybody,
I have a problem with inheritance of dependencies from the parent pom. I
have a multi-module project. The situation is that I need 2 jdbc drivers: an
older version (9.xxx) and a newer version (10.xxx). I declared these
dependencies in the parent pom like
for org.example:site and org.example:parent, respectively. Note that
these two trails do not mirror the project's inheritance tree, but
rather the users' expectations (org.example:site is the main website
artifact, after all).
But no matter what breadcrumbs I define in the site.xml of both
projects
breadcrumbs. What I want to generate
are the following two breadcrumb trails:
Example.org Site
and
Example.org Site Example.org Parent
for org.example:site and org.example:parent, respectively. Note that
these two trails do not mirror the project's inheritance tree, but
rather the users
Hi Lukas,
Which version of the site plugin are you using? Please try latest
snapshots (2.3- or 3.0-beta-4-) and report back.
thanks for the quick reply. Forget to mention that I am using
3.0-beta-4-SNAPSHOT under Maven 3.0.3. Sorry about that.
Best wishes,
Andreas
Parent
for org.example:site and org.example:parent, respectively. Note that
these two trails do not mirror the project's inheritance tree, but
rather the users' expectations (org.example:site is the main website
artifact, after all).
But no matter what breadcrumbs I define in the site.xml of both
Hi Lukas,
Two things:
1) breadcrumbs always get appended, you cannot override or remove a
breadcrumb that has been added in a parent
Yes, this explains why we have breadcrumb trails like the following.
Apache Maven Apache Maven Site
Here, both Maven and Apache Maven Site point to the
if it is inherited
and not explicitly set it in the sample-project's POM).
I understand that maven does inheritance before interpolation, so as
the scm-loc property is set in the sample-project's POM I would expect
all expansions of the property to have the value defined in the POM.
What am I
a trailing
c-p-p-p/sample-project (as does the project URL if it is inherited
and not explicitly set it in the sample-project's POM).
I understand that maven does inheritance before interpolation, so as
the scm-loc property is set in the sample-project's POM I would expect
all expansions
of the effective POM have a trailing
c-p-p-p/sample-project (as does the project URL if it is inherited
and not explicitly set it in the sample-project's POM).
I understand that maven does inheritance before interpolation, so as
the scm-loc property is set in the sample-project's POM I would expect
as I would expect.
- All URLs in the SCM section of the effective POM have a trailing
c-p-p-p/sample-project (as does the project URL if it is inherited
and not explicitly set it in the sample-project's POM).
I understand that maven does inheritance before interpolation, so
Hi Anders,
On Thu, 2011-04-07 at 14:26 +0200, Anders Hammar wrote:
First of all, I think that you're addressing the (what I call) developer way
by adding properties for many tings. Even if this would work, it makes the
poms difficult to read and understand.
What I'm trying to do is to make the
Hi Wolf,
Wolf Geldmacher wrote:
Hi Jörg,
Thanks for the answer.
Can you point me to a place where this behaviour is documented?
It seems to hold for most, but not all URLs, i.e. scm, project URL and
documentation site URL (except for the webAccessUrl of the
Hi all,
I have a question regarding property interpolation and inheritance in
the case of site descriptors. I looks to my like these behave
differently than property interpolation and inheritance in the case of
the POM.
Suppose I have the following element within my parent project's
That's an old bug: http://jira.codehaus.org/browse/MSITE-135
I am currently looking at site inheritance issues, maybe I'll get to it...
-Lukas
Andreas Sewe wrote:
Hi all,
I have a question regarding property interpolation and inheritance in
the case of site descriptors. I looks to my like
Hi Lukas,
That's an old bug: http://jira.codehaus.org/browse/MSITE-135
*sigh* I should really check the issue tracker first. :-(
I am currently looking at site inheritance issues, maybe I'll get to it...
That would be great. Thanks.
Andreas
library. It doesn't seem
to activate the win32 profile in the SWT project. Any ideas?
Gili
--
View this message in context:
http://maven.40175.n5.nabble.com/POM-inheritance-breaks-build-tp3263869p3309523.html
Sent from the Maven - Users mailing list archive at Nabble.com
-plugin to download and unpack the JAR file. To do the latter, I
need the classifier name in the child project.
Thanks,
Gili
--
View this message in context:
http://maven.40175.n5.nabble.com/POM-inheritance-breaks-build-tp3263869p3309568.html
Sent from the Maven - Users mailing list archive
POM inheritance causes builds to break.
Given three POM files:
* C depends on B.
* B inherits from A.
* I can build A and B
* C fails to resolve properties defined in A or B, and as a result
fails
to locate its transitive dependencies. The build breaks.
Please help!
Thanks
cowwoc wrote:
Hi Zac,
I added:
properties
swt.classifierwin32-x86/swt.classifier
/properties
You can define this property in your settings.xmll in the appropriate
profile.
- Jörg
-
To unsubscribe, e-mail:
there is a better way?
Gili
--
View this message in context:
http://maven.40175.n5.nabble.com/POM-inheritance-breaks-build-tp3263869p3308116.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e
Hi Gili,
cowwoc wrote:
Jörg Schaible-3 wrote:
cowwoc wrote:
Hi Zac,
I added:
properties
swt.classifierwin32-x86/swt.classifier
/properties
You can define this property in your settings.xmll in the appropriate
profile.
- Jörg
Jörg,
Isn't one of the main selling
After reading about the pitfalls and spotty implementation of
pseudo-inheritance of profiles, I can report that it appears that for a
profile defined in a parent pom you can activate it from a child as long as
the child doesn't try to activate it using a property value.
So a profile defined
usage.
/Anders
On Thu, Dec 16, 2010 at 23:18, Laird Nelson ljnel...@gmail.com wrote:
After reading about the pitfalls and spotty implementation of
pseudo-inheritance of profiles, I can report that it appears that for a
profile defined in a parent pom you can activate it from a child as long
the problem?
Gili
--
View this message in context:
http://maven.40175.n5.nabble.com/POM-inheritance-breaks-build-tp3263869p3304793.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
in C's pom.
On Sat, Nov 13, 2010 at 11:42 AM, cowwoc cow...@bbs.darktech.org wrote:
Hi,
I've posted a simple testcase at
http://stackoverflow.com/questions/4171222/maven-depending-on-inheriting-artifact-causes-build-error
that demonstrates how POM inheritance causes builds to break.
Given
: Inheritance of distributionManagement
Date: Mon, 29 Nov 2010 17:07:56 +0100
Do the module projects declare a parent, from which the distMgmt will be
inherited?
/Anders (mobile)
Den 2010 11 29 16:27 skrev Pazmiño Mazón, Iván Andrés
iapm270...@sri.ad:
Hi,
I'm having problems with a composite maven 2
Hi,
I'm having problems with a composite maven 2 project. I have set up a
base project which carries the distributionManagement configuration.
When it's extended by another project without modules it works just
fine.
But now I happened to need to extend the base project from another
project
Do the module projects declare a parent, from which the distMgmt will be
inherited?
/Anders (mobile)
Den 2010 11 29 16:27 skrev Pazmiño Mazón, Iván Andrés iapm270...@sri.ad:
Hi,
I'm having problems with a composite maven 2 project. I have set up a
base project which carries the
On Thu, 11 Nov 2010 14:34:05 +0100
chemit che...@codelutin.com wrote:
Hi guys,
I was testing some of my mojo on windows platform (xp) and how
surprised I was to see there is some big problems.
I had some
[ERROR] 'dependencies.dependency.version' for
1 - 100 of 574 matches
Mail list logo
