openejb publishing restored (was Re: M2 Issues and Actions - svn:externals workaround)

[David Blevins <da...@visi.com>]

Ok, Jason and I got it working on gbuild.  Jars are pushed to  
codehaus via webdav *and* I up'ed the frequency to every half hour.    
So...

Current openejb jars *will* be available with in (0-30 min + build  
time) of any commit to openejb.

Does that seem reasonable to everyone?  David Jencks, do you think  
this is good?

-David


On Jun 30, 2006, at 11:14 AM, David Blevins wrote:

> Built and published the latest jars from my mac.
>
> For reference it's simply:  Finder -> Go -> Connect to Server
> Use "https://dav.codehaus.org/dist/openejb/" for the Server  
> Address.  Good idea to click the "+" button to add it to your  
> favorites.
>
> Anyway, working on getting a similar setup on gbuild.
>
> -David
>
>
> On Jun 29, 2006, at 3:35 PM, Jason Dillon wrote:
>
>> FYI, I'm working with David Blevins now to try and get the OpenEJB  
>> jars published... and once published then the defautl build will  
>> not need these sources.  But for folks that want to build G and  
>> OpenEJB in one swoop we can setup a super-build that does this.
>>
>> But, right now still working on how to get Continuum to publish  
>> jars to the Codehaus' WebDAV...
>>
>> --jason
>>
>>
>> On Jun 29, 2006, at 3:20 PM, Jacek Laskowski wrote:
>>
>>> On 6/30/06, David Jencks <da...@yahoo.com> wrote:
>>>
>>>> > Note http rather than https.
>>>>
>>>> I hope someone who actually knows will speak up, but I thought  
>>>> https
>>>> worked fine for non-committers whereas http did not work for
>>>> committers.  If true I would suggest https rather than http.
>>>
>>> AFAIUI, you won't be able to work with the openejb checkout as if it
>>> was a regular checkout. It's only for non-committers' convenience to
>>> let them build Geronimo using M2. OpenEJB committers will have to
>>> remove their own copy of OpenEJB from within Geronimo and work  
>>> with it
>>> outside Geronimo local source directory. Thus, I chose http which is
>>> faster.
>>>
>>>> david jencks
>>>
>>> Jacek
>>>
>>> -- 
>>> Jacek Laskowski
>>> http://www.laskowski.net.pl
>>
>

Re: openejb publishing restored (was Re: M2 Issues and Actions - svn:externals workaround)

[Jason Dillon <ja...@planet57.com>]

> You aren't paying attention to what I said.  Only openejb uses g  
> bits in it, the others can all be built with no g parts present.   
> So, if I change something in g, I know I didn't break anything  
> except maybe openejb.  So, I want to be able to check really easily  
> by having one build that includes everything that depends on g  
> stuff and gets into our assembled server.

Oh... my bad... minor dyslexia always causes me problems.

It is possible to make a build like that.  And as I have said before  
I can help you make that a reality... after we have finished with the  
main m2 build.

Which I think is only really pending the xmlbeans and assembly fixes  
until it is useable... so hopefully we will have m2 functional soon!

--jason

Re: openejb publishing restored (was Re: M2 Issues and Actions - svn:externals workaround)

[David Jencks <da...@yahoo.com>]

On Jun 30, 2006, at 3:27 PM, Jason Dillon wrote:

>> It's very good, but it doesn't help with my desire to be able to  
>> build g + all the stuff that depends on g that goes into g in one  
>> step.  since this isn't possible right now entirely in m2 anyway  
>> due to the plugin issues I think I'll have to be satisfied with a  
>> script that runs m2 in several places.
>
> Thats gotta be one crazy script... commons-lang, log4j, openejb,  
> tranql, specs, commons-cli, commons-lang, commons-collections,  
> howl, derby, <way to many more to list>.

You aren't paying attention to what I said.  Only openejb uses g bits  
in it, the others can all be built with no g parts present.  So, if I  
change something in g, I know I didn't break anything except maybe  
openejb.  So, I want to be able to check really easily by having one  
build that includes everything that depends on g stuff and gets into  
our assembled server.

thanks
david jencks

>
> I don't think that it is feasible to even attempt a system that  
> will build everything in one swoop.
>
> Anyways, I know that is not what you meant.
>
> I think we can provide support for building a bunch of stuff at  
> once for peeps like you who want that, but I do not believe that  
> should be the default that everyone needs to use to get a  
> functional server.
>
> David, once m2 is functional I can help to make a build that will  
> get you want you want while keeping the default build relatively  
> simplified.
>
> --jason
>
>

Re: openejb publishing restored (was Re: M2 Issues and Actions - svn:externals workaround)

[Jason Dillon <ja...@planet57.com>]

> It's very good, but it doesn't help with my desire to be able to  
> build g + all the stuff that depends on g that goes into g in one  
> step.  since this isn't possible right now entirely in m2 anyway  
> due to the plugin issues I think I'll have to be satisfied with a  
> script that runs m2 in several places.

Thats gotta be one crazy script... commons-lang, log4j, openejb,  
tranql, specs, commons-cli, commons-lang, commons-collections, howl,  
derby, <way to many more to list>.

I don't think that it is feasible to even attempt a system that will  
build everything in one swoop.

Anyways, I know that is not what you meant.

I think we can provide support for building a bunch of stuff at once  
for peeps like you who want that, but I do not believe that should be  
the default that everyone needs to use to get a functional server.

David, once m2 is functional I can help to make a build that will get  
you want you want while keeping the default build relatively simplified.

--jason

Re: openejb publishing restored (was Re: M2 Issues and Actions - svn:externals workaround)

[David Jencks <da...@yahoo.com>]

On Jun 30, 2006, at 3:09 PM, David Blevins wrote:

> Ok, Jason and I got it working on gbuild.  Jars are pushed to  
> codehaus via webdav *and* I up'ed the frequency to every half  
> hour.   So...
>
> Current openejb jars *will* be available with in (0-30 min + build  
> time) of any commit to openejb.
>
> Does that seem reasonable to everyone?  David Jencks, do you think  
> this is good?

It's very good, but it doesn't help with my desire to be able to  
build g + all the stuff that depends on g that goes into g in one  
step.  since this isn't possible right now entirely in m2 anyway due  
to the plugin issues I think I'll have to be satisfied with a script  
that runs m2 in several places.

thanks
david jencks

>
> -David
>
>
> On Jun 30, 2006, at 11:14 AM, David Blevins wrote:
>
>> Built and published the latest jars from my mac.
>>
>> For reference it's simply:  Finder -> Go -> Connect to Server
>> Use "https://dav.codehaus.org/dist/openejb/" for the Server  
>> Address.  Good idea to click the "+" button to add it to your  
>> favorites.
>>
>> Anyway, working on getting a similar setup on gbuild.
>>
>> -David
>>
>>
>> On Jun 29, 2006, at 3:35 PM, Jason Dillon wrote:
>>
>>> FYI, I'm working with David Blevins now to try and get the  
>>> OpenEJB jars published... and once published then the defautl  
>>> build will not need these sources.  But for folks that want to  
>>> build G and OpenEJB in one swoop we can setup a super-build that  
>>> does this.
>>>
>>> But, right now still working on how to get Continuum to publish  
>>> jars to the Codehaus' WebDAV...
>>>
>>> --jason
>>>
>>>
>>> On Jun 29, 2006, at 3:20 PM, Jacek Laskowski wrote:
>>>
>>>> On 6/30/06, David Jencks <da...@yahoo.com> wrote:
>>>>
>>>>> > Note http rather than https.
>>>>>
>>>>> I hope someone who actually knows will speak up, but I thought  
>>>>> https
>>>>> worked fine for non-committers whereas http did not work for
>>>>> committers.  If true I would suggest https rather than http.
>>>>
>>>> AFAIUI, you won't be able to work with the openejb checkout as  
>>>> if it
>>>> was a regular checkout. It's only for non-committers'  
>>>> convenience to
>>>> let them build Geronimo using M2. OpenEJB committers will have to
>>>> remove their own copy of OpenEJB from within Geronimo and work  
>>>> with it
>>>> outside Geronimo local source directory. Thus, I chose http  
>>>> which is
>>>> faster.
>>>>
>>>>> david jencks
>>>>
>>>> Jacek
>>>>
>>>> -- 
>>>> Jacek Laskowski
>>>> http://www.laskowski.net.pl
>>>
>>
>

Re: openejb publishing restored (was Re: M2 Issues and Actions - svn:externals workaround)

[Jason Dillon <ja...@planet57.com>]

We should remove the openejb/modules from the G root pom.xml.

Once some of the other issues are sorted I can put together an all-in- 
one-special-build for those folks that want to build openejb+tranql+G  
all at once.

--jason


On Jun 30, 2006, at 3:09 PM, David Blevins wrote:

> Ok, Jason and I got it working on gbuild.  Jars are pushed to  
> codehaus via webdav *and* I up'ed the frequency to every half  
> hour.   So...
>
> Current openejb jars *will* be available with in (0-30 min + build  
> time) of any commit to openejb.
>
> Does that seem reasonable to everyone?  David Jencks, do you think  
> this is good?
>
> -David
>
>
> On Jun 30, 2006, at 11:14 AM, David Blevins wrote:
>
>> Built and published the latest jars from my mac.
>>
>> For reference it's simply:  Finder -> Go -> Connect to Server
>> Use "https://dav.codehaus.org/dist/openejb/" for the Server  
>> Address.  Good idea to click the "+" button to add it to your  
>> favorites.
>>
>> Anyway, working on getting a similar setup on gbuild.
>>
>> -David
>>
>>
>> On Jun 29, 2006, at 3:35 PM, Jason Dillon wrote:
>>
>>> FYI, I'm working with David Blevins now to try and get the  
>>> OpenEJB jars published... and once published then the defautl  
>>> build will not need these sources.  But for folks that want to  
>>> build G and OpenEJB in one swoop we can setup a super-build that  
>>> does this.
>>>
>>> But, right now still working on how to get Continuum to publish  
>>> jars to the Codehaus' WebDAV...
>>>
>>> --jason
>>>
>>>
>>> On Jun 29, 2006, at 3:20 PM, Jacek Laskowski wrote:
>>>
>>>> On 6/30/06, David Jencks <da...@yahoo.com> wrote:
>>>>
>>>>> > Note http rather than https.
>>>>>
>>>>> I hope someone who actually knows will speak up, but I thought  
>>>>> https
>>>>> worked fine for non-committers whereas http did not work for
>>>>> committers.  If true I would suggest https rather than http.
>>>>
>>>> AFAIUI, you won't be able to work with the openejb checkout as  
>>>> if it
>>>> was a regular checkout. It's only for non-committers'  
>>>> convenience to
>>>> let them build Geronimo using M2. OpenEJB committers will have to
>>>> remove their own copy of OpenEJB from within Geronimo and work  
>>>> with it
>>>> outside Geronimo local source directory. Thus, I chose http  
>>>> which is
>>>> faster.
>>>>
>>>>> david jencks
>>>>
>>>> Jacek
>>>>
>>>> -- 
>>>> Jacek Laskowski
>>>> http://www.laskowski.net.pl
>>>
>>
>