The kind of build properties I was talking about was text entries in
build.properties, such as
embed=true
split=true
On Jul 1, 2008, at 4:47 PM, David Avendasora wrote:
> If we are going to look at changing the default build.xml, I have
> some Java Client changes to add. I think they could be controlled
> the same as the Servlet build options are. A "Java Client WebStart"
> checkbox, with a D2JC sub-checkbox during project setup that updates
> the build.properties file would be perfect.
>
> See the Wiki here for the changes I currently make to the build
> process:
>
> http://wiki.objectstyle.org/confluence/display/WO/Java+Client-Building
>
> Dave
>
> On Jul 1, 2008, at 1:36 PM, Kieran Kelleher wrote:
>
>> Sounds like that might be a good idea.
>>
>> Splitting, embedding and tarring certainly might make the
>> deployment learning curve easier for newbies. I would recommend it,
>> however this script might need to be diff'ed with current one to
>> pick up some possible improvements to build.xml (perhaps WAR, etc
>> build stuff) since I branched this embedded split version a while
>> ago .... and it has noit been tested on Windows AFAIK ....... app-
>> bundle-naming (to include version), splitting and embedding are
>> certainly desirable features and having them easily accessible in
>> build.xml would save some new wo-devs having to study the details
>> of ant and the woproject tasks on top of learning WO at the same
>> time.
>>
>> If difficult to merge, it could be added as is to the project
>> templates as an alternative build script. But probably merging into
>> build.xml would again make it easier for newbies. If necessary, the
>> turning on/off of splitting and/or embedding could be done via the
>> build.properties file if people wanted to have option to do that,
>> however, creating a split bundle should probably be default since
>> they don't have to deploy the WSR bundle if they don't want to. If
>> embedding is generally recommended as path of least effort, then
>> maybe it should be enabled by default too so newbies don't have to
>> think about it.
>>
>> Kieran
>>
>> On Jul 1, 2008, at 12:44 PM, Mike Schrag wrote:
>>
>>> Should this go into the default build.xml in wolips?
>>>
>>> On Jul 1, 2008, at 12:24 PM, Kieran Kelleher wrote:
>>>
>>>> The wiki is your friend ........ use the alternative build script
>>>> provided here .... it is also fully explained:
>>>>
>>>> http://wiki.objectstyle.org/confluence/display/WOL/Alternative+Ant+Build+Script+for+Fully+Embedded+and+Split+Install+Bundles
>>>>
>>>> HTH, Kieran
>>>>
>>>>
>>>>
>>>> On Jul 1, 2008, at 11:04 AM, Travis Britt wrote:
>>>>
>>>>> I feel like I'm missing something. My app embeds its frameworks.
>>>>> When doing a split install, is there a way to get the web server
>>>>> resources of those frameworks embedded in my app's WSR woa?
>>>>>
>>>>> The end result would be:
>>>>>
>>>>> [web_doc_root]/WebObjects/MyApp.woa/Frameworks/Framework1.woa/
>>>>> [...]
>>>>>
>>>>> I see the frameworksBaseURL attribute on the woapplication task
>>>>> which points to the correct place, but I'm unclear about how to
>>>>> copy the WSR from the embedded frameworks in there. Or should I
>>>>> just be scripting that myself?
>>>>>
>>>>> Thanks!
>>>>>
>>>>> tb
>>>>>
>>>>
>>>
>>>
>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Tue Jul 01 2008 - 16:52:11 EDT