Project group build definition : variable subsitution
Hi,
I'm working on the SYNERGY SCM provider and the way SYNERGY deals
with its workingcopy is very different from SVN.
My problem is :
I have a project foo, structure is :
foo/
pom.xml
src/
If I checkout with continuum I will have something like this :
[...]/workingdirectory/1/foo.
The foo directory is part of the project and can't be avoided for
SYNERGY.
I have to specify foo/pom.xml in the pom filename for my builds.
There is no problem here but when you start to deal with project
group builds from continuum 1.1beta2 it's impossible :
Group foobar is :
foo/
pom.xml
src/
bar/
pom.xml
src/
So I have on filesystem:
workingdirectory/1/foo
workingdirectory/2/bar
And now how can I use a group defined build? pom.xml are not in the
continuum basedir...
Is there any chance to have access to some sort of project-specific
variable substitution inside project group build definitions?
It would be great to have something like ${project_name} accessible
in Build File, Goals and Arguments.
Thank you for your help.
--
David Causse
Post-scriptum La Poste
Ce message est confidentiel. Sous réserve de tout accord conclu par
écrit entre vous et La Poste, son contenu ne représente en aucun cas un
engagement de la part de La Poste. Toute publication, utilisation ou
diffusion, même partielle, doit être autorisée préalablement. Si vous
n'êtes pas destinataire de ce message, merci d'en avertir immédiatement
l'expéditeur.
Re: UI for Group Actions
On 9/10/07, LAMY Olivier [EMAIL PROTECTED] wrote: In fact, I think Choose a Build Definition is not very clear. The best should be something like : You can choose a Build Definition but if you don't the default one will be used. But it's a little bit huge for a list box ;-) . I wondered if it would use the default. :) If that's it, then put Default Build Definition in as the first element in the drop down, and pre-select it. The behavior is then implied by the way the form looks. I will look at the tooltip feature in webwork to add help/explanation on how does it work. Great idea! And fix CONTINUUM-1439 too (sorry I haven't tested with shell script). So far I haven't been able to reproduce it, and I don't have the database contents anymore. If you can't make it happen just close as Can't Reproduce and I'll reopen if I figure it out. -- Wendy
Re: Wrong icons immediately after adding projects
Wendy Smoak a écrit : When I add a multi-module project, the project group summary shows the 'cancel build' icon for the first project, and 'queued build' icons for the rest. This is incorrect, nothing is building or queued at that time. Not exactly. All projects are in queue. It isn't the build queue but the checkout queue, so icons are correct. If I navigate away and come back, it correctly shows the 'build project' icon for all of them. because your projects are checked out. (This is in the 5th column from the right in r574073 built today.)
Re: SCM Matrix for Continuum?
I think it's up to date but I'll verify. cloumns that are used by Continuum are : changelog, checkout, update The release part use checkin, status, tag columns too edit/unedit and login columns can be used by some scm tools. Emmanuel Wendy Smoak a écrit : I'm in need of an SCM Matrix for a Continuum talk... can someone familiar with maven-scm take a look at the one on the wiki and let me know if it's up to date? http://docs.codehaus.org/display/SCM/SCM+Matrix Also, what columns are relevant for Continuum? Thanks,
Re: Wrong icons immediately after adding projects
On 9/10/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Wendy Smoak a écrit : When I add a multi-module project, the project group summary shows the 'cancel build' icon for the first project, and 'queued build' icons for the rest. This is incorrect, nothing is building or queued at that time. Not exactly. All projects are in queue. It isn't the build queue but the checkout queue, so icons are correct. I can accept the technical reason, but according to the legend at the left, that icon means Queued Build (or Cancel Build' for the first one.) As a user, when I see that icon, the next thing I expect to see is a build result, and that doesn't happen (because it wasn't *really* queued to build, just to check out.) -- Wendy
