[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document
by Supriya Bharadwaj (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ]
Supriya Bharadwaj commented on TOOLSDOC-624:
--------------------------------------------
> Tested the steps
> 5. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Online: Added an admonition for the prerequisite
> 6. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Offline: Added an admonition for the prerequisite
> 3. Install JBoss Developer Studio Integration Stack in Eclipse when Online: Added info for the categories that the user will select (I am not sure if this was required to be added; I did it anyway because I felt it was only apt to have it here)
> 4. Install JBoss Developer Studio Integration Stack in Eclipse when Offline: Added info for the categories that the user will select
> 5. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Online (I am not sure if this was required to be added; I did it anyway because I felt it was only apt to have it here)
> 6. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Offline: Added info for the categories that the user will select
> JBDS-IS 8.0.1: Update Install Document
> ---------------------------------------
>
> Key: TOOLSDOC-624
> URL: https://issues.jboss.org/browse/TOOLSDOC-624
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
>
> 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
> a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install).
> b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19534) fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19534?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19534:
-------------------------------------
Fix Version/s: 4.3.0.Alpha2
> fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui
> -------------------------------------------------------------------------
>
> Key: JBIDE-19534
> URL: https://issues.jboss.org/browse/JBIDE-19534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Fix For: 4.3.0.Alpha2
>
>
> When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui:
> {code}
> Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages
> {code}
> These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19410:
----------------------------------------
The check for early access makes that we use p2 immediately when showing Central, that's why it logs early.
We do need to log it for our dev to understand something is wrong when they'll notice Central isn't behaving as expected and to be able to find the workaround (ticking "Support Software Installation" checkbox) by themselves). Otherwise, we'll just get dozens of IRC interruptions saying "Hey, my appl doesn't show Early-Access things are installed and there is nothing in log".
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years