hi Jim
I think I understand what you are saying and I have been in the same boat,
though in a different aspect.
Here's is what I understand about this, and my feeling is that current
support of inheritance and aggregation do not complement each other.
Project type pom can be used for two
Thanks John,
In this case I could use some help understanding. In every case, without
exception, when I add a dependencies section of a POM file whose
packaging is pom, not once have I intended that POM files artifact to
be what is dependent on those items. In every case it's the children of
Thanks John,
In this case I could use some help understanding. In every case, without
exception, when I add a dependencies section of a POM file whose
packaging is pom, not once have I intended that POM files artifact to
be what is dependent on those items. In every case it's the children of
Hi Jim,
All POMs' dependencies needs to be validated regardless of its packaging.
Regards,
John
Jim Carroll wrote:
It appears that the transitive dependency mechanism is not sensitive
to the packaging. This seems odd to me and is causing me an incredible
amount of grief. I have a parent
@maven.apache.org
cc
Subject
Re: [m2] parent pom
Hi Fredy,
The concept of parent poms can be applied to multi-module projects
wherein it provides you the priviledge of building your modules
individually or as a whole (project).
You need to define your parent pom in your project's root directory (ex.
C
Subject: Re: [m2] parent pom
Thanks for that sample. It helps out a lot. I was wondering why we
have to depend on maven-model? What is that for?
Thanks.
_Mang
Maria Odea Ching [EMAIL PROTECTED]
01/30/2006 10:17 PM
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users
: RE: [m2] parent pom
I guess I don't have a choice, but the issue is that there are other
requirements to share smaller parts of the api to other projects. For instance,
there are some projects that need a jar of a specific package from my project.
For me to make that a separate module, I'd have
Does anyone know if this is possible? Just checking in case it was
missed...
Frank Russo
Senior Developer
FX Alliance, LLC
-Original Message-
From: Frank Russo
Sent: Tuesday, January 31, 2006 12:05 PM
To: Maven Users List
Subject: RE: [m2] parent pom
Does anyone know if the following
d'origine-
De : Frank Russo [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 3 février 2006 14:07
À : Maven Users List
Objet : RE: [m2] parent pom
Does anyone know if this is possible? Just checking in case it was
missed...
Frank Russo
Senior Developer
FX Alliance, LLC
-Original Message-
From
know if this is possible? Just checking in case it was
missed...
Frank Russo
Senior Developer
FX Alliance, LLC
-Original Message-
From: Frank Russo
Sent: Tuesday, January 31, 2006 12:05 PM
To: Maven Users List
Subject: RE: [m2] parent pom
Does anyone know if the following is doable? I
:[EMAIL PROTECTED]
Sent: Friday, February 03, 2006 8:19 AM
To: Maven Users List
Subject: Re: [m2] parent pom
Why do you not create 3 projects like this :
root
- pom.xml
- jar_project
-pom.xml
- war_project
-pom.xml
In your war project, you add a dependency to your jar.
Your
Russo
Senior Developer
FX Alliance, LLC
-Original Message-
From: Maria Odea Ching [mailto:[EMAIL PROTECTED]
Sent: Monday, January 30, 2006 10:17 PM
To: Maven Users List
Subject: Re: [m2] parent pom
Hi Fredy,
The concept of parent poms can be applied to multi-module projects
wherein
To: Maven Users List
Subject: Re: [m2] parent pom
Hi Fredy,
The concept of parent poms can be applied to multi-module projects
wherein it provides you the priviledge of building your modules
individually or as a whole (project).
You need to define your parent pom in your project's root directory
PROTECTED]
Sent: Tuesday, January 31, 2006 8:57 AM
To: Maven Users List
Subject: Re: [m2] parent pom
If your parent project POM lists modules, then those projects will be
built when the parent is built.
Richard Allen
Frank Russo wrote:
I have a question in regards to this. Is there a way to build
-
From: Richard Allen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 8:57 AM
To: Maven Users List
Subject: Re: [m2] parent pom
If your parent project POM lists modules, then those projects will be
built when the parent is built.
Richard Allen
Frank Russo wrote:
I have a question
Developer
FX Alliance, LLC
-Original Message-
From: Richard Allen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 9:54 AM
To: Maven Users List
Subject: Re: [m2] parent pom
See How do I build more than one project at once? here:
http://maven.apache.org/guides/getting-started
modules/.
If anyone knows how to use this, please pass along.
Thanks...
Frank Russo
Senior Developer
FX Alliance, LLC
-Original Message-
From: Richard Allen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 8:57 AM
To: Maven Users List
Subject: Re: [m2] parent pom
If your
Hi Fredy,
The concept of parent poms can be applied to multi-module projects
wherein it provides you the priviledge of building your modules
individually or as a whole (project).
You need to define your parent pom in your project's root directory (ex.
C:\Project\pom.xml ) and the children pom
Yes it does get the parent pom from the repo. You have added your repo
to a profile so it needs to be activated. I'm not sure if this
activation
activeByDefault/
/activation
Does the trick. I would expect activeByDefaulttrue/ActiveByDefault
at least. I did
I can confirm that. I was just working on a common pom (referenced from
internal repo) and was successful having a single profile with the
activation-element like stated below, i.e.:
settings
...
profiles
profile
activation
activeByDefaulttrue/activeByDefault
20 matches
Mail list logo
