[
https://issues.jboss.org/browse/JBIDE-13086?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13086:
----------------------------------------
Don't you need local.target to produce the copy of the TP site
that resides outside Jenkins from which unified.target site is published?
So far, we've been needing a local.target to produce the site, but we could make the
necessary change to get this site created after validation of multiple.target.
And if we're going to drop support for pointing at a locally
built TP as a profile in the parent pom, then we need to FIRST document the alternative
with examples of settings.xml files and usage.
I documented it there:
https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#As_Maven_...
And this needs to be SIMPLE. Currently, a lot of people use
-Plocal.site or equivalent when building, myself included. Switching to a settings.xml
file is nice in that it's a single file to maintain (instead of having to pass in
cmdline args) but we need to make sure it's easy to implement.
Cf documentation.
Clean target-platforms (local.target and jenkins.target no more
useful)
-----------------------------------------------------------------------
Key: JBIDE-13086
URL:
https://issues.jboss.org/browse/JBIDE-13086
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng, target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.CR2
local.target and jenkins.target are no more used in favor of Tycho 0.16 mirroring.
So we don't need to build them any more. They should be removed and the
target-platform site creation process should be reviewed to still provide local mirror
without using the local.target.
--
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