You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Drew Farris (JIRA)" <ji...@apache.org> on 2010/09/21 02:57:32 UTC
[jira] Created: (MAHOUT-505) Alternate mechanism for assembling job
files.
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.
[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Drew Farris resolved MAHOUT-505.
--------------------------------
Resolution: Fixed
> 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.
[jira] Updated: (MAHOUT-505) Alternate mechanism for assembling job
files.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Drew Farris updated MAHOUT-505:
-------------------------------
Attachment: MAHOUT-505.patch
Here's the patch. Built, ran tests, and build-reuters.sh example
I did a mvn deploy and it completed successfully but can't figure out where it wound up. I suspect I don't have the Nexus karma I need for build promotion.
Ted, maybe you can give this a try and see how it works out for you? Were you doing the deploy by hand, or using Husdon?
> 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.
[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912806#action_12912806 ]
Drew Farris commented on MAHOUT-505:
------------------------------------
Some finalName wierdness:
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-5</version>
<executions>
<execution>
<id>job</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<finalName>${project.artifactId}-${project.version}.job</finalName>
<descriptors>
<descriptor>src/main/assembly/job.xml</descriptor>
</descriptors>
</configuration>
</execution>
</executions>
</plugin>
{code}
Results in:
{[INFO] Installing /home/drew/mahout/trunk/core/target/mahout-core-0.4-SNAPSHOT.job-job.jar to /home/drew/maven/repository/org/apache/mahout/mahout-core/0.4-SNAPSHOT/mahout-core-0.4-SNAPSHOT-job.jar}
The former being wrong the latter being correct. So, it's getting deployed to the right location.
> 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.
[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917470#action_12917470 ]
Hudson commented on MAHOUT-505:
-------------------------------
Integrated in Mahout-Quality #370 (See [https://hudson.apache.org/hudson/job/Mahout-Quality/370/])
MAHOUT-505: Alternate mechanism for assembling job files. Now produces *-job.jar instead of *.job, should resolve Hudson artifact indexing issues
> 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.
[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912928#action_12912928 ]
Benson Margulies commented on MAHOUT-505:
-----------------------------------------
With the patch in the current state:
Installing /Users/benson/asf/mahout/trunk/core/target/mahout-core-0.4-SNAPSHOT-job.jar to /Users/benson/.m2/repository/org/apache/mahout/mahout-core/0.4-SNAPSHOT/mahout-core-0.4-SNAPSHOT-job.jar
means
* group org.apache.mahout
* artifact mahout-core
* classifier job
There is no finalName in the current patch.
It uploads:
https://repository.apache.org/content/repositories/snapshots/org/apache/mahout/mahout-core/0.4-SNAPSHOT/mahout-core-0.4-20100921.103833-155-job.jar
I think I see where all the frustration comes from. You can't really control the name of the file uploaded to the repo. finalName is there to let you control the name in 'target', and it has some limitations even with that. You could try turning off 'attach' in the assembly plugin, and then put the build-helper back into the picture, setting the 'type' to job. However, chances are that this will get you back into Ted's original problem.
Ted's original report is that nexus messes up when you attach an artifact that differs only in type from the main artifact. This does not surprise me. 'type' generally derives from the top-level packaging element, and 'classifier' is supposed to be used to distinguish multiple outputs.
If you really want <type>job</type>, then you need to move this to its own project. You may still need the build helper, because I don't know of any way to get the assembly plugin to end up with .job instead of .jar without modifying it. Just putting '.job' in the finalName does not change the <type>.
> 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.
[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912842#action_12912842 ]
Ted Dunning commented on MAHOUT-505:
------------------------------------
{quote}
Ted, maybe you can give this a try and see how it works out for you? Were you doing the deploy by hand, or using Husdon?
{quote}
I was merely observing the outcome of an occult process. Presumably it is run by Hudson, but couldn't say.
> 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.
[jira] Commented: (MAHOUT-505) Alternate mechanism for assembling
job files.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912801#action_12912801 ]
Drew Farris commented on MAHOUT-505:
------------------------------------
Benson, thanks for the tip about finalName -- and yes it looks like <type> is what got us into the mess in the first place, I suspect we need to set classifier to keep nexus happy.
You're more than welcome to take it from here.
Do you know who need to talk to and what do I need to ask for to get the necessary karma for doing build promotion in Nexus?
> 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.