[
https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-23481:
----------------------------------------
Note that adding source to TP site by default would also benefit to regular TP usage.
{quote}The target file in eclipse suffers from a lot of drawbacks. Depending on your
country, it can be very slow to resolve (up to 1 hour for normal people, up to 2 or 3
hours for me in China). There was no real ability to 'retry' or
'continue', as I could when building TP locally. And, when creating a new
workspace, I found it to be completely impossible to find where the TP data was cached in
the old workspace to quickly have the new workspace make use of it. {quote}
Are there bugs et
eclipse.org on this issue? I have some ideas of how to improve that
state, without too much hard work and directly into PDE. Namely:
1. Make all TP fetch content in the same directory/bundle_pool to avoid unnecessary
re-fetch if some TPs share content. A TP resolution happens to be a subset of this
bundle-pool.
2. Make the TP resolution able to also consume the current installation bundle_pool so it
would reuse local artifacts if you have them installed instead of fetching them
3. Make Target-Platform resolution able to resolve sources directly against current
installation in case the TP doesn't contain them
4. Maybe even make the default bundle pool in a user-specific directory rather than
workspace, so it can be shared between instances. BTW, it's what Oomph is using.
If you're interested, please open bugs for each of this proposal, and consider
contributing such changes to PDE. PDE welcome now welcome changes.
[~rob.stryker] For your workflow, all you want is a TP site to contain sources by default,
and to download the zip to create your TP locally.
Fixing the 4 issues mentionted above would be a major improvement for PDE, and would
prevent people from having to implement new plugins that basically try to re-implement the
TP paradigm in different ways, just to troubleshoot some issue.
build target platform sources site (for use with TP and PDE Source
Lookup)
--------------------------------------------------------------------------
Key: JBIDE-23481
URL:
https://issues.jboss.org/browse/JBIDE-23481
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, target-platform
Affects Versions: 4.4.2.AM3
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.x
So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles
on demand (instead of having to build a target platform locally w/ all the sources [2]),
we need to:
[1]
https://github.com/fbricon/pde.source.lookup/
[2]
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
* build a targetplatform with all the sources
* split that repo into two pieces: all the .source files, and everything else
* regen the metadata (featureandbundlepublisher) in each new repo so that all the
features/plugins are uncategorized
OR...
* build a targetplatform without the sources
* transform the .target file so that each IU ends with .source
* build the target platform repo from the new .target file
* verify that sources repo includes the sources of nested features, and those
features' plugins' sources too
----
Then once we have the targetplatform.source repo, publish that and verify it works with
the PDE Source Lookup plugin:
1. install the PDE source lookup plugin
2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source
site
3. for something you want sources, use the plugin and see if it can resolve soources
----
Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio
composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central +
central tp) as a 5th child site.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)