2010/10/27 Grégory Joseph <greg....@gmail.com>: > .. but yes, this project now also needs a standalone/executable jar; > some of the "provided" dependencies are needed at runtime for this. As > far as I can tell, the shade plugin currently does not propose any > solution for this. > > Is there any way this could be considered for the plugin ? Or am I > looking at it the wrong way ? Are there any alternatives ? I suppose I > could split my project and have 2 modules, one simply being the > standalone/shaded version of the other, but it seems overkill, since > they're really the same source.
The multi-module path is the best. Why do you say that they share "the same source"? The shaded project must have a dependency on the original project, so it takes the compiled version, not the source. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
