[ 
https://issues.apache.org/jira/browse/HDT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741860#comment-13741860
 ] 

Rahul Sharma commented on HDT-39:
---------------------------------

I have packed all the jars in the o.a.hadoop.eclipse bundle as we have done in 
the master.

The error you are getting is due to missing licenses in your code check the 
rat.txt file created in the target folder. It should list out which files are 
missing licenses. Also the Exclude: **/.settings/** is for the rat check.

For eclipse settings IMO if we can generate via maven then we do not require 
any settings/classpath in our repo, which we should try to target.

As for the current patch, I have created a bundle o.a.hadoop.eclipse using the 
maven-bundle plugin. We need to create this bundle first as this will contain 
all the required libs.  We should build this via mvn clean install 
-DhadoopBundle.

Next we can build/generate the eclipse setting for the project using mvn clean 
install or  mvn eclipse:eclipse command.

The artifacts generated can be imported in eclipse. We can run as this PDE via 
eclipse.

The one thing that is missing is setting the order and export for eclipse, so 
that it does not show compile warning. I have been trying with the 
maven-eclipse plugin to get that but I do not think that it allows to generate 
such a classpath. I will spend some more time to get around that. 
 

   




 

                
> Use maven build to package bundles
> ----------------------------------
>
>                 Key: HDT-39
>                 URL: https://issues.apache.org/jira/browse/HDT-39
>             Project: Hadoop Development Tools
>          Issue Type: Sub-task
>          Components: Build and infrastructure
>            Reporter: Srimanth Gunturi
>         Attachments: 0001-Added-lazyActivator-for-hdt-core.patch, 
> 0001-HDT-39-Using-maven-to-build-package.patch
>
>
> Currently there are missing JARs which we want to get through pom.xmls.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to