[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23481:
-------------------------------
Sprint: devex #123 November 2016
> 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/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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23481:
-------------------------------
Description:
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.
was:
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
OR...
* build a targetplatform without the sources
* transform the .target file so that each IU ends with .source
* verify that this second .target, when resolved, 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.
> 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/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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23481:
----------------------------------
Assignee: Nick Boldt
> 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), we need to:
> [1] https://github.com/fbricon/pde.source.lookup/
> * 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
> OR...
> * build a targetplatform without the sources
> * transform the .target file so that each IU ends with .source
> * verify that this second .target, when resolved, 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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23481:
-------------------------------
Description:
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
OR...
* build a targetplatform without the sources
* transform the .target file so that each IU ends with .source
* verify that this second .target, when resolved, 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.
was:
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), we need to:
[1] https://github.com/fbricon/pde.source.lookup/
* 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
OR...
* build a targetplatform without the sources
* transform the .target file so that each IU ends with .source
* verify that this second .target, when resolved, 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.
> 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/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
> OR...
> * build a targetplatform without the sources
> * transform the .target file so that each IU ends with .source
> * verify that this second .target, when resolved, 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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23481:
----------------------------------
Summary: 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
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), we need to:
[1] https://github.com/fbricon/pde.source.lookup/
* 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
OR...
* build a targetplatform without the sources
* transform the .target file so that each IU ends with .source
* verify that this second .target, when resolved, 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)
9 years, 5 months
[JBoss JIRA] (JBIDE-23475) split ide-config.properties into multiple files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23475?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23475:
------------------------------------
After lengthy discussion w/ Fred on this, we decided to maintain the single file, ide-config.properties, so as to not break downstream API or necessitate more downloads of more files (a folder or zip).
Instead, I'll create a pom.xml which calls python (or calls a custom mojo) which can assemble ide-config-*.fragment files into a complete ide-config.properties file.
That way the edits can be less destructive / easier to generate & audit, and the stuff that doesn't change (eg., properties for jbt 4.3.x / ds 9.x) need not be changed at all.
> split ide-config.properties into multiple files
> -------------------------------------------------
>
> Key: JBIDE-23475
> URL: https://issues.jboss.org/browse/JBIDE-23475
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, central, central-update
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.Final
>
>
> I'd like to split the contents of the current ide-config.properties file into multiple files so the content is easier to maintain via code generation.
> So, rather than 1 big file [1] we could split this into 5 files:
> * ide-config_4.4.snapshots.properties - contains the properties needed for jbosstools and devstudio CI builds (currently 4.4.2.Final and 10.2.0.GA)
> * ide-config_4.4.staging.properties - contains the properties needed for the latest jbosstools and devstudio staging build (currently 4.4.2.AM3 and 10.2.0.AM3)
> * ide-config_4.4.development.properties - contains the properties needed for the latest jbosstools and devstudio development build (currently 4.4.2.AM2 and 10.1.0.GA)
> * ide-config_4.4.stable.properties - contains the properties needed for the latest jbosstools and devstudio stable build (currently 4.4.1.Final and 10.1.0.GA)
> * ide-config.properties - contains all the other properties for 4.3.x and earlier releases
> [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j...
> By splitting this into smaller files, the contents that need to be changed every 3 weeks when we stage or release a build could be generated destructively, rather than having to worry about making changes w/ sed and not accidentally pushing in an invalid URL or value.
> From the central side of things, we would just want to treat all ide-config*.properties files as if they were pieces of a single file, and load them all into the same hash of properties we currently have from the single file.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23475) split ide-config.properties into multiple files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23475?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23475:
-------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.4.x)
> split ide-config.properties into multiple files
> -------------------------------------------------
>
> Key: JBIDE-23475
> URL: https://issues.jboss.org/browse/JBIDE-23475
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, central, central-update
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.Final
>
>
> I'd like to split the contents of the current ide-config.properties file into multiple files so the content is easier to maintain via code generation.
> So, rather than 1 big file [1] we could split this into 5 files:
> * ide-config_4.4.snapshots.properties - contains the properties needed for jbosstools and devstudio CI builds (currently 4.4.2.Final and 10.2.0.GA)
> * ide-config_4.4.staging.properties - contains the properties needed for the latest jbosstools and devstudio staging build (currently 4.4.2.AM3 and 10.2.0.AM3)
> * ide-config_4.4.development.properties - contains the properties needed for the latest jbosstools and devstudio development build (currently 4.4.2.AM2 and 10.1.0.GA)
> * ide-config_4.4.stable.properties - contains the properties needed for the latest jbosstools and devstudio stable build (currently 4.4.1.Final and 10.1.0.GA)
> * ide-config.properties - contains all the other properties for 4.3.x and earlier releases
> [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j...
> By splitting this into smaller files, the contents that need to be changed every 3 weeks when we stage or release a build could be generated destructively, rather than having to worry about making changes w/ sed and not accidentally pushing in an invalid URL or value.
> From the central side of things, we would just want to treat all ide-config*.properties files as if they were pieces of a single file, and load them all into the same hash of properties we currently have from the single file.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months