Please also see my reply to Marek.
Martin Grebac wrote:
> Btw, isn't Maven migration orthogonal to build script update?
I thought if we'd risk breaking build in various places, we might as
well move to Maven.
>> Also, I saw build scripts that NetBeans produce, and I have to say I'm
>> not a big fan of it. It's really hard to follow, and it's next to
>> impossible to modify, unless you use NetBeans to edit it.
>
> What do you think happened to WSIT build.xml scripts with my update?
> Existing targets left untouched, and NB script is just imported into
> it and hidden in NB project directory. That way you may still write
> your custom targets to build.xml (and let's say even have two ways to
> build the same thing if that's what you prefer and don't want to see
> any NB target invoked), and still there will be only one line in
> build.xml mentioning Netbeans (import nbproject/build-impl.xml).
> And result: nobody had problems with the migration, and NetBeans
> users are more happier now. It does look like a win situation to me,
> don't you think so?
Yeah. If we can avoid the disruption for the build script. I'm all for it!
>> I'm sorry, are you saying that this is impossible with NB regardless
>> of what we do, or is it a limitation that NB has for a free-style Ant
>> project (is that how it's called?)
>> If latter, sounds like an RFE is in order for NB.
>
> I think Marek means that the project setup is incorrect. If you
> screw project setup in "your IDE" by not specifying libraries that the
> project uses, does it work correctly? Does it offer code completion
> for classes in that library?
I'm confused, I thought some limitation in NB makes it impossible for
Ant free-style project to refer to $JAVA_HOME/lib/tools.jar. If so, I
don't see how we could have fixed it by ourselves.
If, OTOH, it's just a matter of adding one library to the existing
project file, then we sure want to make that change.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com