April 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19663) jst/jsf New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19663?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19663: -------------------------------------- Assignee: Alexey Kazakov > jst/jsf New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------- > > Key: JBIDE-19663 > URL: https://issues.jboss.org/browse/JBIDE-19663 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

1 week, 1 day

2
1
0 / 0

[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM: ------------------------------------------------------------ Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/ There are ways to achieve more-than-260-char paths, but do we want to? was (Author: nickboldt): Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... > Align installation default path with installer filename > ------------------------------------------------------- > > Key: JBDS-3044 > URL: https://issues.jboss.org/browse/JBDS-3044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Blocker > Labels: discuss > Fix For: 8.0.0.Beta3 > > > Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync. > This question is open for discussion. Nick pointed out some reasons against this suggestion: > {quote} > Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons: > a) Max is AFK, and will want to vet/veto this idea > b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces > c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience > So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters. > Max Rydahl Andersen WDYT? > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

1 month, 1 week

3
3
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

4 months, 1 week

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

6 months, 1 week

3
7
0 / 0

[JBoss JIRA] (JBIDE-26633) Archive unsupported versions of DevStudio / CRStudio

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26633: ---------------------------------- Summary: Archive unsupported versions of DevStudio / CRStudio Key: JBIDE-26633 URL: https://issues.jboss.org/browse/JBIDE-26633 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.11.0.Final Reporter: Jeff MAURY Assignee: Jeff MAURY Fix For: 4.12.0.AM1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26630) Fix builds for TP based on 2019-06.M2

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26630?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26630: ------------------------------- Story Points: 8 > Fix builds for TP based on 2019-06.M2 > ------------------------------------- > > Key: JBIDE-26630 > URL: https://issues.jboss.org/browse/JBIDE-26630 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.11.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > When the 2019-06.M2 TP will be only, some builds may be failing because of API breaking changes -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26632) webservices unit tests failing following move to 2019-06.M1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26632?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26632: ------------------------------- Story Points: 8 > webservices unit tests failing following move to 2019-06.M1 > ----------------------------------------------------------- > > Key: JBIDE-26632 > URL: https://issues.jboss.org/browse/JBIDE-26632 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.11.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > A few webservices unit test are failing when we moved to 2019-96.M1. It seems that's because the module is not being deployed when starting the server -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26629) Update 4.12.0.AM1 Target Platform (Docker tooling, ...) for 2019-06.M2

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26629?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26629: ------------------------------- Story Points: 13 > Update 4.12.0.AM1 Target Platform (Docker tooling, ...) for 2019-06.M2 > ---------------------------------------------------------------------- > > Key: JBIDE-26629 > URL: https://issues.jboss.org/browse/JBIDE-26629 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.11.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26632) webservices unit tests failing following move to 2019-06.M1

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26632: ---------------------------------- Summary: webservices unit tests failing following move to 2019-06.M1 Key: JBIDE-26632 URL: https://issues.jboss.org/browse/JBIDE-26632 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.11.0.Final Reporter: Jeff MAURY Assignee: Jeff MAURY Fix For: 4.12.0.AM1 A few webservices unit test are failing when we moved to 2019-96.M1. It seems that's because the module is not being deployed when starting the server -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26599?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26599: ------------------------------- Sprint: devex #166 May 2019 > LiveReload does not work with OpenShift3 server adapter > ------------------------------------------------------- > > Key: JBIDE-26599 > URL: https://issues.jboss.org/browse/JBIDE-26599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, openshift > Affects Versions: 4.11.0.Final > Environment: oc cluster up 3.11 from Fedora repo > Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre... > Devstudio + installed livereload: > Version: 12.11.0.GA > Build id: GA-v20190321-1925-B4244 > Build date: 20190321-1925 > JDK 11.02 + F29 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Critical > Fix For: 4.12.0.AM1 > > Attachments: image-2019-03-27-10-30-34-801.png > > > If I try to directly connect to livereload server there is an error message: > {code:java} > HTTP ERROR 500 > Problem accessing /. Reason: > Server Error > Caused by: > java.lang.IllegalArgumentException: Invalid URI host: null (authority: null) > at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506) > at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491) > at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449) > at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438) > at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) > at org.eclipse.jetty.server.Server.handle(Server.java:502) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267) > at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) > at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2019