[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hadoop-dev
Subject:    [jira] Resolved: (HADOOP-3302) Support Maven-based builds
From:       "Eli Collins (JIRA)" <jira () apache ! org>
Date:       2010-12-22 18:48:41
Message-ID: 32627026.273381293043721087.JavaMail.jira () thor
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/HADOOP-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Eli Collins resolved HADOOP-3302.
---------------------------------

    Resolution: Duplicate

Closing as dupe of HADOOP-6671.

> Support Maven-based builds
> --------------------------
> 
> Key: HADOOP-3302
> URL: https://issues.apache.org/jira/browse/HADOOP-3302
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 0.18.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> 
> The reasons I would like to use maven are:
> - the possibility to define artifact templates to define a kind of standard \
>                 layout/design by artifact
> - it is not necessary for every developer to come up with his own ant build-file \
>                 and process
> - the possibility to define and resolve dependencies transitively
> But there are also some disadvantages/concerns I identified:
> Maven is downloading a lot of plugins from a central repository that is not under \
>                 my control
> - What's about the licenses of these plugins? How do I know I am allowed to use \
>                 them for a commercial product?
> - What's about security? How can I be sure, that the plugins are not manipulated \
> and contain the original (delivered by the JAR provider for e.g. junit-jar) \
> contents. I observed, that some plugins didn't pass the md5 checks but have been \
> installed anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]