2006/8/23, Marek Potociar <Marek.Potociar_at_sun.com>:
> The project setup is created from existing ant script that does not 'respect' the build
> script structure required by NB to setup a standard NB project. The result is that you
> cannot fine-tune the project settings end expolit all IDE features. As a result the NB
> usage is degraded to something like 'a plain java editor + build script runner'.
The build script has to perform certain tasks in a certain way. A lot
of the build step is dictated by historical reasons and various
deliverable requirements. So personally, I'd hesitate to rework the
build script if that's just for making NetBeans happier.
If we spend time on the build, I'd rather like to see JAX-WS converted 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.
But then, maybe I'm totaly missing the point and perhaps there's a way
to create a better project layout without touching the existing build
script?
> There are no unit tests set up for the project (at least in NB...). This makes me wonder:
> how is the code quality ensured and how a new code is tested prior to CVS commit to
> aviod regressions?
For licensing and historical reasons, the test is still in the
internal repository. But they are run on every commit. See
http://kohsuke.sfbay.sun.com/hudson/view/JAX-WS/
Also check out
http://ws-test-harness.dev.java.net/ for more modern
test harness. I believe the team is talking about bringing the future
unit test on this harness, right here at java.net.
> The tools.jar is missing in the project library configuration (wouldn't be possible with
> standard NB project setup) which causes errors about unknown packages and classes
> being displayed in source files located under 'tools/wscompile/src'
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.
> The whole JAX-WS is a single project with multiple source roots. IMHO it would make
> sense to follow a NB best practice and split (from NB point of view) this single big
> project into several smaller projects and define dependencies among them. There
> was already a need to have separate source roots, so I suppose the split could be
> done based on a de facto existing "modules". Please, check out from CVS and
> open a WSIT project in NB to see what I mean.
Sounds like a reasonable thing to do!