One of the nice things about the current AS 7 distribution is there aren't duplicated jars all over the place.

Would it be better to just divy up the modules directory into the public vs. private API's, which I understood we needed to do anyway (or something to that affect) to meet our TAG/Andiamo requirements anyway.

Also, is calling this stuff "client" really appropriate?  Isn't it really just the public API's?

Andy

---

From: "David M. Lloyd" <david.lloyd@redhat.com>
To: jboss-as7-dev@lists.jboss.org
Sent: Tuesday, June 14, 2011 8:51:03 AM
Subject: Re: [jboss-as7-dev] JBOSS_HOME/client in AS7 for client accessible jars

On 06/14/2011 03:26 AM, Jaikiran Pai wrote:
> 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?

For client purposes I really think we should have simpler JAR names than
this, maybe based on module name.  For example
"jboss-ejb-api_3.1_spec-1.0.0.Final.jar" could be "javax_ejb_api.jar".

Or perhaps we should use an aggregated javaee.jar.  Either way I don't
like just piling these JARs into the client folder unmodified.

And there will be other client JARs we need too like Remoting, DMR, and
the controller-client JAR.
--
- DML
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev