Right, I think his netbeans is trying to use the javadocs goal, the release profile would do that or it's possible his netbeans is set to automatically make javadoc jars if there aren't SNAPSHOTs it can download.
I'm guessing that most of the builds folks do now in java 8 don't attempt to make javadocs. On Wed, Jun 17, 2015 at 10:32 PM, Joe Witt <[email protected]> wrote: > Sean > > The vast majority of my compilation/builds are in Java 8. I do not > see these issues. Are you thinking what he is observing with Javadoc > behavior during the Netbeans initiated builds is Java 8 related? > > I just did a full clean install through Netbeans and it went smoothly > (slowly but smoothy). Took another look at your log output and the > first line is this > > " > cd C:\Projects dataFascia\incubator-nifi\nifi; "JAVA_HOME=C:\\Program > Files\\Java\\jdk1.8.0_11" cmd /c "\"\"C:\\Program Files\\NetBeans > 8.0\\java\\maven\\bin\\mvn.bat\" -Dfile.encoding=UTF-8 > -Prelease-profile install\"" > " > > So please try to disengage the -Prelease-profile and see what the > outcome of the build is then. > > Thanks > Joe > > On Wed, Jun 17, 2015 at 11:01 PM, Sean Busbey <[email protected]> wrote: > > That sounds like java 8. > > > > Can you make sure your java install is jdk7? > > > > -- > > Sean > > On Jun 17, 2015 9:58 PM, "Joe Witt" <[email protected]> wrote: > > > >> John, > >> > >> It appears that your netbeans build is trying to build the javadocs > >> and isn't ignoring the errors. Our current javadocs do appear to > >> generate a disturbingly high number of errors. It will be a long slow > >> painful process to clean them up and in time they will be. For now > >> though our typical build knows to ignore that. Perhaps netbeans is > >> overriding that behavior somehow. > >> > >> Also of note that often times attachments are blocked (always really). > >> So for cases like this feel free to generate a JIRA where you can > >> attached your logs (which were very helpful by the way). > >> > >> I also noticed the build is taking 10+ minutes for you. Might be a > >> case of an under-resourced system but keep in mind you can do > >> something like 'mvn -T C1 clean install' and Maven will use 1 thread > >> per core that you have. On a bit higher powered box i do something > >> like 'mvn -T C3 clean install' and the full build takes about 2 mins. > >> Just something to keep in mind so building is a bit quicker for you. > >> > >> Thanks > >> Joe > >> > >> On Wed, Jun 17, 2015 at 2:10 PM, John Clark <[email protected]> > >> wrote: > >> > Hi, > >> > > >> > I did get the build to work on a Linux machine (Centos)...the problem > I > >> had > >> > with the ce.gluu.info on one machine is probably caused by my having > >> > installed 'gluu' previously and it named my host 'ce.gluu.info' and I > >> > didn't realize that this had happened. > >> > > >> > Any info on windows builds with NetBeans would still be appreciated. > >> > > >> > Thank you! > >> > > >> > Regards, > >> > John Clark > >> > > >> > > >> > On Tue, Jun 16, 2015 at 4:39 PM, John Clark <[email protected] > > > >> > wrote: > >> > > >> >> Hi, > >> >> > >> >> > >> >> I’m trying to build NiFi from source and have run into a couple > problems > >> >> and was hoping that you could point me to documentation or answers > that > >> >> might help. > >> >> > >> >> I’ve tried to build on Linux and also on Windows with NetBeans and > have > >> >> had problems on both systems. > >> >> > >> >> * Linux Build:* > >> >> > >> >> On Linux I used the NiFi ‘Quickstart’ documentation and following the > >> >> documentation I: > >> >> > >> >> > >> >> 1. Successfully downloaded the code using GIT. > >> >> 2. Set MAVEN_OPTS="-Xms1024m -Xmx3076m -XX:MaxPermSize=256m" > >> >> 3. Successfully built the nifi-parent using 'mvn clean install. > >> >> 4. Successfully built the nifi-nar-maven-plugin using 'mvn clean > >> >> install' > >> >> 5. Attempted to build nifi using mvn -T C2.0 clean install but the > >> >> build resulted in a number of successes and a number of errors. > >> >> 6. The errors in the NiFi build seem to revolve around this > following > >> >> statement: "java.net.UnknownHostException: ce.gluu.info: > >> ce.gluu.info: > >> >> Name or service not known. > >> >> > >> >> Attached is a text file that contains the output of the Linux build. > >> >> > >> >> *Windows Build:* > >> >> > >> >> I'm trying to build on Windows using NetBeans and the first problem > may > >> be > >> >> that you don't support this kind of build. > >> >> > >> >> > >> >> 1. I use the team GIT Clone option to have NetBeans download the > >> >> projects from the same GIT repository. This appears to work fine. > >> >> 2. I build nifi-parent with success. > >> >> 3. I build the nifi-nam-maven-plugin with success. > >> >> 4. When I try to build the nifi project I only get as far as the > NiFi > >> >> properties > >> >> > >> >> I've attached a text file that has the NetBeans build output. > >> >> *I haven't started to dig into the error notations in detail yet. I > do > >> >> notice that in the case of the build failure of 'nifi-properties' it > >> seems > >> >> to be unable to find in > >> >> > >> > 'incubator-nifi\nifi\nifi-commons\nifi-properties\target\test-classes\NiFiProperties\conf\' > >> >> any of the three files, 'nifi.blank.properties', > >> 'nifi.missing.properties > >> >> and 'nifi.properties'. But when I look in that directory all of > those > >> >> files exist and have data.* > >> >> > >> >> *I'm wondering if you have any advice, in general about building with > >> >> NetBeans on Windows.* > >> >> > >> >> Thanks and Regards, > >> >> John > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> > -- Sean
