[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-23510:
-------------------------------------
As per https://github.com/fbricon/pde.source.lookup#installation, the canonical repo for the 0.0.4 bits is https://dl.bintray.com/fbricon/poc/pde.source.lookup/0.0.4.201612181944
> [devdoc] document sources in target platform zip & use of PDE Source Lookup feature
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23510
> URL: https://issues.jboss.org/browse/JBIDE-23510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, devdoc, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM2
>
>
> 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 build a targetplatform with all the sources - done in JBIDE-23481.
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use 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 sources
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23510:
-------------------------------
Fix Version/s: 4.5.1.AM2
(was: 4.5.x)
> [devdoc] document sources in target platform zip & use of PDE Source Lookup feature
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23510
> URL: https://issues.jboss.org/browse/JBIDE-23510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, devdoc, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM2
>
>
> 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 build a targetplatform with all the sources - done in JBIDE-23481.
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use 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 sources
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23510:
-------------------------------
Sprint: devex #127 February 2017, devex #128 February 2017, devex #137 September 2017 (was: devex #127 February 2017, devex #128 February 2017)
> [devdoc] document sources in target platform zip & use of PDE Source Lookup feature
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23510
> URL: https://issues.jboss.org/browse/JBIDE-23510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, devdoc, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM2
>
>
> 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 build a targetplatform with all the sources - done in JBIDE-23481.
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use 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 sources
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24772:
-------------------------------
Description:
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places.
Changes:
* *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272
* *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
* *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
* *DONE* refactoring as per JBDS-3894
* documentation as per JBIDE-23510
was:
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places.
Changes:
* *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272
* *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
* *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
* refactoring as per JBDS-3894
* documentation as per JBIDE-23510
> Refactoring: eliminate devstudio target platform; reuse jbosstools target platform
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-24772
> URL: https://issues.jboss.org/browse/JBIDE-24772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM2
>
>
> Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places.
> Changes:
> * *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272
> * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
> * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
> * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
> * *DONE* refactoring as per JBDS-3894
> * documentation as per JBIDE-23510
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24772:
-------------------------------
Description:
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places.
Changes:
* *MERGED* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272
* *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
* *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
* *DONE* refactoring as per JBDS-3894
* documentation as per JBIDE-23510
was:
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places.
Changes:
* *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272
* *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
* *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
* *DONE* refactoring as per JBDS-3894
* documentation as per JBIDE-23510
> Refactoring: eliminate devstudio target platform; reuse jbosstools target platform
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-24772
> URL: https://issues.jboss.org/browse/JBIDE-24772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM2
>
>
> Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places.
> Changes:
> * *MERGED* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272
> * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
> * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
> * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
> * *DONE* refactoring as per JBDS-3894
> * documentation as per JBIDE-23510
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
[ https://issues.jboss.org/browse/JBDS-3894?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3894:
----------------------------------
Doc updated: https://github.com/jbosstools/jbosstools-devdoc/commits/master
> Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio
> ---------------------------------------------------------------------
>
> Key: JBDS-3894
> URL: https://issues.jboss.org/browse/JBDS-3894
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: central-update, target-platform, updatesite
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.1.0.AM2
>
>
> In https://github.com/jbosstools/jbosstools-discovery/ we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio and jbds.
> Affected: publishing/staging/release scripts, discovery sites, jenkins jobs, etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)