Re: WO Jenkins help
Re: WO Jenkins help
- Subject: Re: WO Jenkins help
- From: David Avendasora <email@hidden>
- Date: Sun, 11 Mar 2012 22:51:19 +0800
Hi Daniel,
I'm cc'ing the list on this because I think it is an important point that the current scripts do not address.
On Mar 10, 2012, at 12:01 AM, Daniel Roy wrote:
> Hi David,
>
> Yes your answer was great, thank you. No worries about the last email - I had forgotten that I had send it :)
>
> One quick question if I may - we have projects in Eclipse that have dependencies on other projects, which I think it normal. When Eclipse builds, it knows to use any libraries associated to the dependent projects when building. We rely on this fact and do not include external JARs or Frameworks in some projects because we know Eclipse will find them during build by looking at the build path.
>
> Jenkins, however, does not know that trick. So:
>
> ProjectA
> Framework1
> Framework2
> ProjectB (depends on ProjectA)
> (makes reference to code that might be included in ProjectA- Framework2)
>
> Jenkins build fails ProjectB on the classes that make reference to code in ProjectA's Frameworks.
>
> If there is no explicit classpath entry in ProjectB for that particular Framework, Jenkins will never know how to successfully build ProjectB. Are we forced to include all Framework references in all projects?
You are correct, that with the existing scripts Project B does not know about the dependencies for Project A without you adding all of Project A's dependencies to Project B.
In theory I could insert Project A's .classpath file into Project B's .classpath file (immediately following the entry for ProjectB) at build-time, then use that "unified" .classpath file to build links to all the dependencies. But that would be a lot of work. It maybe best just to add Project's A's WOFramework dependencies into Project B's.
If I'm missing something and there is a better way to deal with this, please let me know!
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden