Quantcast

[jira] Created: (MNGECLIPSE-462) Subclipse Integration Does Not Support Relative Module Paths

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Created: (MNGECLIPSE-462) Subclipse Integration Does Not Support Relative Module Paths

JIRA jira@codehaus.org
Subclipse Integration Does Not Support Relative Module Paths
------------------------------------------------------------

                 Key: MNGECLIPSE-462
                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-462
             Project: Maven Integration for Eclipse
          Issue Type: Bug
          Components: Repository Management
    Affects Versions: 0.0.12
         Environment: Windows Vista Home Premium, Eclipse Europa 3.3.1.1, Subclipse 1.2.4, M2Eclipse 0.0.12.20071231-1800
            Reporter: Jarrod Carlson
         Attachments: Sample.zip

When checking out a Maven Multi-Module project who's modules are referenced with a relative path, the M2Eclipse Subclipse integration fails to resolve the relative path before attempting to check it out.

    Bogus URL
svn: URL 'https://dev.methodknowledgy.com/svn/MethodKnowledgy/Sample/sample/../sample-api/pom.xml' contains a '..' element

Please find attached a Sample application prototype which caused the error. The archive is an export from the SVN server. Since Eclipse does not support nested projects, the top-level project is 'sample/sample'. Running Maven lifecycles against the project from the command line completes successfully.

--
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

       

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

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MNGECLIPSE-462) Subclipse Integration Does Not Support Relative Module Paths

JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Kuleshov updated MNGECLIPSE-462:
---------------------------------------

    Attachment: mylyn-context.zip

> Subclipse Integration Does Not Support Relative Module Paths
> ------------------------------------------------------------
>
>                 Key: MNGECLIPSE-462
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-462
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Repository Management
>    Affects Versions: 0.0.12
>         Environment: Windows Vista Home Premium, Eclipse Europa 3.3.1.1, Subclipse 1.2.4, M2Eclipse 0.0.12.20071231-1800
>            Reporter: Jarrod Carlson
>         Attachments: mylyn-context.zip, Sample.zip
>
>
> When checking out a Maven Multi-Module project who's modules are referenced with a relative path, the M2Eclipse Subclipse integration fails to resolve the relative path before attempting to check it out.
>     Bogus URL
> svn: URL 'https://dev.methodknowledgy.com/svn/MethodKnowledgy/Sample/sample/../sample-api/pom.xml' contains a '..' element
> Please find attached a Sample application prototype which caused the error. The archive is an export from the SVN server. Since Eclipse does not support nested projects, the top-level project is 'sample/sample'. Running Maven lifecycles against the project from the command line completes successfully.

--
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

       

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

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Closed: (MNGECLIPSE-462) Subclipse Integration Does Not Support Relative Module Paths

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Kuleshov closed MNGECLIPSE-462.
--------------------------------------

         Assignee: Eugene Kuleshov
       Resolution: Fixed
    Fix Version/s: 0.9.3

Jarrod, thanks for the test project. Scheckout wizard had been rewriten for 0.9.2 build and I've verified it with your test project.

> Subclipse Integration Does Not Support Relative Module Paths
> ------------------------------------------------------------
>
>                 Key: MNGECLIPSE-462
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-462
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Repository Management
>    Affects Versions: 0.0.12
>         Environment: Windows Vista Home Premium, Eclipse Europa 3.3.1.1, Subclipse 1.2.4, M2Eclipse 0.0.12.20071231-1800
>            Reporter: Jarrod Carlson
>            Assignee: Eugene Kuleshov
>             Fix For: 0.9.3
>
>         Attachments: mylyn-context.zip, Sample.zip
>
>
> When checking out a Maven Multi-Module project who's modules are referenced with a relative path, the M2Eclipse Subclipse integration fails to resolve the relative path before attempting to check it out.
>     Bogus URL
> svn: URL 'https://dev.methodknowledgy.com/svn/MethodKnowledgy/Sample/sample/../sample-api/pom.xml' contains a '..' element
> Please find attached a Sample application prototype which caused the error. The archive is an export from the SVN server. Since Eclipse does not support nested projects, the top-level project is 'sample/sample'. Running Maven lifecycles against the project from the command line completes successfully.

--
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

       

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

    http://xircles.codehaus.org/manage_email


Loading...