Re: [Ivyplugins-user] Problems running IvyPublisher pre-2.0 with latest sources

[Eugene S. <eu...@gm...>]

Jan,

Re: " we ended up adding IP to every CC project to get it working.."
For this particular reason when i was working with CruiseControl i was 
using project plugin. This gave me a possibility to configure common 
stuff via variables like ${your_variable} and then when you define your 
<project> you just need to define those variable to get it working. Take 
a look - it can probably save you a lot of time configuring your stuff.

Best of luck,
Eugene

On 6/17/2009 5:29 PM, Jan Barnholt wrote:
> It looks like you have to add the <IvyPublisher> to each project, even those that are not the ones other projects depend on but that are at the top of the food chain, i.e. depending on several projects but are themselves not producing any artifacts any other project depend on.
>
> From the documentation it looks like you would have to add IP just for projects on which other projects depend, e.g. your common 'libraries' - not your 'apps'.
> However, on our CC installation we ended up adding IP to every CC project to get it working.. still, might be some misconfiguration on our side.
>
> Cheers,
> Jan
>
> ________________________________
>
> From: Eugene Sajine [mailto:eu...@gm...]
> Sent: Wednesday, 17 June 2009 9:19 a.m.
> To: Jan Barnholt
> Cc: Ulrik Sandberg; ivy...@li...
> Subject: Re: [Ivyplugins-user] Problems running IvyPublisher pre-2.0 with latest sources
>
>
> Jan,
>
> That's great! Did you resolve your issue with dependent projects build?
>
> Eugene
>