Jerome Lacoste schreef:
On 4/23/07, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:
I also have a dependency on spring-core:
/repo/org/springframework/spring-core/2.0.2/spring-core-2.0.2.jar
So I need a different classpathPrefix depending on the dependency.
what is your use case ?
I am not sure that the repository-like structure allowed by the
assembly plugin was designed to allow you to run your app from the
generated repository.
Some suggestions:
1- don't assemble as a maven repository (do you really need it ?)
For the sake of namespacing, yes:
/org/foo/bar-1.0.jar
/org/doo/bar-1.0.jar
are 2 different jars, with different classes.
2- don't depend on the generated classpath (e.g. use a wrapper to
start your app)
You mean a shell script? Then we need to keep 2 verions in sync:
wrapper.bat and wrapper.sh.
Or do you mean a wrapper jar? We have separate processes that reuse the
same jars and want to minimize network traffic.
How can we avoid having to rewrite the classpath with each dependency
change in this case?
3- rewrite the generated classpath once your repository has been created.
In the jar? Problem is we need the groupId of each artifact.
4- patch the jar plugin to accept a classpath generator that matches
your requirement
That would be the full solution.
I would pick option 1 or 3.
Cheers,
J
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
