Thanks Robert.

Yes, you are right, I am using the latest version of JDK. I fixed
the javadoc, and it seems to be working fine, though I am getting exceptions
in next area! (not Maven).

If you think downgrading JDK to the previous version will resolve
many of my issues, I will go ahead and do it.

All I want to do is to install Hadoop, and then run Pig for a data
analysis that I am pursuing.

Thanks,
Venkat.



On Fri, Dec 19, 2014 at 2:22 PM, Robert Scholte <[email protected]>
wrote:

> So this is not a Maven3 issue, but a JDK8 (kind of) issue. (seems like you
> upgraded the JDK as well)
> Oracle introduced with JDK8 a more strict parsing of the javadocs.
>
> Since the javadoc is incorrect, it fails.
> You have 3 options:
> - Use JDK7 or less
> - Fix the javadoc. The problem here is that <String> and <File> are
> invalid HTML-tags. You should escape it to &lt;String&gt; and &lt;File&gt;
> - Add -Xdoclint:none or -Xdoclint:syntax (I think), see docs[1]. This way
> you can suppress these errors.
>
> The maven-javadoc-plugin still struggles a bit with -Xdoclint[2]. A single
> -Xdoclint argument works fine, multiple is not yet supported(comma
> separation handling fails).
>
> thanks,
> Robert
>
> [1] https://docs.oracle.com/javase/8/docs/technotes/tools/
> unix/javadoc.html#BEJEFABE
> [2] https://jira.codehaus.org/browse/MJAVADOC-387
>
> Op Fri, 19 Dec 2014 04:03:00 +0100 schreef Martin Gainty <
> [email protected]>:
>
>
>  take a look at :
>> /**
>>      * Method getExcludePackageNames.
>>      *
>>      * @return List
>>      */
>>     public java.util.List<String> getExcludePackageNames()
>>
>> //if i change
>> //@return List to
>> //@return List<String>
>> //i get the same error you get
>>
>> please file enhancement request at
>> https://jira.codehaus.org/browse/MJAVADOC
>>
>> thanks,
>> M-
>>
>>
>>
>>
>> Date: Fri, 19 Dec 2014 07:50:15 +0530
>> Subject: Fwd: Fwd: Error while creating hadoop package 2.6.0 with Maven
>> 3.2.3
>> From: [email protected]
>> To: [email protected]
>>
>> Thanks Robert.
>> I did a -e and also a -X, -X option shows error messagesthat are
>> specifically related to 'Unknown tag' for String andFile. Looks like
>> something related to 'Mojo' declaration, butnot sure. I am not a full time
>> developer.
>> Anything related to Maven with PATH variable?
>> Logs attached.
>> Thanks,Venkat.
>> On Thu, Dec 18, 2014 at 11:27 PM, Robert Scholte <[email protected]>
>> wrote:Hi,
>>
>>
>>
>> I guess you should be able to resolve the warnings, but that's a
>> different issue.
>>
>>
>>
>> When the build of the Apache Hadoop Maven Plugins 2.6.0 starts, I only
>> see "Downloading...."
>>
>> Normally this should be followed by "Downloaded...", which means that the
>> download attempt actually succeeded.
>>
>> For some reason something goes wrong here.
>>
>>
>>
>> You might want to add -e to get a stacktrace, which could give you an
>> extra hint (or worst case, add -X for debug logging)
>>
>>
>>
>> thanks,
>>
>> Robert
>>
>>
>>
>> Op Thu, 18 Dec 2014 18:18:51 +0100 schreef Venkat Ramakrishnan <
>> [email protected]>:
>>
>>
>>
>>
>> Hi,
>>
>>
>>
>> I am getting an error related to an issue with Maven plugins while
>>
>> generating Hadoop 2.6.0 package with Maven 3.2.3.
>>
>>
>>
>> I did check Maven plugin page to see if I can resolve the issue, but,
>>
>> could not figure out the exact course of action.
>>
>>
>>
>> Any help to move forward with the hadoop installation would be
>>
>> much appreciated.
>>
>>
>>
>> The logs are attached.
>>
>>
>>
>> Thanks & Best Regards,
>>
>> Venkat Ramakrishnan.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: [email protected]
>>
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to