FYI I call that a local aggregator pom. I typically set them up for the
various projects I jump between. I can then just open the whole set of
projects from intellij in one go and as this is maven I can safely discard
all the IDE's project info and have it regenerated from the pom and the
pom's rea
We are doing something similar with what I call an assembly project.
I have the following structure:
assembly
- pom.xml
- projectA
- pom.xml
- projectB
- pom.xml
- projectC
- pom.xml
- projectX
- pom.xml
Where the assembly's pom.xml contains like:
pom
projectA
p
On 7 January 2014 15:29, Mark Derricutt wrote:
>
>>> When the project is relatively new and the internally-developed dependency
>>> "A" is no where near being mature, nearly every change being made to
>>> "Project X" requires a corresponding change to A. At this point in the
>>> development cycle
>> When the project is relatively new and the internally-developed dependency
>> "A" is no where near being mature, nearly every change being made to
>> "Project X" requires a corresponding change to A. At this point in the
>> development cycle (and for many months in the foreseeable future) I act
uild A, then build X. And this
certainly makes sense when you step back and think about it... it's just not
terribly convenient.
--
View this message in context:
http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp461
On 7 January 2014 09:42, erich8 wrote:
> Barrie Treloar wrote
>> When you build Product X the libraries A, B and C should already
>> exist. You dont want to rebuild them just to build Product X, that
>> will slow down your development process.
>> Ideally A, B, and C are released versions, but if
.. it's just not
terribly convenient.
--
View this message in context:
http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p5780688.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
module?
-Kane
--
View this message in context:
http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p4616738.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Wayne,
>
> Yes, I understand I don't have to have to depend on C from product X, but do
> I need to include it as a module?
>
> -Kane
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-
Wayne is absolutely right ( and one of the best resources in the forum).
Maven imposes a very rigid way of organizing software development.
If you fight it, you will lose.
You can prolong the date of final defeat but you will lose.
If you want to gain the productivity that Maven can give:
1) Le
> Yes, I understand I don't have to have to depend on C from product X, but do
> I need to include it as a module?
You are getting modules, dependencies and artifacts mixed up.
The module concept is simply a convenient way for building an
application which is composed of several parts.
Say top (p
On Thu, Jul 21, 2011 at 3:28 AM, kanesee wrote:
> Hi Wayne,
>
> Yes, I understand I don't have to have to depend on C from product X, but do
> I need to include it as a module?
Re-read my message, well actually I should have written this
Modules != Dependencies
All Modules really do is make ma
Hi Wayne,
Yes, I understand I don't have to have to depend on C from product X, but do
I need to include it as a module?
-Kane
--
View this message in context:
http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-ident
> Using the same example where libraries A and B depend on C. If Product X
> needs these libraries, can it just include as modules A and B or does it
> need C as well? That is, can a parent project just include the top-level
> projects or does it need to specify every component in the dependency tr
l? That is, can a parent project just include the top-level
projects or does it need to specify every component in the dependency tree?
--
View this message in context:
http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p46
On Wed, Jul 20, 2011 at 10:22 AM, kanesee wrote:
> I guess I don't really understand the Maven modules then.
>
> Well, this is what I have. My company has a bunch of "components" and our
> own home-brewed build system. We want to translate it to the Maven
> environment.
> The "library components"
duct Y may need A and B.
I'd like to be able to run mvn on the product components and have it
automatically compile and package its library components.
So is dependency or module more appropriate here or some mix of the two?
--
View this message in context:
http://maven.40175.n5.nabble.com/Mis
On Wed, Jul 20, 2011 at 9:44 AM, kanesee wrote:
> Well, I would like to be able to call a maven phase like compile in the
> top-level parent project and have it combine all of its
> dependencies/submodules. That's really the only reason I'm using modules
> instead of sticking with dependencies.
S
n.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p4614151.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user
On Wed, Jul 20, 2011 at 8:14 AM, kanesee wrote:
> So it seems Maven handles dependency inheritance pretty well.
> Let's say I have a parent project A that depends on projects B and C. And
> both B and C depend on D. This works fine as dependencies.
>
> But suppose I wanted to make B and C modules
erstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p4614028.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For ad
http://maven.40175.n5.nabble.com/Misunderstanding-modules-Two-or-more-projects-in-the-reactor-have-the-same-identifier-tp4614001p4614001.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e
22 matches
Mail list logo
