You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/05/30 11:57:01 UTC

[jira] [Commented] (SLING-3620) POM preparations for release

    [ https://issues.apache.org/jira/browse/SLING-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013475#comment-14013475 ] 

Robert Munteanu commented on SLING-3620:
----------------------------------------

* http://svn.apache.org/viewvc?view=revision&revision=1598530 use the ASF parent pom
* http://svn.apache.org/viewvc?view=revision&revision=1598531 set SCM information in all poms

> POM preparations for release
> ----------------------------
>
>                 Key: SLING-3620
>                 URL: https://issues.apache.org/jira/browse/SLING-3620
>             Project: Sling
>          Issue Type: Task
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Critical
>             Fix For: Sling Eclipse IDE 1.0.0
>
>
> The POMs we use are working for regular building, but they must be tweaked a bit before releasing. Some ( probably non-exhaustive ) notes
> * scm settings for all projects
> * ensure that gpg signing is performed when releasing
> * ensure that p2 signing is performed when releasing
> It seems that we can use the ASF parent pom , unlike the Sling parent pom.



--
This message was sent by Atlassian JIRA
(v6.2#6252)