Thanks Pascal for the ideas. I already have something working in Jenkins where
I modified the setupWorkspace shell script from WOJenkins to take parameter
that is a custom classpath filename (which resides in the relevant project).
This custom classpath contains the required custom Frameworks, and compiles
without issue, but then I'm back to the ant build problem where the ant build
only includes the files in the original .classpath file, since this is
hardcoded in the related WOLips classes.
I'll keep digging, and if I find any solutions I'll post back to the list :)
-Daniel
On 2012-03-14, at 6:35 PM, Pascal Robert wrote:
>
> Le 2012-03-14 à 16:50, Daniel Roy a écrit :
>
>> 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" />
>
> The only way I can think is to modify the WOJenkins to look at something else
> than .classpath… or probably to use Maven.
>
>> …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.
>
> So you won't have 10 jobs, but you will end up with calling 10 Ant tasks in
> Jenkins anyway. Or you do something to the build files that Wonder uses.
>
>> 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 protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
>>
>> This email sent to [email protected]
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
