Bryan, If JBoss code is needed for building then it might be an issue as JBoss is using LGPL. Any libraries that are checked into the lib dir in the project has to have a compatible license.
An alternative would be to use some form of abstraction with reflection. This prevents the need for having JBoss libraries at compile time. I used a similar strategy to support Realtime Java constructs. Regards, Rajith On Tue, Jun 23, 2009 at 10:51 PM, Bryan Kearney<bkear...@redhat.com> wrote: > Carl Trieloff wrote: >> >> I expect people might create deployers for other containers like spring, >> websphere etc. So I would think we create a directory >> for each as they are created under the Java directory, and make it >> optional to build them >> >> my 2 cents >> Carl. >> > > I would be fine with that.. it would require having the jboss code to do the > build, but as long as it is optional I would think it would be ok. > > -- bk > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
