Hello everyone,
just recently I checked out again latest JAX-WS sources from
"rearch-2005" branch. I was pleased that the sources can be opened as a
project in Netbeans. However I have some comments about several things
on this NB project configuration that call for an improvement:
- 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'.
- 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? It is
being developed by SUN engineers using SUN development software (such
as NB) which in turn gets improved due to the feedback from SUN
engineers, right? (sorry, I couldn't resist this rhetorical question...)
- 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'
- 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.
I am looking froward to your thoughts.
WBR,
Marek
--
Marek Potociar
Web Technologies & Standards
Sun Microsystems Czech