You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Sachin Patel <sp...@gmail.com> on 2005/11/01 13:41:37 UTC

Re: [continuum] BUILD SUCCESSFUL: Geronimo

This is great!!

continuum wrote:
> http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/21
> 

Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by Matt Hogstrom <ma...@hogstrom.org>.
Sweet :)

Sachin Patel wrote:
> Could I we this up for devtools as well?
> 
> Sachin Patel wrote:
>> This is great!!
>>
>> continuum wrote:
>>> http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/21 
>>>
>>>
>>
> 
> 
> 


gbuild: devtools in continuum (was Re: [continuum] BUILD SUCCESSFUL: Geronimo)

Posted by David Blevins <da...@visi.com>.
On Nov 1, 2005, at 1:33 PM, Sachin Patel wrote:

> Only tricky part is that I depend on Eclipse, and a handful of  
> other Eclipse projects to build.  And I'm usually picking up weekly  
> builds from them to build against.  So is there something that  
> could be set up to be able to upload these external dependencies? I  
> really wish my eclipse dependencies could be downloadable with  
> Maven :)
>

Dunno.  I don't know where they would be uploaded to.  Do you think  
it may be just as easy to download them and install them into the  
maven.local.repo?

I use some goop (a.k.a. jelly) like this in openejb 1 to download  
tomcat into the maven.repo.local.  Something somewhat similar may  
work for you.

     <goal name="setup:tomcat50">
       <j:set var="tomcat.version" value="5.0.28"/>
       <j:set var="tomcat.download" value="http://www.ibiblio.org/pub/ 
mirrors/apache/jakarta/tomcat-5/v${tomcat.version}/bin/jakarta-tomcat- 
${tom\cat.version}.zip"/>
       <attainGoal name="setup:tomcat"/>
     </goal>
     <goal name="setup:tomcat55">
       <j:set var="tomcat.version" value="5.5.9"/>
       <j:set var="tomcat.download" value="http://www.ibiblio.org/pub/ 
mirrors/apache/jakarta/tomcat-5/v${tomcat.version}/bin/jakarta-tomcat- 
${tom\cat.version}.zip"/>
       <attainGoal name="setup:tomcat"/>
     </goal>

     <goal name="setup:tomcat4">
       <j:set var="tomcat.version" value="4.1.31"/>
       <j:set var="tomcat.download" value="http://www.ibiblio.org/pub/ 
mirrors/apache/jakarta/tomcat-4/v4.1.31/bin/jakarta-tomcat-$ 
{tomcat.version\}.zip"/>
       <attainGoal name="setup:tomcat"/>
     </goal>

     <goal name="setup:tomcat">
       <j:set var="targetDir" value="${basedir}/target/"/>

       <j:set var="tomcat.dist" value="${maven.repo.local}/tomcat/ 
distributions/jakarta-tomcat-${tomcat.version}.zip"/>
       <j:set var="tomcat.home" value="${targetDir}/jakarta-tomcat-$ 
{tomcat.version}"/>
       <j:set var="openejb.home" value="${targetDir}/openejb-$ 
{pom.currentVersion}" />

       <!-- Download tomcat if it isn't in the repo -->
       <u:file var="fileAsFile" name="${tomcat.dist}"/>
       <j:if test="${!(fileAsFile.exists())}">
         <mkdir dir="${maven.repo.local}/tomcat/distributions"/>
         <get src="${tomcat.download}" dest="${tomcat.dist}"/>
       </j:if>

       <!-- Unzip if not unzipped -->
       <u:file var="fileAsFile" name="${tomcat.home}"/>
       <j:if test="${!(fileAsFile.exists())}">
         <unjar src="${tomcat.dist}" dest="${targetDir}"/>
         <chmod dir="${tomcat.home}/bin" perm="u+x" includes="**/*.sh"/>
       </j:if>
     </goal>






Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by Sachin Patel <sp...@gmail.com>.
Only tricky part is that I depend on Eclipse, and a handful of other 
Eclipse projects to build.  And I'm usually picking up weekly builds 
from them to build against.  So is there something that could be set up 
to be able to upload these external dependencies? I really wish my 
eclipse dependencies could be downloadable with Maven :)

David Blevins wrote:
> 
> On Nov 1, 2005, at 12:55 PM, Sachin Patel wrote:
> 
>> David Blevins wrote:
>>
>>> On Nov 1, 2005, at 4:46 AM, Sachin Patel wrote:
>>>
>>>> Could I we this up for devtools as well?
>>>>
>>>>
>>> Absolutely.
>>> I'm not exactly sure how to build, though.  Seems most of the 
>>> project.xmls use the <extends> tag so we won't be able to put them in 
>>> continuum as maven 1 projects.
>>>
>>
>> Don't understand.  Geronimo is using <extends> as well.  What makes it 
>> different?
>>
> 
> No difference, we run Geronimo as shell project too.   I've never built 
> devtools, though, so if you can help me there I could whip something up 
> like I did for Geronimo.
> 
>>
>>> Is the inheritance actually useful to you or just there to follow 
>>> convention?
>>>
>>
>> Its useful.  I need a parent project.properties as I have a good 
>> number of properties shared across the individual projects.  I'd hate 
>> to have to respecify them multiple times.
>>
> 
> That's cool.  Continuum gets smart enough to do things like report which 
> test failed, etc. when you are dealing with a maven 1 or 2 project.  Up 
> to you if that is worth the trade-off of loosing project.xml 
> inheritance.  You can always poke at it later if you like.  You could 
> also convert to m2 and keep the inheritance if you are interested in the 
> "smarter" continuum support.
> 
> I'd really like to flatten the inheritance in Geronimo but there are 
> like 40+ modules compared to 4 in the devtools.  I'm jealous :)
> 
> -David
> 
> 
>>
>>> -David
>>>
>>>> Sachin Patel wrote:
>>>>
>>>>
>>>>> This is great!!
>>>>> continuum wrote:
>>>>>
>>>>>
>>>>>> http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/21 
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>
>>
> 
> 

Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by David Blevins <da...@visi.com>.
On Nov 1, 2005, at 2:21 PM, Brett Porter wrote:

> On 11/2/05, David Blevins <da...@visi.com> wrote:
>
>>
>> That's cool.  Continuum gets smart enough to do things like report
>> which test failed, etc. when you are dealing with a maven 1 or 2
>> project.  Up to you if that is worth the trade-off of loosing
>> project.xml inheritance.  You can always poke at it later if you
>> like.  You could also convert to m2 and keep the inheritance if you
>> are interested in the "smarter" continuum support.
>>
>
> You shouldn't need to get rid of inheritence, just only build the
> common root (which I thought you were doing anyway).
>

I set up Geronimo as a shell project, then added a script called ./ 
maven.sh that just executes 'maven "$@"'
(see the build definition at http://ci.gbuild.org/continuum/servlet/ 
continuum/target/View.vm/fid/shellProject/id/1)

I'm not sure how to do it the way you describe.  We essentially have  
this in our layout:

project.xml (child)
etc/project.xml (parent)
modules/*/project.xml (child)
plugins/*/project.xml (child)
applications/*/project.xml (child)

> Certainly a feature for Continuum 1.1.
>

Sounds good to me.

-David


Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by Brett Porter <br...@gmail.com>.
On 11/2/05, David Blevins <da...@visi.com> wrote:
>
> That's cool.  Continuum gets smart enough to do things like report
> which test failed, etc. when you are dealing with a maven 1 or 2
> project.  Up to you if that is worth the trade-off of loosing
> project.xml inheritance.  You can always poke at it later if you
> like.  You could also convert to m2 and keep the inheritance if you
> are interested in the "smarter" continuum support.

You shouldn't need to get rid of inheritence, just only build the
common root (which I thought you were doing anyway).

Note that this doesn't affect m2 at all as the parents are referenced
from the repository, not the file system.

Certainly a feature for Continuum 1.1.

>
> I'd really like to flatten the inheritance in Geronimo but there are
> like 40+ modules compared to 4 in the devtools.  I'm jealous :)

I don't think flattening is a good goal, its an important tool in
factoring the build correctly.

Cheers,
Brett

Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by David Blevins <da...@visi.com>.
On Nov 1, 2005, at 12:55 PM, Sachin Patel wrote:

> David Blevins wrote:
>
>> On Nov 1, 2005, at 4:46 AM, Sachin Patel wrote:
>>
>>> Could I we this up for devtools as well?
>>>
>>>
>> Absolutely.
>> I'm not exactly sure how to build, though.  Seems most of the  
>> project.xmls use the <extends> tag so we won't be able to put them  
>> in continuum as maven 1 projects.
>>
>
> Don't understand.  Geronimo is using <extends> as well.  What makes  
> it different?
>

No difference, we run Geronimo as shell project too.   I've never  
built devtools, though, so if you can help me there I could whip  
something up like I did for Geronimo.

>
>> Is the inheritance actually useful to you or just there to follow  
>> convention?
>>
>
> Its useful.  I need a parent project.properties as I have a good  
> number of properties shared across the individual projects.  I'd  
> hate to have to respecify them multiple times.
>

That's cool.  Continuum gets smart enough to do things like report  
which test failed, etc. when you are dealing with a maven 1 or 2  
project.  Up to you if that is worth the trade-off of loosing  
project.xml inheritance.  You can always poke at it later if you  
like.  You could also convert to m2 and keep the inheritance if you  
are interested in the "smarter" continuum support.

I'd really like to flatten the inheritance in Geronimo but there are  
like 40+ modules compared to 4 in the devtools.  I'm jealous :)

-David


>
>> -David
>>
>>> Sachin Patel wrote:
>>>
>>>
>>>> This is great!!
>>>> continuum wrote:
>>>>
>>>>
>>>>> http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ 
>>>>> ProjectBuild/id/1/buildId/21
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>
>


Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by Sachin Patel <sp...@gmail.com>.
David Blevins wrote:
> 
> On Nov 1, 2005, at 4:46 AM, Sachin Patel wrote:
> 
>> Could I we this up for devtools as well?
>>
> 
> Absolutely.
> 
> I'm not exactly sure how to build, though.  Seems most of the 
> project.xmls use the <extends> tag so we won't be able to put them in 
> continuum as maven 1 projects.  

Don't understand.  Geronimo is using <extends> as well.  What makes it 
different?

Is the inheritance actually useful to
> you or just there to follow convention?

Its useful.  I need a parent project.properties as I have a good number 
of properties shared across the individual projects.  I'd hate to have 
to respecify them multiple times.

> 
> -David
> 
> 
>> Sachin Patel wrote:
>>
>>> This is great!!
>>> continuum wrote:
>>>
>>>> http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/21 
>>>>
>>>>
>>>>
>>
>>
> 
> 

Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by David Blevins <da...@visi.com>.
On Nov 1, 2005, at 4:46 AM, Sachin Patel wrote:

> Could I we this up for devtools as well?
>

Absolutely.

I'm not exactly sure how to build, though.  Seems most of the  
project.xmls use the <extends> tag so we won't be able to put them in  
continuum as maven 1 projects.  Is the inheritance actually useful to  
you or just there to follow convention?

-David


> Sachin Patel wrote:
>
>> This is great!!
>> continuum wrote:
>>
>>> http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ 
>>> ProjectBuild/id/1/buildId/21
>>>
>>>
>
>


Re: [continuum] BUILD SUCCESSFUL: Geronimo

Posted by Sachin Patel <sp...@gmail.com>.
Could I we this up for devtools as well?

Sachin Patel wrote:
> This is great!!
> 
> continuum wrote:
>> http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/21 
>>
>>
>