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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-23481:
-------------------------------------

I've used Fred's lookup plugin once in the past, when I was evaluating / testing for him whether it worked at all. I haven't used it in a long time since, unfortunately.   My impressions at the time are hard to recall exactly, but I'll try. 

In general, I liked that it would fetch sources if you didn't have them, but I always already had them, for a few reasons. The reason is I don't use a .target file directly. 

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. 

What's worse, I often needed different TPs. I often need the JBT one, or, an older maintenance one different than master, or the JBTIS TP, etc. Trying to switch workspaces between these environments could sap 2 or 3 hours of my day *on a good day*, or make me 100% useless on a bad one. 

Basically, I evaluated Fred's plugin as it fit into my current workflow, and Fred's plugin, while nice, didn't fit into my workflow. 

However, it seems there are new workflows that could exist that would be very easy and for which Fred's plugin could be very handy. For example, a dev could download the TP zip file (instead of building locally with sources flag), and then install the sources plugin. 

Unfortunately, I'd need to evaluate this workflow, as I haven't evaluated it in the past. And since my current workflow of building TP on my own with sources works so well, I'm not really sure it's worth my effort to completely change my format. 

However, since a new TP is being released as we speak, I may feel generous enough to test a new workflow with it and get back to you with more details. 


> 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
>             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/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)