Here is the dependency tree on the distribution module (mvn
dependency:tree). servlet-api.jar comes through commons configuration, which
is Apache, which makes me think that it is an acceptable dependency? Or does
commons configuration erroneously include it? Either way, we don't need it.
[dependency:tree]
org.apache.qpid:qpid-distribution:jar:1.0-incubating-M2.1-SNAPSHOT
org.apache.qpid:qpid-client:jar:1.0-incubating-M2.1-SNAPSHOT:compile
org.apache.qpid:qpid-common:jar:1.0-incubating-M2.1-SNAPSHOT:compile
org.apache.mina:mina-java5:jar:1.0.0:compile
org.apache.mina:mina-core:jar:1.0.0:compile
backport-util-concurrent:backport-util-concurrent:jar:
2.2:compile
org.slf4j:slf4j-api:jar:1.4.0:compile
org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.0:compile
commons-collections:commons-collections:jar:3.2:compile
commons-lang:commons-lang:jar:2.1:compile
org.apache.mina:mina-filter-ssl:jar:1.0.0:compile
org.apache.qpid:qpid-broker:jar:1.0-incubating-M2.1-SNAPSHOT:compile
log4j:log4j:jar:1.2.12:compile
org.slf4j:slf4j-log4j12:jar:1.4.0:compile
commons-cli:commons-cli:jar:1.0:compile
commons-logging:commons-logging:jar:1.0.4:compile
commons-configuration:commons-configuration:jar:1.2:compile
dom4j:dom4j:jar:1.4:compile
jaxen:jaxen:jar:1.0-FCS:compile
saxpath:saxpath:jar:1.0-FCS:compile
msv:msv:jar:20020414:compile
relaxngDatatype:relaxngDatatype:jar:20020414:compile
isorelax:isorelax:jar:20020414:compile
commons-logging:commons-logging-api:jar:1.0.4:compile
commons-digester:commons-digester:jar:1.6:compile
commons-beanutils:commons-beanutils:jar:1.6:compile
commons-beanutils:commons-beanutils-core:jar:1.7.0:compile
commons-codec:commons-codec:jar:1.3:compile
xerces:xercesImpl:jar:2.2.1:compile
xalan:xalan:jar:2.7.0:compile
xml-apis:xml-apis:jar:1.0.b2:compile
javax.servlet:servlet-api:jar:2.3:compile
org.apache.qpid.management:org.apache.qpid.management.ui:jar:1.0-incubating-M2.1-SNAPSHOT:compile
com.ibm.icu:com.ibm.icu:jar:3.4.4:compile
org.eclipse.jface:org.eclipse.jface:jar:3.2.0:compile
org.eclipse.core:org.eclipse.core.commands:jar:3.2.0:compile
org.eclipse.core:org.eclipse.core.contenttype:jar:3.2.0:compile
org.eclipse.core:org.eclipse.core.expressions:jar:3.2.0:compile
org.eclipse.core:org.eclipse.core.jobs:jar:3.2.0:compile
org.eclipse.core:org.eclipse.core.runtime:jar:3.2.0:compile
org.eclipse.core:org.eclipse.core.runtime.compatibility.auth:jar:3.2.0:compile
org.eclipse.core:org.eclipse.core.runtime.compatibility.registry:jar:3.2.0:runtime
org.eclipse.equinox:org.eclipse.equinox.common:jar:3.2.0:compile
org.eclipse.equinox:org.eclipse.equinox.preferences:jar:3.2.0:compile
org.eclipse.equinox:org.eclipse.equinox.registry:jar:3.2.0:compile
org.eclipse.help:org.eclipse.help:jar:3.2.0:compile
org.eclipse.osgi:org.eclipse.osgi:jar:3.2.0:compile
org.eclipse.swt:org.eclipse.swt.win32.win32.x86:jar:3.2.0:compile
org.eclipse.swt:org.eclipse.swt:jar:3.2.0:compile
org.eclipse.ui:org.eclipse.ui.forms:jar:3.2.0:compile
org.eclipse.ui:org.eclipse.ui.workbench:jar:3.2.1:compile
org.eclipse.ui:org.eclipse.ui:jar:3.2.0:compile
On 14/11/2007, Rupert Smith <[EMAIL PROTECTED]> wrote:
>
> Presumably we can just ditch the servlet-api jar? Something that some
> stupid Maven plug-in pulls into the build as a transitive dependency for no
> good reason.
>
> On 14/11/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote:
> >
> >
> > I think we are missing a dir / file that has a copy of all the
> > non-apache lics that we use in it
> >
> > Carl.
> >
> >
> >
> > -------- Original Message --------
> > Subject: Re: [VOTE][ANN] Qpid M2 Release
> > Date: Wed, 14 Nov 2007 10:07:53 -0500
> > From: Kevan Miller <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > References: <[EMAIL PROTECTED]
> > >
> >
> >
> >
> > Hi Rajith,
> > Where is the license information for artifacts included in your
> > binaries?
> > Your notice files refer to non-apache licenses for a number of your
> > artifacts. I would expect to see these licenses included in your
> > distribution. You don't give any license info for a few jars (e.g. msv
> > and servlet-api jars). If servlet-api is a Sun jar, then I think you
> > probably have an issue...
> >
> > Here's my -1 until the above issues are resolved.
> >
> > --kevan
> > On Nov 12, 2007, at 12:33 PM, Rajith Attapattu wrote:
> >
> > > Folks,
> > >
> > > The Qpid PPMC is happy to notify the completion of the vote for the
> > > Qpid M2
> > > release.
> > > We would appreciate if the incubator PMC could ratify the release.
> > >
> > > There were 12 binding votes in total, including 3 mentor votes.
> > > The following is the vote thread.
> > >
> > http://mail-archives.apache.org/mod_mbox/incubator-qpid-dev/200711.mbox/browser
> > >
> > > Here are the details pertaining to the vote.
> > >
> > > The signed artifacts for the M2 final release is available at
> > > http://people.apache.org/~rajith/qpid-release/M2/Final/<http://people.apache.org/%7Erajith/qpid-release/M2/Final/>
> > <http://people.apache.org/%7Erajith/qpid-release/M2/Final/
> > > >
> > >
> > > The keys are located at,
> > > https://svn.apache.org/repos/asf/incubator/qpid/tags/M2/Final/java/
> > > KEYS
> > >
> > > All artifacts can be downloaded as a single tar file at,
> > > http://people.apache.org/~rajith/qpid-release/M2/Final/final.tar.gz
> > <http://people.apache.org/%7Erajith/qpid-release/M2/Final/final.tar.gz><
> > http://people.apache.org/%7Erajith/qpid-release/M2/Final/final.tar.gz
> > > >
> > >
> > > The release artifacts can be built using the following tag,
> > > https://svn.apache.org/repos/asf/incubator/qpid/tags/M2/Final/
> > >
> > > Regards,
> > >
> > > Rajith Attapattu
> > > Red Hat
> > > Blog http://mutlix.blogspot.com/
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
