[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4175 at 11/22/16 2:15 PM:
------------------------------------------------------------
I've installed everything from Central (except JRebel) and I believe only these are still a problem:
||Item||Result||Description or Errors||
|Atlassian_Connector|(x)|JBDS-4191|No new builds in upstream so this is probably not fixable
|Spring_IDE|(x)|JBDS-4190|Fixed in master branch for Spring IDE 3.8.3.CI (no idea when 3.8.3.RELEASE is due)
|Teiid Designer|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|JRebel|(?)||
Other JBTIS/JBDSIS connectors could not be found to install them. Possible problem with the IS site?
was (Author: nickboldt):
I've installed everything from Central (except JRebel) and I believe only these are still a problem:
||Item||Result||Description or Errors||
|Atlassian_Connector|(x)|JBDS-4191|
|Spring_IDE|(x)|JBDS-4190|
|Teiid Designer|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|JRebel|(?)||
Other JBTIS/JBDSIS connectors could not be found to install them. Possible problem with the IS site?
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.x
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4175 at 11/22/16 2:14 PM:
------------------------------------------------------------
I've installed everything from Central (except JRebel) and I believe only these are still a problem:
||Item||Result||Description or Errors||
|Atlassian_Connector|(x)|JBDS-4191|
|Spring_IDE|(x)|JBDS-4190|
|Teiid Designer|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|JRebel|(?)||
Other JBTIS/JBDSIS connectors could not be found to install them. Possible problem with the IS site?
was (Author: nickboldt):
I've installed everything from Central (except JRebel) and I believe only these are still a problem:
||Item||Result||Description or Errors||
|Atlassian_Connector|(x)|JBDS-4191|
|Spring_IDE|(x)|JBDS-4190|
|Teiid Designer|(x)|JBDS-4189|
|JRebel|(?)||
Other JBTIS/JBDSIS connectors could not be found to install them. Possible problem with the IS site?
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.x
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4189) problem installing teiid designer: depends on slf4j 1.7.10 (newer version) and javax.servlet 3.1.0 BUNDLE (not package)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4189?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4189:
-----------------------------
Parent: (was: JBDS-4175)
Issue Type: Enhancement (was: Sub-task)
> problem installing teiid designer: depends on slf4j 1.7.10 (newer version) and javax.servlet 3.1.0 BUNDLE (not package)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4189
> URL: https://issues.jboss.org/browse/JBDS-4189
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> problem installing teiid designer: depends on slf4j 1.7.10 (newer version) and javax.servlet 3.1.0 BUNDLE (not package)
> {code}
> depends on & installs slf4j.api_1.7.10:
> * org.teiid.designer.datatools 10.0.2.Final-v20161108-1636-B72 requires org.apache.directory.api.ldap.* & org.apache.directory.api.util
> * org.apache.directory.studio.slf4j-eclipselog_2.0.0.v20150618 requires slf4j 1.7.10 (fragment-host)
> * org.apache.directory.api.ldap.schema_1.0.0.M30 requires 1.7.10
> * org.apache.directory.api.asn1.ber requires 1.7.10
> * org.apache.directory.api.ldap.extras.aci requires 1.7.10
> depends on and installs javax.servlet:
> * org.teiid.designer.modelgenerator.salesforce -> require-bundle javax.servlet;bundle-version="[3.1.0,4.0.0)"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4188) Use of help docs causes lucene 5 index errors in console log
by Mat Booth (JIRA)
[ https://issues.jboss.org/browse/JBDS-4188?page=com.atlassian.jira.plugin.... ]
Mat Booth commented on JBDS-4188:
---------------------------------
Hmm, there's a couple of problems here -- one of which is that webtools doesn't seem to generate indexes at build time and instead have lucene 3 indexes checked directly into source control... This is a deficiency of the upstream webtools build.
The missing indexes are strange, I'll have to look into that.
However, these errors should be "benign" as Eclipse should just re-index the docs if there is no valid pre-built one; as you say it shouldn't prevent usage.
Can you file a bug against rh-eclipse46?
> Use of help docs causes lucene 5 index errors in console log
> ------------------------------------------------------------
>
> Key: JBDS-4188
> URL: https://issues.jboss.org/browse/JBDS-4188
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, upstream
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Mat Booth
> Priority: Minor
> Fix For: 10.x
>
> Attachments: external-window.png
>
>
> As of the latest rpm build (10.2-0.20161117.2130) if you click on the (?) icon in any dialog (eg., Help > About > (?) ) you get a TON of Eclipse Help errors caused by Lucene 5.4.1 trying to read content which I presume was created with Lucene 3.5:
> {code}
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.565
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.consumption.ui.doc.user_1.0.700.v201610271000 [429]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.610
> !MESSAGE Help index declared, but missing for plugin org.eclipse.dstore.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.616
> !MESSAGE Help index declared, but missing for plugin org.eclipse.platform.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.638
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.axis2.ui.doc.user_1.0.200.v201610271000 [425]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.638
> !MESSAGE Help index declared, but missing for plugin org.eclipse.jdt.doc.user.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.640
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.command.env.doc.user_1.5.400.v201610271000 [455]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.675
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.dtdeditor.doc.user_1.0.700.v201610271000 [487]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.676
> !MESSAGE Help index declared, but missing for plugin org.eclipse.jdt.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.678
> !MESSAGE Help index declared, but missing for plugin org.eclipse.platform.doc.user.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.680
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.j2ee.doc.user_1.1.400.v201610271000 [392]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.687
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.xmleditor.doc.user_1.0.700.v201610271000 [554]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.697
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.xsdeditor.doc.user_1.0.800.v201610271000 [557]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.707
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ejb.doc.user_1.1.301.v201610271000 [387]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.715
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.axis.ui.doc.user_1.1.200.v201610271000 [418]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.716
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.wsdl.ui.doc.user_1.0.850.v201610271000 [467]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.725
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.webtools.doc.user_1.0.500.v201610271000 [543]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.733
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.server.ui.doc.user_1.1.600.v201610271000 [658]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.738
> !MESSAGE Help index declared, but missing for plugin org.eclipse.pde.doc.user.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.745
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.doc.user_1.0.700.v201610271000 [439]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.747
> !MESSAGE Help index declared, but missing for plugin org.eclipse.rse.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.749
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.wsi.ui.doc.user_1.0.750.v201610271000 [471]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.760
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610271000 [536]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.762
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.server.ui.doc.user_1.0.600.v201610271000 [649]. Please use an index built with Lucene 5 or higher.
> java.net.URISyntaxException: Illegal character in path at index 56: localhelp:/org.eclipse.mylyn.wikitext.help.ui/help/Mylyn WikiText User Guide.html?lang=en_CA
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3053)
> at java.net.URI.<init>(URI.java:588)
> at java.net.URL.toURI(URL.java:939)
> at org.eclipse.help.internal.base.util.ProxyUtil.getProxy(ProxyUtil.java:57)
> at org.eclipse.help.internal.base.util.ProxyUtil.getConnection(ProxyUtil.java:108)
> at org.eclipse.help.internal.base.util.ProxyUtil.getStream(ProxyUtil.java:124)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.isXHTML(HTMLSearchParticipant.java:108)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:47)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:248)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:630)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:604)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:32)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> java.net.URISyntaxException: Illegal character in path at index 56: localhelp:/org.eclipse.mylyn.wikitext.help.ui/help/Mylyn WikiText User Guide.html?lang=en_CA
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3053)
> at java.net.URI.<init>(URI.java:588)
> at java.net.URL.toURI(URL.java:939)
> at org.eclipse.help.internal.base.util.ProxyUtil.getProxy(ProxyUtil.java:57)
> at org.eclipse.help.internal.base.util.ProxyUtil.getConnection(ProxyUtil.java:108)
> at org.eclipse.help.internal.base.util.ProxyUtil.getStream(ProxyUtil.java:124)
> at org.eclipse.help.search.SearchParticipantXML.addDocument(SearchParticipantXML.java:308)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:53)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:248)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:630)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:604)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:32)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help documentation could not be indexed completely.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/ide/undo/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/debug/ui/launchConfigurations/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/activities/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/jdom/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.rse.doc.isv/reference/extension-points/org_eclipse_rse_core_systemTypeProviders.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23510:
-------------------------------
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 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
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 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.
> [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, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.Final
>
>
> 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)
9 years, 4 months
[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23510:
----------------------------------
Summary: [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, target-platform
Affects Versions: 4.4.2.AM3
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.2.Final
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, 4 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with TP and PDE Source Lookup)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23481:
-------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.4.x)
> 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.2.Final
>
>
> 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, 4 months