Re: Eclipse builds - force custom framework selections to be packaged
Re: Eclipse builds - force custom framework selections to be packaged
- Subject: Re: Eclipse builds - force custom framework selections to be packaged
- From: Daniel Roy <email@hidden>
- Date: Wed, 14 Mar 2012 16:50:01 -0400
| Hi,
Pascal: The projects are linked as WO Frameworks.
I'm trying to figure out how I can build an application (in Jenkins) in multiple ways, each with it's own set of dependent frameworks. So, for example:
Client A Application1 FrameworkA FrameworkB
Client B Application1 FrameworkB
If I could specify a custom classpath file contained within the project that could be read during the build process, like:
<frameworks root="ProjectLocal" embed="${embed.ProjectLocal}" eclipse="true" classpath="mycustom.classpath" />
…I might be able to force the build to include the different frameworks when required. I want to avoid having to copy the same project 10 times in Eclipse just so they can each have their own set of frameworks references.
Am I dreaming that this is possible?
Thanks,
Daniel
On 2012-03-14, at 4:39 PM, Chuck Hill wrote: On 2012-03-14, at 1:09 PM, Daniel Roy wrote: Hi,
In Eclipse, when I select "WOLips Ant Tools -> Install…", I'm presented with a list of open projects. From the image I've attached, FrameworkA is on the build path of MyApplication, so it's checked. But I can also include FrameworkB by checking it, and it gets compiled before the build happens, but it's not included in the packaged application. This is because build.xml is specifying "eclipse=true" for the frameworkset and that only respects the application's .classpath file for framework references.
Why would you want it as part of the application? It is not on the classpath so the application is not using it...
Is there any way to force the inclusion of FrameworkB in the final packaged application? Will I have to modify the application's build.xml to explicitly include the outside-of-classpath frameworks? What is the intent of allowing the selection of other frameworks at build time if they aren't included in the packaged application for deployment?
My guess is that it is a defect. -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/gvc/practical_webobjects
|
_______________________________________________
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