You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/12/18 20:31:44 UTC

[jira] Updated: (AXIS2-4183) mvn eclipse:eclipse fails on aar and mar projects

     [ https://issues.apache.org/jira/browse/AXIS2-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen updated AXIS2-4183:
-----------------------------------

    Attachment: AXIS2-4183.patch.txt

Attached patch for this issue. Since I'm not sure about possible side effects, I will only commit it after the 1.5 release.

> mvn eclipse:eclipse fails on aar and mar projects
> -------------------------------------------------
>
>                 Key: AXIS2-4183
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4183
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.4.1
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>            Priority: Minor
>         Attachments: AXIS2-4183.patch.txt
>
>
> This issue was originally reported here: http://markmail.org/message/4bpdnwvx5v4rpt6d
> When mvn eclipse:eclipse is executed on a Maven project with aar or mar packaging it fails to create the .classpath file, and the .project file is basically empty (no natures and no builders). This makes it impossible to import the project into Eclipse. I solved a similar problem in Synapse by correcting the Plexus component descriptor of the corresponding Maven plugin (see r709895).
> This issue might also be related to AXIS2-2647.

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