April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ] Rafael Benevides commented on JBIDE-22128: ------------------------------------------ The java project was imported using "Import Maven project" from https://github.com/redhat-helloworld-msa/hello The pom.xml contains the openshift profile that creates the ROOT.war[1] which seems to be a common approach. [1]https://github.com/redhat-helloworld-msa/hello/blob/master/pom.xml#L181... > Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile > --------------------------------------------------------------------------- > > Key: JBIDE-22128 > URL: https://issues.jboss.org/browse/JBIDE-22128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > > I have a Java project with an "openshift" maven profile that creates a ROOT.war > When I create a "Server Adapter", the openshift plugins deploys the name of the project.war > The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ] Rafael Benevides edited comment on JBIDE-22128 at 4/6/16 6:06 PM: ------------------------------------------------------------------ The java project was imported using "Import Maven project" from https://github.com/redhat-helloworld-msa/hello The pom.xml contains the openshift profile that creates the ROOT.war[1] which seems to be a common approach. [1] https://github.com/redhat-helloworld-msa/hello/blob/master/pom.xml#L181-L194 was (Author: rafabene): The java project was imported using "Import Maven project" from https://github.com/redhat-helloworld-msa/hello The pom.xml contains the openshift profile that creates the ROOT.war[1] which seems to be a common approach. [1]https://github.com/redhat-helloworld-msa/hello/blob/master/pom.xml#L181... > Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile > --------------------------------------------------------------------------- > > Key: JBIDE-22128 > URL: https://issues.jboss.org/browse/JBIDE-22128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > > I have a Java project with an "openshift" maven profile that creates a ROOT.war > When I create a "Server Adapter", the openshift plugins deploys the name of the project.war > The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-20387: --------------------------------------- This and some other FreeMarker IDE plugin fixes remain unmerged after 4 months now. Is there any way this process can be helped? > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.3.0.Beta2 > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.x > > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22128: ------------------------------------- Please provide exact steps to reproduce. How did you create the openshift project? > Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile > --------------------------------------------------------------------------- > > Key: JBIDE-22128 > URL: https://issues.jboss.org/browse/JBIDE-22128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > > I have a Java project with an "openshift" maven profile that creates a ROOT.war > When I create a "Server Adapter", the openshift plugins deploys the name of the project.war > The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22129: -------------------------------- Fix Version/s: 4.3.1.CR1 > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22129 > URL: https://issues.jboss.org/browse/JBIDE-22129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.3.1.CR1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22129: -------------------------------- Labels: respin-b (was: ) > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22129 > URL: https://issues.jboss.org/browse/JBIDE-22129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.3.1.CR1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22129: ----------------------------------- Summary: Watches should not try to reconnect when a project has been deleted Key: JBIDE-22129 URL: https://issues.jboss.org/browse/JBIDE-22129 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22129: ----------------------------------- Assignee: Jeff Cantrill > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22129 > URL: https://issues.jboss.org/browse/JBIDE-22129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21112) D&D install is not working with Internet explorer 11 and MS Edge 20

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21112?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-21112: ------------------------------------- Assignee: Snjezana Peco > D&D install is not working with Internet explorer 11 and MS Edge 20 > ------------------------------------------------------------------- > > Key: JBIDE-21112 > URL: https://issues.jboss.org/browse/JBIDE-21112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Affects Versions: 4.3.0.Final > Environment: Windows 10 > Microsoft Edge 20.10240.16384.0 > Microsoft Internet Explorer 11.0.10240.16384 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: LATER > > > D&D (JBIDE-15499) links to Central from Edge or MS Explorer is not working. > Dropping the same link from Chrome triggers the installation. > The same issue is effecting Eclipse marketplace client. I've opened bug there: https://bugs.eclipse.org/bugs/show_bug.cgi?id=482588 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22126) OpenShift tooling - New application buttons are truncated

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22126?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22126 at 4/6/16 3:22 PM: ----------------------------------------------------------------------- On my Ubuntu, the fix of JBIDE-22032 improved these buttons, they were truncated before exactly as shown on the screenshot. The attached pull request checks the required width for the button, and if it is larger than the default width, sets it. I also now applied this method to Server Settings wizard page and editor section since they were not covered by JBIDE-22032 and I have checked that buttons in them remained truncated in my environment. was (Author: scabanovich): On my Ubuntu, the fix of JBIDE-22032 improved these buttons, they were truncated before exactly as shown on the screenshot. The attached pull request checks the required width for the button, and if it is larger than the default width, sets it. > OpenShift tooling - New application buttons are truncated > --------------------------------------------------------- > > Key: JBIDE-22126 > URL: https://issues.jboss.org/browse/JBIDE-22126 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Attachments: openshift_buttons.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2016