Thread: [Ivyplugins-user] Project specific basedir?
Brought to you by:
ulsa
From: Jan B. <Jan...@ar...> - 2009-06-17 21:16:24
|
Hello everyone, In our setup all projects except one have their ivy.xml file at the root of their project folder. So we've set up IvyPublisher in our CC config file as <plugin name="ivypublisher" classname="net.sf.ivyplugins.ivypublisher.IvySuccessPublisher" project="${project.name}" basedir="${ccwork}/checkout/${project.name}" /> Works fine - except for one .. funny .. project, that liked to have it's ivy.xml in a subdirectory checkout/${project.name}/Build I was wondering if you can specify the basedir (or ivy.xml) location on a project-level? Maybe by setting a local property in the project a la <ivypublisher> <property name="ivy.conf.basedir" value="${ccwork}/checkout/${project.name}/Build" /> </ivypublisher> or something similar? Thanks, Jan |
From: Ulrik S. <ulr...@ja...> - 2009-06-18 11:03:25
|
You should be able to override any attributes when you actually use a plugin. Doesn't this work? <plugin name="ivypublisher" classname="net.sf.ivyplugins.ivypublisher.IvySuccessPublisher" project="${project.name}" basedir="${ccwork}/checkout/${project.name}" /> ... <project name="OK"> <ivypublisher /> <project name="funny"> <ivypublisher basedir="${ccwork}/checkout/${project.name}/Build" /> On Wed, Jun 17, 2009 at 11:16 PM, Jan Barnholt < Jan...@ar...> wrote: > Hello everyone, > > In our setup all projects except one have their ivy.xml file at the root of > their project folder. > So we've set up IvyPublisher in our CC config file as > > <plugin name="ivypublisher" > classname="net.sf.ivyplugins.ivypublisher.IvySuccessPublisher" > project="${project.name}" > basedir="${ccwork}/checkout/${project.name}" /> > Works fine - except for one .. funny .. project, that liked to have it's > ivy.xml in a subdirectory > checkout/${project.name}/Build > > I was wondering if you can specify the basedir (or ivy.xml) location on a > project-level? > Maybe by setting a local property in the project a la > > <ivypublisher> > <property name="ivy.conf.basedir" > value="${ccwork}/checkout/${project.name}/Build" /> > </ivypublisher> > > or something similar? > > Thanks, > Jan > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > ivyplugins-user mailing list > ivy...@li... > https://lists.sourceforge.net/lists/listinfo/ivyplugins-user > > -- Ulrik |
From: Jan B. <Jan...@ar...> - 2009-06-18 20:00:54
|
Thanks, Ulrik - I didn't realize you could also set the attributes at the <ivypublisher> tag on the project level! Works like a breeze for us. Maybe worth a short note in the docs to give users an idea how flexible IP is? Cheers, Jan ________________________________ From: ulr...@gm... [mailto:ulr...@gm...] On Behalf Of Ulrik Sandberg Sent: Thursday, 18 June 2009 11:02 p.m. To: Jan Barnholt Cc: ivy...@li... Subject: Re: [Ivyplugins-user] Project specific basedir? You should be able to override any attributes when you actually use a plugin. Doesn't this work? <plugin name="ivypublisher" classname="net.sf.ivyplugins.ivypublisher.IvySuccessPublisher" project="${project.name}" basedir="${ccwork}/checkout/${project.name}" /> ... <project name="OK"> <ivypublisher /> <project name="funny"> <ivypublisher basedir="${ccwork}/checkout/${project.name}/Build" /> |
From: Ulrik S. <ulr...@ja...> - 2009-06-19 05:52:40
|
Sure, we can add this in the doc, but it's really a generic CruiseControl feature<http://cruisecontrol.sourceforge.net/main/plugins.html#preconfiguration>which you can use with any plugin. On Thu, Jun 18, 2009 at 10:00 PM, Jan Barnholt < Jan...@ar...> wrote: > Thanks, Ulrik - > I didn't realize you could also set the attributes at the <ivypublisher> > tag on the project level! > > Works like a breeze for us. > Maybe worth a short note in the docs to give users an idea how flexible IP > is? > > Cheers, > Jan > > ________________________________ > > From: ulr...@gm... [mailto:ulr...@gm...] On Behalf > Of Ulrik Sandberg > Sent: Thursday, 18 June 2009 11:02 p.m. > To: Jan Barnholt > Cc: ivy...@li... > Subject: Re: [Ivyplugins-user] Project specific basedir? > > > You should be able to override any attributes when you actually use a > plugin. Doesn't this work? > > <plugin name="ivypublisher" > classname="net.sf.ivyplugins.ivypublisher.IvySuccessPublisher" > project="${project.name}" > basedir="${ccwork}/checkout/${project.name}" /> > ... > <project name="OK"> > <ivypublisher /> > <project name="funny"> > <ivypublisher basedir="${ccwork}/checkout/${project.name}/Build" /> > > -- Ulrik |
From: Jan B. <Jan...@ar...> - 2009-06-21 19:59:45
|
Hmm.. thanks Ulrik - I wasn't aware of this! Cheers, Jan ________________________________ From: ulr...@gm... [mailto:ulr...@gm...] On Behalf Of Ulrik Sandberg Sent: Friday, 19 June 2009 5:53 p.m. To: Jan Barnholt Cc: ivy...@li... Subject: Re: [Ivyplugins-user] Project specific basedir? Sure, we can add this in the doc, but it's really a generic CruiseControl feature <http://cruisecontrol.sourceforge.net/main/plugins.html#preconfiguration> which you can use with any plugin. |