[
https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912966#action_12912966
]
Drew Farris commented on MAHOUT-505:
------------------------------------
Ok, I was missing something, everything does get deployed properly with this
patch
For example. using Ted's original query:
https://repository.apache.org/index.html#nexus-search;gav~org.apache.mahout~mahout-core~~~~kw,versionexpand
The core jar artifact is now correct.
So, one question is whether everyone is happy with the name {{-job.jar}}
instead of {{.job}} for out job files.
Another question is whether we need mahout-core.job >and< mahout-examples.job
or whether mahout-examples.job would be sufficient.
It is also worth asking whether {{job}} files should be deployed to the
repository in the first place. If not, we keep thing in the build as they are
and simply avoid attaching the job artifacts to the main artifact wit h the
build helper plugin.
> 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
> Attachments: MAHOUT-505.patch
>
>
> 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.
