[JBoss JIRA] (JBDS-3834) Install fail - what next?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3834:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Install fail - what next?
> -------------------------
>
> Key: JBDS-3834
> URL: https://issues.jboss.org/browse/JBDS-3834
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM2
>
> Attachments: error.PNG, fail_install.PNG
>
>
> Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 10 months
[JBoss JIRA] (JBDS-4188) Use of help docs causes lucene 5 index errors in console log
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4188?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4188:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> 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: 11.0.0.AM2
>
> 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)
6 years, 10 months
[JBoss JIRA] (JBDS-4067) Review labels shown for software components on confirmation page
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4067?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4067:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Review labels shown for software components on confirmation page
> ----------------------------------------------------------------
>
> Key: JBDS-4067
> URL: https://issues.jboss.org/browse/JBDS-4067
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> On confirmation page installer shows list of components from software stack. For most components there is detection algorithm that can find already installed components, so installer can skip install. There should be term selected for set of version for the required components:
> * required;
> * recommended;
> * tested;
> * ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 10 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3627:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 11.0.0.AM2
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 10 months