Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343166 - bad interaction between m2e and pde
Summary: bad interaction between m2e and pde
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-18 11:28 EDT by Igor Fedorenko CLA
Modified: 2021-04-19 13:25 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Fedorenko CLA 2011-04-18 11:28:29 EDT 
Just ran into rather bad collision between m2e (or m2e-tycho) and pde while working on m2e code... 

After changing m2e parent pom.xml to use new version of Tycho (0.11.1 up from 0.11.0), most of m2e projects got "Project configuration is not up-to-date with pom.xml. Run project configuration update" error marker as expected.

Running maven project configuration update on some of the project, however, fails with a pop-up error dialog that says "jars/some-nested-jar.jar [in project-name] is not on project's build path". 

After this, project is completely stripped off java build path configuration.

Forcing dependency update on the project appears to make the problem go away.
Comment 1 Matthew Piggott CLA 2011-04-18 13:51:58 EDT 
I believe I have seen this as well, if I recall correctly using Update Configuration a second time works.
Comment 2 Igor Fedorenko CLA 2011-04-28 11:28:52 EDT 
m2e/tycho integration is out of scope for m2e/indigo work
Comment 3 Denis Roy CLA 2021-04-19 13:25:30 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/