I've been seeing many users asking how to add the Java EE (and other client accessible) jars to their classpath while developing against AS7: http://community.jboss.org/thread/167943?tstart=0 http://community.jboss.org/thread/164255 https://issues.jboss.org/browse/JBIDE-8718 In previous versions, we had JBOSS_HOME/client folder where we used to ship the Java EE jars and some JBoss specific ones for end users to add them to their compile/runtime classpath. This is currently missing in AS7 and users are finding it difficult to find and refer to those jars within the "modules" of AS7. Some users have run into classpath being too long issues too, due to this. To overcome this, I have this patch https://github.com/jaikiran/jboss-as/commit/f2f01c839ba9540d2aee3d13a5e5d... which creates a<jboss-as-dist>/client folder containing (right now just) the spec API jars. The sole purpose of JBOSS_HOME/client is to make available these client accessible jars.More jars may be added later on, if it makes sense to include them there. Thoughts? If no one has any objection, can this branch https://github.com/jaikiran/jboss-as/commits/client-lib be pulled upstream please? -Jaikiran _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

I'll take this opportunity to mention that I just released version 2.0.0.CR1 of the jboss-javaee6-specs-bom to align with upcoming 7.0.0.CR1 release. In addition, I've created a jboss-javaee6-web-specs-bom which defines the EE APIs that will be provided in the AS 7 web profile configuration. These poms allow the EE APIs to be brought into your maven project adding a single dependency. See my recent blog post[3] on the subject. The use of the pom will also be referenced in Pete's Developer Guide. Shelly McGowan JBoss, by Red Hat [1]https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec... [2]https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec... [3]http://community.jboss.org/blogs/donnamishelly/2011/04/29/jboss-java-ee... ----- Original Message ----- From: "Jaikiran Pai" <jpai(a)redhat.com&gt; To: jboss-as7-dev(a)lists.jboss.org Sent: Tuesday, June 14, 2011 4:26:22 AM Subject: [jboss-as7-dev] JBOSS_HOME/client in AS7 for client accessible jars I've been seeing many users asking how to add the Java EE (and other client accessible) jars to their classpath while developing against AS7: http://community.jboss.org/thread/167943?tstart=0 http://community.jboss.org/thread/164255 https://issues.jboss.org/browse/JBIDE-8718 In previous versions, we had JBOSS_HOME/client folder where we used to ship the Java EE jars and some JBoss specific ones for end users to add them to their compile/runtime classpath. This is currently missing in AS7 and users are finding it difficult to find and refer to those jars within the "modules" of AS7. Some users have run into classpath being too long issues too, due to this. To overcome this, I have this patch https://github.com/jaikiran/jboss-as/commit/f2f01c839ba9540d2aee3d13a5e5d... which creates a <jboss-as-dist>/client folder containing (right now just) the spec API jars. The sole purpose of JBOSS_HOME/client is to make available these client accessible jars.More jars may be added later on, if it makes sense to include them there. Thoughts? If no one has any objection, can this branch https://github.com/jaikiran/jboss-as/commits/client-lib be pulled upstream please? -Jaikiran _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

I've been seeing many users asking how to add the Java EE (and other client accessible) jars to their classpath while developing against AS7:

Thoughts? If no one has any objection, can this branch https://github.com/jaikiran/jboss-as/commits/client-lib be pulled upstream please?