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

Srimanth Gunturi commented on HDT-39:
-------------------------------------

[~rahul.sharma], thank you for taking effort on generating the pom files.

I applied the patch and did 'mvn eclipse:clean eclipse:eclipse' - which gave me 
the following exception. It looks like we are still referencing the 
'org.apache.hadoop.eclipse' name in pom.xml.

===================================
[INFO] Computing target platform for MavenProject: 
org.apache.hdt:org.apache.hdt.core:0.0.1-SNAPSHOT @ 
/Users/sgunturi/dev/git/incubator-hdt/org.apache.hdt.core/pom.xml
[WARNING] Missing POM for 
org.apache.hdt:org.apache.hadoop.eclipse:jar:0.0.1-SNAPSHOT
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve project 
dependencies: Missing:
[ERROR] ----------
[ERROR] 1) org.apache.hdt:org.apache.hadoop.eclipse:jar:0.0.1-SNAPSHOT
===================================

Going through the patch I noticed the following:
* .settings folder is ignored. I think it should not be ignored as it contains 
valuable project specific settings.
* Fragment 'org.apache.hdt.hadoop.release' should not be renamed to 
'org.apache.hdt.release'. The reason is that the fragment contains all Hadoop 
Release specific JARs for a Hadoop version (hdfs clients, zk clients, etc.). 
Renaming it would suggest that its a hdt release - which it is not. 
                
> 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-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