February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21637) Deploy-only does not create .dodeploy marker

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21637?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21637: ------------------------------------- I'm sorry but I simply disagree. This shouldn't work as you're expecting it to. The deploy-only server is intended to be 100% agnostic of individual app-server behaviors. No other app-servers require a .dodeploy marker, and so that simply isn't part of the logic. Similarly, the deploy-only server also doesn't do JMX requests or management requests to see if the module was properly published. The intention of the deploy-only server is simply to create the war, in either exploded or zipped format, in a given folder, for users to potentially copy/paste, scp, rsync, or do whatever else. The deploy-only server also has support for zipping, which the user can configure. The only thing the deploy-only server even mentions that might make it seem jboss-specific is some text on the deployments tab, and that is only because the work to change some of the labels / options was more than I thought was reasonable at the time. Question: If the deploy-only server is expected to place a .dodeploy marker, is it also expected to read the resultant markers for a .deployed? How would this function when used against a tomcat server? Or a glassfish server? Or a fuse server? Clearly placing a .dodeploy marker is not reasonable in 90% of the different possibilities for the deploy-only server is likely to be used. > Deploy-only does not create .dodeploy marker > -------------------------------------------- > > Key: JBIDE-21637 > URL: https://issues.jboss.org/browse/JBIDE-21637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > > When you create a deploy-only server adapter, point it to a deployment dir of a running WildFly server and then deploy a project (exploded war, which is the default), the server will say: > {code} > 14:17:45,258 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0004: Found jboss-kitchensink.war in deployment directory. To trigger deployment create a file called jboss-kitchensink.war.dodeploy > {code} > I'm not exactly sure if the deploy-only server adapter should do this or not - how can it know if you want it or not. But Max says it should work and is a bug if it doesn't. > One workaround is to use zipped deployment in the server adapter settings. Another would be to change your server not to require the marker and deploy everything immediately. But it would be best if this just worked without any intervention. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-552: ---------------------------------- Just testing the snapshot build. It runs into the jdk issue but otherwise looks good. I've updated the earlyaccess.properties in the 4.3.mars dir so it should be ready with the next snapshot build. Here's how I ran it: {code} ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-stack/discovery/master/earlyaccess/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-stack/discovery/master/ \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-stack/discovery/master/earlyaccess/ \ -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/discovery/jbosstools-earlyaccess.properties {code} > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-552: ---------------------------------- I've configured http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p2... with these settings: Install targets: * eclipse-jee-mars-2-RC1-linux.gtk.x86.tar.gz * eclipse-platform-4.5.2RC1-linux-gtk.tar.gz Source sites, JBTIS: * http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... * http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... Source sites, JBDSIS: * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/disc... * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/disc... So that's 2 x 2 x 2 = 8 tests to run. > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21590: --------------------------------------- [~mlabuda] Are you able to confirm if the build you tested was at least https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift... which included the PR for JBIDE-21457? Can you provide additional steps or a screen cast demonstrating the behavior as I'm still unable to reproduce. > Explorer: OpenShift connection is not refreshed upon project deletion > --------------------------------------------------------------------- > > Key: JBIDE-21590 > URL: https://issues.jboss.org/browse/JBIDE-21590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.1.CR1 > > > Upon deletion of a project under a connection in OpenShift explorer view, the deleted project is still visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Enable debug mode on OpenShift servers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21625: -------------------------------- Description: Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes (was: Need to easily enable debug mode on EAP/Node images) > Enable debug mode on OpenShift servers > -------------------------------------- > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Priority: Critical > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21331) Connection wizard: it looks as if the wizard is creating new connection instances several times

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21331?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21331: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.CR1) > Connection wizard: it looks as if the wizard is creating new connection instances several times > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-21331 > URL: https://issues.jboss.org/browse/JBIDE-21331 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.4.x > > > The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification) > {code:title=ConnctionWizardPageModel} > private void initEditConnection(IConnection connection) { > this.selectedConnection = connection; > this.connection = connection.clone(); > ... > {code} > {code:title=ConnctionWizardPageModel} > public IStatus connect() { > ... > try { > this.connection = createConnection(); > ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20587) IClient calls are executed in UI thread

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20587?page=com.atlassian.jira.plugi... ] Jeff Cantrill closed JBIDE-20587. --------------------------------- Resolution: Cannot Reproduce Closing at [~rawagner] suggestions as we may have already resolved this in one of our many refactorings. > IClient calls are executed in UI thread > --------------------------------------- > > Key: JBIDE-20587 > URL: https://issues.jboss.org/browse/JBIDE-20587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Rastislav Wagner > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > org.jboss.tools.openshift.core.connection.Connection is using UI thread while executing calls to IClient. Some of these calls may take longer time (for example getting logs) thus should not be running in UI thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21638) Show in Web Browser does not work with deploy-only server

by Martin Malina (JIRA)

Martin Malina created JBIDE-21638: ------------------------------------- Summary: Show in Web Browser does not work with deploy-only server Key: JBIDE-21638 URL: https://issues.jboss.org/browse/JBIDE-21638 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.1.Beta2 Reporter: Martin Malina Assignee: Rob Stryker When you start a wildfly server from CLI and then create a deploy-only server in Eclipse and point it to your server's dir, the server adapter in Servers view should allow Show In -> Web Browser. Currently is disabled for me. Also, when you deploy an app, you should be able to do Show In -> Web Browser on the module. Currently this is also disabled for me. According to Max this should definitely work. As is also seen in his demo here: https://www.youtube.com/watch?v=ng6jlGTfETA#t=7h05m40s -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21637) Deploy-only does not create .dodeploy marker

by Martin Malina (JIRA)

Martin Malina created JBIDE-21637: ------------------------------------- Summary: Deploy-only does not create .dodeploy marker Key: JBIDE-21637 URL: https://issues.jboss.org/browse/JBIDE-21637 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.1.Beta2 Reporter: Martin Malina Assignee: Rob Stryker When you create a deploy-only server adapter, point it to a deployment dir of a running WildFly server and then deploy a project (exploded war, which is the default), the server will say: {code} 14:17:45,258 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0004: Found jboss-kitchensink.war in deployment directory. To trigger deployment create a file called jboss-kitchensink.war.dodeploy {code} I'm not exactly sure if the deploy-only server adapter should do this or not - how can it know if you want it or not. But Max says it should work and is a bug if it doesn't. One workaround is to use zipped deployment in the server adapter settings. Another would be to change your server not to require the marker and deploy everything immediately. But it would be best if this just worked without any intervention. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3585) Update support matrix to include OS X El Capitan (10.11)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3585?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3585. ------------------------------- Closing. > Update support matrix to include OS X El Capitan (10.11) > -------------------------------------------------------- > > Key: JBDS-3585 > URL: https://issues.jboss.org/browse/JBDS-3585 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.Beta2 > > > OS X El Capitan 10.11 was released in autumn 2015 and we actually tested JBDS 9.0 with it already, but it was too late to change the support matrix. So let's do it for JBDS 9.1. > I suggest to have the latest two versions for JBDS 9.1, i.e. Yosemite and El Capitan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016