[jbosstools-issues] [JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13319976#comment-13319976 ] 

Mickael Istria commented on JBIDE-23481:
----------------------------------------

Why having split repositories for data and src? Why not simply include sources in the aggregated TP site directly? We have the options to do it, and it has been requested multiple times already. Then it can be used by target platform/regular PDE lookup and by this additional lookup.


> build target platform sources site (for use with 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
>
> 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/target_platforms/target_platforms_for_consumers.adoc#build-target-platform-bootstrapped-from-zip
> * 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)