openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: Eclipse Plugin for OpenJPA
Date Wed, 25 Feb 2009 07:03:36 GMT

On Feb 24, 2009, at 11:31 AM, Bill Stoddard wrote:

> Donald Woods wrote:
>> No idea.  It had already been created before I started working on  
>> Geronimo.
>>
>> From the ASF page -
>>   http://www.apache.org/foundation/how-it-works.html#incubator
>> it sounds like sub-projects should go through the incubator, so  
>> maybe we should just create a branch for tooling under the existing  
>> openjpa project and just handle it just as another OpenJPA binary  
>> release with its own JIRA component for bug/feature tracking and  
>> not deal with the sub-project process overhead for now.
>>
>>
> No need to go through the incubator to create a tooling sub-project  
> for OpenJPA.   Maybe 'sub-project' is not quite the right term here,  
> but the point is that the OpenJPA team can carve out svn space to  
> develop and maintain OpenJPA Eclipse tooling and you can package/ 
> release that stuff however you see fit (usual caveats apply). No  
> need for incubator foo here...

+1

Craig
>
>
> Bill
>
>> -Donald
>>
>>
>> Pinaki Poddar wrote:
>>> Yup, I agree.
>>> Did this separate subproject require approval from Apache Board?
>>>
>>>
>>> Donald Woods wrote:
>>>> For Geronimo, we also setup a Devtools subproject for our Eclipse  
>>>> plugins.  I would suggest doing that for OpenJPA, as the maven  
>>>> builds are different enough that you don't want non-Eclipse users  
>>>> to deal with the delays of downloading an Eclipse runtime for the  
>>>> build steps.  Also, you may want to release the tooling more or  
>>>> less often than a given branch(es) or support different levels of  
>>>> Eclipse with different versions of the plugins.
>>>>
>>>>
>>>> -Donald
>>>>
>>>>
>>>> Kevin Sutter wrote:
>>>>> Hi Pinaki,
>>>>> Thanks for starting this activity.  I've noticed that OpenEJB  
>>>>> has a
>>>>> separate
>>>>> project for the OpenEJB Eclipse Plugin.  Maybe we should consider
>>>>> following
>>>>> the same path?  Not sure if it's a lot of overhead to have a  
>>>>> separate
>>>>> project like that or not.
>>>>>
>>>>> Thoughts?
>>>>> Kevin
>>>>>
>>>>> On Mon, Feb 23, 2009 at 9:55 AM, Pinaki Poddar  
>>>>> <ppoddar@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>> For Eclipse IDE users, a plugin is available to help  
>>>>>> development with
>>>>>> OpenJPA [1]. It adds a builder step to Java projects in Eclipse
>>>>>> workspace
>>>>>> so
>>>>>> that all your persistent classes are bytecode enhanced as part  
>>>>>> of the
>>>>>> Eclipse's incremental compilation process.
>>>>>> Please note that, at this point, this plugin is in very early  
>>>>>> stage of
>>>>>> development and is not part of official OpenJPA release or  
>>>>>> maintenance.
>>>>>>
>>>>>> [1]
>>>>>> http://people.apache.org/~ppoddar/eclipse/index.html<http://people.apache.org/%7Eppoddar/eclipse/index.html

>>>>>> >
>>>>>>
>>>>>> Regards --
>>>>>>
>>>>>> Pinaki
>>>>>> -- 
>>>>>> View this message in context:
>>>>>> http://n2.nabble.com/Eclipse-Plugin-for-OpenJPA-tp2372730p2372730.html
>>>>>> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>
>>>
>>
>

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Mime
View raw message