[JBoss JIRA] (JBTIS-809) Cannot install Fuse tooling from EA without GA
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-809?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-809:
------------------------------------
Workaround Description: Add the GA update site (or GA zip file)
Workaround: Workaround Exists
> Cannot install Fuse tooling from EA without GA
> ----------------------------------------------
>
> Key: JBTIS-809
> URL: https://issues.jboss.org/browse/JBTIS-809
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.1.GA
> Environment: JBDS-IS 9.0.1.CR2
> Reporter: Andrej Podhradsky
>
> Cannot install Fuse tooling from EA without GA due to the following error
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959)
> Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found
> {code}
> the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-809) Cannot install Fuse tooling from EA without GA
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-809?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-809:
------------------------------------
Description:
Cannot install Fuse tooling from EA without GA due to the following error
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959)
Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found
{code}
the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case.
was:
Cannot install Fuse tooling from EA without GA due to the following error
{code}
{code}
the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case.
> Cannot install Fuse tooling from EA without GA
> ----------------------------------------------
>
> Key: JBTIS-809
> URL: https://issues.jboss.org/browse/JBTIS-809
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.1.GA
> Environment: JBDS-IS 9.0.1.CR2
> Reporter: Andrej Podhradsky
>
> Cannot install Fuse tooling from EA without GA due to the following error
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959)
> Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found
> {code}
> the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-809) Cannot install Fuse tooling from EA without GA
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-809:
---------------------------------------
Summary: Cannot install Fuse tooling from EA without GA
Key: JBTIS-809
URL: https://issues.jboss.org/browse/JBTIS-809
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 9.0.1.GA
Environment: JBDS-IS 9.0.1.CR2
Reporter: Andrej Podhradsky
Cannot install Fuse tooling from EA without GA due to the following error
{code}
{code}
the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22758) Context menu for multiple selected server modules has two 'remove' options
by Jan Richter (JIRA)
Jan Richter created JBIDE-22758:
-----------------------------------
Summary: Context menu for multiple selected server modules has two 'remove' options
Key: JBIDE-22758
URL: https://issues.jboss.org/browse/JBIDE-22758
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.1.AM2
Reporter: Jan Richter
Attachments: remove.png
I have multiple projects deployed to a server (wildfly in my case) and when I select at least 2 and right click on them, the context menu shows two remove entries.
They both have different icons and they pretty much do the same, except the second one also opens an empty shell along with the confirm prompt.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3769.
-----------------------------
Closing as done.
> Remove JSPM from dependencies
> -----------------------------
>
> Key: JBDS-3769
> URL: https://issues.jboss.org/browse/JBDS-3769
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Critical
> Labels: havoc
> Fix For: 10.1.0.AM2
>
>
> After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
> Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3958) Transpile code at build time instead of run time
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3958?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3958.
-----------------------------
Closing as done.
> Transpile code at build time instead of run time
> ------------------------------------------------
>
> Key: JBDS-3958
> URL: https://issues.jboss.org/browse/JBDS-3958
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Jan Richter
> Fix For: 10.1.0.AM2
>
>
> The major slowing factor in the initial load time is babel transpiling the code when the application starts (currently run as jspm subroutine).
> Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ERT-349) Add JavaScript formatting option for anonymous functions [EBZ#315507]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-349:
---------------------------------------
Summary: Add JavaScript formatting option for anonymous functions [EBZ#315507]
Key: ERT-349
URL: https://issues.jboss.org/browse/ERT-349
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Friendly Jira Robot
Priority: Trivial
Fix For: Future
Build Identifier: Build id: 20100218-1602
It should be possible to set white-space formatting rules differently for anonymous functions and named functions.
Use-case: It should be possible to stipulate that white-space must precede the opening parenthesis in an anonymous function declaration while named function declaration should not.
Example:
var foo = function () {
// some code
};
function foo() {
// some code
}
Reproducible: Always
Steps to Reproduce:
Not really a bug, more of a feature request. Go to Window > Preferences > Web > JavaScript > Code Style > Formatter. Under the White Space tab open Declarations and see that there is only a setting for Functions (not Named Functions and Anonymous Functions)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months