| Hi,
I've setup Jenkins in test to start building our frameworks and applications. WOJenkins is excellent - thank you so much for providing this David Avendasora (and anyone else who may have helped)!
We build our own ERPrototypes because we have some custom types we need to use. Our frameworks use this ERPrototypes framework instead of the vanilla Wonder ERPrototypes. We reference our ERPrototypes framework as a Project dependency in the build path instead of a Library (framework) dependency. This works fine in Eclipse because Eclipse can magically account for the linked project and include the linked project's files in the build process. However, Jenkins can't resolve the dependency.
Using the scripts provided in WOJenkins, the build process never pulls in the required framework because the .classpath entry in the affected Eclipe project is as follows:
<classpathentry combineaccessrules="false" exported="true" kind="src" path="/ERPrototypes"/>
I've tried modifying the WOJenkins setup script to unpack the ERPrototypes framework into the correct location of the affected project, but that doesn't make any difference during build time because ant doesn't know about the dependency.
Does anyone have any ideas how the build can be accomplished? I could modify the .classpath file of the affected project after it's pulled down from SVN and change the ERPrototypes line to be the standard "WOFramework/ERPrototypes", since our ERPrototype is build before all other frameworks in the Jenkins build process. Or, is there possibly another way?
Thanks, Daniel |