geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <>
Subject Re: Proposal: apache-wide specs project
Date Tue, 08 Nov 2005 23:59:52 GMT

On Nov 8, 2005, at 6:30 PM, Brett Porter wrote:

> This is an interesting idea.
> What scope do you envisage? Would it only be JSRs, or would, for
> example, stdcxx in the incubator be able to join?

it should be open for anything

> Do you see any issues with having a single project but specs that
> encompass a variety of technologies that might not overlap?

I don't.

The original motivation when we first concocted this scheme was to  
get rid of the multitude of implementations of the same thing, which  
sometimes lead to problems due to multiple factories in the classpath.

The one that bit me hard was JAXR, because both Scout and Geronimo  
had an implementation of the API, and the API has a factory, and .....

So each spec should be relatively independent, but this project would  
provide neutral territory for the projects.


> I think it is fine to start with an org.apache.specs group either way
> as it isn't going to clash with anything.
> I think it would be good to discuss this more broadly, but I'm not
> sure of a suitable apache wide list other than community@
> - Brett
> On 11/8/05, David Jencks <> wrote:
>> Many people have talked on and off about setting up an apache-wide
>> specs project.  With the recent move to separate our copies of the
>> specs and build them with maven 2 perhaps this is a good time to  
>> try to
>> get this started.
>> Here are some steps we could take:
>> -Identify projects with java spec implementations in them.  They
>> include at least:
>>    geronimo
>>    tomcat
>>    pluto (have already expressed interest)
>>    axis
>>    scout (?)
>> --Approach the projects to see if they are interested
>> --Appropriate the M2 groupId org.apache.specs
>> --Based on the support we get  proposing a new top level project.   
>> This
>> is going to be an unusual project in that it's expected that changes
>> will only take place when new specs come out :-)
>> We could all start using the groupId org.apache.specs even before an
>> actual project was set up.  This might just cause confusion though.
>> Thoughts?
>> many thanks
>> david jencks

Geir Magnusson Jr                                  +1-203-665-6437

View raw message