[Source] building latest NPS branch

[Don Brutzman]

thank you for f2f explanation...

On 6/30/2014 9:43 AM, Norbraten, Terry (CIV) wrote:
> LIne 278 of the nbproject/project.xml is for profiling a NetBeans project which has a specific target in nbproject/ide-targets.xml, a NetBeans generated “extra” Ant script for NB specific things.  This target would not belong in the ${basedir}/build.xml as some developer may use command line only to build and have nothing to do with NetBeans.  “build.xml” will remain the primary script

aha, i see now.  added the following note to nbproject/ide-file-targets.xml


     <!-- The regular build.xml is still the primary Ant build file.  It is therefore imported first.
          Additional targets found in this file support Netbeans-specific capabilities. -->
     <!-- TODO: move general targets up and over to build.xml (or somesuch file nearby) for general use. -->
     <import file="../build.xml"/>

> A list of implemented Nodes are annotated on the Xj3D Implementation Status page here: http://www.xj3d.org/status.html

yeah we should autogenerate this somehow, good future issue

> It hasn’t been updated in quite a while though.  And yes, the README could use an update as well.

will start as README.txt

> Javadoc has always been in need of work, so, fire away on that.

again thanks!

> On Jun 30, 2014, at 8:39 AM, Don Brutzman <brutzman at nps.edu> wrote:
>
>> Terry, thanks for adding Arc2D support to Xj3D.
>>
>> Wondering, is there a list somewhere of nodes supported by Xj3D?
>>
>> The README file in the root looks like it needs revision (talks about CVS and other old stuff), perhaps we should create a README.txt that is up to date.  Many repositories (such as sourceforge) and build systems look for that - also the extension tells file systems how to handle the file.  Make sense?
>>
>> Also please confirm that build.xml is now primary for the NPS branch, if so we should modify the netbeans project configuration (nbproject/project.xml line 278).
>>
>> Netbeans 8 (and presumably Java 8) is much stricter about errors in Javadoc, not permitting illegal character entities and other invalid HTML source which often occurs when source is copied verbatim into javadoc blocks.  Currently the Javadoc target reports 100+ errors and 100+ warnings in the full build.  You just checked in a large number of class updates - don't want to interfere with further refactoring until ready.  Is it OK to start cleaning up javadoc entries in the source?
>>
>> Latest 'build all' results checked into build.out.xml
>>
>> 	http://svn.xj3d.org/xj3d_code/branches/NPS/build.out.txt
>>
>> all the best, Don
>> --
>> Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
>> X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
>


all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman