[JBoss JIRA] (JBIDE-17500) Review EAP runtimes available for download
by Martin Malina (JIRA)
Martin Malina created JBIDE-17500:
-------------------------------------
Summary: Review EAP runtimes available for download
Key: JBIDE-17500
URL: https://issues.jboss.org/browse/JBIDE-17500
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta2
Environment: JBDS 8.0.0.Beta2a B106
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta3
The Download runtime UI offers many versions of EAP, but it seems that not all of them are valid.
I'm not sure if all of this is taken from stacks, if so, a JIRA with JDF will be required as well.
When you open Preferences -> JBoss Tools -> JBoss Runtime Detection
and click Download..., you're offered JBoss runtimes for download.
In the list, there are these EAP versions:
JBoss EAP 6.0.0
JBoss EAP 6.0.1
JBoss EAP 6.1.0
JBoss EAP 6.2.0
6.0.0 and 6.0.1 are listed as manual downloads and if I want to download them, I am offered this link:
http://www.jboss.org/products/
>From there, I can get to https://www.jboss.org/products/eap/download/
The oldest version of EAP this contains is 6.1.0.
Probably the only place to get older EAP is access.redhat.com.
So we should either remove these older versions from the list (I would prefer that) or link to access.redhat.com.
Then there is 6.1.0 and 6.2.0, both available through the Download Manager, which is fine. But the site also contains 6.3.0.Beta so we might offer that, too?
The same applies to Portal - we list JPP 6.0.0 and point users to jboss.org/products. But that only offers JPP 6.1.0. So I would vote for removing the JPP 6.0.0 entry.
And last, WildFly 8.1.0.Final is available, so we should add that.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-17496:
--------------------------------
Assignee: Mickael Istria
> Central installation fails if done right after Eclipse start
> ------------------------------------------------------------
>
> Key: JBIDE-17496
> URL: https://issues.jboss.org/browse/JBIDE-17496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B106
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.Beta2
>
> Attachments: connector-error.png, problems-occurred.png
>
>
> When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
> I can reproduce some sort of errors every time (I tried 4 or 5 times), but only on a completely fresh install of JBDS/JBT (no central repo data cached).
> It looks like there is a race condition.
> Several times when I tried to install Findbugs, I got:
> {quote}
> The following connectors are not available: FindBugs
> Proceed with the installation anyways?
> {quote}
> Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
> !connector-error.png!
> If I proceed anyway, the install dialog is empty.
> If I click that I don't want to install, I get this:
> {code}
> Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> {code}
> !problems-occurred.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17499) Context menu in a OpenShift Explorer contains item Domain without selected connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17499?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17499:
----------------------------------
Description:
In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without selected connection) and also this menu item is not working (after click on this item nothing happens).
!contextmenu.png!
was:
In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without related connection) and also this menu item is not working (after click on this item nothing happens).
!contextmenu.png!
> Context menu in a OpenShift Explorer contains item Domain without selected connection
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17499
> URL: https://issues.jboss.org/browse/JBIDE-17499
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Marián Labuda
> Priority: Minor
> Attachments: contextmenu.png
>
>
> In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without selected connection) and also this menu item is not working (after click on this item nothing happens).
> !contextmenu.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17499) Context menu in a OpenShift Explorer contains item Domain without selected connection
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-17499:
-------------------------------------
Summary: Context menu in a OpenShift Explorer contains item Domain without selected connection
Key: JBIDE-17499
URL: https://issues.jboss.org/browse/JBIDE-17499
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Beta2
Reporter: Marián Labuda
Priority: Minor
Attachments: contextmenu.png
In a OpenShift explorer context menu are 2 menu items under sub item New - Connection and Domain. It is not reasonable to have new domain menu item here (without related connection) and also this menu item is not working (after click on this item nothing happens).
!contextmenu.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17279) Visual Page Editor: Visual tab is not refreshing
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17279?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17279.
-------------------------------
Verified with JBDS Beta2-v20140601-0744-B106
> Visual Page Editor: Visual tab is not refreshing
> ------------------------------------------------
>
> Key: JBIDE-17279
> URL: https://issues.jboss.org/browse/JBIDE-17279
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta1
> Environment: Ubuntu linux
> Reporter: Daniel Azarov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta2
>
> Attachments: VPERefresh.png
>
>
> 1. Create project
> 2. Create file index.html
> {code}
> <html>
> <body>
> <h1>Header</h1>
> <p>Paragraph 1</p>
> <p>Paragraph 2</p>
> </body>
> </html>
> {code}
> 3. Open file in Visual Page Editor
> 4. Change Header to Header 123
> FAIL:
> Visual tab is not refreshed:
> !VPERefresh.png!
> Note:
> Any resize (splitter move, window minimize/maximize) of Visual tab refreshes it.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-17498:
--------------------------------
Assignee: Gorkem Ercan
> Can't run default hybrid project on device
> ------------------------------------------
>
> Key: JBIDE-17498
> URL: https://issues.jboss.org/browse/JBIDE-17498
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: windows
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
>
> After choosing *Run As.. -> Run on Android Device* getting exception:
> {code}
> !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618
> !MESSAGE Ant Build Failed
> !STACK 1
> org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> ... 12 more
> !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618
> !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> !STACK 0
> E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620
> !MESSAGE Build failed... Build artifact does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17163) Visual Preview: Preview shows blank screen for related css, js files
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17163?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17163.
-------------------------------
Verified with JBDS Beta2-v20140601-0744-B106
> Visual Preview: Preview shows blank screen for related css, js files
> --------------------------------------------------------------------
>
> Key: JBIDE-17163
> URL: https://issues.jboss.org/browse/JBIDE-17163
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
>
> 1. Open HTML page
> 2. Open HTML Preview. Preview is showing previously opened HTML page
> 3. Open CSS file linked to opened HTML page.
> 4. HTML preview still should show preview of opened HTML page not preview of opened CSS file (which is empty). User wants to make changes to CSS file but to see visual results of changes he made he must activate editor with opened HTML page. Would be more useful to see results of changes made to CSS file immediately after CSS file is saved.
> The same applies for JavaScript files or other files which are included to HTML file (templates...)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months