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

[David Lloyd (JIRA)]

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

David Lloyd commented on JBEE-73:
---------------------------------

I'd be in favor of this - with shade it'd be super easy to do; we just need to make sure that *we* do not ever consume this JAR as a dependency or all manner of thing could get messed up.

> 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: Shelly McGowan
>
> 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