You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bodhayan Chakraborty (JIRA)" <ji...@codehaus.org> on 2010/10/13 17:54:32 UTC

[jira] Created: (MNG-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.

Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.
------------------------------------------------------------------------------------------------------

                 Key: MNG-4863
                 URL: http://jira.codehaus.org/browse/MNG-4863
             Project: Maven 2 & 3
          Issue Type: Bug
          Components: Plugins and Lifecycle
    Affects Versions: 3.0
         Environment: Windows XP, Jdk 1.6.0_20
            Reporter: Bodhayan Chakraborty


Hi,

I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. 

...........................
[ERROR] Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 cannot be cast to groovy.lang.GroovyObject -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
...........................

This is the plugin that I am using.

<plugin>
	<groupId>org.codehaus.groovy.maven</groupId>
	<artifactId>gmaven-plugin</artifactId>
	....
	....
</plugin>

But if I change the plugin like below, it is working. 

<plugin>
	<groupId>org.codehaus.gmaven</groupId>
	<artifactId>gmaven-plugin</artifactId>
	<version>1.3</version>
	....
	....
</plugin>

Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to 3.0?

Please let me know,

Thanks,
Bodhayan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239456#action_239456 ] 

Olivier Lamy commented on MNG-4863:
-----------------------------------

yes it's mandatory :-)

> Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4863
>                 URL: http://jira.codehaus.org/browse/MNG-4863
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0
>         Environment: Windows XP, Jdk 1.6.0_20
>            Reporter: Bodhayan Chakraborty
>
> Hi,
> I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. 
> ...........................
> [ERROR] Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 cannot be cast to groovy.lang.GroovyObject -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> ...........................
> This is the plugin that I am using.
> <plugin>
> 	<groupId>org.codehaus.groovy.maven</groupId>
> 	<artifactId>gmaven-plugin</artifactId>
> 	....
> 	....
> </plugin>
> But if I change the plugin like below, it is working. 
> <plugin>
> 	<groupId>org.codehaus.gmaven</groupId>
> 	<artifactId>gmaven-plugin</artifactId>
> 	<version>1.3</version>
> 	....
> 	....
> </plugin>
> Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to 3.0?
> Please let me know,
> Thanks,
> Bodhayan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (MNG-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4863.
----------------------------------

    Resolution: Won't Fix
      Assignee: Benjamin Bentmann

> Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4863
>                 URL: http://jira.codehaus.org/browse/MNG-4863
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0
>         Environment: Windows XP, Jdk 1.6.0_20
>            Reporter: Bodhayan Chakraborty
>            Assignee: Benjamin Bentmann
>
> Hi,
> I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. 
> ...........................
> [ERROR] Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 cannot be cast to groovy.lang.GroovyObject -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> ...........................
> This is the plugin that I am using.
> <plugin>
> 	<groupId>org.codehaus.groovy.maven</groupId>
> 	<artifactId>gmaven-plugin</artifactId>
> 	....
> 	....
> </plugin>
> But if I change the plugin like below, it is working. 
> <plugin>
> 	<groupId>org.codehaus.gmaven</groupId>
> 	<artifactId>gmaven-plugin</artifactId>
> 	<version>1.3</version>
> 	....
> 	....
> </plugin>
> Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to 3.0?
> Please let me know,
> Thanks,
> Bodhayan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira