[richfaces-planning-issues] [JBoss JIRA] Commented: (RFPL-694) Fire up all automated tag based builds in Hudson

[Pavol Pitonak (JIRA)]

    [ https://jira.jboss.org/browse/RFPL-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12539400#action_12539400 ] 

Pavol Pitonak commented on RFPL-694:
------------------------------------

All release jobs should be run with "mvn clean verify". Additional profiles should be activated only for docs. Clover plugin is IMHO unnecessary because it is switched on in trunk jobs.

All jobs should use Hudson's local Maven repo for downloaded dependencies, i.e. in local repo will be only artifacts from staging repo.

Kicker has to remove all bits from local repo which have version ${VERSION}.

We need to find a way how to define staging repo:
  * ~/.m2/settings.xml in profile doesn't work
  * richfaces-parent - works for most of jobs, not for all


> Fire up all automated tag based builds in Hudson
> ------------------------------------------------
>
>                 Key: RFPL-694
>                 URL: https://jira.jboss.org/browse/RFPL-694
>             Project: RichFaces Planning
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.0.Milestone1
>            Reporter: Prabhat Jha
>            Assignee: Pavol Pitonak
>             Fix For: 4.0.0.Milestone1
>
>
> As per 4.x release process, pls make sure that builds are made out of M1 tag: 4.0.0.20100713-M1. These builds should not download bits from staging repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira