[jira] Created: (MNGECLIPSE-366) Plugin picks up local project rather than installed artifact

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

[jira] Created: (MNGECLIPSE-366) Plugin picks up local project rather than installed artifact

JIRA jira@codehaus.org
Plugin picks up local project rather than installed artifact
------------------------------------------------------------

                 Key: MNGECLIPSE-366
                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-366
             Project: Maven Integration for Eclipse
          Issue Type: Bug
          Components: Dependency Resolver
    Affects Versions: 0.0.10
         Environment: Eclipse 3.3, Maven 2.0.7, Win XP
            Reporter: Tom Nichols
             Fix For: 0.0.11
         Attachments: mvn-project-deps.PNG

I have two maven-enabled projects.  A has a dependency on B.  So I build B and install it.  Then maybe I make changes to B that are still in progress.  Oops!  A is picking up B as it exists in Eclipse, rather than from my local repo!  

I imagine this is a 'feature' since it didn't exist in 0.0.9.  Personally I find this very frustrating since basically I can't specify what released/installed version of B I want to use since it's open in Eclipse.  

I attached a PNG..  Hopefully it helps illustrate what I'm talking about.  If there is some documentation somewhere that explains this behavior, I apologise.. please point me to it :)

--
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] Issue Comment Edited: (MNGECLIPSE-366) Plugin picks up local project rather than installed artifact

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102054 ]

Stefan Seidel edited comment on MNGECLIPSE-366 at 7/12/07 7:34 AM:
-------------------------------------------------------------------

It's one of the major features of the plugin. See MNGECLIPSE-59. Since 0.0.11 it is only picking up the artifact from the workspace if the version number matches your dependency.


 was:
It's one of the major features of the plugin. See MNGECLIPSE-59.

> Plugin picks up local project rather than installed artifact
> ------------------------------------------------------------
>
>                 Key: MNGECLIPSE-366
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-366
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.10
>         Environment: Eclipse 3.3, Maven 2.0.7, Win XP
>            Reporter: Tom Nichols
>             Fix For: 0.0.11
>
>         Attachments: mvn-project-deps.PNG
>
>
> I have two maven-enabled projects.  A has a dependency on B.  So I build B and install it.  Then maybe I make changes to B that are still in progress.  Oops!  A is picking up B as it exists in Eclipse, rather than from my local repo!  
> I imagine this is a 'feature' since it didn't exist in 0.0.9.  Personally I find this very frustrating since basically I can't specify what released/installed version of B I want to use since it's open in Eclipse.  
> I attached a PNG..  Hopefully it helps illustrate what I'm talking about.  If there is some documentation somewhere that explains this behavior, I apologise.. please point me to it :)

--
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-366) Plugin picks up local project rather than installed artifact

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

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

Eugene Kuleshov updated MNGECLIPSE-366:
---------------------------------------

    Fix Version/s:     (was: 0.0.11)

First of all, please try the latest dev build from
http://m2eclipse.codehaus.org/update-dev/

If that doesn't help, we'll need a sample project that would allow us to reproduce this issue. See the following document for some tips. http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues

> Plugin picks up local project rather than installed artifact
> ------------------------------------------------------------
>
>                 Key: MNGECLIPSE-366
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-366
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.10
>         Environment: Eclipse 3.3, Maven 2.0.7, Win XP
>            Reporter: Tom Nichols
>         Attachments: mvn-project-deps.PNG
>
>
> I have two maven-enabled projects.  A has a dependency on B.  So I build B and install it.  Then maybe I make changes to B that are still in progress.  Oops!  A is picking up B as it exists in Eclipse, rather than from my local repo!  
> I imagine this is a 'feature' since it didn't exist in 0.0.9.  Personally I find this very frustrating since basically I can't specify what released/installed version of B I want to use since it's open in Eclipse.  
> I attached a PNG..  Hopefully it helps illustrate what I'm talking about.  If there is some documentation somewhere that explains this behavior, I apologise.. please point me to it :)

--
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] Commented: (MNGECLIPSE-366) Plugin picks up local project rather than installed artifact

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

    [ http://jira.codehaus.org/browse/MNGECLIPSE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102094 ]

Tom Nichols commented on MNGECLIPSE-366:
----------------------------------------

Apologies for the duplicate report.

I updated to 0.0.11 - timestamp is 20070603 - is that the latest version?  I do not see any option to configure per-project workspace dep resolution.  Also, the workspace dependency seems to be picked up regardless of whether or not the versions match in the POM.

I'll try to create a couple of projects to duplicate.  Thanks.

> Plugin picks up local project rather than installed artifact
> ------------------------------------------------------------
>
>                 Key: MNGECLIPSE-366
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-366
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.10
>         Environment: Eclipse 3.3, Maven 2.0.7, Win XP
>            Reporter: Tom Nichols
>         Attachments: mvn-project-deps.PNG
>
>
> I have two maven-enabled projects.  A has a dependency on B.  So I build B and install it.  Then maybe I make changes to B that are still in progress.  Oops!  A is picking up B as it exists in Eclipse, rather than from my local repo!  
> I imagine this is a 'feature' since it didn't exist in 0.0.9.  Personally I find this very frustrating since basically I can't specify what released/installed version of B I want to use since it's open in Eclipse.  
> I attached a PNG..  Hopefully it helps illustrate what I'm talking about.  If there is some documentation somewhere that explains this behavior, I apologise.. please point me to it :)

--
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-366) Plugin picks up local project rather than installed artifact

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

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

Eugene Kuleshov closed MNGECLIPSE-366.
--------------------------------------

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

It been possible to turn off workspace project resolution for quite while and since 0.9.1 that configuration been moved into project properties dialog.

> Plugin picks up local project rather than installed artifact
> ------------------------------------------------------------
>
>                 Key: MNGECLIPSE-366
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-366
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.10
>         Environment: Eclipse 3.3, Maven 2.0.7, Win XP
>            Reporter: Tom Nichols
>            Assignee: Eugene Kuleshov
>             Fix For: 0.9.1
>
>         Attachments: mvn-project-deps.PNG
>
>
> I have two maven-enabled projects.  A has a dependency on B.  So I build B and install it.  Then maybe I make changes to B that are still in progress.  Oops!  A is picking up B as it exists in Eclipse, rather than from my local repo!  
> I imagine this is a 'feature' since it didn't exist in 0.0.9.  Personally I find this very frustrating since basically I can't specify what released/installed version of B I want to use since it's open in Eclipse.  
> I attached a PNG..  Hopefully it helps illustrate what I'm talking about.  If there is some documentation somewhere that explains this behavior, I apologise.. please point me to it :)

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