I have several cases where I need to override the default JDK implementations via the Java endorsed JAR override mechanism (for example, by setting java.endorsed.dirs). When I create a software distribution, I use the assembly plugin to place all runtime dependencies in a lib directory, and to place all JARs to be used in the endorsed JAR override mechanism in a lib/endorsed directory. I also proivde some platform-dependent script files used for launching my application(s), each of which sets the java.endorsed.dirs property on behalf of the user. One thing I don't like is that my assembly descriptors are all identical (since I follow this pattern on all my appllications) except for where I need to specify which dependencies are to be placed in the endorsed directory. It would add value for me if there were a way to list which Jars are endorsed, perhaps by adding a new dependency scope of "endorsed". I could then make a generic assembly descriptor that places all "runtime" dependencies in lib and all "endorsed" dependencies in lib/endorsed. Does anyone agree that this would be a good addition to Maven, and if so, under what subproject would I post a JIRA issue?
Thanks, Mike -- View this message in context: http://www.nabble.com/What-do-you-think%3A-add-new-%22endorsed%22-dependency-scope--tf2105667.html#a5803817 Sent from the Apache Maven Developers List forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
