[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 reassigned JBIDE-19534:
----------------------------------------
Assignee: Andre Dietisheim
Resolution: Done
merged and pushed to upstream/master
> 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
> Assignee: 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
> org.jboss.tools.openshift.express.ui also has 2 message classes:
> * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages
> * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages
--
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 closed JBIDE-19534.
------------------------------------
nothing for QE to verify, closing.
> 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
> Assignee: 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
> org.jboss.tools.openshift.express.ui also has 2 message classes:
> * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages
> * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages
--
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 commented on JBIDE-19534:
------------------------------------------
The message class obviously was copied over from org.jboss.tools.openshift.express.ui while keeping the keys.
I'll remove what's not being used.
> 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
> org.jboss.tools.openshift.express.ui also has 2 message classes:
> * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages
> * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-15714:
------------------------------------------------
{quote}So just to play devils advocate here - if we force refresh on the preview browser, why do have a button to disable refresh on the visual/source part ?
shouldn't that button affect both ?
{quote}
It shouldn't. There is nothing to disable for Preview tab.
Preview tab's purpose is to show the editor content visual representation, provide ability to fill in the forms, click to links, etc. Preview tab content always been refreshed on its activation to show latest changes in the source.
Visual/Source tab purpose is to provide communication between visual and source parts, see visual representation of changes user made without switching to another tab. If you don't want to see preview update on each change in editor - choose refresh-on-save or do refreshes manually.
> Dynamic content assist for AngularJS expressions in html files
> --------------------------------------------------------------
>
> Key: JBIDE-15714
> URL: https://issues.jboss.org/browse/JBIDE-15714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: Diagram.gliffy, vpe.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3276) JBDS-IS Installer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3276:
-------------------------------------------
These are looking really good - do you have a screenshot of how the page will look like ?
about where to put the installer i'm wonderig if we shouldn't just do it inside devstudio installer and have it as another variant of the installer ?
anything for/against that ?
> JBDS-IS Installer
> -----------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform, requirements
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Denis Golovin
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
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:
-------------------------------------
Description:
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
org.jboss.tools.openshift.express.ui also has 2 message classes:
* org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages
* org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages
was:
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
> 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
> org.jboss.tools.openshift.express.ui also has 2 message classes:
> * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages
> * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Arun Gupta commented on JBIDE-19507:
------------------------------------
+1, very nicely described and this will make our tooling compelling.
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Batch Property Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty
> Example:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class RenamablePropertyBatchlet implements Batchlet {
>
> @Inject @BatchProperty String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> During rename of field "otherName" changes for job.xml references should be added in Refactoring:
> !PropertyRename.png!
> 3. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3384:
-------------------------------------------
[~rob.stryker] can you work with [~mickael_istria] and [~dgolovin] to make sure our Mars M6 and Devstudio installer actually have the right things needed for users to have the nice terminal (for alpha2) and preferably remove any non-used terminal UI (this could be done post-alpha2)
> Investigate how the terminal changes in Mars will/should affect us
> -------------------------------------------------------------------
>
> Key: JBDS-3384
> URL: https://issues.jboss.org/browse/JBDS-3384
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build, forge, openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
>
> Terminal (console) support in eclipse mars is changing and we should
> make sure we adjust for it.
> Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
> Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now.
> This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new.
> As we find what it entails we should link those issues to this jira.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3384:
--------------------------------------
Fix Version/s: 9.0.0.Alpha2
> Investigate how the terminal changes in Mars will/should affect us
> -------------------------------------------------------------------
>
> Key: JBDS-3384
> URL: https://issues.jboss.org/browse/JBDS-3384
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build, forge, openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
>
> Terminal (console) support in eclipse mars is changing and we should
> make sure we adjust for it.
> Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
> Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now.
> This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new.
> As we find what it entails we should link those issues to this jira.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years