> Now I realize that the projects and the launch configurations should
> have different class paths. The projects should link with the other
> projects, and the launch configuration should link with the built
> frameworks.
>
> How I build, incrementally or using Ant, does not affect this.
That is true. The incremental build is just faster (and probably more
buggy).
Did you try it? Did it work? Tell me that it works great, please!
> Now, if
> > you check the "Use incremental builder" checkbox, the ant build is
> > automatically disabled (i.e., there is no *automatic* ant build done.
> You
Yes?
> The "Build after JavaBuild" option is a global WOLips preference, but
> "Use incremental builder" is per project. Will it disable Ant for this
> project even though it's turned on globally?
Yes. The Build after JavaBuild disables (AFAIK) the actual building, but it
doesn't remove the builder. The incremental builder ignores the flag (since
it's much faster, anyway -- and then because it comes from a place without
such a flag ... ok, I'll stop repeating that. Tomorrow, promised.)
> What does "Is a WebObjects Project" do?
It attaches the WOLips Project Nature to the project, much like the with the
Sysdeo Tomcat plugin (which is where I stole the idea). This means you can
convert a plain JavaProject into a WOLips Project with this checkbox. (It
looked like the simplest way of getting the natures attached, from the
user's point of view, no wizards, just a simple Checkbox in plain sight.)
Harald
_______________________
Our documentation manager was showing her 2 year old son around the office.
He was introduced to me, at which time he pointed out that we were both
holding bags of popcorn. We were both holding bottles of juice. But only
*he* had a lollipop.
He asked his mother, "Why doesn't HE have a lollipop?"
Her reply: "He can have a lollipop any time he wants to. That's
what it means to be a programmer."
This archive was generated by hypermail 2.0.0 : Wed Mar 05 2003 - 15:50:31 EST