[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3199:
-----------------------------------
[~manaRH], [~mjobanek] : the archetypes look fine to me, except for a couple minor issues :
- RF kitchensink cheatsheet : line numbers are off in pom.xml
- RF kitchensink kitchensinkrf-quickstart-ds.xml still uses hardcoded file name (the html5 and spring ones are fine)
- pool-name and connectionUrl in -ds.xml still use hardcoded kitchensinkrf-quickstart (or wfk-spring-quickstart) in spring and kitchensink archetypes
Nothing blocking a release, but it'd be cleaner if that was fixed beforehand.
The rest is really ok
> Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3199
> URL: https://issues.jboss.org/browse/JBDS-3199
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 8.1.0.GA
>
>
> These "kitchensink" strings are retained:
> grep -ir kitchen *
> main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source>
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS"
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true"
> test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS"
> test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ]
Catherine Robson commented on JBIDE-18813:
------------------------------------------
[~burrsutter] and [~maxandersen] - would you like to add some more input here? I didn't want to do another revision until I got more widespread input.
> Convert JBoss Central to an HTML5 page
> --------------------------------------
>
> Key: JBIDE-18813
> URL: https://issues.jboss.org/browse/JBIDE-18813
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha1
>
> Attachments: Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.png, Central Design Concept B.bmml, Central Design Concept B.bmml, Central Design Concept B.png, JBoss Access Panel Concept.bmml, JBoss Access Panel Concept.png, JBoss Central User Stories and Flows.gliffy, Screen Shot 2015-01-16 at 4.38.58 PM.png
>
>
> Central Page requires new capabilities :
> - needs more customization (display content depending on user preferences)
> - needs to scale with JBDS-IS, Fuse content
> - access to more examples, with filtering capabilities
> Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach :
> - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility
> - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-12351) JMX connection to servers cannot be established with IPv6
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-12351:
-------------------------------------
My testing indicates this bug is present for local and remote jmx requests when ip6 is used.
> JMX connection to servers cannot be established with IPv6
> ---------------------------------------------------------
>
> Key: JBIDE-12351
> URL: https://issues.jboss.org/browse/JBIDE-12351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 3.3.0.Final
> Environment: Fedora 17 32bit
> EAP 6.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: f2f2014
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log:
> {code}
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-12351) JMX connection to servers cannot be established with IPv6
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-12351:
--------------------------------
Fix Version/s: 4.2.3.Beta1
> JMX connection to servers cannot be established with IPv6
> ---------------------------------------------------------
>
> Key: JBIDE-12351
> URL: https://issues.jboss.org/browse/JBIDE-12351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 3.3.0.Final
> Environment: Fedora 17 32bit
> EAP 6.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: f2f2014
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log:
> {code}
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-12351) JMX connection to servers cannot be established with IPv6
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-12351:
--------------------------------
Summary: JMX connection to servers cannot be established with IPv6 (was: Remote JMX connection to servers cannot be established with IPv6)
> JMX connection to servers cannot be established with IPv6
> ---------------------------------------------------------
>
> Key: JBIDE-12351
> URL: https://issues.jboss.org/browse/JBIDE-12351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 3.3.0.Final
> Environment: Fedora 17 32bit
> EAP 6.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
>
> When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log:
> {code}
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19045:
---------------------------------------------
now that [~dgolovin] merged https://github.com/jbosstools/jbosstools-target-platforms/pull/124 and https://github.com/jbosstools/jbosstools-jst/pull/450 in which put tern *inside* jst updatesite which of the listed PR's are still relevant ?
> Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
> -------------------------------------------------------
>
> Key: JBIDE-19045
> URL: https://issues.jboss.org/browse/JBIDE-19045
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central, jsp/jsf/xml/html source editing, target-platform
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.3.Beta1
>
>
> We are going to update Tern to v0.7.0 for 4.2.x.
> Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
> p2diff output:
> {code}
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> < tern.eclipse.ide.tools.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.ui [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.jar [0.7.0.201412012159]
> < tern.server.nodejs [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159]
> < tern.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.core [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.jsdt [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159]
> < tern.eclipse [0.7.0.201412012159]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.core [0.6.0.201409231610]
> > tern-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610]
> > tern.server.nodejs [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610]
> > tern-jsdt-feature.feature.jar [0.6.0.201409231610]
> > tern-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.ui [0.6.0.201409231610]
> > tern-jsdt-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610]
> > tern.eclipse [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610]
> > tern.eclipse.ide.ui [0.6.0.201409231610]
> > tern.core [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.core [0.6.0.201409231610]
> > tern.eclipse.ide.jsdt [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610]
> === Summary ===
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18581) jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded
by Sande Gilda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18581?page=com.atlassian.jira.plugi... ]
Sande Gilda edited comment on JBIDE-18581 at 2/5/15 7:24 AM:
-------------------------------------------------------------
[~fbricon]: Sorry, I just saw the email. I am not familiar with this change. Is this a WFK quickstart? Is it resolved, and if so, what was the resolution?
If I don't respond in the future, please ping me on IRC.
was (Author: sgilda):
[~fbricon]: Sorry, I just saw the email. I am not familiar with this change. Is this a WFK quickstart? Is it resolved? If I don't respond in the future, please ping me on IRC.
> jboss-kitchensink-backbone's graph profile defines repo which cannot be loaded
> ------------------------------------------------------------------------------
>
> Key: JBIDE-18581
> URL: https://issues.jboss.org/browse/JBIDE-18581
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.2.0.CR2
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.2.3.Beta1
>
>
> graph profile defines http://mvnplugins.fusesource.org/repo/releas which always timed out for me. Im unable to open in via browser either.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months