Sylvain Wallez pisze:
Well, you can do pretty much what you want with Ivy, since it is
basically used to build an Ant classpath from an ivy.xml file that
describes the project's dependencies. The dependencies are resolved
using a chain of repositories.
In this particular case, we could have a chain consisting in a local
repository (checked in in SVN), Cocoon's own repository and then the
main Maven repository.
And since this is really about building a classpath (the library path in
this case), we don't actually _need_ a local repository, and can build a
classpath that is the concatenation of artifacts pulled from a
repository and jar files in a "local-lib" directory.
Ok. I understand how it helps if one checkouts source code from svn and builds
it before running. How about packaging?
Such solution makes it impossible to use module as dependency for other one.
For cocoon-forms-sample it's not a problem at all because it's not likely that it will become a dependency to any other artifact but what
about generalized situation?
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
