You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jason Dillon <ja...@planet57.com> on 2006/11/08 01:58:58 UTC

svn:external include of openejb2 into G ?

Now that OpenEJB is at Apache, I don't see any reason why we don't  
use svn:externals to include the openejb2 modules directly into the  
server/trunk tree.

Then we will have a "openejb" tree (peer to modules) and can build  
everything at once... giving us a better chance of always keeping in  
sync.

  * * *

Only need to add the svn prop, and make a few changes to the top- 
level pom.xml to make it work.  Appears to build fine too.  I think  
this is a good short-term solution to help keep dev in

Comments (either way)?

--jason

Re: svn:external include of openejb2 into G ?

Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 11/8/06, Jason Dillon <ja...@planet57.com> wrote:
> Now that OpenEJB is at Apache, I don't see any reason why we don't
> use svn:externals to include the openejb2 modules directly into the
> server/trunk tree.
>
> Then we will have a "openejb" tree (peer to modules) and can build
> everything at once... giving us a better chance of always keeping in
> sync.

Are there any (possible) problems you're aware of? Will openejb
developers end up with two copies of openejb repo locally?

If answers are negative, I'm for it.

Jacek

-- 
Jacek Laskowski
http://www.jaceklaskowski.pl

Re: svn:external include of openejb2 into G ?

Posted by David Jencks <da...@yahoo.com>.
On Nov 7, 2006, at 5:54 PM, Matt Hogstrom wrote:

> The easier a build can be for new comers is desirable.  I keep them  
> separate.

Does this mean you want openejb2 as an svn:externals?  I think that  
will considerably reduce the typical new users problems getting a  
working build.

thanks
david jencks

> On Nov 7, 2006, at 8:41 PM, David Jencks wrote:
>
>>
>> On Nov 7, 2006, at 4:58 PM, Jason Dillon wrote:
>>
>>> Now that OpenEJB is at Apache, I don't see any reason why we  
>>> don't use svn:externals to include the openejb2 modules directly  
>>> into the server/trunk tree.
>>>
>>> Then we will have a "openejb" tree (peer to modules) and can  
>>> build everything at once... giving us a better chance of always  
>>> keeping in sync.
>>>
>>>  * * *
>>>
>>> Only need to add the svn prop, and make a few changes to the top- 
>>> level pom.xml to make it work.  Appears to build fine too.  I  
>>> think this is a good short-term solution to help keep dev in
>>>
>>> Comments (either way)?
>>
>> I'm + 0.2 on having the svn externals but I would really really  
>> like a profile in the root g pom so I can build g + openejb at  
>> once.  I've been keeping this in my pom for months and would sure  
>> like to have it committed.  I have completely failed in putting it  
>> in a separate profiles.xml file.
>>
>> thanks
>> david jencks
>>
>>>
>>> --jason
>>
>>
>
> Matt Hogstrom
> matt@hogstrom.org
>
>
>


Re: svn:external include of openejb2 into G ?

Posted by Matt Hogstrom <ma...@hogstrom.org>.
The easier a build can be for new comers is desirable.  I keep them  
separate.
On Nov 7, 2006, at 8:41 PM, David Jencks wrote:

>
> On Nov 7, 2006, at 4:58 PM, Jason Dillon wrote:
>
>> Now that OpenEJB is at Apache, I don't see any reason why we don't  
>> use svn:externals to include the openejb2 modules directly into  
>> the server/trunk tree.
>>
>> Then we will have a "openejb" tree (peer to modules) and can build  
>> everything at once... giving us a better chance of always keeping  
>> in sync.
>>
>>  * * *
>>
>> Only need to add the svn prop, and make a few changes to the top- 
>> level pom.xml to make it work.  Appears to build fine too.  I  
>> think this is a good short-term solution to help keep dev in
>>
>> Comments (either way)?
>
> I'm + 0.2 on having the svn externals but I would really really  
> like a profile in the root g pom so I can build g + openejb at  
> once.  I've been keeping this in my pom for months and would sure  
> like to have it committed.  I have completely failed in putting it  
> in a separate profiles.xml file.
>
> thanks
> david jencks
>
>>
>> --jason
>
>

Matt Hogstrom
matt@hogstrom.org




Re: svn:external include of openejb2 into G ?

Posted by David Jencks <da...@yahoo.com>.
On Nov 7, 2006, at 4:58 PM, Jason Dillon wrote:

> Now that OpenEJB is at Apache, I don't see any reason why we don't  
> use svn:externals to include the openejb2 modules directly into the  
> server/trunk tree.
>
> Then we will have a "openejb" tree (peer to modules) and can build  
> everything at once... giving us a better chance of always keeping  
> in sync.
>
>  * * *
>
> Only need to add the svn prop, and make a few changes to the top- 
> level pom.xml to make it work.  Appears to build fine too.  I think  
> this is a good short-term solution to help keep dev in
>
> Comments (either way)?

I'm + 0.2 on having the svn externals but I would really really like  
a profile in the root g pom so I can build g + openejb at once.  I've  
been keeping this in my pom for months and would sure like to have it  
committed.  I have completely failed in putting it in a separate  
profiles.xml file.

thanks
david jencks

>
> --jason


Re: svn:external include of openejb2 into G ?

Posted by Paul McMahan <pa...@gmail.com>.
I can see how this would benefit those who work on both openejb and
geronimo.  But for folks who don't mind picking up openejb from the
snapshot repo would making this change cause top down builds and svn
operations such as checkout, update, and status to take much longer?

Best wishes,
Paul

On 11/7/06, Jason Dillon <ja...@planet57.com> wrote:
> Now that OpenEJB is at Apache, I don't see any reason why we don't
> use svn:externals to include the openejb2 modules directly into the
> server/trunk tree.
>
> Then we will have a "openejb" tree (peer to modules) and can build
> everything at once... giving us a better chance of always keeping in
> sync.
>
>   * * *
>
> Only need to add the svn prop, and make a few changes to the top-
> level pom.xml to make it work.  Appears to build fine too.  I think
> this is a good short-term solution to help keep dev in
>
> Comments (either way)?
>
> --jason
>