OutOfBoxVersionabilityComments

Comments on Out-of-the-Box Versionability

Current OutOfBoxVersionability proposal addresses just one of the aspects of the problem - shared libraries. There is several other problems which are more important:


  • The biggest problem is that user customizing their project and adding jar/library/project dependency has no idea and no control what's gonna happen. Simple amendment could be to always ask how to reference artifact being added to project. Below is rough UI which purpose is to list all possible options (in no particular order) just to facilitate discussion:

(Picture illustrates the case when C:\repo\libs\jakarta\commons-lang.jar is being added to project C:\dev\trunk\myjava)

Image:add-reference_OutOfBoxVersionabilityComments.png

This UI would be used to add any artifact to project, that is jar/library/project/J2SE platform/J2EE Server/... Not all options are always available, e.g. for platform it will be only environment variable; but user should have control over what is the name of variable at least as they will need to document it for their colleagues - after fresh checkout you need to set variable JDK_5 to something.

I would also argue that in most of the case the default recommended option should be to simply copy everything to project folder. Even the libraries including their javadoc/sources.


  • Current inability to attach sources/javadoc with regular jar is another problem. Java Library is IDE concept which you need to be aware of and understand it. I believe that first time users will just ignore it, put jars on classpath and later when they debug project or wanna see javadoc they would expect (in worst case) that IDE asks them where are the sources/javadoc once and from then it just work. Btw. associating javadoc/sources with the project would use the customizer described in first paragraph - user has control how javadoc/sources will be referenced.


  • Project UI should indicate or just show where relative/sharable paths are used, where env variables are used and where fully qualified paths are used.


  • Fresh build checkout should not fail with javac compilation error, but stating which environment properties are not set
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo