Updated 3.3.X pom.xml and other build files as needed for updated jboss maven repo
----------------------------------------------------------------------------------
Key: RFPL-532
URL: https://jira.jboss.org/jira/browse/RFPL-532
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build
Reporter: Jay Balunas
Assignee: Andrey Markhel
Priority: Critical
Fix For: 3.3.4.BETA1, ENT_3.3.1.SP2
Review and update both enterprise/3.3.X and community/3.3.X branch builds as needed to support new jboss maven repos. Part of this task is reviewing the related wiki pages by the jboss.org team on the changes. http://community.jboss.org/wiki/MavenRepository-FAQ is a good starting point.
Even if the builds are working we need to make sure we are not relying on older repo settings.
Not this may also effect how we reference 3rd party repos - please review the wiki pages for more.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Updated 4.0.X pom.xml and other build files as needed for updated jboss maven repo
----------------------------------------------------------------------------------
Key: RFPL-533
URL: https://jira.jboss.org/jira/browse/RFPL-533
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build
Reporter: Jay Balunas
Assignee: Konstantin Mishin
Priority: Critical
Fix For: 4.0.0.ALPHA2
Review and update the 4.0 module's and builds as needed to support new jboss maven repos. Part of this task is reviewing the related wiki pages by the jboss.org team on the changes. http://community.jboss.org/wiki/MavenRepository-FAQ is a good starting point.
Even if the builds are working we need to make sure we are not relying on older repo settings.
Not this may also effect how we reference 3rd party repos - please review the wiki pages for more.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
configure and run all automated tests to be run in Winland
----------------------------------------------------------
Key: RFPL-577
URL: https://jira.jboss.org/jira/browse/RFPL-577
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Prabhat Jha
Assignee: Lukas Fryc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Update hudson builds for changes to JBoss mvn repo
--------------------------------------------------
Key: RFPL-534
URL: https://jira.jboss.org/jira/browse/RFPL-534
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build
Reporter: Jay Balunas
Assignee: Jay Balunas
Priority: Critical
Fix For: 3.3.4.BETA1, ENT_3.3.1.SP2, 4.0.0.ALPHA2
Nick or I will need to update the hudson builds for the changes in the JBoss mvn repo. This will include updating the snapshot repo settings, and any repo build setting on the command line.
http://community.jboss.org/wiki/MavenRepository-FAQ is a good starting point for what needs to be done
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira