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/10/23 19:28:19 UTC

[jira] Created: (MAHOUT-532) Update plugin versions in the POM structure

Update plugin versions in the POM structure
-------------------------------------------

                 Key: MAHOUT-532
                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
             Project: Mahout
          Issue Type: Bug
    Affects Versions: 0.4
            Reporter: Benson Margulies
            Assignee: Benson Margulies
             Fix For: 0.5


I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.


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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924260#action_12924260 ] 

Drew Farris commented on MAHOUT-532:
------------------------------------

I'm running into the following problem when building via 'mvn -e clean install' with this patch applied. Looks like we could be hitting http://jira.codehaus.org/browse/SUREFIRE-640. As the issue suggests changing redirectTestOutputToFile to false resolves the issue. Generally I prefer to keep the output redirected to a file  It is easier to troubleshoot unit test issues if the output is preserved in one file per test instead of having the explicitly capture the output of the entire maven build. Perhaps we should consider rolling back to an earlier version of the surefire plugin?

{noformat}
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error while executing forked tests.; nested exception is org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error while executing forked tests.; nested exception is org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error while executing forked tests.; nested exception is org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser
	at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:579)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
	... 17 more
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: Error while executing forked tests.; nested exception is org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser
	at org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:685)
	at org.apache.maven.surefire.booter.SurefireBooter.forkSuites(SurefireBooter.java:485)
	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkOnce(SurefireBooter.java:385)
	at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:246)
	at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:575)
	... 19 more
Caused by: org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser
	at org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:227)
	at org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:114)
	at org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:681)
	... 23 more
Caused by: java.lang.NullPointerException
	at org.apache.maven.surefire.booter.output.FileOutputConsumerProxy.consumeOutputLine(FileOutputConsumerProxy.java:162)
	at org.apache.maven.surefire.booter.output.ForkingStreamConsumer.consumeLine(ForkingStreamConsumer.java:74)
	at org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:197)
	at org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:137)
{noformat}


> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924276#action_12924276 ] 

Benson Margulies commented on MAHOUT-532:
-----------------------------------------

Updated to old version.

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924268#action_12924268 ] 

Ted Dunning commented on MAHOUT-532:
------------------------------------

I like the separate output files as well so I would vote for downgrading.

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Updated: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated MAHOUT-532:
------------------------------------

    Attachment: MAHOUT-532.patch

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch, MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924251#action_12924251 ] 

Ted Dunning commented on MAHOUT-532:
------------------------------------


+1.

I have been using the parallel build stuff for a bit and it actually works under maven 2.

But upgrading the different versions is a great idea.



> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924405#action_12924405 ] 

Ted Dunning commented on MAHOUT-532:
------------------------------------

Looks good on my side:
{code}
$ mvn -Prelease clean install
   ... MANY lines deleted ...
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 77 minutes 57 seconds
[INFO] Finished at: Sun Oct 24 16:06:31 PDT 2010
[INFO] Final Memory: 103M/123M
[INFO] ------------------------------------------------------------------------
$
{code}

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Updated: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated MAHOUT-532:
------------------------------------

    Attachment:     (was: MAHOUT-532.patch)

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Updated: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated MAHOUT-532:
------------------------------------

    Attachment: MAHOUT-532.patch

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924406#action_12924406 ] 

Ted Dunning commented on MAHOUT-532:
------------------------------------

The mahout-math jar appears to be in *-job.jar

There seems to be some redundancy in directory structure in the distribution/target directory:
{code}
$ pwd
distribution/target/mahout-distribution-0.5-SNAPSHOT/mahout-distribution-0.5-SNAPSHOT
$
{code}
Since the actual artifacts look pretty good, I assume that this is not important.




> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924275#action_12924275 ] 

Benson Margulies commented on MAHOUT-532:
-----------------------------------------

in process.

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch, MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Updated: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated MAHOUT-532:
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.5)
                   0.4
           Status: Resolved  (was: Patch Available)

patch applied.

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.4
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Updated: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies updated MAHOUT-532:
------------------------------------

    Status: Patch Available  (was: Open)

It would be good if some other people would try this out.

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924264#action_12924264 ] 

Drew Farris commented on MAHOUT-532:
------------------------------------

Verified that either downgrading to 2.5 or setting redirectTestOutputToFile to false resolve this issue, I'd prefer the former. Anyone else care?

> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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


[jira] Commented: (MAHOUT-532) Update plugin versions in the POM structure

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAHOUT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924424#action_12924424 ] 

Hudson commented on MAHOUT-532:
-------------------------------

Integrated in Mahout-Quality #425 (See [https://hudson.apache.org/hudson/job/Mahout-Quality/425/])
    MAHOUT-532: update poms to resolve warnings from M3 and take relatively current plugin versions


> Update plugin versions in the POM structure
> -------------------------------------------
>
>                 Key: MAHOUT-532
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-532
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 0.5
>
>         Attachments: MAHOUT-532.patch
>
>
> I suspect that some of Sean's problems with pushing a release have to do with the staleness of the versions of various critical plugins, such as the maven release plugin. Under this JIRA, I propose to move everything up to current released versions. As a side-benefit, parallel builds under maven 3 should become possible.

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