[
https://issues.jboss.org/browse/JBIDE-15772?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15772:
------------------------------------
Looks like it was a refactoring of an older approach to generating the update site. In the
past I had Ant script which used associate.properties, but thanks to Mickael's new
mojo, we could move to using config within the pom itself.
https://github.com/jbosstools/jbosstools-integration-tests/commit/4cb230b...
If you're worried about it being safe to remove... apply the PR, then build locally,
and try to install the test features from the generated update site. If Eclipse complains
about missing dependencies, you need to have something in there to resolve the upstream
stuff from JBT. If it doesn't then you don't.
Simple?
Remove referenced juno sites in integration-tests site pom
----------------------------------------------------------
Key: JBIDE-15772
URL:
https://issues.jboss.org/browse/JBIDE-15772
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: qa
Affects Versions: 4.1.1.Beta1
Reporter: Martin Malina
Assignee: Martin Malina
Fix For: 4.1.1.Final
https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si...
{code}
<
associateSite>http://download.jboss.org/jbosstools/updates/juno/soa-to...
<
associateSite>http://download.jboss.org/jbosstools/updates/juno/</a...
<
associateSite>http://download.jboss.org/jbosstools/updates/stable/juno...
<
associateSite>http://download.jboss.org/jbosstools/updates/development...
{code}
These are added when you add the integration-tests update site to Eclipse to resolve
dependencies.
We most probably don't need them. Or if we do, we should update to kepler links.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira