RE: inter project dependencies

I've found part of a solution to the problem. Following some tips on krysalis wiki site on the usage of ruper I added to module.xml another jars repository:

<jars repository="module" href="./build" />

and to the depend tag the following:

<depend project="B" repository="module" version="1.0.0-dev-20030318" />

This actually works as far as having ./build/B/B-1.0.0-dev-20030318.jar in project A's compilation classpath generating that jar as part of project A's build process it seems. So, great!

But that is not exactly what I want because I just want to have the current version of project B. Apart from adding a custom target that copies B-1.0.0-dev-20030318.jar to B.jar which I consider to be a bit of a hack, isn't there a better option?

Thanks,
U.

Unico Hommes wrote:
>
> Nick Chalko wrote
> > 
> > Unico Hommes wrote:
> > 
> > >Hi,
> > >
> > >Some time ago I supplied a patch for inter project 
> > dependencies within a module. I must admit I haven't been 
> > monitoring the changes to centipede much, but I was wondering 
> > whether some of that had made it in. I recently updated 
> > centipede to the current CVS HEAD but I can't get inter 
> > project dependencies to work. Is there something special I 
> > should do to make that work. 
> > >
> > 
> > >A quick look at getdepend.xsl didn't make things much 
> > clearer. What's attribute 'export' on 'depend' element tell Ruper?
> > >  
> > >
> > Things marked export="true"  are included in the 
> distribution when a 
> > project is built.
> > 
> > >Regards,
> > >U.
> 
> 
> Thanks for your reply Nick. It doesn't yet explain me how to 
> solve my particular problem though. My situation is that I 
> have a project A that has a java dependency on project B. 
> 
> module.xml looks something like:
> 
> <module>
> ...
>   <project name="A">
>     ...
>     <depend project="B" />
>   </project>
> 
>   <project name="B">
>     <ant target="package" />
>     ...
>   </project>
> 
> </module>
> 
> What can I do to have project B's classes added to project 
> A's compilation path? Previously I had gotten that working 
> with a change I made to makeclasspath.xsl but that approach 
> seems to have been abandoned in the most recent centipede.
> 
> Should I declare another repository in module.xml and 
> reference that in the depend tag? Will the ant target 
> declared in project B get called when project B is declared 
> to be a dependency on A?
> 
> Thanks,
> U.


-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? 
You could win a Tablet PC. Get a free Tablet PC hat just for playing. 
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en