You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Roland Klein (JIRA)" <ji...@codehaus.org> on 2006/01/06 12:04:01 UTC
[jira] Created: (MNGECLIPSE-27) Problems editing pom.xml by hand
Problems editing pom.xml by hand
--------------------------------
Key: MNGECLIPSE-27
URL: http://jira.codehaus.org/browse/MNGECLIPSE-27
Project: Maven 2.x Plug-in for Eclipse
Type: Bug
Environment: WIN2K, Eclipse3.1, m2eclipse 0.0.3 (rev8 2006-01-03), maven-embedder-2.0.1-dep.jar
Reporter: Roland Klein
Assigned to: Eugene Kuleshov
If you edit pom.xml by hand, then several calls to Maven2Builder.build() take place. And in this method the call to Maven2Plugin.getDefault().resolveClasspathEntries() after the first time return an empty entries array.
- i inserted in Maven2Plugin:360 a call to resetMavenEmbedder(); This is not the preserving resources and maybe there is better way to tell MavenEmbedder to reset, because the call resetMavenEmbedder() results in instatiating a new MavenEmbedder ;-(
- now everytime a call to Maven2Builder.build() suceeds and the entries array is filled up correctly,
but in the eclipse package explorer the libs are shown directly under the project and not under the
ClasspathContainer and no description of the Container is shown. The build suceeds too and all
dependencies are resolved correctly. If i close the project and the second instance of eclipse and
then reopen both, everything works fine classpathEntries are shown under ClasspathContainer and so on. Any ideas?
--
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, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNGECLIPSE-27) Problems editing pom.xml by hand
Posted by "Roland Klein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-27?page=all ]
Roland Klein closed MNGECLIPSE-27:
----------------------------------
Resolution: Won't Fix
Hello Eugene,
i tested the latest revision (rev.14) with eclipse 3.1 and 3.2M4 in both enviroments all works fine.
But than i changed the Embedder to maven-embedder-2.0.1-dep.jar and then MavenEmbedder finds a duplicate projectId in my pom.xml.
To make it short, the distribution in svn works, so i close this issue.
Roland
> Problems editing pom.xml by hand
> --------------------------------
>
> Key: MNGECLIPSE-27
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-27
> Project: Maven 2.x Plug-in for Eclipse
> Type: Bug
> Versions: 0.0.3
> Environment: WIN2K, Eclipse3.1, m2eclipse 0.0.3 (rev8 2006-01-03), maven-embedder-2.0.1-dep.jar
> Reporter: Roland Klein
> Assignee: Eugene Kuleshov
> Fix For: 0.0.4
>
>
> If you edit pom.xml by hand, then several calls to Maven2Builder.build() take place. And in this method the call to Maven2Plugin.getDefault().resolveClasspathEntries() after the first time return an empty entries array.
> - i inserted in Maven2Plugin:360 a call to resetMavenEmbedder(); This is not the preserving resources and maybe there is better way to tell MavenEmbedder to reset, because the call resetMavenEmbedder() results in instatiating a new MavenEmbedder ;-(
> - now everytime a call to Maven2Builder.build() suceeds and the entries array is filled up correctly,
> but in the eclipse package explorer the libs are shown directly under the project and not under the
> ClasspathContainer and no description of the Container is shown. The build suceeds too and all
> dependencies are resolved correctly. If i close the project and the second instance of eclipse and
> then reopen both, everything works fine classpathEntries are shown under ClasspathContainer and so on. Any ideas?
--
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, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNGECLIPSE-27) Problems editing pom.xml by hand
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-27?page=all ]
Eugene Kuleshov updated MNGECLIPSE-27:
--------------------------------------
Version: 0.0.4
Fix Version: 0.0.5
> Problems editing pom.xml by hand
> --------------------------------
>
> Key: MNGECLIPSE-27
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-27
> Project: Maven 2.x Plug-in for Eclipse
> Type: Bug
> Versions: 0.0.4
> Environment: WIN2K, Eclipse3.1, m2eclipse 0.0.3 (rev8 2006-01-03), maven-embedder-2.0.1-dep.jar
> Reporter: Roland Klein
> Assignee: Eugene Kuleshov
> Fix For: 0.0.5
>
>
> If you edit pom.xml by hand, then several calls to Maven2Builder.build() take place. And in this method the call to Maven2Plugin.getDefault().resolveClasspathEntries() after the first time return an empty entries array.
> - i inserted in Maven2Plugin:360 a call to resetMavenEmbedder(); This is not the preserving resources and maybe there is better way to tell MavenEmbedder to reset, because the call resetMavenEmbedder() results in instatiating a new MavenEmbedder ;-(
> - now everytime a call to Maven2Builder.build() suceeds and the entries array is filled up correctly,
> but in the eclipse package explorer the libs are shown directly under the project and not under the
> ClasspathContainer and no description of the Container is shown. The build suceeds too and all
> dependencies are resolved correctly. If i close the project and the second instance of eclipse and
> then reopen both, everything works fine classpathEntries are shown under ClasspathContainer and so on. Any ideas?
--
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, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNGECLIPSE-27) Problems editing pom.xml by hand
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-27?page=comments#action_55094 ]
Eugene Kuleshov commented on MNGECLIPSE-27:
-------------------------------------------
Can you please clarify if Maven2Builder.build() is being called on every save or there are some other events that kick it?
> Problems editing pom.xml by hand
> --------------------------------
>
> Key: MNGECLIPSE-27
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-27
> Project: Maven 2.x Plug-in for Eclipse
> Type: Bug
> Environment: WIN2K, Eclipse3.1, m2eclipse 0.0.3 (rev8 2006-01-03), maven-embedder-2.0.1-dep.jar
> Reporter: Roland Klein
> Assignee: Eugene Kuleshov
>
>
> If you edit pom.xml by hand, then several calls to Maven2Builder.build() take place. And in this method the call to Maven2Plugin.getDefault().resolveClasspathEntries() after the first time return an empty entries array.
> - i inserted in Maven2Plugin:360 a call to resetMavenEmbedder(); This is not the preserving resources and maybe there is better way to tell MavenEmbedder to reset, because the call resetMavenEmbedder() results in instatiating a new MavenEmbedder ;-(
> - now everytime a call to Maven2Builder.build() suceeds and the entries array is filled up correctly,
> but in the eclipse package explorer the libs are shown directly under the project and not under the
> ClasspathContainer and no description of the Container is shown. The build suceeds too and all
> dependencies are resolved correctly. If i close the project and the second instance of eclipse and
> then reopen both, everything works fine classpathEntries are shown under ClasspathContainer and so on. Any ideas?
--
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, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org