And thanks, Robby!
I was considering a couple of alternatives.
This makes it clearer.
Jos
On 03/10/2012 06:20 PM, Robby Pelssers wrote:
Hi Jos,
Just speaking for myself here but the parent pom is mostly a pom that you just
reference because it contains a list of dependencies including the version
numbers. That way you just have to include any dependencies you need in your
pom's referencing this parent pom and you can leave out the versions. This
ensures that all projects use the same versions of jars.
You can also declare e.g. all known modules for this project like.
<modules>
<module>../productinformationwebapp</module>
<module>../productpreview</module>
<module>../producttransformer</module>
<module>../shared</module>
</modules>
So if you do a mvn install it will trigger a reactor build in this case.
It will typically also contain any repositories used (e.g. enterprise maven
repository(
<repositories>
<repository>
<id>nxp-releases</id>
<url>http://ecm.evelopers.com:8081/nexus/content/groups/public</url>
<snapshots><enabled>false</enabled></snapshots>
<releases><enabled>true</enabled></releases>
</repository>
<repository>
<id>nxp-snapshots</id>
<url>http://ecm.evelopers.com:8081/nexus/content/groups/public-snapshots</url>
<snapshots><enabled>true</enabled></snapshots>
<releases><enabled>false</enabled></releases>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>mycompany-releases</id>
<url>....</url>
<snapshots><enabled>false</enabled></snapshots>
<releases><enabled>true</enabled></releases>
</pluginRepository>
<pluginRepository>
<id>mycompany-snapshots</id>
<url>....</url>
<snapshots><enabled>true</enabled></snapshots>
<releases><enabled>false</enabled></releases>
</pluginRepository>
</pluginRepositories>
<distributionManagement>
<repository>
<id>mycompany-releases</id>
<url>.....</url>
</repository>
<snapshotRepository>
<uniqueVersion>false</uniqueVersion>
<id>mycompany-snapshots</id>
<url>.....</url>
</snapshotRepository>
</distributionManagement>
Robby
-----Original Message-----
From: Jos Snellings [mailto:jos.snelli...@pandora.be]
Sent: Saturday, March 10, 2012 3:13 PM
To: users@cocoon.apache.org
Subject: Re: parent of parent artifact?
Thanks for sharing this, Thorsten.
How do your poms then all fit together? Via a parent pom?
I have to draw up an architecture for a similar project: XML content is
addressable via web services.
(not necessarily cocoon).
Cheers,
Jos
On 03/10/2012 01:27 AM, Thorsten Scherler wrote:
major dep to the gui block which then has the deps
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
