-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 8 May 2006, Jorg Heymans wrote:
I'ld say we carry the burden of managing the dependencies by hand for
now and wait until this is resolved.
I've run a little script agains the code base. We already have
dependencies of the same artifact with different versions:
POM: ./blocks/cocoon-portal/cocoon-portal-impl/pom.xml
group=castor artifact=castor version=0.9.6
POM: ./blocks/cocoon-scratchpad/cocoon-scratchpad-impl/pom.xml
group=castor artifact=castor version=0.9.7
POM: ./blocks/cocoon-chaperon/cocoon-chaperon-impl/pom.xml
group=castor artifact=castor version=0.9.7
POM: ./tools/cocoon-block-deployer/cocoon-deployer-core/pom.xml
group=castor artifact=castor version=1.0M1
POM: ./core/cocoon-blocks-fw/cocoon-blocks-fw-demo2/pom.xml
group=org.apache.cocoon artifact=cocoon-blocks-fw-impl
version=1.0.0-SNAPSHOT
POM: ./core/cocoon-blocks-fw/cocoon-blocks-fw-servlet-impl/pom.xml
group=org.apache.cocoon artifact=cocoon-blocks-fw-impl
version=1.0-SNAPSHOT
POM: ./core/cocoon-core/pom.xml
group=org.apache.excalibur.components.sourceresolve
artifact=excalibur-sourceresolve version=2.1
POM: ./blocks/cocoon-scratchpad/cocoon-scratchpad-impl/pom.xml
group=excalibur-sourceresolve artifact=excalibur-sourceresolve
version=2.1
POM: ./tools/cocoon-block-deployer/cocoon-deployer-core/pom.xml
group=oro artifact=oro version=2.0.7
POM: ./blocks/cocoon-forms/cocoon-forms-impl/pom.xml
group=oro artifact=oro version=2.0.8
What should we do with those?
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEYfr1LNdJvZjjVZARAgKeAKDFxNY3k6MJ0IwYvDVR9s9OGBtfsgCeK3e4
uT6n4KfYkmNclJstGHojX34=
=+qov
-----END PGP SIGNATURE-----
