geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sachin Patel <>
Subject Re: [discuss] Eclipse as a Geronimo sub-project
Date Tue, 23 Aug 2005 13:59:47 GMT
As far as what users want, let me make a generic statement.  The server 
tooling area is already an established area, especially in commercial 
tools such as WebSphere Application Toolkit and Rational Application 
Developer.  Now IBM, BEA, and many other participants are actively 
involved  in the WTP effort in which the goal is to provide tooling 
support for J2EE and other application servers that not only provides a 
strong set of J2EE functionality but is also a completely extendable 
framework.  We need to avoid two parallel efforts here in our tooling 
support for Geronimo but rather build and leverage these frameworks and 
projects that have been accepted and established already in the open 
source community, and use this as our starting blueprint. If and when 
this is an Apache subproject, its critical that the Eclipse and Apache 
communities communicate and work together.  So my opinion is that we 
don't need to be re-inventing the wheel here, but keep our roadmap and 
requirements focused on providing the Geronimo specific pieces that 
integrate nicely with WTP.  So what the community wants for J2EE and 
server tooling is constantly being discussed in the Eclipse community, 
we just need to start getting involved in those discussions and bring 
forth feature requests to them.


Geir Magnusson Jr. wrote:
> On Aug 23, 2005, at 12:14 AM, Dain Sundstrom wrote:
>> On Aug 22, 2005, at 8:24 PM, Geir Magnusson Jr. wrote:
>>> So we now have a subproject policy.
>>> Any thoughts on taking the IBM eclipse tooling contribution as a  
>>> subproject?  It's independent, has interested people that are  
>>> annoying us with patches :) adds value to the project and grows  the 
>>> community in a technically diverse way,  and has a plausible  roadmap.
>>> I would suggest that if we do so, we'd move the current code from  
>>> sandbox and add Sachin Patel as a committer for the subproject.
>>> This is a sensitive issue because of there's a person involved, so  
>>> if anyone has any issues that need to be discussed confidentially,  
>>> please feel free to post to, or mail to me  
>>> or another PMC member.
>> I think it is a bit premature to make this a full fledged  
>> subproject.  I personally don't use eclipse so I don't know if it  
>> builds, or is what users want.
> Maybe we should hear from people who know the space then.  I hear  
> that a few people use Eclipse :)
>>   For now, I think the sandbox is appropriate place to incubate the  
>> code and community.   We need to be careful when creating  
>> subprojects, so we don't end up with lots of abandoned codebases.
> I think we'd just dump them if work stopped, just like we do with  
> other code.
>>   I guessing this will happen quickly for the eclipse plugin given  
>> how many eclipse users there are out there and we will be better  off 
>> for waiting a bit.
> Why?
> geir
>> -dain

View raw message