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: Pascal Robert <email@hidden>
- Date: Wed, 14 Mar 2012 16:31:06 -0400
Hi Daniel,
I guess that's a bug, but are you linking your projects as "project" (in the Projects tab in the build path) instead of as WO frameworks (in the Library tab in the build path)?
> 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.
>
> 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?
>
> <PastedGraphic-5.png>
>
> Thanks,
>
> Daniel
>
>
>
> _______________________________________________
> 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
_______________________________________________
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