You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/07/06 14:11:35 UTC
[jira] [Assigned] (CAMEL-5221) Tighter integration of release
builds with camel extras
[ https://issues.apache.org/jira/browse/CAMEL-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-5221:
----------------------------------
Assignee: Henryk Konsek
Henryk and Christian is helping with releasing camel extra more frequently
> Tighter integration of release builds with camel extras
> -------------------------------------------------------
>
> Key: CAMEL-5221
> URL: https://issues.apache.org/jira/browse/CAMEL-5221
> Project: Camel
> Issue Type: Improvement
> Components: tooling
> Reporter: Caspar MacRae
> Assignee: Henryk Konsek
>
> I can understand the fragmentation due to licencing, but it'd be great to see tighter integration with the standard Apache build.
> Possibly this could be achieved with the Apache Camel build's release (deploy to central) using the maven-scm-plugin to checkout and build camel-extras which would in turn deploy it to central or Sonatype OSS? (Does the redirect apache-extras.org cover the groupId policy?)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira