On Nov 8, 2007, at 5:56 AM, Mike Schrag wrote:
> Points for discussion:
>
> 1) Why are all WO frameworks in a single classpath container? This
> seems like it makes everything needlessly complicated -- we have to
> write custom classpath ordering vs just using classpath itself and
> Eclipse built-in features. In reality, I believe each individual
> framework should be a container, so I would have
> ERExtensions.framework as an entry in my classpath. Then I can
> just reorder the frameworks with the classpath ordering tool, and
> this much more closely models how WO runtime will treat these.
I like that. It will be more work to setup a project (vs just
checking off items in the current WebObejcts Library) but more flexible.
> 2) Do we even need ant.*? Couldn't there be an ant task ("or
> something") that loads classpath out of the Eclipse .classpath
> file? Somehow Eclipse itself does this, right?
We might want to keep the ant.* stuff for those not using Eclipse
(IntelliJ etc.). The need to have the classpath twice has always
slightly annoyed me.
> 3) I had a third, but I don't remember it :)
I agree with that too. :-)
Chuck
--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/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Thu Nov 08 2007 - 14:10:30 EST