You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2010/09/21 03:05:32 UTC

[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling job files.

    [ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912797#action_12912797 ] 

Benson Margulies commented on MAHOUT-505:
-----------------------------------------

You can always use finalName to change the job jar name that lands in target, as opposed to that in the maven repo.

I'm not sure if we can diddle the <type> for the assembly plugin to an arbitrary suffix, but that might trigger the nexus bug all over.

You want me to take care of this?


> Alternate mechanism for assembling job files.
> ---------------------------------------------
>
>                 Key: MAHOUT-505
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-505
>             Project: Mahout
>          Issue Type: Improvement
>    Affects Versions: 0.4
>            Reporter: Drew Farris
>            Assignee: Drew Farris
>            Priority: Minor
>
> Per discussion here:
> http://www.lucidimagination.com/search/document/6082249e667f2a1b/problem_with_our_jar_publishing
> Assembly job files using the assembly plugin/descriptor instead of an ant taks and the build helper plugin. This results in job files being named {-job.jar} instead of {.job}, but that seems to be necessary to prevent nexus from overwriting the main jar artifacts with the jar files. 

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