[
https://issues.jboss.org/browse/JBIDE-22584?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22584:
------------------------------------
Would it be reasonable to suggest that if this file doesn't exist, we could throw a
more educational error message, or simply skip that provisioning step and continue the
build without the failure? WDYT, [~fbricon] ?
Or is this simply a case of "complicated build setup requires manual bootstrapping of
earlyaccess.properties file even though there's nothing in there that is needed for
JBT 4.4 or devstudio 10" ?
jbosstools-central build and jbosstools-discovery build both depend
on the existence of a *-earlyaccess.properties file
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-22584
URL:
https://issues.jboss.org/browse/JBIDE-22584
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, central, central-update
Affects Versions: 4.4.0.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.x
Normally, jbosstools-central is built before jbosstools-discovery.
However, running jbosstools-central build for the first time, ran into this:
{code}
22:43:51 [INFO] org.jboss.tools.community.central .................. FAILURE [ 0.556 s]
22:43:51 [INFO] org.jboss.tools.community.central.feature .......... SKIPPED
22:43:51 [INFO] central.maven.examples.site ........................ SKIPPED
22:43:52 [ERROR] Failed to execute goal
com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget
(get-earlyaccess-listing) on project org.jboss.tools.community.central: IO Error: Could
not get content -> [Help 1]
{code} --
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs...
Or, this could be a problem w/ bootstrapping values in ide-config.properties?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)