You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Paolo Castagna (JIRA)" <ji...@apache.org> on 2010/05/21 15:22:17 UTC

[jira] Commented: (NUTCH-825) Publish nutch artifacts to central maven repository

    [ https://issues.apache.org/jira/browse/NUTCH-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869979#action_12869979 ] 

Paolo Castagna commented on NUTCH-825:
--------------------------------------

Publishing the Nutch artifacts is beneficial not only to Maven users, but also to Ivy ones as well as all the others tools which are compatible with the de-facto Maven repository layout conventions.

Other Apache projects are using Ant+Ivy and, at the same time, publishing artifacts (or aiming to do it) to the Maven central repository.

Perhaps, it would be worth considering the pros/cons of Ant+Ivy vs. Ant+Maven respect to "publishing" (i.e. beneficial to Nutch users) in addition to the dependency management (i.e. beneficial to Nutch developer).

IMHO, as I have said, in NUTCH-821... for publishing, Ant+Maven might be a simpler solution.

> Publish nutch artifacts to central maven repository
> ---------------------------------------------------
>
>                 Key: NUTCH-825
>                 URL: https://issues.apache.org/jira/browse/NUTCH-825
>             Project: Nutch
>          Issue Type: New Feature
>            Reporter: Enis Soztutar
>
> As per the discussion at NUTCH-821, publishing nutch artifacts to maven will be nice. NUTCH-821 already introduces dependency management with ivy. As for the remaining, ant task for generating pom files should be developed, and artifacts should be published to maven repo by a committer after a release. 

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