| Summary: | Adding a new maven module corrupts the parent POM | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Sahoo <sanjeeb.sahoo> | ||||
| Component: | m2e | Assignee: | Milos Kleint <mkleint> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | mkleint, pascal | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Sahoo
Created attachment 187384 [details]
Test case.
the workaround is surprisingly to keep the parent-pom editor opened when creating the module. I've rewritten the entire handling of <modules> section in the pom editor to use the DOM tree operations (based on SSE XML stuff) rather than the EMF model from maven.edit. It seemed to fix the issue. the disturbing part is that I was not able to figure out what actually removed the file content. My guess is that's some sort of model synchronization issues.. . |