Hi Pierre,
let's start with woproject:
The documentation for the woproject tasks are available online:
http://objectstyle.org/woproject/ant/index.html Anyway these docs does
not describe all the enhancements since december. The docs in the cvs
are up to date. I'll put them online when I find the time to
test/release woproject 1.0.0. The woproject docs talk about taskdefs
like:
<taskdef name="woapplication"
classname="org.objectstyle.woproject.ant.WOApplication">
<classpath refid="classpath"/>
</taskdef>
You can ignore them until you start build outside of WOLips.
Ant/ExternalTool support.
Both of them launch ant and the result is the same. Both are provided
by Eclipse. You can get the ant output when launched with the External
Tool support.
The TargetBuilder is for JavaClient development. It can switch the
Eclipse classpath for the different build styles (server/client).
I leave it to harald to talk about the Incremental Builder.
Flexibility:
The provided build.xml is only a starting point. You can change it to
fit your needs. At least this is what I do.
Disable/enable the build. Thanks to rapid turnaround mode, there is no
need to enable the build until it's time to deploy. I don't know if
this is also true for JavaClient development.
Ulrich
Am Montag, 12.05.03 um 10:13 Uhr schrieb Pierre Bernard:
> Hi!
>
> Where can I find information about the different build styles WOLips
> offers:
>
> 1. WOProject Build (configured in the preferences)
> 1.1 Ant
> 1.2 External tool
>
> 2. Incremental (activated in a project properties, replaces WOProject
> build)
>
> 3. Target builder (activated by creating a targets.plist file and
> chosing WOLips -> update Target Builder from the conextual menu)
>
> I have read the help pages on the subject. After several months of use
> of WOLips I have a pretty good idea about how how the Ant build works.
> I also appreaciate its flexibility as I have customized my build.xml
> files to: do an install build by default, run EOGenerator, create
> signed JAR files for use with JavaClient,...
>
> As doing a complete WOLips build of projects takes some time and is
> often not needed until I actually want to test my code, I disable
> WOLips building using the (+)/(-) buttons so that the build is not
> done every time Eclipse updates my class files.
>
> I however don't see the advantages of running WOLips as an external
> tool.
>
> I can even less imagine what the incremenatl build is about. It also
> seems to be about performance during development, but I don't see what
> it does beyond what Eclipse does when WOLips is temporarily disabled
> using the (-) button.
>
> Pierre.
>
>
> **********************************************************************
> This email and any files transmitted with it are intended solely for
> the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the sender
> of this message. (Pierre.Bernar..cl.lu)
> This email message has been checked for the presence of computer
> viruses; however this protection does not ensure this message is
> virus free.
> Banque centrale du Luxembourg; Tel ++352-4774-1; http://www.bcl.lu
> **********************************************************************
>
This archive was generated by hypermail 2.0.0 : Mon May 12 2003 - 04:57:26 EDT