You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2010/02/16 18:15:27 UTC
[jira] Created: (ARIES-173) Activities for creating 0.1 release
Activities for creating 0.1 release
-----------------------------------
Key: ARIES-173
URL: https://issues.apache.org/jira/browse/ARIES-173
Project: Aries
Issue Type: Task
Reporter: Jeremy Hughes
This is an umbrella task for the activities needed to get our source tree / poms / distribution etc in shape for the 0.1 release.
* rename 1.0 release in JIRA to 0.1
* change 1.0.0-incubating-SNAPSHOT 0.1-incubating-SNAPSHOT
* use maven-assembly plugin to create a zip and tar.gz of the release artifacts
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ARIES-173) Activities for creating 0.1 release
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated ARIES-173:
-------------------------------
Attachment: ARIES-173.diff
This is a start on cleaning up the poms so aries projects are releasable. I'm hampered by the blueprint and application projects as in svn having failing tests in my environment.
Despite the discussion on the dev list about the possibility of releasing aries as one project, the poms are already set up so that is impractical.
This patch adds scm info for poms that are missing it and cleans up quite a few version problems and various other things.
Some of the application bundles stop compiling when the order of the dependencies is changed to alphabetical. I think we need to figure out appropriate exclusions so the dependencies do not need to be in a particular order. (the problem appears to be that osgi 3 artfacts get on the maven classpath before osgi 4.2 artifacts).
more later....
> Activities for creating 0.1 release
> -----------------------------------
>
> Key: ARIES-173
> URL: https://issues.apache.org/jira/browse/ARIES-173
> Project: Aries
> Issue Type: Task
> Reporter: Jeremy Hughes
> Assignee: Jeremy Hughes
> Attachments: ARIES-173.diff
>
>
> This is an umbrella task for the activities needed to get our source tree / poms / distribution etc in shape for the 0.1 release.
> * rename 1.0 release in JIRA to 0.1
> * change 1.0.0-incubating-SNAPSHOT 0.1-incubating-SNAPSHOT
> * use maven-assembly plugin to create a zip and tar.gz of the release artifacts
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ARIES-173) Activities for creating 0.1 release
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes reassigned ARIES-173:
-----------------------------------
Assignee: Jeremy Hughes
> Activities for creating 0.1 release
> -----------------------------------
>
> Key: ARIES-173
> URL: https://issues.apache.org/jira/browse/ARIES-173
> Project: Aries
> Issue Type: Task
> Reporter: Jeremy Hughes
> Assignee: Jeremy Hughes
>
> This is an umbrella task for the activities needed to get our source tree / poms / distribution etc in shape for the 0.1 release.
> * rename 1.0 release in JIRA to 0.1
> * change 1.0.0-incubating-SNAPSHOT 0.1-incubating-SNAPSHOT
> * use maven-assembly plugin to create a zip and tar.gz of the release artifacts
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ARIES-173) Activities for creating 0.1 release
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834326#action_12834326 ]
Guillaume Nodet commented on ARIES-173:
---------------------------------------
Fwiw, renaming the maven version from 1.0.0-incubating-SNAPSHOT to 0.1-incubating-SNAPSHOT is not mandatory as one can choose the version for the release and the version for the next snapshot during the release process.
> Activities for creating 0.1 release
> -----------------------------------
>
> Key: ARIES-173
> URL: https://issues.apache.org/jira/browse/ARIES-173
> Project: Aries
> Issue Type: Task
> Reporter: Jeremy Hughes
> Assignee: Jeremy Hughes
>
> This is an umbrella task for the activities needed to get our source tree / poms / distribution etc in shape for the 0.1 release.
> * rename 1.0 release in JIRA to 0.1
> * change 1.0.0-incubating-SNAPSHOT 0.1-incubating-SNAPSHOT
> * use maven-assembly plugin to create a zip and tar.gz of the release artifacts
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.