April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-9563. ---------------------------------------- Fix Version/s: 4.2.0.Final Resolution: Done marking this as resolved against 4.2.0.Final where we added WF 8.2 support. Thanks for verifying [~mmalina] and Happy Birthday :) > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.2.0.Final > > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9563: -------------------------------------- And BTW I did want to check if WildFly just is set up for jsp devel mode by default, but I couldn't find it in standalone.xml and then I realized there is Undertow there, so it's all different. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9563. -------------------------------- Closing again. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina resolved JBIDE-9563. ---------------------------------- Resolution: Done Resolving again. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9563: -------------------------------------- ok, so indeed it seems to have been fixed. I checked these three servers with JBDS 8.1.0.GA: JBoss AS 7.1.1 - hot deployment does not work - once you change the config according to AS7-659 (jsp devel mode) it works JBoss EAP 6.3.0 - same as above - hot deployment does not work - once I changed the config to jsp devel mode, it worked WildFly 8.2 - hot deployment works out of the box To be clear, this is what I did: 1. Set up a server in JBDS using runtime detection 2. Start the server 3. Deploy a dynamic web project with a jsp file 4. Check the jsp page in a browser 5. Change some text in the jsp, save 6. Check the jsp page in a browser again Assert: Is the change visible in the browser? So it seems all is good then. > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19476) Add label validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19476: ------------------------------------------ [~jcantrill] Can you please add steps so that QE [~mlabuda] can reproduce and verify this? > Add label validation > -------------------- > > Key: JBIDE-19476 > URL: https://issues.jboss.org/browse/JBIDE-19476 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19476) Add label validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19476: ------------------------------------------ corrected minors, merged and pushed to upstream/master > Add label validation > -------------------- > > Key: JBIDE-19476 > URL: https://issues.jboss.org/browse/JBIDE-19476 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-19291 at 4/29/15 5:39 AM: ---------------------------------------------------------------- I can still see this in my installation of JBDS 9.0.0.Alpha2 BYOE inside Eclipse Mars M6. So reopening. You might prefer reopening the other JIRA, but this one accurately shows the error message. Edit: Same thing happens in nightly installed today. was (Author: mmalina): I can still see this in my installation of JBDS 9.0.0.Alpha2 BYOE inside Eclipse Mars M6. So reopening. You might prefer reopening the other JIRA, but this one accurately shows the error message. > "Unable to execute early startup code ..." exception after starup. > ------------------------------------------------------------------ > > Key: JBIDE-19291 > URL: https://issues.jboss.org/browse/JBIDE-19291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > After startup in error log there is this error: > {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19590: --------------------------------------------- sounds good! > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19190: --------------------------------------------- I thought we said we would keep as is for now and then do the extraction when needed ? I would say close this issue as done and add whatever cleanup is needed when JBIDE-15481 gets done ? > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 April 2015