-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 10 May 2006, Antonio Gallardo wrote:
Date: Wed, 10 May 2006 10:22:06 -0500
From: Antonio Gallardo <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Maven dependencies
Hi Giacomo,
Thanks for pointing out this.
Is this a eggs chicken problem? Try to explain, blocks should have
independence on his own dependencies or is this not desired (all the blocks
should have the same dependencies)? Am I mixing here the osgi promise? I am
not confrontating. I want to find a way to solve this.
Yes, it may you are mixing thhings. As long as we don't have the blocks
being separated by their own classloader we do have a problem if we end
up having multiple versions of the same artifact in WEB-INF/lib.
If we COMPLETELY switch to OSGI based Cocoon-Blocks (which should have
classloader isolation) than a block can have whatever artifact it needs,
as long as it is not exposing it to the world.
HTH
Giacomo
>
Best Regards,
Antonio Gallardo
Giacomo Pati escribió:
-----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-----
- --
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)
iD8DBQFEYvXzLNdJvZjjVZARAlsfAKDnUfTdN+8BqybWG2llBNu77we1NQCdESfz
RjGj3LACv3oUtRv0qClh9D8=
=Gb4D
-----END PGP SIGNATURE-----
