[jbosstools-issues] [JBoss JIRA] (JBIDE-11496) Customized Maven libraries not persisted correctly
Snjezana Peco (JIRA)
jira-events at lists.jboss.org
Fri Apr 6 17:32:47 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682383#comment-12682383 ]
Snjezana Peco commented on JBIDE-11496:
---------------------------------------
This issue is caused by a bug in m2e. It seems that the bug is introduced by a newer version of m2e.
M2e's EMF model (PomResourceImpl) and its WTP model (IDomModel) aren't synchronized.
The destination file is saved using the WTP's IDomModel which isn't valid if a model is changed using the EMF model.
I have fixed the issue by converting m2e POM model to pure Maven model and saving it using pure Maven.
BTW,
I don't see how this issue is related to JBIDE-10911. As to JBIDE-10911 you just need to add a new library provider.
> Customized Maven libraries not persisted correctly
> --------------------------------------------------
>
> Key: JBIDE-11496
> URL: https://issues.jboss.org/browse/JBIDE-11496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 3.3.0.Beta2
> Environment: Windows 7
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 3.3.0.Beta3
>
>
> As said on the jbosstools-dev ML :
> I've been looking at the Maven Library provider lately for JBIDE-10911 and there's something I don't quite understand :
> In https://github.com/jbosstools/jbosstools-svn-mirror/blob/trunk/maven/plugins/org.jboss.tools.maven.core/src/org/jboss/tools/maven/core/libprov/MavenLibraryProviderInstallOperation.java#L96 when libraryResource is saved, the generated file (<workspace_area>/org.jboss.maven.core/<library_name>/template.xml) contains the original contents of the template, not those from libraryModel (chosen by the user in the JPA wizard page).
> I can't figure out what's wrong in the code. Do you have any idea?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list