[JBoss JIRA] (JBIDE-17705) 'Connection Reset' exception reported when opening html5 files
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17705?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-17705:
-------------------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> 'Connection Reset' exception reported when opening html5 files
> --------------------------------------------------------------
>
> Key: JBIDE-17705
> URL: https://issues.jboss.org/browse/JBIDE-17705
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: Windows 8.1
> x86_64
> Java 8
> Reporter: Denis Golovin
> Fix For: 4.2.0.CR1
>
>
> {code}java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(Unknown Source)
> at java.net.SocketInputStream.read(Unknown Source)
> at sun.nio.cs.StreamDecoder.readBytes(Unknown Source)
> at sun.nio.cs.StreamDecoder.implRead(Unknown Source)
> at sun.nio.cs.StreamDecoder.read(Unknown Source)
> at java.io.InputStreamReader.read(Unknown Source)
> at java.io.BufferedReader.fill(Unknown Source)
> at java.io.BufferedReader.readLine(Unknown Source)
> at java.io.BufferedReader.readLine(Unknown Source)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.getItialRequestLine(VpvSocketProcessor.java:220)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:59)
> at java.lang.Thread.run(Unknown Source){code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17452) RichFaces project is hiding list of members when run with JDK 8
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17452?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-17452:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> RichFaces project is hiding list of members when run with JDK 8
> ---------------------------------------------------------------
>
> Key: JBIDE-17452
> URL: https://issues.jboss.org/browse/JBIDE-17452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Linux 64 bit
> Java Oracle JDK 1.8
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> 1. Import RichFaces project from Central
> 2. Run it on JBoss AS server 7.1.1.Final
> 3. Open application URL in BrowserSim
> 4. Open members list in BrowserSim
> 5. Enter member in Web Browser
> ASSERT: New member appears in BrowserSim
> 6. Wait for a moment (3-5 secs.)
> ERROR: List of members disappeared in BrowserSim
> It works fine when BrowserSim runs with Java Oracle JDK 1.7.0_51
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17452) RichFaces project is hiding list of members when run with JDK 8
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17452?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-17452:
-------------------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> RichFaces project is hiding list of members when run with JDK 8
> ---------------------------------------------------------------
>
> Key: JBIDE-17452
> URL: https://issues.jboss.org/browse/JBIDE-17452
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Linux 64 bit
> Java Oracle JDK 1.8
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> 1. Import RichFaces project from Central
> 2. Run it on JBoss AS server 7.1.1.Final
> 3. Open application URL in BrowserSim
> 4. Open members list in BrowserSim
> 5. Enter member in Web Browser
> ASSERT: New member appears in BrowserSim
> 6. Wait for a moment (3-5 secs.)
> ERROR: List of members disappeared in BrowserSim
> It works fine when BrowserSim runs with Java Oracle JDK 1.7.0_51
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17733) Remove EGit from Central Discovery
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-17733:
-------------------------------------
No we don't have such requirements at the example level. If there were any, that'd need to be fixed.
> Remove EGit from Central Discovery
> ----------------------------------
>
> Key: JBIDE-17733
> URL: https://issues.jboss.org/browse/JBIDE-17733
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: discovery
> Affects Versions: 4.2.0.Beta2
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta3
>
>
> Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed.
> So we should remove EGit from our Central discovery catalogs.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17311) jvmmonitor agent project moved + renamed into jbt-server repo
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17311?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17311:
-------------------------------------
I simply meant that the agent code needs to find a home to live, and was suggesting it live near the "other" jvmmonitor code, ie, the plugins in jbosstools-server. But I'm not sure where it should go. Openshift's client jar has its own github repository. And nobody seems to know how to build the agent jar's source code.
Also, there's a danger that changing the package names in the agent might break parts of our jvmmonitor plugs that may look for those mbeans. I'm currently not able to quantify this risk, though. It might be non-existant, or it might be very high. At this point, I have no idea. But changing the name of the mbeans the agent adds will break anyone looking for those mbeans.
> jvmmonitor agent project moved + renamed into jbt-server repo
> -------------------------------------------------------------
>
> Key: JBIDE-17311
> URL: https://issues.jboss.org/browse/JBIDE-17311
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jmx
> Affects Versions: 4.2.0.Beta2
> Reporter: Rob Stryker
> Fix For: 4.2.0.Beta3
>
>
> The file "jvmmonitor-agent.jar" is currently a built component separate from its project. This must be somehow unified with the other jvm-monitor code in terms of where it lives and how it gets built.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months