Hi ,
There is a new Version of WOLips in the CVS. From now on incremental
builds of frameworks are supported. This version still uses a build.xml
file. But it`s hidden for the user. So its automatically invoked on
save, rebuild and so on. On my Cube a incremental build in Eclipse takes
about 2 seconds for a small framework and the time includes the build of
the framework.
I`ll add a page to the documentation on how to set up the classpath
including the wo jars. A later version will assist you with that.
Currently you have to run the WOApp by hand in Eclipse.
Hot-code-replacement depends on your JVM. As far as I know Version 1.4
and above works. I am using a normal JavaProject so this should work.
But I never had a chance to test it.
As far as I can see you have done the parts missing in WOLips in your
plugin. What about merging them.
Best regards
Ulrich
Am Donnerstag den, 15. August 2002, um 23:59, schrieb Harald Niesche:
Hi,
I'd like to know more about how the WOLips plugin is being used -- I have
not really used it yet (because I didn't understand it :-( ).
As far as I understand, you'll need to write a WOProject build.xml in
order
to use WOLips, right?
Does that work well with incremental builds triggered by saving a file?
How do you add the WebObjects frameworks to the classpath?
Does the WOLips plugin support hot-code-replacement in a running
WebObjects
application?
This is the motivation for my questions:
I have written a tiny plugin to support development of WebObjects
frameworks
and applications with Eclipse that consists of an IClasspathContainer
implementation (it let's you select all the frameworks you need) and an
Eclipse builder that builds the .framework or .woa structure using the
delta
information provided by Eclipse (it doesn't create .jar files which
seems to
be saving a lot of time -- recompile / restart is really quite fast).
I'd like to release the plugin to interested parties (on request) and
would
like to investigate how code / knowledge about the structure of
WebObjects
applications and frameworks could be shared between WOProject and an
incremental Eclipse builder.
Next steps for my Plugin would be
- wizard for creation of projects
- wizard / basic editing support for Components (.wo-Folders) --
although
I'm not sure whether we could expect trouble if we support WO
development on
platforms besides MacOSX and Windows
- Java Runner (forgot the Eclipse name) that configures a JVM for
running
the WO application, currently I need to massage the classpath and current
directory manually
But maybe what I did is just redundant because WOLips already does all
that
...
(I only noticed WOProject / WOLips recently, when my plugin already
worked
quite well...)
Harald
This archive was generated by hypermail 2.0.0 : Fri Aug 16 2002 - 03:37:42 EDT