[
https://issues.jboss.org/browse/JBDS-1435?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-1435:
-------------------------------------
It is enough to remove jbds-target-platform builder, hudson project related to it and bits
from download site.
requirements/jbds-target-platform is referenced to target platform built by
https://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/devstudio-4.0...
My question again, why don't you test before commit changes?
Two different target plaforms for JBDS
--------------------------------------
Key: JBDS-1435
URL:
https://issues.jboss.org/browse/JBDS-1435
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 4.0.0.CR1
Attachments: JBDS-1435.patch, Screenshot.png
Build 1:
http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/devstu...
uses this target platform:
/home/hudson/static_build_env/jbds/jbds-target-platform/jbds400-e361-wtp322.target/ (this
is generated by
http://hudson.qa.jboss.com/hudson/job/devstudio-4.0_stable_branch.target-...)
Build 2:
http://hudson.qa.jboss.com/hudson/job/devstudio-4.0.0.Beta2.nightly/
uses this target platform:
/qa/services/http/binaries/RHDS/requirements/helios/JBDS-4.0.0-target-p2repo (created
once by Denis by hand)
Must determine how these are different and get them in synch so that
devstudio-4.0_stable_branch.updatesite build is once again green.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira