[CAMEL-1608] Fix pom.xml files to support nexus based release process

• Type: Task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.6.0, 2.0-M1
• Fix Version/s: 2.0-M2
• Assignee: Hadrian Zbarcea
• Reporter: Hadrian Zbarcea
• Created: 13/May/09 03:03
• Updated: 21/Nov/09 11:58
• Resolved: 16/Jun/09 02:16

Description

When profiles are explicitly activated in maven using -P, the <activeByDefault> value specified in a profile activation configuration is not considered. This is the case with the maven-release-plugin configuration where the profiles to be activated are specified as <arguments>. As the enable-schemagen profile (and a couple others) where not specified, camel-schema.xsd was not generated and pretty much all tests using the xml dsl were failing. Many thanks to Dan Kulp from the Apache Maven team for helping with this.

However there is one more blocker I will have to take care before 1.6.1 can be released. During the release:prepare phase the poms are regenerated and the <?xml> decl, the apache license notice is lost and there are issues with white spaces. This seems related to the fact that the <project> element is not on one line as per the new maven release guide. Fixing this may take a day or two as we have so many poms but I'll do it as the highest prio. Once I'll get it to work and release 1.6.1, I'll tackle 2.0-M2. The good news is that once we have this fixed, the release process will be much simplified.