You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2018/05/24 15:23:00 UTC
[jira] [Commented] (ARIES-619) Fix SPI-FLY and SUBSYSTEM tio use
release by bundle scheme
[ https://issues.apache.org/jira/browse/ARIES-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489199#comment-16489199 ]
David Bosschaert commented on ARIES-619:
----------------------------------------
This is a very old issue and I'm not sure it's still relevant. [~zoe] [~hughesj] do you think we still need this, or can the issue be closed?
> Fix SPI-FLY and SUBSYSTEM tio use release by bundle scheme
> ----------------------------------------------------------
>
> Key: ARIES-619
> URL: https://issues.apache.org/jira/browse/ARIES-619
> Project: Aries
> Issue Type: Bug
> Reporter: zoe slattery
> Assignee: Jeremy Hughes
> Priority: Major
>
> In summary:
> Split parent and reactor poms (Reactor just contains a list of modules, no SCM element)
> Add packageinfo files for package export versions
> Make each bundle pom depend on the 0.4 released parent (if possible)
> Switch depenedencies to point at released versions (where possible)
> Add an SCM element to each modules pom.
> Fix build warnings caused by default settings for maven-bundle-plugin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)