On 13.01.2006, at 00:09, Brian E. Fox wrote:
I personally think that minijar needs to be able to have the minimized jars be packaged into wars,ears etc, replacing the full size jar
...so the deps get included in the artifact package itself?
(obviously configurable which ones). If making it an archiver does that, then heck yeah. In its current form, I don't see how it can be used in areal reproducible build because the jars generated would at best be included alongside the full size ones. Unless I completely missed something?
No, that's right. Well, I can basically see the following usecases 1. Inline the deps and include all the required classes into the one standalone jar. 2. Whereever you would use the original jar use the minimal jar. So buildinng a war etc would include the minimal ones instead of the originals. 3. The current way where you can just mix and match whether you like to use the full ones or the minimal ones. That's probably more for libraries rather than a full standalone app. So it probably makes sense to somehow integrate it into the packaging process. How do you guys picture that integration? cheers -- Torsten
PGP.sig
Description: This is a digitally signed message part