Nabble - Maven Eclipse - Dev

[jira] Closed: (MNGECLIPSE-280) Picks up pom.xml in current project or in target of another project

2008-04-19T10:25:55Z

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

Eugene Kuleshov closed MNGECLIPSE-280.
--------------------------------------

Resolution: Incomplete

Please feel free to reopen this and provide test project that would allow us to reproduce this issue. Thanks.

> Picks up pom.xml in current project or in target of another project
> -------------------------------------------------------------------
>
> Key: MNGECLIPSE-280
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-280
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.10
> Environment: Eclipse 3.2
> Reporter: Ben Tatham
>
> When a pom.xml of a dependency is found anywhere in the Eclipse Workspace, the Eclipse project containing that dependency is added to the Maven2 Dependencies Library. Normally, this is great. It means you can modify the project pom to point to a dependency that is also in development together with the current project.
> However, some use cases require that Maven unpack some dependencies for a variety of reasons (like war overlays). Therefore, the pom.xml of the dependency shows up in the target folder somewhere. This results in one of two things happening:
> 1) If the dependency pom is found in the target of another project, that other project is added to the Maven2 Dependencies Library. However, that project may or may not actually have the jars/classes needed in its classpath. And this can also lead to depending on a parent project sometimes.
> 2) If the dependency pom is found in the same eclipse project, nothing happens, and you cannot build. I assume that the current project is attempted to be added to the Maven2 Dependencies Library and Eclipse itself (JDT?) blocks that because it makes no sense.
> I suggest an (optional) filter on what is searched when looking for projects in the Eclipse Workspace. Perhaps blocking all pom.xml's under target would make sense. Or perhaps make it a white list, such that only pom.xml in the root of a project is allowed to be searched.

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

[jira] Closed: (MNGECLIPSE-400) When project artifact contains extra classes not defined in the source, it is not added to the dependent project's classpath

2008-04-19T10:23:55Z

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

Eugene Kuleshov closed MNGECLIPSE-400.
--------------------------------------

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

We now support resource filtering, that also allows to specify custom goals to be executed automatically on resource changes.

However as I mentioned in my last comment, this is pretty much against Maven philosophy and it is better to reorganize codebase to use Maven dependency management.

> When project artifact contains extra classes not defined in the source, it is not added to the dependent project's classpath
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: MNGECLIPSE-400
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-400
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Dependency Resolver
> Environment: Windows XP, Eclipse
> Reporter: zalym
> Assignee: Eugene Kuleshov
> Fix For: 0.9.1
>
> Attachments: MNGECLIPSE-400-projects.zip
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I have a core models project and then lots of implementation specific models. The impl projects depends on the core models, with optional specified as true. The implementation project contains the classes of the core as well. The core is referred to only by the implementation, and all other projects depends on the impl project.
> When I depend on the implementation project, m2eclipse doesn't recognize the additional classes from the model. It recognises only those classes specified in the implementation. So it shows compile errors in eclipse, but works from the command line.
> I think the reason is that the plugin resolves to the eclipse project and not the generated artifact. Ideally it should mirror maven functionality which is the final artifact rather than the sources.

[jira] Closed: (MNGECLIPSE-449) Import Wizard uses default compiler settings when thay are not declared in pom.xml

2008-04-19T10:19:55Z

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

Eugene Kuleshov closed MNGECLIPSE-449.
--------------------------------------

Resolution: Incomplete

Provided test project has commented out compiler settings, so we use defaults when importing project.

Please submit separate enhancement requests or post to the dev mailing list if you need additional integration support.

> Import Wizard uses default compiler settings when thay are not declared in pom.xml
> ----------------------------------------------------------------------------------
>
> Key: MNGECLIPSE-449
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-449
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Wizards
> Affects Versions: 0.0.12
> Environment: Window XP, Eclipse 3.2.2
> Reporter: Irene Levina
> Attachments: www.zip
>
>
> Maven Import Wizard always use default value for JavaCore.COMPILER_COMPLIANCE option, thus project that has source code compliant with JAVA 5 (and up) would be imported with an errors.
> To reproduce issue unzip attachment to any dir on your local drive and use Maven Import Wizard to import it, you will see that imported project will contain errors.
> Way around user should use project preferences to change project compiler compliance level to 5.0
> However it would be nice that wizard would provide choice to the user to specify compiler complience level.

[jira] Closed: (MNGECLIPSE-341) Maven dependencies are ignored when maven enabled project is included

2008-04-19T10:11:55Z

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

Eugene Kuleshov closed MNGECLIPSE-341.
--------------------------------------

Resolution: Fixed

It doesn't seem anything left here. please feel free to reopen if I missed something.

> Maven dependencies are ignored when maven enabled project is included
> ---------------------------------------------------------------------
>
> Key: MNGECLIPSE-341
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-341
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Dependency Resolver
> Affects Versions: 0.0.9
> Environment: linux, eclipse 3.2.2 M20070212-1330
> Reporter: Achim Abeling
> Priority: Minor
> Attachments: eclipsemavenbug.tar.gz, eclipsemavenbug.tar.gz
>
>
> I have two maven enabled projects: A and B.
> A has a dependency to e.g. commons-lang.
> B has a dependency to e.g. commons-logging.
> A has project B as a required project.
> When project B is before project A's dependencies in the build class path order the dependencies of project A are totally lost. Only the dependencies of project B are included.
> This can be checked by looking at the system property "java.class.path" in a test class: the value does not contain commons-lang.
> It shows (in my testcase):
> /home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug2:/home/aabeling/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar:/home/aabeling/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar:/home/aabeling/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar:/home/aabeling/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar:/home/aabeling/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar:/home/aabeling/EclipseWorkspaces/workspace/eclipsemavenbug1/bin
> My test case with the two projects is attached. The project eclipsemavenbug1 contains a class which can be started in Eclipse to show the bug.

[jira] Updated: (MNGECLIPSE-299) Property ${settings.localRepository} isn't recognized from antrun plugin

2008-04-19T10:09:55Z

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

Eugene Kuleshov updated MNGECLIPSE-299:
---------------------------------------

Summary: Property ${settings.localRepository} isn't recognized from antrun plugin (was: Property ${settings.localRepository} isn't recognized)

> Property ${settings.localRepository} isn't recognized from antrun plugin
> ------------------------------------------------------------------------
>
> Key: MNGECLIPSE-299
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-299
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Maven Embedder
> Affects Versions: 0.0.10, 0.0.11
> Reporter: Vincent ASTRUC
> Attachments: eclipse_conf.txt, MNGECLIPSE-299.zip
>
>
> With the version 0.0.9 this property is recognized

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

2008-04-18T21:46:55Z

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

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

2008-04-18T21:44:55Z

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

[jira] Closed: (MNGECLIPSE-423) Cannot find parent POM

2008-04-18T20:41:55Z

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

Eugene Kuleshov closed MNGECLIPSE-423.
--------------------------------------

Resolution: Cannot Reproduce

Closing as not reproducible. Please feel free to reopen if you still experiencing this issue. Thanks.

> Cannot find parent POM
> ----------------------
>
> Key: MNGECLIPSE-423
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-423
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.12
> Reporter: Vincent ASTRUC
> Assignee: Eugene Kuleshov
> Attachments: eclipse_conf.txt, MNGECLIPSE-423.zip, proxy.png
>
>
> If you have a project with a parent, the parent could not be retrieved from remote repository by eclipse. You must execute a goal to download the parent.
> We use a maven proxy to access to the remote repository.

[jira] Closed: (MNGECLIPSE-498) Transitive Dependencies Not included in Eclipse

2008-04-18T20:39:55Z

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

Eugene Kuleshov closed MNGECLIPSE-498.
--------------------------------------

Assignee: John Casey
Resolution: Fixed
Fix Version/s: 0.9.2

Verified hat it works with 0.9.2 build

> Transitive Dependencies Not included in Eclipse
> -----------------------------------------------
>
> Key: MNGECLIPSE-498
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-498
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Dependency Resolver
> Affects Versions: 0.9.0
> Environment: Mac OS X Leopard 10.5.2, Eclipse Europa 3.3.2
> Reporter: Jarrod Carlson
> Assignee: John Casey
> Fix For: 0.9.2
>
> Attachments: pom.xml
>
>
> Transitive dependencies are not being included in the Eclipse environment using the latest build of the plugin (0.9.0.20080310-1400-Sonatype).
> Project A depends on project B, which depends on project C. Project A has Java code referencing code in project C. Eclipse has compilation errors, because it cannot resolve class types found in project C.
> An example: We are building a web service application. Our project depends on org.springframework.ws :: spring-ws-core-tiger : 1.0.3, which in turn depends on org.springframework.ws :: spring-ws-core : 1.0.3. Our project references org.springframework.ws.server.endpoint.AbstractMarshallingPayloadEndpoint, but Eclipse is unable to resolve this class type, because spring-ws-core is not included in the Maven Dependencies.
> Adding spring-ws-core as a direct dependency of our project resolved the build error in Eclipse, but other dependencies are not listed.

[jira] Closed: (MNGECLIPSE-552) Directory renaming while importing maven existing project into eclipse

2008-04-18T20:18:55Z

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

Eugene Kuleshov closed MNGECLIPSE-552.
--------------------------------------

Assignee: Eugene Kuleshov
Resolution: Fixed

Fixed in trunk. When importing local Maven projects directories not renamed

> Directory renaming while importing maven existing project into eclipse
> ----------------------------------------------------------------------
>
> Key: MNGECLIPSE-552
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-552
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Wizards
> Affects Versions: 0.9.2
> Environment: Eclipse Europa 3.3.2, Jdk 1.6u5
> Reporter: Sergey Elin
> Assignee: Eugene Kuleshov
> Fix For: 0.9.3
>
> Attachments: mylyn-context.zip
>
>
> When importing existing multimodule project via Maven Project wizard, root directory name was changed to artifactId ant it broke catalog structure.

[jira] Updated: (MNGECLIPSE-552) Directory renaming while importing maven existing project into eclipse

2008-04-18T20:16:55Z

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

Eugene Kuleshov updated MNGECLIPSE-552:
---------------------------------------

Attachment: mylyn-context.zip

> Directory renaming while importing maven existing project into eclipse
> ----------------------------------------------------------------------
>
> Key: MNGECLIPSE-552
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-552
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Wizards
> Affects Versions: 0.9.2
> Environment: Eclipse Europa 3.3.2, Jdk 1.6u5
> Reporter: Sergey Elin
> Fix For: 0.9.3
>
> Attachments: mylyn-context.zip
>
>
> When importing existing multimodule project via Maven Project wizard, root directory name was changed to artifactId ant it broke catalog structure.

[jira] Assigned: (MNGECLIPSE-523) performance problem open/close project

2008-04-18T10:26:55Z

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

Igor Fedorenko reassigned MNGECLIPSE-523:
-----------------------------------------

Assignee: Igor Fedorenko

> performance problem open/close project
> --------------------------------------
>
> Key: MNGECLIPSE-523
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-523
> Project: Maven Integration for Eclipse
> Issue Type: Improvement
> Components: Dependency Resolver
> Affects Versions: 0.9.1
> Reporter: manuel aldana
> Assignee: Igor Fedorenko
> Priority: Critical
> Attachments: logAfterCheckout.txt, logRebuild.txt
>
>
> when opening or closing a project inside workspace the maven auto builing ('Updating Maven Dependencies') takes very long to complete (around a minute). the same is when checking out or deleting a project
> for me this is a major issue, for i keep only open projects in workspace i am working on. i.e. i am checking-out/closing/opening very often. for this performance reasons i still have to use 0.0.12 version. with 0.0.12 in fact i had to make Project->Clean... manually, when workspace changed. never the less this went much quicker (around 15 seconds vs. 1 minute of auto refresh).
> eclipse install is very slim and there are only two checked out projects, so i guess it has something to do with dep-resolving refresh after project-set workspace change.

[jira] Commented: (MNGECLIPSE-523) performance problem open/close project

2008-04-18T06:56:55Z

[ http://jira.codehaus.org/browse/MNGECLIPSE-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131274#action_131274 ]

Igor Fedorenko commented on MNGECLIPSE-523:
-------------------------------------------

I am glad to hear that m2eclipse performs well for you now, Manuel. The proper fix for this problem will require changes to maven embedder, and we'll try to implement it in 0.9.3/0.9.4 timeframe. Thank you for your patience and all the help diagnosing thing bug.

> performance problem open/close project
> --------------------------------------
>
> Key: MNGECLIPSE-523
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-523
> Project: Maven Integration for Eclipse
> Issue Type: Improvement
> Components: Dependency Resolver
> Affects Versions: 0.9.1
> Reporter: manuel aldana
> Priority: Critical
> Attachments: logAfterCheckout.txt, logRebuild.txt
>
>
> when opening or closing a project inside workspace the maven auto builing ('Updating Maven Dependencies') takes very long to complete (around a minute). the same is when checking out or deleting a project
> for me this is a major issue, for i keep only open projects in workspace i am working on. i.e. i am checking-out/closing/opening very often. for this performance reasons i still have to use 0.0.12 version. with 0.0.12 in fact i had to make Project->Clean... manually, when workspace changed. never the less this went much quicker (around 15 seconds vs. 1 minute of auto refresh).
> eclipse install is very slim and there are only two checked out projects, so i guess it has something to do with dep-resolving refresh after project-set workspace change.

[jira] Commented: (MNGECLIPSE-523) performance problem open/close project

2008-04-18T03:29:56Z

[ http://jira.codehaus.org/browse/MNGECLIPSE-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131240#action_131240 ]

manuel aldana commented on MNGECLIPSE-523:
------------------------------------------

found out the reason why resolution is hanging. certain dependencies in my internal repository did not have a pom.xml provided and m2eclipse always tried to resolve it again. after cleaning up repository (redeploying with adding pom.xml for all problematic dependencies it worked fine) performance is good.

suggestion for patch: in case pom of dependency cannot be found, m2eclipse should remember this and not constantly trying to resolve it again. otherwise time costs can be severe. trying to resolve poms again should be done once a day or by explicit manual trigger.

for better diagnostics, maybe a logging output could be done, to tell user to provide a pom for dependency.

> performance problem open/close project
> --------------------------------------
>
> Key: MNGECLIPSE-523
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-523
> Project: Maven Integration for Eclipse
> Issue Type: Improvement
> Components: Dependency Resolver
> Affects Versions: 0.9.1
> Reporter: manuel aldana
> Priority: Critical
> Attachments: logAfterCheckout.txt, logRebuild.txt
>
>
> when opening or closing a project inside workspace the maven auto builing ('Updating Maven Dependencies') takes very long to complete (around a minute). the same is when checking out or deleting a project
> for me this is a major issue, for i keep only open projects in workspace i am working on. i.e. i am checking-out/closing/opening very often. for this performance reasons i still have to use 0.0.12 version. with 0.0.12 in fact i had to make Project->Clean... manually, when workspace changed. never the less this went much quicker (around 15 seconds vs. 1 minute of auto refresh).
> eclipse install is very slim and there are only two checked out projects, so i guess it has something to do with dep-resolving refresh after project-set workspace change.

[jira] Commented: (MNGECLIPSE-552) Directory renaming while importing maven existing project into eclipse

2008-04-18T00:51:55Z

[ http://jira.codehaus.org/browse/MNGECLIPSE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131216#action_131216 ]

Thomas Diesler commented on MNGECLIPSE-552:
-------------------------------------------

I think I found a work around for this:

#1 before importing change the artifactId in pom.xml to the directory name (i.e. trunk)
#2 do the import
#3 restore pom.xml
#4 rename the project to the artifactId

> Directory renaming while importing maven existing project into eclipse
> ----------------------------------------------------------------------
>
> Key: MNGECLIPSE-552
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-552
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Wizards
> Affects Versions: 0.9.2
> Environment: Eclipse Europa 3.3.2, Jdk 1.6u5
> Reporter: Sergey Elin
> Fix For: 0.9.3
>
>
> When importing existing multimodule project via Maven Project wizard, root directory name was changed to artifactId ant it broke catalog structure.

[jira] Commented: (MNGECLIPSE-335) Add a Wizard Export to manually add artifacts to a remote repository

2008-04-17T22:12:55Z

[ http://jira.codehaus.org/browse/MNGECLIPSE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131208#action_131208 ]

Eugene Kuleshov commented on MNGECLIPSE-335:
--------------------------------------------

Somehow this patch slipped out of the horizon. Guillaume, would you be able to update it to the latest code? Let's not worry about icons now.

> Add a Wizard Export to manually add artifacts to a remote repository
> --------------------------------------------------------------------
>
> Key: MNGECLIPSE-335
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-335
> Project: Maven Integration for Eclipse
> Issue Type: New Feature
> Components: Wizards
> Affects Versions: 0.0.10
> Reporter: Guillaume Sauthier
> Attachments: network_local.png, patch.txt
>
>
> This issue is linked to MNGECLIPSE-51.

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

2008-04-17T22:10:55Z

[ 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 :)

[jira] Closed: (MNGECLIPSE-364) Source file attachment not working in Eclipse 3.3?

2008-04-17T22:04:55Z

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

Eugene Kuleshov closed MNGECLIPSE-364.
--------------------------------------

Resolution: Fixed
Fix Version/s: 0.9.0

Since 0.9 version it is possible to attach custom sources to jars in "Maven Dependencies" classpath container.

> Source file attachment not working in Eclipse 3.3?
> --------------------------------------------------
>
> Key: MNGECLIPSE-364
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-364
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.11
> Reporter: Dave Syer
> Fix For: 0.9.0
>
>
> Attach source archive broken in Eclipse 3.3? If I attach a zip file containing source code, and then select OK when the plugin asks me if I want to install the source code, it actually replaces my jar file with teh source attachment archive - so it immediately becomes unusable.

[jira] Closed: (MNGECLIPSE-429) Classpath resolution

2008-04-17T22:04:55Z

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

Eugene Kuleshov closed MNGECLIPSE-429.
--------------------------------------

Resolution: Cannot Reproduce

It doesn't seem like we have issue here. Dependency viewer (not yet available) should address concerns related to dependency origins.

> Classpath resolution
> --------------------
>
> Key: MNGECLIPSE-429
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-429
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Dependency Resolver
> Affects Versions: 0.0.12
> Reporter: Markus Wolf
>
> The resolved classpath does contain dependencies which are explicitly marked as excluded in the pom.xml.
> These should not be added to eclipse path, since this could lead to wrong dependencies being used for compilation/runtime.

[jira] Closed: (MNGECLIPSE-391) Show stack traces somewhere

2008-04-17T21:54:55Z

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

Eugene Kuleshov closed MNGECLIPSE-391.
--------------------------------------

Resolution: Fixed

Debug option in Maven launch configuration should enable printing exceptions. Please reopen if there is something else is missing.

> Show stack traces somewhere
> ---------------------------
>
> Key: MNGECLIPSE-391
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-391
> Project: Maven Integration for Eclipse
> Issue Type: Improvement
> Components: Maven Launcher
> Affects Versions: 0.0.12
> Reporter: Aaron Digulla
> Attachments: mngeclipse-391.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When Maven throws an exception, there is no way to see it in the current plugin.
> Please log exceptions to the error log and/or show them in the console when "Debug" is enabled.

[jira] Updated: (MNGECLIPSE-527) Archetype Filtering

2008-04-17T21:48:55Z

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

Eugene Kuleshov updated MNGECLIPSE-527:
---------------------------------------

Attachment: mylyn-context.zip

> Archetype Filtering
> --------------------
>
> Key: MNGECLIPSE-527
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-527
> Project: Maven Integration for Eclipse
> Issue Type: Improvement
> Components: Wizards
> Affects Versions: 0.9.1
> Environment: N/A
> Reporter: Rob Evans
> Assignee: Eugene Kuleshov
> Fix For: 0.9.3
>
> Attachments: mylyn-context.zip
>
>
> In out corporate rollout of Maven and m2eclipse, we'd like to be able to exclude archetypes in the new project wizard. In a nutshell, we only want our folks to use archetypes approved or provided by our internal software engineering overlords.

[jira] Closed: (MNGECLIPSE-527) Archetype Filtering

2008-04-17T21:46:55Z

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

Eugene Kuleshov closed MNGECLIPSE-527.
--------------------------------------

Assignee: Eugene Kuleshov
Resolution: Fixed

Implemented Archetype catalog management backend, new UI for editing catalogs and selecting them in new Maven project wizard, as well as new extension point for packaging catalogs with custom product/distribution. See wiki page for more details.

Note that because od limitation outlined in ARCHETYPE-161 remote catalog url should be pointing to a folder that contains archetype-catalog.xml. Because catalogs bundled within custom plugins also loaded using url scheme, "name" attribute can be only pointing to "archetype-catalog.xml" file and in order to have more then one catalog bundled within same plugin it is necessary to put them into separate folders.

> Archetype Filtering
> --------------------
>
> Key: MNGECLIPSE-527
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-527
> Project: Maven Integration for Eclipse
> Issue Type: Improvement
> Components: Wizards
> Affects Versions: 0.9.1
> Environment: N/A
> Reporter: Rob Evans
> Assignee: Eugene Kuleshov
> Fix For: 0.9.3
>
>
> In out corporate rollout of Maven and m2eclipse, we'd like to be able to exclude archetypes in the new project wizard. In a nutshell, we only want our folks to use archetypes approved or provided by our internal software engineering overlords.

[jira] Commented: (MNGECLIPSE-498) Transitive Dependencies Not included in Eclipse

2008-04-17T17:00:55Z

[ http://jira.codehaus.org/browse/MNGECLIPSE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131189#action_131189 ]

John Casey commented on MNGECLIPSE-498:
---------------------------------------

this issue should be fixed by now. I just committed an integration test verifying the fix, but the fix itself has been in maven for at least a couple of weeks now.

> Transitive Dependencies Not included in Eclipse
> -----------------------------------------------
>
> Key: MNGECLIPSE-498
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-498
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Components: Dependency Resolver
> Affects Versions: 0.9.0
> Environment: Mac OS X Leopard 10.5.2, Eclipse Europa 3.3.2
> Reporter: Jarrod Carlson
> Attachments: pom.xml
>
>
> Transitive dependencies are not being included in the Eclipse environment using the latest build of the plugin (0.9.0.20080310-1400-Sonatype).
> Project A depends on project B, which depends on project C. Project A has Java code referencing code in project C. Eclipse has compilation errors, because it cannot resolve class types found in project C.
> An example: We are building a web service application. Our project depends on org.springframework.ws :: spring-ws-core-tiger : 1.0.3, which in turn depends on org.springframework.ws :: spring-ws-core : 1.0.3. Our project references org.springframework.ws.server.endpoint.AbstractMarshallingPayloadEndpoint, but Eclipse is unable to resolve this class type, because spring-ws-core is not included in the Maven Dependencies.
> Adding spring-ws-core as a direct dependency of our project resolved the build error in Eclipse, but other dependencies are not listed.

[jira] Commented: (MNGECLIPSE-507) antrun broken with m2eclipse 0.9.0

2008-04-17T08:12:56Z

[ http://jira.codehaus.org/browse/MNGECLIPSE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131143#action_131143 ]

Eugene Kuleshov commented on MNGECLIPSE-507:
--------------------------------------------

Jit, we found that issue is actually deeper then John's workaround and it is related to quite complicated classloading stuff. We are still investigating proper solution.

> antrun broken with m2eclipse 0.9.0
> ----------------------------------
>
> Key: MNGECLIPSE-507
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-507
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Jit
> Attachments: MNGECLIPSE-parent.zip, MNGECLIPSE-test.zip
>
>
> Since upgrading to the 0.9.0 plugin the antrun task configured in the attached sample project fails to run.
> To recreate the issue follow these steps:
> 1. Add the MNGECLIPSE-parent and MNGECLIPSE-test projects to Eclipse.
> 2. Enable the Maven plugin for both projects.
> 3. Install the MNGECLIPSE-parent project via 'mvn install'.
> 4. From the Maven context menu select 'Update Source Folders' on the MNGECLIPSE-test project.
> 5. This produces the following error:
> ----------------
> [org.apache.maven:maven-project:jar:2.0.1:runtime, org.apache.maven:maven-plugin-api:jar:2.0.1:runtime, org.apache.maven:maven-profile:jar:2.0.1:runtime, junit:junit:jar:3.8.1:runtime, org.apache.maven:maven-artifact-manager:jar:2.0.1:runtime, org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime, ant:ant:jar:1.6.5:runtime, org.apache.maven:maven-artifact:jar:2.0.1:runtime, org.codehaus.plexus:plexus-utils:jar:1.1:runtime, org.apache.maven:maven-model:jar:2.0.1:runtime, ant:ant-launcher:jar:1.6.5:runtime, org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime, org.apache.maven:maven-repository-metadata:jar:2.0.1:runtime]
> for plugin: /plugins/org.apache.maven.plugins:maven-antrun-plugin:1.1@48/thread:Worker-5
> 28/03/08 12:22:41 GMT: [DEBUG] Looking up mojo org.apache.maven.plugins:maven-antrun-plugin:1.1:run in realm /plugins/org.apache.maven.plugins:maven-antrun-plugin:1.1@48/thread:Worker-5 - descRealmId=/plugins/org.apache.maven.plugins:maven-antrun-plugin:1.1@48/thread:Worker-5
> 28/03/08 12:22:41 GMT: [DEBUG] Looked up - org.apache.maven.plugin.antrun.AntRunMojo@1291e95 - ClassRealm[/plugins/org.apache.maven.plugins:maven-antrun-plugin:1.1@48/thread:Worker-5, parent: ClassRealm[plexus.core, parent: null]]
> 28/03/08 12:22:41 GMT: [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-antrun-plugin:1.1:run' with override configurator -->
> 28/03/08 12:22:41 GMT: [DEBUG] (f) artifacts = [org.apache.maven:maven-project:jar:2.0.1:runtime, org.apache.maven:maven-plugin-api:jar:2.0.1:runtime, org.apache.maven:maven-profile:jar:2.0.1:runtime, junit:junit:jar:3.8.1:runtime, org.apache.maven:maven-artifact-manager:jar:2.0.1:runtime, org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime, ant:ant:jar:1.6.5:runtime, org.apache.maven:maven-artifact:jar:2.0.1:runtime, org.codehaus.plexus:plexus-utils:jar:1.1:runtime, org.apache.maven:maven-model:jar:2.0.1:runtime, ant:ant-launcher:jar:1.6.5:runtime, org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime, org.apache.maven:maven-repository-metadata:jar:2.0.1:runtime]
> 28/03/08 12:22:41 GMT: [DEBUG] (f) project = MavenProject: org.maven.ide.eclipse.projects:MNGECLIPSE-test:0.0.1-SNAPSHOT @ C:\CPDS_CVS\MNGECLIPSE-test\pom.xml
> 28/03/08 12:22:41 GMT: [DEBUG] (f) tasks =
> 28/03/08 12:22:41 GMT: [DEBUG] -- end configuration --
> 28/03/08 12:22:41 GMT: antrun:run
> 28/03/08 12:22:41 GMT: [DEBUG] Setting context classloader for plugin to: /plugins/org.apache.maven.plugins:maven-antrun-plugin:1.1@48/thread:Worker-5 (instance is: ClassRealm[/plugins/org.apache.maven.plugins:maven-antrun-plugin:1.1@48/thread:Worker-5, parent: ClassRealm[plexus.core, parent: null]])
> 28/03/08 12:22:42 GMT: [INFO] Executing tasks
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=compile.classpath, user=false)
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=build.sysclasspath, user=false)
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=dir.gen.src, user=false)
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=dir.gen.src.dest, user=false)
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=database.type, user=false)
> 28/03/08 12:22:42 GMT: [DEBUG] getProperty(ns=null, name=dir.gen.src, user=false)
> 28/03/08 12:22:42 GMT: [FATAL ERROR] org.apache.maven.plugin.antrun.AntRunMojo#execute() caused a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date. Check the realms:
> 28/03/08 12:22:42 GMT: [FATAL ERROR] Plugin realm = /plugins/org.apache.maven.plugins:maven-antrun-plugin:1.1@48/thread:Worker-5
> urls[0] = file:/c:/.m2/org/apache/maven/plugins/maven-antrun-plugin/1.1/maven-antrun-plugin-1.1.jar
> urls[1] = file:/c:/.m2/junit/junit/3.8.1/junit-3.8.1.jar
> urls[2] = file:/c:/.m2/ant/ant/1.6.5/ant-1.6.5.jar
> urls[3] = file:/c:/.m2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> urls[4] = file:/c:/.m2/ant/ant-launcher/1.6.5/ant-launcher-1.6.5.jar
> 28/03/08 12:22:42 GMT: [FATAL ERROR] Container realm = plexus.core
> 28/03/08 12:22:42 GMT: ERROR mojo-execute : antrun:run : org/apache/log/format/Formatter
> 28/03/08 12:22:42 GMT: Build error for /MNGECLIPSE-test/pom.xml; java.lang.NoClassDefFoundError: org/apache/log/format/Formatter
> ----------------
> Using plugin version 0.0.12 everything works correctly (no errors), everything works correctly from the command line.

[jira] Closed: (MNGECLIPSE-556) localRepository settings misinterpreted for local settings.xml

2008-04-17T06:40:55Z

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

Igor Fedorenko closed MNGECLIPSE-556.
-------------------------------------

Resolution: Cannot Reproduce

I believe problems with eclipse:eclipse (a.k.a maven-eclipse-plugin) should be reported here http://jira.codehaus.org/browse/MECLIPSE. Closing this issues because m2eclipse reported to work as expected. Please reopen this issue with m2eclipse does not properly handle <localRepository>.

> localRepository settings misinterpreted for local settings.xml
> --------------------------------------------------------------
>
> Key: MNGECLIPSE-556
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-556
> Project: Maven Integration for Eclipse
> Issue Type: Bug
> Affects Versions: 0.9.2
> Environment: Windows XP, Maven 2.0.7, Eclipse 3.3.2
> settings.xml in %USERPROFILE%\.m2 directory
> Reporter: Hayo
>
> The local repository was set as follows
> <localRepository>${user.home}/.m2/repository</localRepository>
> which is documented as the default to do.
> When i run "mvn eclipse:eclipse" Maven2 produces entries in .classpath which all contain a superflouous .m2/repository. E.g.
> <classpathentry kind="var" path="M2_REPO/.m2/repository/javamail/activation/1.4.1/activation-1.4.1.jar"/>
> Of course, the project will not compile under Eclipse.
> In a second project i have additionally set this file as the global settings.xml in the Sonatype Maven Integration. In that case, when i run the maven scripts from inside Eclipse, the problem does not appear.

[jira] Issue Comment Edited: (MNGECLIPSE-507) antrun broken with m2eclipse 0.9.0

2008-04-17T04:45:55Z

[ http://jira.codehaus.org/browse/MNGECLIPSE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131114#action_131114 ]

jitesh edited comment on MNGECLIPSE-507 at 4/17/08 6:44 AM:
---------------------------------------------------------

Hi John,

Thanks for the pointer. Having added the dependency under the plugin section I can confirm that the 'Update Source Folders' now works correctly with the 0.9 version of the plugin!

I'm a little surprised that the old version of the plugin (0.0.12) and the Maven CLI work when the dependency is just listed at the project level. I guess they're a little more lenient. Would be interesting to find out whether the Maven spec allows project level dependencies to be available to plugin tasks.

Thanks

Jit

was (Author: jitesh):
Hi John,

Thanks the pointer. Having added the dependency under the plugin section I can confirm that the 'Update Source Folders' now works correctly with the 0.9 version of the plugin!

I'm a little surprised that the old version of the plugin (0.0.12) and the Maven CLI work when the dependency is just listed at the project level. I guess they're a little more lenient. Would be interesting to find out whether the Maven spec allows project level dependencies to be available to plugin tasks.

Thanks

Jit