[JBoss JIRA] (JBIDE-19095) OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19095:
-------------------------------------
Steps to Reproduce:
# ASSERT: Have an application on OpenShift.
# EXEC: In OpenShift Explorer: select your application and pick *List All Environment Variables*
# ASSERT: ConsoleView is opened and lists all environment variables.
# EXEC: Check the first line of the output
Result:
It says "Snapshot Restore/Deploy for application...."
!erroneous-snapshot-restore-title.png!
was:
ASSERT: Have an application on OpenShift.
EXEC: Show all environment variables for the application.
EXEC: Open ConsoleView with listed variables.
> OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19095
> URL: https://issues.jboss.org/browse/JBIDE-19095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: environment_variables
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: erroneous-snapshot-restore-title.png
>
>
> While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19095) OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19095:
-------------------------------------
Attachment: erroneous-snapshot-restore-title.png
> OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19095
> URL: https://issues.jboss.org/browse/JBIDE-19095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: environment_variables
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: erroneous-snapshot-restore-title.png
>
>
> While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18963) when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18963?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18963:
---------------------------------------------
It is a problem *when* you have invalid components.
Try use a component name in whatsnew headers that does not exist in components.yml and you will get that hard to grasp error above.
> when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18963
> URL: https://issues.jboss.org/browse/JBIDE-18963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.2.3.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.0.Alpha1
>
>
> today when having invalid components you get something like:
> {code}
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65:in `block (4 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `block (3 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `block (2 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `block in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `instance_eval'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65531:in `__tilt_70190394039780'
> {code}
> as found in https://github.com/jbosstools/jbosstools-website/pull/311/files
> the logic is all embedded in haml leaving no room for proper error handling.
> should do some basic asserts in the pipeline for that ids actually exists in components.yml or at least just use component id as fall back name.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3319) JBDS 9.0 installer underreports space requirement by 225 - 250MB
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3319:
-------------------------------------------
I would not expect that big a size drop unless target platform content changed. [~nickboldt] Can you please investigate that since it should be known to our releng why our installer suddenly changes in size.
> JBDS 9.0 installer underreports space requirement by 225 - 250MB
> ----------------------------------------------------------------
>
> Key: JBDS-3319
> URL: https://issues.jboss.org/browse/JBDS-3319
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.2.GA
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Fix For: 9.0.0.Alpha1
>
>
> The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required:
> Disk Space:
> Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB
> The actual install uses this much:
> du -sh installdir/
> 822M installdir/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19187) CordovaSim + localhost:8080 fail
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19187?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19187:
-------------------------------------
[~burrsutter], could you please attach the project?
(1) Frankly, can't get the livereload problem. IMHO 404 is not coupled with livereload. Does it stop working?
(2) in terms of XHR and 500 server error - there is no silver bullet to handle all cross domain ajax due to the fact that it depends dramatically on the remote server setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work... . We do have 3 proxy setting (local / remote / disabled) - at least one of them should work for this particular case.
< With that said, CordovaSim was handling localhost:8080 well…at the time the video was made. Any ideas?
hmm.. that's weird that it started to failing cause we do not have any relevant changes that could have broken everything that way. I do believe changing the proxy might tackle the issue.
(3) [~akazakov], [~vrubezhny] seems to be coupled with js validation - could you take a look?
> CordovaSim + localhost:8080 fail
> --------------------------------
>
> Key: JBIDE-19187
> URL: https://issues.jboss.org/browse/JBIDE-19187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Environment: JBDS 8
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: localhost_error.png
>
>
> The following logic used to work and now fails:
> $.getJSON("http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members", function(data) {
> $("#contacts").empty();
> var items = [];
> $.each(data, function(key, val) {
> console.log("item: " + key + " " + val.name);
> items.push("<li><a href='#"+ key + "'>" + val.name +"</a></li>");
> });
> $("#contacts").append(items);
> $("#contacts").listview("refresh");
> });
> -------
> as seen in this youtube video and comments
> https://www.youtube.com/watch?v=FstGLMr3W8s&feature=gp-n-y&google_comment...
> ---- Using the Chrome Debugger (via CordovaSim, right-click, Dev Tools)
> has the following error message:
> https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo... 500 () rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=h...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19095) OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19095:
-------------------------------------
Fix Version/s: 4.2.3.Beta1
4.3.0.Alpha1
> OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19095
> URL: https://issues.jboss.org/browse/JBIDE-19095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: environment_variables
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19153) Unable to use hibernate console when DTD is not accessible (hibernate.org down)
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19153?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-19153:
-----------------------------------
Right, that's what i figured.
> Unable to use hibernate console when DTD is not accessible (hibernate.org down)
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19153
> URL: https://issues.jboss.org/browse/JBIDE-19153
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Final
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> Inaccessible DTD causes blocking Hibernate Console usage (as DTD cannot be loaded)
> If DTD is not accessible It would be more useful to disable DTD validation rather than block further usage and just show some warning.
> {code}
> org.hibernate.HibernateException: Could not parse configuration: C:\Users\jpeterka\workspace\tmp\hb\mvn-hibernate35\src\main\java\hibernate.cfg.xml
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1586)
> at org.hibernate.cfg.Configuration.configure(Configuration.java:1554)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.configure(ConfigurationProxy.java:94)
> at org.hibernate.console.ConfigurationFactory.loadConfigurationXML(ConfigurationFactory.java:350)
> at org.hibernate.console.ConfigurationFactory.configureStandardConfiguration(ConfigurationFactory.java:278)
> at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:175)
> at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:97)
> at org.hibernate.eclipse.console.common.HibernateExtension$5.execute(HibernateExtension.java:166)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189)
> at org.hibernate.eclipse.console.common.HibernateExtension.buildWith(HibernateExtension.java:163)
> at org.hibernate.eclipse.console.common.HibernateExtension.build(HibernateExtension.java:134)
> at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:189)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:43)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.dom4j.DocumentException: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd
> at org.dom4j.io.SAXReader.read(SAXReader.java:484)
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1576)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19153) Unable to use hibernate console when DTD is not accessible (hibernate.org down)
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19153?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-19153:
---------------------------------
Priority: Major (was: Blocker)
Hibernate.org is back online so I changed this from blocker to major. This issue is more about offline mode. When some remote DTD is not accessible feature should not be blocked.
> Unable to use hibernate console when DTD is not accessible (hibernate.org down)
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19153
> URL: https://issues.jboss.org/browse/JBIDE-19153
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Final
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> Inaccessible DTD causes blocking Hibernate Console usage (as DTD cannot be loaded)
> If DTD is not accessible It would be more useful to disable DTD validation rather than block further usage and just show some warning.
> {code}
> org.hibernate.HibernateException: Could not parse configuration: C:\Users\jpeterka\workspace\tmp\hb\mvn-hibernate35\src\main\java\hibernate.cfg.xml
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1586)
> at org.hibernate.cfg.Configuration.configure(Configuration.java:1554)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.configure(ConfigurationProxy.java:94)
> at org.hibernate.console.ConfigurationFactory.loadConfigurationXML(ConfigurationFactory.java:350)
> at org.hibernate.console.ConfigurationFactory.configureStandardConfiguration(ConfigurationFactory.java:278)
> at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:175)
> at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:97)
> at org.hibernate.eclipse.console.common.HibernateExtension$5.execute(HibernateExtension.java:166)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189)
> at org.hibernate.eclipse.console.common.HibernateExtension.buildWith(HibernateExtension.java:163)
> at org.hibernate.eclipse.console.common.HibernateExtension.build(HibernateExtension.java:134)
> at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:189)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:43)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.dom4j.DocumentException: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd
> at org.dom4j.io.SAXReader.read(SAXReader.java:484)
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1576)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19024) org.jboss.tools.tycho-plugins:target-platform-utils - source downloading enhancement
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19024?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-19024.
----------------------------------
Thanks [~tkleszczynski]
> org.jboss.tools.tycho-plugins:target-platform-utils - source downloading enhancement
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19024
> URL: https://issues.jboss.org/browse/JBIDE-19024
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Tomasz Kleszczyński
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha1
>
>
> Testing Mojo for mirroring the installation units I encountered three problems.
> 1. Using tycho 0.22.0 there is problem with creating TargetPlatform used for resolving source artifacts. Tycho complains that execution environment 'Mock' is not known.
> 2. Mirrored versions of source artifacts could be different that code artifacts. This is because plugin tries to resolve source artifact without specifying version.
> 3. Downloading sources for IU *.feature.group is not supported.
> I fixed the first issue and implemented second and third. Please expect pull request.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19184:
---------------------------------------------
[~mmusaji] any chance you got a project and steps to reproduce this ?
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months