[
https://issues.jboss.org/browse/JBIDE-10950?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10950:
------------------------------------
OK, I've added the new requirement here:
http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.2.1.F...
Use it in place of CR1 and CR2 in these tests / config files:
{code}
./tests/org.jboss.tools.seam221CR1.core.test/pom.xml
./tests/org.jboss.tools.seam221CR1.core.test/requirements.properties
./tests/org.jboss.tools.seam221CR1.ui.test/pom.xml
./tests/org.jboss.tools.seam221CR1.ui.test/requirements.properties
./tests/org.jboss.tools.seam221CR2.core.test/pom.xml
./tests/org.jboss.tools.seam221CR2.core.test/requirements.properties
./tests/org.jboss.tools.seam221CR2.ui.test/pom.xml
./tests/org.jboss.tools.seam221CR2.ui.test/requirements.properties
{code}
use seam 2.2.1.Final instead of 2.2.1.CR1 and 2.2.1.CR2 in
requirements?
------------------------------------------------------------------------
Key: JBIDE-10950
URL:
https://issues.jboss.org/browse/JBIDE-10950
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
There's a newer version of the Seam runtime available for use w/ building/testing:
http://sourceforge.net/projects/jboss/files/JBoss%20Seam/2.2.1.Final/
Yes, we're still using
http://softlayer.dl.sourceforge.net/project/jboss/JBoss%20Seam/2.2.1.CR1/
as noted in this build:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
Should we just be using the .Final, or is there some reason we're stuck using the two
CR1 and CR2 builds?
Note: the requirements bootstrap job runs against the requirement builders in this
folder:
https://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/
https://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.2.1....
https://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.2.1....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira