9:42 a.m.
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
2:09 p.m.
New subject: [JBoss JIRA] Commented: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
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
1:59 p.m.
New subject: [JBoss JIRA] Commented: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
Andrew Rubinger commented on JBEE-73:
-------------------------------------
Shouldn't this be handled by the Surefire Manifest JAR? Which only applies when
forking tests in a new VM, I suppose.
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
2:01 p.m.
New subject: [JBoss JIRA] Commented: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on JBEE-73:
---------------------------------
For testing, sure, that could work, but for actual client applications people will
probably want to have one JAR, I would think.
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
1:57 a.m.
New subject: [JBoss JIRA] Commented: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
Nicklas Karlsson commented on JBEE-73:
--------------------------------------
Surefire might do some workarounds as it works for me in maven but the windows-limitation
makes "run as" in Eclipse on an Arquillian test useless for incontainer
profiles.
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
3:14 p.m.
New subject: [JBoss JIRA] Assigned: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan reassigned JBEE-73:
----------------------------------
Assignee: John Casey (was: Shelly McGowan)
pls comment
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
4:13 p.m.
New subject: [JBoss JIRA] Commented: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
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
4:15 p.m.
New subject: [JBoss JIRA] Assigned: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
John Casey reassigned JBEE-73:
------------------------------
Assignee: Shelly McGowan (was: John Casey)
let me know if you need specific examples on this.
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
9:57 a.m.
New subject: [JBoss JIRA] (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
Paul Gier updated JBEE-73:
--------------------------
Component/s: javaee6_specs_bom
(was: javaee_6.0_spec)
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: javaee6_specs_bom
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:55 p.m.
New subject: [JBoss JIRA] (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
Paul Gier updated JBEE-73:
--------------------------
Assignee: Paul Gier (was: Shelly McGowan)
Fix Version/s: JavaEE 6 Spec APIs 1.0.0
Affects Version/s: (was: 1.0.0.Final-javaee_6.0)
Create a uber-jar for the JBoss JavaEE APIs
-------------------------------------------
Key: JBEE-73
URL: https://issues.jboss.org/browse/JBEE-73
Project: JBoss JavaEE Spec APIs
Issue Type: Feature Request
Components: javaee-specs
Reporter: Aslak Knutsen
Assignee: Paul Gier
Fix For: JavaEE 6 Spec APIs 1.0.0
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 p.m.
New subject: [JBoss JIRA] (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs
[
https://issues.jboss.org/browse/JBEE-73?page=com.atlassian.jira.plugin.sy...
]
Paul Gier closed JBEE-73.
-------------------------
Resolution: Done
Created a shaded uber jar in
[fc0ccee9|https://github.com/jboss/jboss-javaee-specs/commit/fc0ccee96bea1...]
Create a uber-jar for the JBoss JavaEE APIs
-------------------------------------------
Key: JBEE-73
URL: https://issues.jboss.org/browse/JBEE-73
Project: JBoss JavaEE Spec APIs
Issue Type: Feature Request
Components: jboss-javaee-specs
Reporter: Aslak Knutsen
Assignee: Paul Gier
Fix For: JavaEE 6 Spec APIs 3.0.0
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4583
days inactive
4987
days old
10 comments
8 participants
participants (8)
-
Andrew Rubinger (JIRA) -
Aslak Knutsen (JIRA)
-
David Lloyd (JIRA)
-
John Casey (JIRA)
-
Nicklas Karlsson (JIRA)
-
Paul Gier (JIRA)
-
Paul Gier (Updated) (JIRA)
-
Shelly McGowan (JIRA)