[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854577#action_12854577
]
Doug Cutting commented on HADOOP-6671:
--------------------------------------
> The directory moving/renaming unfortunately tends not to work too well with
> Subversion and branches (or I was doing it wrong) so I don't know how big the
> benefit would be to start a new one for doing this.
Yes, if the branch is at all long-lived it will require lots of merges to keep
it up to date, and such merges will not be easy.
In my experience tree reorganizations are easier to develop as:
- a shell script that contains a sequence of 'svn mv' commands
- a patch file to be applied after the script has run
For example, AVRO-163 was developed this way.
> To use maven for hadoop common builds
> -------------------------------------
>
> Key: HADOOP-6671
> URL: https://issues.apache.org/jira/browse/HADOOP-6671
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.22.0
> Reporter: Giridharan Kesavan
>
> We are now able to publish hadoop artifacts to the maven repo successfully [
> Hadoop-6382]
> Drawbacks with the current approach:
> * Use ivy for dependency management with ivy.xml
> * Use maven-ant-task for artifact publishing to the maven repository
> * pom files are not generated dynamically
> To address this I propose we use maven to build hadoop-common, which would
> help us to manage dependencies, publish artifacts and have one single xml
> file(POM) for dependency management and artifact publishing.
> I would like to have a branch created to work on mavenizing hadoop common.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
