Look at http://repo2.maven.org/maven2/javax/enterprise/cdi-api/1.0-CR1/, it is also ASL2 license but copyrighted by RedHat. So, we develop our own API with Apache Foundation way with under control of the Apache. Same for the atinject api.
Thanks; --Gurkan 2009/10/14 Mark Struberg <[email protected]> > yea, I also have no idea about whether we are allowed to use it or not. > > FYI: the artifact pom says it's ASL2 licensed > http://repo2.maven.org/maven2/javax/inject/javax.inject/1/ > > In any case we should keep our atinject module in SVN but should mark it as > 'development only' and remove it from the modules list (so it doesn't get > deployed and packaged anymore). > The argument pro keeping it in SVN is: what to do if atinject-2-snapshot > will be developed some day and we need to release a atinject-2-beta or > something? > > LieGrue, > strub > > --- On Wed, 10/14/09, Gurkan Erdogdu <[email protected]> wrote: > > > From: Gurkan Erdogdu <[email protected]> > > Subject: Re: atinject-api is available at maven-central > > To: [email protected] > > Date: Wednesday, October 14, 2009, 11:45 AM > > I just want to stick with our > > implementation and apis. > > > > On the other hand, I have no very detailed information > > about licensing issues however. > > > > Thanks; > > > > --Gurkan > > > > > > > > > > ________________________________ > > From: Mark Struberg <[email protected]> > > To: [email protected] > > Sent: Wed, October 14, 2009 12:27:13 PM > > Subject: Re: atinject-api is available at maven-central > > > > Hi Gurkan! > > > > For what I know the reason why most of the other J2EE apis > > are not used by e.g. geronimo is mostly caused by license > > problems, isn't? Kevan, David? > > > > If the license is ASL compatible I see no problem, but I'm > > not experienced in this case. At least Jason is Apache > > member and maven PMC, so I guess he wouldn't push any > > incompatible license to maven-central. > > > > Whats the official ASF line in this case? > > > > LieGrue, > > strub > > > > --- On Wed, 10/14/09, Gurkan Erdogdu <[email protected]> > > wrote: > > > > > From: Gurkan Erdogdu <[email protected]> > > > Subject: Re: atinject-api is available at > > maven-central > > > To: [email protected] > > > Date: Wednesday, October 14, 2009, 10:07 AM > > > Hi; > > > > > > Why would you like to drop our module? > > > > > > I think we must use our module api instead of using > > theirs. > > > We can not > > > depend any api for our implementation. If you see > > other > > > projects in Apache, > > > you see lot of API modules for Java EE specs. > > > > > > If you look at jboss impl. it is also Apache License > > but it > > > is copyrighted > > > by jboss.(if you look at source code, there is an > > > @Copyright etc..) > > > > > > So, I would like to stick with our apis including > > at-inject > > > and > > > webbeans-api. > > > > > > Thanks; > > > > > > --Gurkan > > > > > > > > > 2009/10/14 Mark Struberg <[email protected]> > > > > > > > Hi! > > > > > > > > Bob and Jason today pushed the tagged v1 of the > > > atinject-api to mavens > > > > central repository. > > > > > > > > I will again check the license, but think it was > > > released under ASL2. So we > > > > could now theoretically drop our atinject-api > > module > > > and use the one from > > > > central instead. > > > > > > > > TODOs: > > > > .) again check the license > > > > .) adopt LICENSE and NOTICE files where needed > > > > .) drop our the atinject-api module > > > > > > > > anything else? > > > > > > > > LieGrue, > > > > strub > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Gurkan Erdogdu > > > http://gurkanerdogdu.blogspot.com > > > > > > > > > > > > > -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
