Maven plug-in and Mylyn plug-in conflict in the way they work with parent objects (packages)

The m2eclipse does not provide any special integration for Mylyn. The "Maven Dependencies" container is contributed using standard JDT extension points and Mylyn is supposed to handle its content.

One thing that could be special for Maven projects is that they often use modules hierarchy and in that case the same resources could exist in more then one place in Eclipse workspace. We have added special filter to the Package Explorer to hide modules under the parent project, but I doubt it affects Mylyn. Though multiple locations for the same resource might affect it.

BTW, you may have to refresh your repository settings to get 0.9.7 version shown.

I don't really know how eclipse is structured inside and how artifacts are represented. I can only assume m2eclipse and Mylyn operate on same structures but not sure how so I can't answer why- I only know the end result.

I am not talking about specific support for Mylyn, I am talking about something m2eclipse does (the way it operates with internal project representation) conflicts with what Mylyn does. It may be because one of the plug-ins don't follow "recommended" way or may be an unresolvable architectural issue (or something inbetween). If you feel end result (see screenshot on Mylyn's issue) is OK feel free to close the report but I find both plug-ins very useful and would love to be able to use them both.

Specific project I'm working on is not modular, not sure if the Explorer integration is always loaded though. I also don't think the issue is with the explorer, it seems more likely that m2eclipse does something with the package representation inside the eclipse that causes Mylyn to drop it from the context. What- no clue.

On repository- now sure what you mean. When you create a new issue in Jira, it provides a list of versions to assign an issue to. I don't see 0.9.7 there- how do I refresh that?

Michael, after project is imported, it is just plain JDT project, so there isn't really anything m2eclipse operates with.

The only place I can think of is that m2eclipse adds some text decorations to the project names, but that decoration is also not any different from the decoration added by version control plugins, so pretty common practice supported by Eclipse platform.

Also, action "Maven / Update Project configuration" recreates project folders and action "Maven / Update dependencies" flush content of the "Maven Dependencies" container but that also should not affect Mylyn, because as far as I know it is not referencing those objects by instance but using keys generated by JDT and those key values should be the same.

PS: I do see 0.9.7 version on the web UI (marked as not released), if you are using Mylyn to submit issues, please consult its user guide for instructions how to refresh cashed information for your task repositories.

0.9.7- in released list now. I didn't scroll into unreleased section since a) I didn't know it was there (shows how much I know) and b) because I'm using "release" update site. Anywho, that question is resolved now.

One plain JDT project... If you don't have any listeners/timers/schedulers/update checks/whatever else done at runtime of the editor then the issue is likely with Mylyn although it does seem odd that it works half-way. If m2eclipse does not interact with the project structure at runtime I'd have expect Mylyn to either work or not.

Anyway, the bug is reported for Mylyn as well and it is possible that the issue is with something completely else so if you are confident it's not related feel free to close the issue. Im just trying to be helpful