[jira] Moved: (MOJO-1733) Cannot get chronos-maven-plugin to work. mojo-sandbox:5-SNAPSHOT.pom cannot be found

     [
https://jira.codehaus.org/browse/MOJO-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MSANDBOX-50 to MOJO-1733:
--------------------------------------------

     Complexity: Intermediate
    Component/s:     (was: maven-pom-plugin)
                 chronos
            Key: MOJO-1733  (was: MSANDBOX-50)
        Project: Mojo  (was: Maven 2.x Sandbox)

> Cannot get chronos-maven-plugin to work. mojo-sandbox:5-SNAPSHOT.pom cannot be found
> ------------------------------------------------------------------------------------
>
>                 Key: MOJO-1733
>                 URL: https://jira.codehaus.org/browse/MOJO-1733
>             Project: Mojo
>          Issue Type: Bug
>          Components: chronos
>         Environment: windows, maven 2, jmeter 2.4
>            Reporter: Simon Kofod
>
> I've created a java project based on maven and the documentation found here: 
> http://mojo.codehaus.org/chronos-maven-plugin/usage.html
> When I run maven I get the following error after maven has tried to download mojo-sandbox-5-snapshot.pom
from different locations:
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR

[jira] Created: (MOJO-1734) stopOnFailed doesn't work

stopOnFailed doesn't work
-------------------------

                 Key: MOJO-1734
                 URL: https://jira.codehaus.org/browse/MOJO-1734
             Project: Mojo
          Issue Type: Bug
          Components: chronos
    Affects Versions: chronos-maven-plugin-1.0
            Reporter: Krzysztof Krason
            Assignee: Kent Soelvsten

stopOnFailed option doesn't fail the build if there are errors in jmeter

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jira] Created: (MEXEC-98) "object is not an instance of declaring class" error

"object is not an instance of declaring class" error
----------------------------------------------------

                 Key: MEXEC-98
                 URL: https://jira.codehaus.org/browse/MEXEC-98
             Project: Maven 2.x Exec Plugin
          Issue Type: Bug
            Reporter: Markus

I got this error when using the exec:java mojo. An other people as well:
http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201006.mbox/%3C4C162860.5050307 <at> 4sengines.com%3E

The reason is that I only wrote "public void main(String[] args)" and forgot the static. However, this
silly error message is due to a bug in ExecJavaMojo.java line 291:
main.invoke( main, new Object[]{arguments} );

it should say:
main.invoke( null, new Object[]{arguments} );

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jira] Assigned: (MEXEC-88) ExecMojo: SuccessCodes config seems not to be recognized by commons exec framework

     [
https://jira.codehaus.org/browse/MEXEC-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte reassigned MEXEC-88:
-----------------------------------

    Assignee: Robert Scholte

> ExecMojo: SuccessCodes config seems not to be recognized by commons exec framework
> ----------------------------------------------------------------------------------
>
>                 Key: MEXEC-88
>                 URL: https://jira.codehaus.org/browse/MEXEC-88
>             Project: Maven 2.x Exec Plugin
>          Issue Type: Bug
>          Components: exec
>    Affects Versions: 1.2
>            Reporter: Daniel Strassenburg
>            Assignee: Robert Scholte
>            Priority: Blocker
>         Attachments: ExecMojo.java.patch, MEXEC-88.patch
>
>
> I used the successCodes config to tell the exec-mojo not to fail in case of error codes e.g. 0,1,2,3.
Unfortunately, the maven build fails with the exception below.
> Excerpt from mojo config:
> {noformat}
> [DEBUG]   (f) basedir = build/basedir
> [DEBUG]   (f) classpathScope = runtime

[jira] Closed: (MEXEC-88) ExecMojo: SuccessCodes config seems not to be recognized by commons exec framework

     [
https://jira.codehaus.org/browse/MEXEC-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MEXEC-88.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.1

Fixed in [rev. 14643|http://fisheye.codehaus.org/changelog/mojo/?cs=14643]
I've refactored the Test to an integration-test.
Thanks for the patch!

> ExecMojo: SuccessCodes config seems not to be recognized by commons exec framework
> ----------------------------------------------------------------------------------
>
>                 Key: MEXEC-88
>                 URL: https://jira.codehaus.org/browse/MEXEC-88
>             Project: Maven 2.x Exec Plugin
>          Issue Type: Bug
>          Components: exec
>    Affects Versions: 1.2
>            Reporter: Daniel Strassenburg
>            Assignee: Robert Scholte
>            Priority: Blocker
>             Fix For: 1.2.1
>
>         Attachments: ExecMojo.java.patch, MEXEC-88.patch
>

[jira] Created: (MEXEC-99) Use int[] instead of java.util.List for successCodes

Use int[] instead of java.util.List for successCodes
----------------------------------------------------

                 Key: MEXEC-99
                 URL: https://jira.codehaus.org/browse/MEXEC-99
             Project: Maven 2.x Exec Plugin
          Issue Type: Improvement
          Components: exec
    Affects Versions: 1.2
            Reporter: Robert Scholte
            Priority: Minor

With successCodes as a List we have to do the parsing/casting within the plugin. By using and int-array for
the successCodes (as the {{Executor}} expects them) we can let Plexus do the casting.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jira] Closed: (MEXEC-99) Use int[] instead of java.util.List for successCodes

     [
https://jira.codehaus.org/browse/MEXEC-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MEXEC-99.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.1
         Assignee: Robert Scholte

Fixed in [rev. 14644|http://fisheye.codehaus.org/changelog/mojo/?cs=14644]

> Use int[] instead of java.util.List for successCodes
> ----------------------------------------------------
>
>                 Key: MEXEC-99
>                 URL: https://jira.codehaus.org/browse/MEXEC-99
>             Project: Maven 2.x Exec Plugin
>          Issue Type: Improvement
>          Components: exec
>    Affects Versions: 1.2
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 1.2.1
>
>
> With successCodes as a List we have to do the parsing/casting within the plugin. By using and int-array for
the successCodes (as the {{Executor}} expects them) we can let Plexus do the casting.

RE: [VOTE] Javier Murciego as commiter] WAS: [mojo-dev] Commiter access

[jira] Closed: (MEXEC-98) "object is not an instance of declaring class" error

     [
https://jira.codehaus.org/browse/MEXEC-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MEXEC-98.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.1
         Assignee: Robert Scholte

Fixed in [rev. 14645|http://fisheye.codehaus.org/changelog/mojo/?cs=14645]
I've added a check if the main method is static. If not, throw an exception with a proper message.

> "object is not an instance of declaring class" error
> ----------------------------------------------------
>
>                 Key: MEXEC-98
>                 URL: https://jira.codehaus.org/browse/MEXEC-98
>             Project: Maven 2.x Exec Plugin
>          Issue Type: Bug
>            Reporter: Markus
>            Assignee: Robert Scholte
>             Fix For: 1.2.1
>
>
> I got this error when using the exec:java mojo. An other people as well:
> http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201006.mbox/%3C4C162860.5050307 <at> 4sengines.com%3E
> The reason is that I only wrote "public void main(String[] args)" and forgot the static. However, this
silly error message is due to a bug in ExecJavaMojo.java line 291:
> main.invoke( main, new Object[]{arguments} );
> it should say:
> main.invoke( null, new Object[]{arguments} );

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jira] Closed: (MEXEC-97) The POMs for the manual test projects are inconsistently named

     [
https://jira.codehaus.org/browse/MEXEC-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MEXEC-97.
-------------------------------

    Resolution: Won't Fix

Manual tests? No, those tests need to be refactored to integration tests. See MEXEC-77.

> The POMs for the manual test projects are inconsistently named
> --------------------------------------------------------------
>
>                 Key: MEXEC-97
>                 URL: https://jira.codehaus.org/browse/MEXEC-97
>             Project: Maven 2.x Exec Plugin
>          Issue Type: Improvement
>          Components: exec
>    Affects Versions: 1.2
>            Reporter: Siegfried Goeschl
>            Priority: Trivial
>
> The artifactIds and name of the manual test projects are inconsistent (e.g. duplicate artifiactId) -
nothing critical but I had a look at creating a parent pom for those manual test project in order to run them
all and Maven complained.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email