incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HAMA-366) Remove unnecessary dependencies.
Date Tue, 15 Mar 2011 11:15:29 GMT

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

Edward J. Yoon updated HAMA-366:
--------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Thanks for the comments and new patch!
+1, I've committed this.

> Remove unnecessary dependencies.
> --------------------------------
>
>                 Key: HAMA-366
>                 URL: https://issues.apache.org/jira/browse/HAMA-366
>             Project: Hama
>          Issue Type: Improvement
>          Components: build 
>    Affects Versions: 0.2.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.2.0
>
>         Attachments: dependencies.patch, dependencies2.patch
>
>
> Hi,
> > While doing that I found the commons-el-from-jetty dependency and could not
> > find a pointer to the project (nor in Maven repositories).
> > Does anyone have any clue about it?
> The jetty and http related dependencies were included for future web
> monitoring tool. However, I think it seems better to remove them from
> dependencies list at this time.
> Unnecessary dependencies:
>  - commons-el-from-jetty-5.1.4.jar
>  - commons-math-1.1.jar
>  - jetty-6.1.14.jar
>  - jetty-util-6.1.14.jar
>  - libthrift-r771587.jar
> > Also the Commons CLI is at 2.0-SNAPSHOT and it's not good to have
> > dependencies from SNAPSHOTS as you can imagine, so I switched my local copy
> > to version 1.2 and everything is still working.
> > Once we get rid of the above issues I can provide a new patch to Maven POM.
> +1
> On Tue, Mar 15, 2011 at 2:44 AM, Tommaso Teofili
> - Hide quoted text -
> <tommaso.teofili@gmail.com> wrote:
> > Hi again,
> > I am going through Maven POM to make sure it's compliant with Maven good
> > practices and release rules (even if we're not going to make the release
> > through Maven at the moment).
> > While doing that I found the commons-el-from-jetty dependency and could not
> > find a pointer to the project (nor in Maven repositories).
> > Does anyone have any clue about it?
> > Also the Commons CLI is at 2.0-SNAPSHOT and it's not good to have
> > dependencies from SNAPSHOTS as you can imagine, so I switched my local copy
> > to version 1.2 and everything is still working.
> > Once we get rid of the above issues I can provide a new patch to Maven POM.
> > Cheers,
> > Tommaso
> >

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message