[TRINIDAD-871] Without this new project.xml, the maven-jdev-plugin requires project migration on each usage.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.5-plugins
• Fix Version/s: 1.2.6-plugins
• Assignee: Unassigned
• Reporter: Gary Kind
• Created: 17/Dec/07 17:37
• Updated: 27/Jan/10 08:45
• Resolved: 18/Dec/07 08:34

Description

JDev had a bug where 2 of the installed components version breadcrumbs changed on each new build of JDev. This made it impossible for the maven-jdev-plugin's project.xml file, used to create a .jpr (jdev project) file, to be used in JDev without migration to the "present" version. In a large workspace with multiple projects, this is very time-consuming. The major goal of the maven-jdev-plugin is to avoid this time-consuming migration. JDev has now fixed this problem and the attached patch file corrects the maven-jdev-plugin's project.xml file so that the migration does not occur. This patch is really a MUST in the next version of the maven-jdev-plugin