March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (LOCUS-39) Consider using Eclipse Bundle Recipes (EBR)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-39?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-39: ---------------------------- Fix Version/s: LATER > Consider using Eclipse Bundle Recipes (EBR) > ------------------------------------------- > > Key: LOCUS-39 > URL: https://issues.jboss.org/browse/LOCUS-39 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > Fix For: LATER > > > I've had the opportunity to attend a presentation about EBR, a technology to turn plain jars from Maven as OSGi bunle (generating MANIFEST, source bundle, p2 metadata...). I have the impression that it fits quite nicely most of our Locus bundles, we should consider adopting it. > More background about EBR: > * http://www.eclipse.org/ebr > * http://de.slideshare.net/guw/tasty-recipes-for-osgi-bundles -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-47) Locus plug-ins have errors after importing into workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-47?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-47: ---------------------------- Fix Version/s: LATER > Locus plug-ins have errors after importing into workspace > --------------------------------------------------------- > > Key: LOCUS-47 > URL: https://issues.jboss.org/browse/LOCUS-47 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: LATER > > > There are several problems with locus plrojects after importing them into workspace as maven projects: > 1. plugins/pom.xml appears in workspace with name "plugins" and it could conflict with other imported modules because we have the same names all over jbosstools; > 2. org.jboss.tools.locus.mockito uses restricted API and JDT reports it as Error; > 3. org.jboss.tools.locus.dmr export packages that created during maven build and reported as missing in eclipse. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21970) Allow user to turn on/off showing console when output changes

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-21970: ------------------------------------- Summary: Allow user to turn on/off showing console when output changes Key: JBIDE-21970 URL: https://issues.jboss.org/browse/JBIDE-21970 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift, server Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Xavier Coulon Priority: Critical Fix For: 4.3.1.CR1, 4.4.0.Alpha1 At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-47) Locus plug-ins have errors after importing into workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-47?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-47: ---------------------------- Fix Version/s: (was: 1.7.0) > Locus plug-ins have errors after importing into workspace > --------------------------------------------------------- > > Key: LOCUS-47 > URL: https://issues.jboss.org/browse/LOCUS-47 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: LATER > > > There are several problems with locus plrojects after importing them into workspace as maven projects: > 1. plugins/pom.xml appears in workspace with name "plugins" and it could conflict with other imported modules because we have the same names all over jbosstools; > 2. org.jboss.tools.locus.mockito uses restricted API and JDT reports it as Error; > 3. org.jboss.tools.locus.dmr export packages that created during maven build and reported as missing in eclipse. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21970) Allow user to turn on/off showing console when output changes

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21970?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21970: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > Allow user to turn on/off showing console when output changes > ------------------------------------------------------------- > > Key: JBIDE-21970 > URL: https://issues.jboss.org/browse/JBIDE-21970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-47) Locus plug-ins have errors after importing into workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-47?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-47: ---------------------------- Fix Version/s: 1.7.0 (was: 1.5.0) > Locus plug-ins have errors after importing into workspace > --------------------------------------------------------- > > Key: LOCUS-47 > URL: https://issues.jboss.org/browse/LOCUS-47 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 1.7.0 > > > There are several problems with locus plrojects after importing them into workspace as maven projects: > 1. plugins/pom.xml appears in workspace with name "plugins" and it could conflict with other imported modules because we have the same names all over jbosstools; > 2. org.jboss.tools.locus.mockito uses restricted API and JDT reports it as Error; > 3. org.jboss.tools.locus.dmr export packages that created during maven build and reported as missing in eclipse. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21969: ------------------------------------- Description: steps to reproduce: # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) # EXEC: launch New OpenShift 3 Server Adapter wizard # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) # EXEC: create the adapter by picking service, local project etc. # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser # ASSERT: Route chooser shows up (since there are several routes available) Result: There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project) !route-chooser.png! was: steps to reproduce: # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) # EXEC: launch New OpenShift 3 Server Adapter wizard # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) # EXEC: create the adapter by picking service, local project etc. # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser # ASSERT: Route chooser shows up (since there are several routes available) Result: !route-chooser.png! There's no way to permanently choose a route. The route chooser will always show up > Show in Browser: route chooser should allow to user to choose route permanently > ------------------------------------------------------------------------------- > > Key: JBIDE-21969 > URL: https://issues.jboss.org/browse/JBIDE-21969 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Attachments: route-chooser.png > > > steps to reproduce: > # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace > # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) > # EXEC: launch New OpenShift 3 Server Adapter wizard > # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) > # EXEC: create the adapter by picking service, local project etc. > # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser > # ASSERT: Route chooser shows up (since there are several routes available) > Result: > There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project) > !route-chooser.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21969: ------------------------------------- Attachment: route-chooser.png > Show in Browser: route chooser should allow to user to choose route permanently > ------------------------------------------------------------------------------- > > Key: JBIDE-21969 > URL: https://issues.jboss.org/browse/JBIDE-21969 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Attachments: route-chooser.png > > > steps to reproduce: > # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace > # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) > # EXEC: launch New OpenShift 3 Server Adapter wizard > # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) > # EXEC: create the adapter by picking service, local project etc. > # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser > # ASSERT: Route chooser shows up (since there are several routes available) > Result: > !route-chooser.png! > There's no way to permanently choose a route. The route chooser will always show up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21969: ---------------------------------------- Summary: Show in Browser: route chooser should allow to user to choose route permanently Key: JBIDE-21969 URL: https://issues.jboss.org/browse/JBIDE-21969 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Andre Dietisheim steps to reproduce: # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project) # EXEC: launch New OpenShift 3 Server Adapter wizard # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected) # EXEC: create the adapter by picking service, local project etc. # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser # ASSERT: Route chooser shows up (since there are several routes available) Result: !route-chooser.png! There's no way to permanently choose a route. The route chooser will always show up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3711) JBDS setup is called after installation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3711?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3711: -------------------------------- Fix Version/s: 9.1.0.CR1 > JBDS setup is called after installation > --------------------------------------- > > Key: JBDS-3711 > URL: https://issues.jboss.org/browse/JBDS-3711 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since the JDK path is otherwise already set during the headless installation. -- 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 March 2016