How to use Maven/Ant from SCM?

[Hilco Wijbenga <hi...@gmail.com>]

We have Ant stored in CVS as part of our project so that after a
checkout everything is available for a build (it also facilitates
reproducible builds). I would like to setup Continuum to build our
project but I don't see how I can get Continuum to use "our" Ant.

As we will be moving to Maven in the near future the same would apply
there: we'd put Maven in CVS and we'd want to use "our" Maven to run
the build.

Is this currently possible? If yes, how?

Re: How to use Maven/Ant from SCM?

[Emmanuel Venisse <em...@venisse.net>]

you'll can choose a path so 2 and 3 will be supported.

Hilco Wijbenga a écrit :
> On 2/16/07, Emmanuel Venisse <em...@venisse.net> wrote:
>> I think you'll can choose a particular version by build definition, 
>> and a version will be
>> defined by a path to the install.
> 
> I'm not sure I understand you.
> 
> 1. Pick a particular Ant version (1.6.2, 1.6.3, 1.6.4, 1.6.5, etcetera);
> 2. Use a particular Ant installation on the Continuum server (e.g.
> /opt/ant-1.6.5-sec, or /opt/ant-1.6.5-with-optional-tasks);
> 3. Use the Ant that came with the project
> (.../continuum/working-directory/my_project/ant-for-this-project).
> 
> So only option 1 would be supported?
> 
> 
> 

Re: How to use Maven/Ant from SCM?

[Hilco Wijbenga <hi...@gmail.com>]

On 2/16/07, Emmanuel Venisse <em...@venisse.net> wrote:
> I think you'll can choose a particular version by build definition, and a version will be
> defined by a path to the install.

I'm not sure I understand you.

1. Pick a particular Ant version (1.6.2, 1.6.3, 1.6.4, 1.6.5, etcetera);
2. Use a particular Ant installation on the Continuum server (e.g.
/opt/ant-1.6.5-sec, or /opt/ant-1.6.5-with-optional-tasks);
3. Use the Ant that came with the project
(.../continuum/working-directory/my_project/ant-for-this-project).

So only option 1 would be supported?

Re: How to use Maven/Ant from SCM?

[Emmanuel Venisse <em...@venisse.net>]

I think you'll can choose a particular version by build definition, and a version will be defined by a path to the install.

Emmanuel

Hilco Wijbenga a écrit :
> On 2/16/07, Emmanuel Venisse <em...@venisse.net> wrote:
>> We'll introduce continuum profiles where you'll can define some things 
>> like jdk,
>> maven, ant versions
> 
> Would that mean just an Ant version? Or would I be able to tell
> Continuum to use a particular Ant installation, either "somewhere" on
> the server (e.g. /opt/ant-1.6.5-sec, or
> /opt/ant-1.6.5-with-optional-tasks) or as part of the checkout
> (.../continuum/working-directory/my_project/ant-for-this-project)?
> 
> 
> 

Re: How to use Maven/Ant from SCM?

[Hilco Wijbenga <hi...@gmail.com>]

On 2/16/07, Emmanuel Venisse <em...@venisse.net> wrote:
> We'll introduce continuum profiles where you'll can define some things like jdk,
> maven, ant versions

Would that mean just an Ant version? Or would I be able to tell
Continuum to use a particular Ant installation, either "somewhere" on
the server (e.g. /opt/ant-1.6.5-sec, or
/opt/ant-1.6.5-with-optional-tasks) or as part of the checkout
(.../continuum/working-directory/my_project/ant-for-this-project)?

Re: How to use Maven/Ant from SCM?

[Emmanuel Venisse <em...@venisse.net>]

Hilco Wijbenga a écrit :
> On 2/15/07, Emmanuel Venisse <em...@venisse.net> wrote:
>> In your case, I see only one solution. You need to use the Shell project.
>> In your project, you create a little shell script that run your 
>> ant/maven for the build,
>> and use it as the command line to run.
> 
> Too bad. :-(
> 
> I discovered that CruiseControl has an option to set which Ant to use
> (although I don't know the details). Are there plans to add something
> similar to Continuum? Perhaps two checkouts, the first for the build
> tool, the second for the source? It seems fairly simple to do.

We'll introduce continuum profiles where you'll can define some things like jdk, maven, ant versions

> 
> (This is assuming that my setup is reasonably representative. I got
> the impression that this (i.e. having your build tool in your SCM) was
> advertised as kind of a best practice.)
> 
> Cheers,
> Hilco
> 
> 
> 

Re: How to use Maven/Ant from SCM?

[Hilco Wijbenga <hi...@gmail.com>]

On 2/15/07, Emmanuel Venisse <em...@venisse.net> wrote:
> In your case, I see only one solution. You need to use the Shell project.
> In your project, you create a little shell script that run your ant/maven for the build,
> and use it as the command line to run.

Too bad. :-(

I discovered that CruiseControl has an option to set which Ant to use
(although I don't know the details). Are there plans to add something
similar to Continuum? Perhaps two checkouts, the first for the build
tool, the second for the source? It seems fairly simple to do.

(This is assuming that my setup is reasonably representative. I got
the impression that this (i.e. having your build tool in your SCM) was
advertised as kind of a best practice.)

Cheers,
Hilco

Re: How to use Maven/Ant from SCM?

[Emmanuel Venisse <em...@venisse.net>]

In your case, I see only one solution. You need to use the Shell project.
In your project, you create a little shell script that run your ant/maven for the build, and use it as the command line to run.

Emmanuel

Hilco Wijbenga a écrit :
> We have Ant stored in CVS as part of our project so that after a
> checkout everything is available for a build (it also facilitates
> reproducible builds). I would like to setup Continuum to build our
> project but I don't see how I can get Continuum to use "our" Ant.
> 
> As we will be moving to Maven in the near future the same would apply
> there: we'd put Maven in CVS and we'd want to use "our" Maven to run
> the build.
> 
> Is this currently possible? If yes, how?
> 
> 
>