Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of aok123@bellsouth.net
 designates 205.152.59.64 as permitted sender)
Message-ID: <454C110E.4080302@bellsouth.net>
Date: Fri, 03 Nov 2006 23:03:26 -0500
From: Alex Karasulu <aok123@bellsouth.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: OSGi Initiative Status
References: <454A43AF.6030306@bellsouth.net>
	 <1162509345.4612.166.camel@trout>
  <454B3CAB.3090203@bellsouth.net>	 <1162586471.4609.62.camel@trout>
  <454BC85E.3030903@bellsouth.net> <1162609287.4609.117.camel@trout>
In-Reply-To: <1162609287.4609.117.camel@trout>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

John E. Conlon wrote:
> On Fri, 2006-11-03 at 17:53 -0500, Alex Karasulu wrote:
> 
>> Ok what are we moving into felix common?
> Four third party wrapping projects:
> antlr-osgi 
> commons-collections-osgi 
> commons-lang-osgi       
> server-logger-osgi 
>   (The first three projects have no java sources, they only have a
> pom.xml, while the server-logger-osgi, adds only an OSGi Activator class
> for dynamic manipulation of log levels in an OSGi environment.) Few
> moving parts.

Cool thanks.

>>  And will not moving our stuff 
>> over to felix common not make it harder for others to commit on those 
>> sources?
> There will be little reason to change these once these build and deploy
> a valid bundle to a maven repository. They will then be available to us
> as well as others that may not use ADS/Mina. The commons effort at Felix
> is only a stopgap effort with the goal to make valid OSGi bundles from
> common libraries that now are not valid OSGi bundles. 

Ok understood.  Sounds good thanks for the update John.

>> Alex can
>>> you get with Richard Hall and create a place for the commons, and get me
>>> a svn userid/pw with commit access so I can redeploy our common
>>> dependencies to there? If necessary (from the felix community
>>> standpoint) I can also help with other wrapping efforts besides the few
>>> we need.
>> Rather than get with Richard (a person) we should be asking about how to 
>> start working the commons thing on the community's dev list. 
> Right
>>  Also if 
>> you're a main driver for doing things in there you can get commit rights 
>> which should be the case.
> Ditto
>>> Mina
>>> There will open a window of opportunity for us to add OSGi wrapping
>>> subproject project to Mina as soon as Peter Royal creates a Java5
>>> optimized Mina 1.0.0 compatible branch. Can you help facilitate the
>>> idea? JIRA:  http//issues.apache.org/jira/browse/DIRMINA-27 
>> You already have rights to commit to the directory project which still 
>> for now includes MINA.  
> Don't remember seeing an email with username/password for svn. How can I
> obtain these?

Hmmm you'll have to ask at infrastructure@apache.org.  They will be able 
to help you.  If I remember correctly there might be a form to set your 
svn password out there.

You're in the authz file so your account was created and I was able to 
add you.

>> I recommend creating a private MINA branch in 
>> your personal sandbox area and making the appropriate changes there then 
>> presenting this idea to the MINA dev list.
>>
>> WDYT?
>>
>> This should be more proactive and they can see just what you are 
>> proposing first hand by investigating your branch.
> This is what I had in mind as well.

Great.

Thanks,
Alex