February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21640) Allow deploy-only server to support profiles to more properly support server-specific behavior

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21640: ----------------------------------- Summary: Allow deploy-only server to support profiles to more properly support server-specific behavior Key: JBIDE-21640 URL: https://issues.jboss.org/browse/JBIDE-21640 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Reporter: Rob Stryker In order to get deploy-only server to add .dodeploy markers, we'd need to allow some mechanism for the users to change such setting. However, once support for .dodeploy is added, support for .deployed (and others) would also be requested. Basically, what's being requested here is support for wildfly-style publishing behavior vs standard publishing behavior. -- 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21637?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21637: -------------------------------- Fix Version/s: LATER > 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 > Fix For: LATER > > > 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] (JBIDE-21638) Show in Web Browser does not work with deploy-only server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21638?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21638: ------------------------------------- I've opened a subtask which is a pre-req. > 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 > Fix For: LATER > > > 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-21639) Allow users to set a web port for deploy-only server

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21639: ----------------------------------- Summary: Allow users to set a web port for deploy-only server Key: JBIDE-21639 URL: https://issues.jboss.org/browse/JBIDE-21639 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Affects Versions: LATER Reporter: Rob Stryker Deploy-only server cannot support show-in web browser for servers that don't use port 80 unless the UI provides a way for the users to override such a setting in the server editor. -- 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21638?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21638: -------------------------------- Fix Version/s: LATER > 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 > Fix For: LATER > > > 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] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-482 at 2/3/16 11:25 AM: ----------------------------------------------------------- The last of the components are now updated. The only remaining components, ESB and jBPM3 are no longer being built (legacy only) and will be deprecated soon. !lic1.png|thumbnail! was (Author: pleacu): The last of the components are now updated. The only remaining components, ESB and jBPM3 are no longer being built (legacy only) and will be deprecated soon. > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png, lic1.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-482. ------------------------------ Resolution: Done The last of the components are now updated. The only remaining components, ESB and jBPM3 are no longer being built (legacy only) and will be deprecated soon. > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png, lic1.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-482: ----------------------------- Attachment: lic1.png > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png, lic1.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- 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 Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21590: ---------------------------------- Attachment: video.ogg-1.ogv At first I refreshed connection to show that the project is there after creation and then after I deleted it I selected Refresh context menu on it again to show that it was deleted and it is not supposed to be shown. Then I demonstrated clear use case - create, refresh connection (bcs of other GTK 3 issue when a new project is shown as blank tree item), deleted connection and it was there. After refreshing of a connection, the project disappeared. > 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 > > Attachments: video.ogg-1.ogv > > > 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] (JBTIS-484) Teiid Designer - - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-484?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-484. ------------------------------ Resolution: Done Latest TD 10.0.0.beta2 fixes the issue. > Teiid Designer - - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------------------- > > Key: JBTIS-484 > URL: https://issues.jboss.org/browse/JBTIS-484 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: teiid > Reporter: Paul Leacu > Assignee: Barry LaFond > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: lic1.png, td1.png > > > Please make sure that Teiid Designer is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- 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