That's not an exception to the inheritence rule described.
On 11/21/05, Jörg Schaible [EMAIL PROTECTED] wrote:
Arik Kfir wrote on Friday, November 18, 2005 7:20 PM:
in m2 you can define the version once - in the parent POM via
a dependencyManagement section. All child POMs just state
the
Arik Kfir wrote on Friday, November 18, 2005 7:20 PM:
in m2 you can define the version once - in the parent POM via
a dependencyManagement section. All child POMs just state
the group artifact IDs, without the version (they inherit the
version from the parent).
Well, with exceptions:
This is a question for Maven 1 2, although I know that the answers will be
different.
Let's say that I have a multiproject with subprojects. Some build jars, one
builds a war, a couple that build an ejb jar and an ejb client jar, and one
builds an ear. Now let's say that I need the Spring jar in
in m2 you can define the version once - in the parent POM via a
dependencyManagement section. All child POMs just state the group
artifact IDs, without the version (they inherit the version from the
parent).
as for m1, I think it can only be done via a property...
On 11/18/05, Ballard, Ken
Ballard, Ken wrote:
This is a question for Maven 1 2, although I know that the answers will be
different.
Let's say that I have a multiproject with subprojects. Some build jars, one
builds a war, a couple that build an ejb jar and an ejb client jar, and one
builds an ear. Now let's say that I
Hi
I'm trying to create a maven project containing several components.
I've read:
http://wiki.codehaus.org/maven/CreatingJ2eeApplications
But here's my question:
Is it correct that the dependencies of jar files within a multiproject build
uses the maven.repo.local to interchange the results?
yes, that is correct.
On Thu, 29 Jul 2004 22:27:42 +0200, mr.x [EMAIL PROTECTED] wrote:
Hi
I'm trying to create a maven project containing several components.
I've read:
http://wiki.codehaus.org/maven/CreatingJ2eeApplications
But here's my question:
Is it correct that the dependencies
For now this is indeed the only way. That's essentially what the
multiproject:install goal does.
-john
On Thu, 2004-07-29 at 16:27, mr.x wrote:
Hi
I'm trying to create a maven project containing several components.
I've read:
http://wiki.codehaus.org/maven/CreatingJ2eeApplications
But
On Wed, 2004-06-02 at 23:42, Dan Tran wrote:
Jerome,
take a look at this link
http://wiki.codehaus.org/maven/CreatingJ2eeApplications
I base mine on that example and it works like a champ
hope it helps
it helped a lot ;)
I found my problem to be a dependency declaration one:
in the
I am trying to get multiproject dependencies work. But am having a hard
time. The doc didn't seem to contain the answers to my question.
My idea is to test the multiproject functionality doing the following
project/core
project/web
I then need core to be built before web.
Detailed Setup
Subject: how to make multiproject dependencies work
I am trying to get multiproject dependencies work. But am having a hard
time. The doc didn't seem to contain the answers to my question.
My idea is to test the multiproject functionality doing the following
project/core
project/web
I
Subject: Re: multiproject dependencies
Beta10 multiproject has some bugs :-)
Use the released version.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nathan Coast [EMAIL PROTECTED] wrote on 10/09/2003 04:11:51 PM:
:)
just tried using
: RE: multiproject dependencies
I know this has been answered before, but just for clarity.
When running the Multiproject goal and there is a dependency ordering
requirement, does the Multiproject analyse the sub-projects dependencies and
work out the correct order to build.
If this is correct
crap! A talking muffin!
-Original Message-
From: Bateman, Patrick eMEDIA [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 5:39 AM
To: 'Maven Users List'
Subject: RE: multiproject dependencies
I know this has been answered before, but just for clarity.
When
:)
just tried using multiproject and it barfed with
maven-multiproject-plugin-1.0-SNAPSHOT/plugin.jelly:149:61: j:set This
tag does not understand the 'name' attribute
I checked the jelly docs and set doesn't seem to take a name attribute.
I was using maven beta 10. I'm rebuilding maven from
fyi, building from cvs fixes this problem.
Nathan Coast wrote:
:)
just tried using multiproject and it barfed with
maven-multiproject-plugin-1.0-SNAPSHOT/plugin.jelly:149:61: j:set This
tag does not understand the 'name' attribute
I checked the jelly docs and set doesn't seem to take a name
On Wednesday 10 Sep 2003 07:58, Nathan Coast wrote:
fyi, building from cvs fixes this problem.
Also, you were using the SNAPSHOT of multiproject that came with beta10. There
was a new version released to
http://www.ibiblio.org/maven/maven/plugins/
a week or so ago which fixed many things.
--
Beta10 multiproject has some bugs :-)
Use the released version.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nathan Coast [EMAIL PROTECTED] wrote on 10/09/2003 04:11:51 PM:
:)
just tried using multiproject and it barfed with
Hi,
Does the multiproject plugin build dependent projects in the correct
order (like the reactor does).
thanks
Nathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Well, yes, since it uses the reactor.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nathan Coast [EMAIL PROTECTED] wrote on 10/09/2003 02:54:58 PM:
Hi,
Does the multiproject plugin build dependent projects in the correct
order (like the
20 matches
Mail list logo
