One for each artifact that needs to be released is ok, that wasn't my question.
I now also have a distributionmodule that takes info from the release modules in order to group the libraries and to create one release bundle, as it is explained in the link you don't like much :-) I'll take a look at this Antonio Petrelli wrote: > > 2010/12/9 fhomasp <thomas.peet...@realdolmen.com>: >> You're talking about Tiles and accessing the parent directory. Could you >> explain a bit further? > > I have a better idea, here is the source: > http://svn.apache.org/repos/asf/tiles/framework/trunk/assembly/ > >> And the idea of an extra "distribution" module, that's not the way to go >> then? > > I guess that *one* assembly module is enough. In Tiles, within that > single module, we build source, library, documentation assemblies from > one single module. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://maven.40175.n5.nabble.com/Create-complicated-client-jar-release-target-s-tp3295582p3298637.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
