[jboss-jira] [JBoss JIRA] Commented: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs

[John Casey (JIRA)]

    [ https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589469#comment-12589469 ] 

John Casey commented on JBEE-73:
--------------------------------

You could create a separate project called something like jboss-javaee-6.0-all, then make the main artifact for that project an assembly that just unzips all dependencies (with scope set to 'provided' in that dependencySet). In the POM, you'd just put a single dependency on the jboss-javaee-6.0, with a scope of 'provided'. The configuration for the assembly plugin in the POM should be appendAssemblyId == false. The assembly descriptor should set includeBaseDirectory == false.

The only caution here is that if a client builds an application using jboss-javaee-6.0-all as a dependency, and _doesn't_ mark that dependency as scope == provided, then those API classes may wind up in the deployable (EAR, WAR, etc.)...duplicating those already in the core classloader for the server.

So, if we document that case really well, it should be very simple to create this project.

Is this a problem beyond running JUnit tests? If not, is there a simple way to create a test launcher for Arquillian or something? Maybe that's the lazy way out, but I wanted to ask.

> Create a uber-jar for the JBoss JavaEE APIs
> -------------------------------------------
>
>                 Key: JBEE-73
>                 URL: https://issues.jboss.org/browse/JBEE-73
>             Project: JBoss JavaEE APIs
>          Issue Type: Feature Request
>          Components: javaee_6.0_spec
>    Affects Versions: 1.0.0.Final-javaee_6.0
>            Reporter: Aslak Knutsen
>            Assignee: John Casey
>
> My Windows users are having problems.. 
> Windows has a limitation on how long the ClassPath can be, when you start to include libraries like, jbossas-client(249 deps) and jboss-javaee-6.0 (x) windows refuse to execute the java process. 
> http://community.jboss.org/message/586381#586381
> Would it be possible to release a uber-jar v. of the jboss-javaee-6.0 pom? Basically merge it into one artifact. Most users don't care about the individual specs, they use EE. And as long as the pom is there as well, they have both options.
> <dependency>
>    <groupId>org.jboss.spec</groupId>
>    <artifactId>jboss-javaee-6.0-all</artifactId> <-- using a different artifact id is probably easier to setup -->
>    <version>1.0.0.Final</version>
>    <type>jar</type> <-- a single jar -->
> </dependency>
> http://maven.apache.org/plugins/maven-shade-plugin/
> ?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira