Is activemq using JSPs?

On Tue, Aug 18, 2015 at 2:42 PM Christopher Shannon <
[email protected]> wrote:

> Thanks John and Hiram.
>
> I will use the Tomcat Serlvet and JSP api jars instead of the standard ones
> since they are ASL.  That solves the problem for the API.
>
> Are the other jars ok that I listed since they are CDDL?  These are the
> actual implementation jars that Jetty uses for JSP/JSTL.
>
> <dependency>
> <groupId>org.glassfish.web</groupId>
> <artifactId>javax.servlet.jsp</artifactId>
> </dependency>
> <dependency>
> <groupId>org.glassfish.web</groupId>
> <artifactId>javax.servlet.jsp.jstl</artifactId>
> </dependency>
>
>
> On Tue, Aug 18, 2015 at 1:28 PM, Hiram Chirino <[email protected]>
> wrote:
>
> > We prefer ASL when it's available. That's whey we package Germino
> versions.
> >
> > On Tuesday, August 18, 2015, Christopher Shannon <
> > [email protected]> wrote:
> >
> > > Dan,
> > >
> > > The jms 2.0 api jar is also CDDL (as well as GPL) but it looks like we
> > had
> > > to use a geronimo version of it in Artemis.  Any idea why? For example,
> > > this seems to apply to the servlet 3.1 spec jar that I listed and the
> > fact
> > > that we had to use a different jar file for jms 2.0 leads me to believe
> > we
> > > can't use the servlet 3.1 jar either.
> > >
> > >
> > > On Tue, Aug 18, 2015 at 12:41 PM, Daniel Kulp <[email protected]
> > > <javascript:;>> wrote:
> > >
> > > > CDDL is category B and can be used:
> > > >
> > > > http://apache.org/legal/resolved.html#category-b
> > > >
> > > >
> > > > Dan
> > > >
> > > >
> > > >
> > > > > On Aug 18, 2015, at 12:33 PM, Christopher Shannon <
> > > > [email protected] <javascript:;>> wrote:
> > > > >
> > > > > Actually, re-reading the Apache guidance I'm not sure that CDDL can
> > be
> > > > > included either if the source is available.  So any guidance is
> > > > appreciated
> > > > > from anyone who has dealt with the licensing stuff before.
> > > > >
> > > > > On Tue, Aug 18, 2015 at 11:57 AM, Christopher Shannon <
> > > > > [email protected] <javascript:;>> wrote:
> > > > >
> > > > >> I'm working on upgrading to Jetty 9.2.x to fix:
> > > > >> https://issues.apache.org/jira/browse/AMQ-5356
> > > > >>
> > > > >> Part of the upgrade requires updating dependencies for the servlet
> > and
> > > > jsp
> > > > >> jars. Jetty has two different versions of jsp implementations it
> is
> > > > >> supposed to work. The jetty-jsp works fine but I'm not sure if the
> > > > >> dependencies are compatible with Apache licensing.  Supposedly
> Jetty
> > > > also
> > > > >> works with apache-jsp (which is Tomcat) but I've had lots of
> issues
> > > > trying
> > > > >> to get it to work right.
> > > > >>
> > > > >> I know we can't use GPL licensed dependencies but I think the
> > > > dependencies
> > > > >> below are both GPL and CDDL.  Can we still use the dependencies
> > since
> > > > they
> > > > >> are also under CDDL or is that not allowed?
> > > > >>
> > > > >> <dependency>
> > > > >> <groupId>javax.servlet</groupId>
> > > > >> <artifactId>javax.servlet-api</artifactId>
> > > > >> <version>3.1</version>
> > > > >> </dependency>
> > > > >> <dependency>
> > > > >> <groupId>javax.servlet.jsp</groupId>
> > > > >> <artifactId>javax.servlet.jsp-api</artifactId>
> > > > >> <version>2.3.1</version>
> > > > >> </dependency>
> > > > >> <dependency>
> > > > >> <groupId>org.glassfish.web</groupId>
> > > > >> <artifactId>javax.servlet.jsp</artifactId>
> > > > >> <version>2.3.2</version>
> > > > >> </dependency>
> > > > >> <dependency>
> > > > >> <groupId>org.glassfish.web</groupId>
> > > > >> <artifactId>javax.servlet.jsp.jstl</artifactId>
> > > > >> <version>1.2.2</version>
> > > > >> </dependency>
> > > > >>
> > > > >>
> > > >
> > > > --
> > > > Daniel Kulp
> > > > [email protected] <javascript:;> - http://dankulp.com/blog
> > > > Talend Community Coder - http://coders.talend.com
> > > >
> > > >
> > >
> >
> >
> > --
> > Hiram Chirino
> > Engineering | Red Hat, Inc.
> > [email protected] | fusesource.com | redhat.com
> > skype: hiramchirino | twitter: @hiramchirino
> >
>

Reply via email to