You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2009/06/16 04:18:38 UTC

[jira] Resolved: (CAMEL-1608) Fix pom.xml files to support nexus based release process

     [ https://issues.apache.org/activemq/browse/CAMEL-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea resolved CAMEL-1608.
------------------------------------

    Resolution: Fixed

> Fix pom.xml files to support nexus based release process
> --------------------------------------------------------
>
>                 Key: CAMEL-1608
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1608
>             Project: Apache Camel
>          Issue Type: Task
>    Affects Versions: 1.6.0, 2.0-M1
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>            Priority: Blocker
>             Fix For: 2.0-M2
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.