June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi... ] Vsevolod Golovanov commented on JBIDE-20071: -------------------------------------------- Project structure is: * EAR ** EJB ** WAR *** JAR-UI-1 *** JAR-UI-2 (JAR-UIs are in WAR's WEB-INF/lib directory.) Yes, JAR-UIs have: # classes; # JSF/Facelet resources: XHTMLs, images, css, js... Servlets look at JAR-UI's META-INF/web-fragment.xml and combine it with web.xml. JSF looks up resources in META-INF/resources. Changes to classes get applied by Eclipse/JBDS on the fly as usual. But changes to JSF resources don't get picked up. IDE/Tools deploy them, the new files are there, but VFS still returns old files from the temporary directory (more ramblings [here|http://stackoverflow.com/questions/28326523/hot-deploying-resources-...]). I've checked that when placing exploded JAR-UI in WAR/WEB-INF/lib: * server does start; * when changing a JSF resource, and reloading a page, it does use the updated resources. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20018) Eclipse doesn't prompt for workspace

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20018?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20018. ------------------------------ > Eclipse doesn't prompt for workspace > ------------------------------------ > > Key: JBIDE-20018 > URL: https://issues.jboss.org/browse/JBIDE-20018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.3.0.Beta1 > Environment: eclipse mars RC2, JBT 4.3.0.Beta1 > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > I remember we had this [1] issue before, but it is here again. > [1] https://issues.jboss.org/browse/JBIDE-19627 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20015) Properties view: Error when displaying build hook URL for a sti-build config

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20015?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20015. --------------------------------- Verified in JBDS 9.0.0.Beta1a build ID B50. > Properties view: Error when displaying build hook URL for a sti-build config > ---------------------------------------------------------------------------- > > Key: JBIDE-20015 > URL: https://issues.jboss.org/browse/JBIDE-20015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Assignee: Jeff Cantrill > Priority: Critical > Labels: respin-a > Fix For: 4.3.0.Beta1 > > Attachments: sti-error.png > > > Description of problem: > When retrieve the build hook URL for a sti-build config in jbt, it always failed with error. > Version-Release number of selected component (if applicable): > openshift v3 plug: 3.0.0.Beta2-v20150609-2129-B831 > How reproducible: > Always > Steps to Reproduce: > 1.Add a build config from the command line using 'osc' that has a build trigger > 2.In eclipse, Open the OpenShift explorer view and expand the project to view the buildconfig > 3.In eclipse, Click the buildconfig > 4.Verify in the property pane that the build hook url matches what is returned from running the command 'osc describe buildconfig <buildconfigname> -n <projectname>' > Actual results: > 4. When open the property pane. It meet error. > error info: An error has occurred. See error log for more details. > No enum constant com.openshift.restclient.model.build.BuildStrategyType.Source > Expected results: > 4. Should show the build hook url well. > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20068) Show in Web Browser via Livereload Server doesn't work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20068?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-20068: ------------------------------------- Assignee: Fred Bricon (was: Xavier Coulon) Fred, can you review those 2 PR please ? > Show in Web Browser via Livereload Server doesn't work > ------------------------------------------------------ > > Key: JBIDE-20068 > URL: https://issues.jboss.org/browse/JBIDE-20068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta1-v20150614-0409-B50, Fedora 21, Oracle Java 1.8, JBoss AS 7.1.1.Final > Reporter: Vlado Pakan > Assignee: Fred Bricon > Priority: Critical > Labels: respin-b > Fix For: 4.3.0.Beta1 > > > 1. Create HTML5 project via JBoss Central > 2. Run it on JBossAS 7.1.1.Final > 3. Select this server in Server View > 4. Expand server and select HTML5 project > 5. Click on context menu Show In > Web Browser via Livereload Server > ERROR: Browser displays HTML error 500. Ur in Web Browser is: http://localhost:54437/jboss-as-kitchensink-html5-mobile > App is working when Web Browser is pointed to http://localhost:8080/jboss-as-kitchensink-html5-mobile/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20068) Show in Web Browser via Livereload Server doesn't work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20068?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20068: --------------------------------------- The message that appears on the user's web browser is: {code} Problem accessing /jboss-as-kitchensink-html5-mobile. Reason: java.lang.NoClassDefFoundError: org/eclipse/jetty/util/thread/SpinLock {code} > Show in Web Browser via Livereload Server doesn't work > ------------------------------------------------------ > > Key: JBIDE-20068 > URL: https://issues.jboss.org/browse/JBIDE-20068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta1-v20150614-0409-B50, Fedora 21, Oracle Java 1.8, JBoss AS 7.1.1.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Labels: respin-b > Fix For: 4.3.0.Beta1 > > > 1. Create HTML5 project via JBoss Central > 2. Run it on JBossAS 7.1.1.Final > 3. Select this server in Server View > 4. Expand server and select HTML5 project > 5. Click on context menu Show In > Web Browser via Livereload Server > ERROR: Browser displays HTML error 500. Ur in Web Browser is: http://localhost:54437/jboss-as-kitchensink-html5-mobile > App is working when Web Browser is pointed to http://localhost:8080/jboss-as-kitchensink-html5-mobile/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20068) Show in Web Browser via Livereload Server doesn't work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20068?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20068: --------------------------------------- The LiveReload plugins' AMNIFEST.MF were still requiring {{jetty-* 9.2.5}} bundles while they should have explicitely specified {{9.2.10}}. As a result, DevStudio ships with a mix of 9.2.9 and 9.2.10 bundles, and one of them {{jetty-util 9.2.9}} misses a class that's only available in version {{9.2.10}} The problem does not happen on dev machine using the JBoss Tools TP since it contains all the plugins This relates to https://github.com/jbosstools/jbosstools-target-platforms/pull/147 > Show in Web Browser via Livereload Server doesn't work > ------------------------------------------------------ > > Key: JBIDE-20068 > URL: https://issues.jboss.org/browse/JBIDE-20068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta1-v20150614-0409-B50, Fedora 21, Oracle Java 1.8, JBoss AS 7.1.1.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Labels: respin-b > Fix For: 4.3.0.Beta1 > > > 1. Create HTML5 project via JBoss Central > 2. Run it on JBossAS 7.1.1.Final > 3. Select this server in Server View > 4. Expand server and select HTML5 project > 5. Click on context menu Show In > Web Browser via Livereload Server > ERROR: Browser displays HTML error 500. Ur in Web Browser is: http://localhost:54437/jboss-as-kitchensink-html5-mobile > App is working when Web Browser is pointed to http://localhost:8080/jboss-as-kitchensink-html5-mobile/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20068) Show in Web Browser via Livereload Server doesn't work

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20068?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20068: ---------------------------------------- It seems like you livereload bundle is missing some necessary jetty dependencies in order to work well. > Show in Web Browser via Livereload Server doesn't work > ------------------------------------------------------ > > Key: JBIDE-20068 > URL: https://issues.jboss.org/browse/JBIDE-20068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Beta1 > Environment: JBDS 9.0.0.Beta1-v20150614-0409-B50, Fedora 21, Oracle Java 1.8, JBoss AS 7.1.1.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Labels: respin-b > Fix For: 4.3.0.Beta1 > > > 1. Create HTML5 project via JBoss Central > 2. Run it on JBossAS 7.1.1.Final > 3. Select this server in Server View > 4. Expand server and select HTML5 project > 5. Click on context menu Show In > Web Browser via Livereload Server > ERROR: Browser displays HTML error 500. Ur in Web Browser is: http://localhost:54437/jboss-as-kitchensink-html5-mobile > App is working when Web Browser is pointed to http://localhost:8080/jboss-as-kitchensink-html5-mobile/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20071: --------------------------------------------- so your jars have the resources not the war ? just want to make sure you actually got that usecase and not just a jar withi classes where exploded wont help with respect to hot reload > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20072) Connection refused exception is not clearly presented to the user

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20072?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20072: ------------------------------------------ [~jcantrill] I would think that having the exception in log is a good thing while maybe we want to improve the error in viewer? > Connection refused exception is not clearly presented to the user > ----------------------------------------------------------------- > > Key: JBIDE-20072 > URL: https://issues.jboss.org/browse/JBIDE-20072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Fix For: 4.3.0.Beta2 > > Attachments: Exception.png > > > Trying to connect using an existing connection to a server that is not available does not display nice to the user and the console logs show: > {code} > com.openshift.restclient.OpenShiftException: Exception getting the resource > at com.openshift.internal.restclient.DefaultClient.handleHttpClientException(DefaultClient.java:396) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:241) > at com.openshift.internal.restclient.DefaultClient.getCurrentUser(DefaultClient.java:402) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:93) > at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:407) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:210) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:200) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:263) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:335) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.restclient.http.HttpClientException: java.net.ConnectException: Connection refused > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:217) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:151) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:130) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:92) > at com.openshift.internal.restclient.DefaultClient.getVersion(DefaultClient.java:307) > at com.openshift.internal.restclient.DefaultClient.getOpenShiftVersions(DefaultClient.java:283) > at com.openshift.internal.restclient.DefaultClient.getOpenShiftAPIVersion(DefaultClient.java:297) > at com.openshift.internal.restclient.DefaultClient.getTypeMappings(DefaultClient.java:332) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:232) > ... 9 more > Caused by: java.net.ConnectException: Connection refused > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1889) > at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1884) > at java.security.AccessController.doPrivileged(Native Method) > at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1883) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1456) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:200) > ... 17 more > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:656) > at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) > at sun.net.NetworkClient.doConnect(NetworkClient.java:180) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:527) > at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:275) > at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:147) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20066) openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20066?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20066: ------------------------------------ Tycho version used shouldn't matter, as 0.22 and 0.23 are mostly compatible. And yes, the job sets jbosstools_site_stream = 4.3.mars so upstream deps were the correct ones from the 4.3.mars branch, not the master stuff. > openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2 > --------------------------------------------------------- > > Key: JBIDE-20066 > URL: https://issues.jboss.org/browse/JBIDE-20066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > Current Beta1a update site includes openshift plugins in version Beta2: > http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/ > {code} > org.jboss.tools.openshift.egit.integration.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools > org.jboss.tools.openshift.egit.integration.feature.source 3.0.0.Beta2-v20150613-0235-B25 > org.jboss.tools.openshift.express.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools > org.jboss.tools.openshift.express.feature.source 3.0.0.Beta2-v20150613-0235-B25 > org.jboss.tools.openshift.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools > org.jboss.tools.openshift.feature.source 3.0.0.Beta2-v20150613-0235-B25 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015