hdt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDT-39) Use maven build to package bundles
Date Fri, 16 Aug 2013 05:26:49 GMT

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

Srimanth Gunturi commented on HDT-39:

Thank you for pointing to the rat.txt, I was able to build the plugins for the first time!

I would like to request the Hadoop release bundle to be called 'org.apache.hdt.hadoop.release'.
This is because it will contain not the entire Hadoop release, but only JARs HDT requires
for a Hadoop release (that too only components we support - HDFS, MR, ZK, etc.). We will be
stepping on Hadoop main project's namespace by releasing it with 'org.apache.hadoop.eclipse'.
If Hadoop ever decided to generate its own plugins, we will be in error. 

With regards to generating all of bundle metadata (.settings etc.) via maven settingsā€¦ I
would like to put forward my reservations, and the community can discuss on this. All we are
trying to do is package JAR bundles. 

Firstly, adding a level of indirection just to generate some static files is a lot of effort.
If there is truly dynamic content based on metadata, I can understand. Files under .settings/
are generally static, and do not require all the extra effort of maven generating them. So
IMHO, the .settings folder (and any other static file) should not be ignored.

Secondly, we will be pegged to maven-tycho plugins capabilities and release schedules - all
so that we can build JARs. With Eclipse 4 and other Eclipse versions coming out every in quick
succession, we will have to wait for maven-tycho to support any new feature. For example,
the experimentation with export order in class paths - if maven-tycho didnt support it, we
are stuck at a difficult place.

Thirdly, we are a very small community with a lot of dev work ahead. Taking a developer a
week to get a packaging just right is expensive. Maybe when we have many contributors, we
can come back to this. 

For the above reasons, I would like to request to keep maven plugins usage to a bare minimum,
and use it only where absolutely necessary. 
> 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

View raw message