You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <ma...@gmail.com> on 2007/06/10 20:36:16 UTC
Licenses, notices and adding dependencies
All,
After Noel (rightfully) wagged his finger for our beta 2 release, I
have been going through our notice and license files.
- spring was not in a notice file, but we do ship it in wicket-examples
- joda time was not in a notice file, but we do ship it
- wicket listed in the notice file a CC dependency on a drag/drop
library that was removed
- servlet api 2.3 is probably a problem for distribution: the trail
leads to Craig McClanahan, from a maven 1 repository, but without any
way to determine whether the library is Craig's or (illegally) copied
from java.sun.com
- we now ship ASM, but it was not in a notice (I don't know where it came from)
- we ship Avalon and LogKit
- cglib is also ASL2 licensed, but was not in a notice
- we have commons-logging and slf4j in our examples project
The notice thing is easily fixable (I'll commit it soon). However, I
respectfully ask any and all members to check the license of a
library, and add it to the notice file. If you remove a depenceny,
remove it also from the notice file. If you upgrade a version, check
the license and see if it has changed (the log4j license thing would
have been caught then) and adjust if necessary.
The avalon/logkit/stuff seems to come from our spring dependency. I
don't see a quick fix for this (removing commons-logging from the
spring dependency causes compilation errors in wicket-examples).
Martijn
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
RE: Licenses, notices and adding dependencies
Posted by "Noel J. Bergman" <no...@devtech.com>.
Is the obvious too much so? Ask Craig about the provanance.
--- Noel
Re: Licenses, notices and adding dependencies
Posted by Martijn Dashorst <ma...@gmail.com>.
On 6/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> whats wrong with 2.4? it is java 1.4.
It's newer than 2.3. And I don't have the time to hunt for a jar with
a compatible license that is traceable (i.e. somewhere in the jar).
Geronimo seems like a good candidate:
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-servlet_2.4_spec/1.1/
Martijn
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
Re: Licenses, notices and adding dependencies
Posted by Igor Vaynberg <ig...@gmail.com>.
whats wrong with 2.4? it is java 1.4.
-igor
On 6/10/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> But that is servlet api 2.4 or 2.5, not 2.3...
>
> Martijn
>
> On 6/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > afir, jetty has their own servlet api jar if that helps.
> >
> > -igor
> >
> >
> > On 6/10/07, Martijn Dashorst <ma...@gmail.com> wrote:
> > >
> > > All,
> > >
> > > After Noel (rightfully) wagged his finger for our beta 2 release, I
> > > have been going through our notice and license files.
> > >
> > > - spring was not in a notice file, but we do ship it in
> wicket-examples
> > > - joda time was not in a notice file, but we do ship it
> > > - wicket listed in the notice file a CC dependency on a drag/drop
> > > library that was removed
> > > - servlet api 2.3 is probably a problem for distribution: the trail
> > > leads to Craig McClanahan, from a maven 1 repository, but without any
> > > way to determine whether the library is Craig's or (illegally) copied
> > > from java.sun.com
> > > - we now ship ASM, but it was not in a notice (I don't know where it
> came
> > > from)
> > > - we ship Avalon and LogKit
> > > - cglib is also ASL2 licensed, but was not in a notice
> > > - we have commons-logging and slf4j in our examples project
> > >
> > > The notice thing is easily fixable (I'll commit it soon). However, I
> > > respectfully ask any and all members to check the license of a
> > > library, and add it to the notice file. If you remove a depenceny,
> > > remove it also from the notice file. If you upgrade a version, check
> > > the license and see if it has changed (the log4j license thing would
> > > have been caught then) and adjust if necessary.
> > >
> > > The avalon/logkit/stuff seems to come from our spring dependency. I
> > > don't see a quick fix for this (removing commons-logging from the
> > > spring dependency causes compilation errors in wicket-examples).
> > >
> > > Martijn
> > >
> > > --
> > > Join the wicket community at irc.freenode.net: ##wicket
> > > Wicket 1.2.6 contains a very important fix. Download Wicket now!
> > > http://wicketframework.org
> > >
> >
>
>
> --
> Join the wicket community at irc.freenode.net: ##wicket
> Wicket 1.2.6 contains a very important fix. Download Wicket now!
> http://wicketframework.org
>
Re: Licenses, notices and adding dependencies
Posted by Martijn Dashorst <ma...@gmail.com>.
But that is servlet api 2.4 or 2.5, not 2.3...
Martijn
On 6/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> afir, jetty has their own servlet api jar if that helps.
>
> -igor
>
>
> On 6/10/07, Martijn Dashorst <ma...@gmail.com> wrote:
> >
> > All,
> >
> > After Noel (rightfully) wagged his finger for our beta 2 release, I
> > have been going through our notice and license files.
> >
> > - spring was not in a notice file, but we do ship it in wicket-examples
> > - joda time was not in a notice file, but we do ship it
> > - wicket listed in the notice file a CC dependency on a drag/drop
> > library that was removed
> > - servlet api 2.3 is probably a problem for distribution: the trail
> > leads to Craig McClanahan, from a maven 1 repository, but without any
> > way to determine whether the library is Craig's or (illegally) copied
> > from java.sun.com
> > - we now ship ASM, but it was not in a notice (I don't know where it came
> > from)
> > - we ship Avalon and LogKit
> > - cglib is also ASL2 licensed, but was not in a notice
> > - we have commons-logging and slf4j in our examples project
> >
> > The notice thing is easily fixable (I'll commit it soon). However, I
> > respectfully ask any and all members to check the license of a
> > library, and add it to the notice file. If you remove a depenceny,
> > remove it also from the notice file. If you upgrade a version, check
> > the license and see if it has changed (the log4j license thing would
> > have been caught then) and adjust if necessary.
> >
> > The avalon/logkit/stuff seems to come from our spring dependency. I
> > don't see a quick fix for this (removing commons-logging from the
> > spring dependency causes compilation errors in wicket-examples).
> >
> > Martijn
> >
> > --
> > Join the wicket community at irc.freenode.net: ##wicket
> > Wicket 1.2.6 contains a very important fix. Download Wicket now!
> > http://wicketframework.org
> >
>
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
Re: Licenses, notices and adding dependencies
Posted by Igor Vaynberg <ig...@gmail.com>.
afir, jetty has their own servlet api jar if that helps.
-igor
On 6/10/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> All,
>
> After Noel (rightfully) wagged his finger for our beta 2 release, I
> have been going through our notice and license files.
>
> - spring was not in a notice file, but we do ship it in wicket-examples
> - joda time was not in a notice file, but we do ship it
> - wicket listed in the notice file a CC dependency on a drag/drop
> library that was removed
> - servlet api 2.3 is probably a problem for distribution: the trail
> leads to Craig McClanahan, from a maven 1 repository, but without any
> way to determine whether the library is Craig's or (illegally) copied
> from java.sun.com
> - we now ship ASM, but it was not in a notice (I don't know where it came
> from)
> - we ship Avalon and LogKit
> - cglib is also ASL2 licensed, but was not in a notice
> - we have commons-logging and slf4j in our examples project
>
> The notice thing is easily fixable (I'll commit it soon). However, I
> respectfully ask any and all members to check the license of a
> library, and add it to the notice file. If you remove a depenceny,
> remove it also from the notice file. If you upgrade a version, check
> the license and see if it has changed (the log4j license thing would
> have been caught then) and adjust if necessary.
>
> The avalon/logkit/stuff seems to come from our spring dependency. I
> don't see a quick fix for this (removing commons-logging from the
> spring dependency causes compilation errors in wicket-examples).
>
> Martijn
>
> --
> Join the wicket community at irc.freenode.net: ##wicket
> Wicket 1.2.6 contains a very important fix. Download Wicket now!
> http://wicketframework.org
>