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 >
