November 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-363) Additional user documentation needed to explain/clarify install options

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-363?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-363: ----------------------------- Assignee: Michelle Murray > Additional user documentation needed to explain/clarify install options > ----------------------------------------------------------------------- > > Key: JBTIS-363 > URL: https://issues.jboss.org/browse/JBTIS-363 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Michelle Murray > Fix For: 8.0.0.Beta1 > > > If a user selects to install a subset of the individual components in a package grouping as displayed in JBoss Central - for example, if the user opts to install only the Fuse related items from the "JBoss Integration and SOA Development" group - then JBoss Central will continue to mark that group as not installed. > This behavior is correct, but may cause confusion for users if they expect that installing one component from a group will mark that group as being installed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-350) Missing BPEL source plugins

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-350: -------------------------------- Assignee: Paul Leacu > Missing BPEL source plugins > --------------------------- > > Key: JBTIS-350 > URL: https://issues.jboss.org/browse/JBTIS-350 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > After installing all components included in Beta1 there are only the following souce plugins for BPEL > org.jboss.tools.bpel.runtimes.source_1.2.101.Final-v20140108-1353-B1045.jar > org.switchyard.tools.ui.bpel.source_2.0.0.v20141011-0508-H499-Alpha3.jar > but there are much more BPEL plugins such as > org.eclipse.bpel.ui, org.eclipse.bpel.ui.validator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18794) Move shared properties related to JRE paths and itest.skip into parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18794?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18794: --------------------------------------------- Yes, none of this was *declared* by me. it was found by collaboration between Rob and I to find the best default. Mickael says it is good to have "skips" be default false; I think that depends on the situation. For things related to what tests are run I definitely think it is good to have it be false. But we actually have skipPrivateRequirements default to true because most wont actually have vpn access; I can also see that skipSigning is in here - but that might just be leftovers since signing actually never been used in production. I've left comments in the PR on making the docs/comments a bit more clear/specific. > Move shared properties related to JRE paths and itest.skip into parent pom > -------------------------------------------------------------------------- > > Key: JBIDE-18794 > URL: https://issues.jboss.org/browse/JBIDE-18794 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, server > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Some properties (and maybe the -Pitest profile) in the root of jbosstools-server can eventually be moved into the parent pom for reuse by other projects. > (This was suggested by Max to Rob at some point on 2014/11/20.) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18450) Include EGit 3.5.0 in JBDS 8.0.1 / 8.1 / 9.0 [TBD]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18450?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18450: ------------------------------------------ [~mickael_istria] my guts tell me to use this for 4.3.x, dont touch a floating ship. We'd need extensive testing which I dont think we have the time to do for maintenance. > Include EGit 3.5.0 in JBDS 8.0.1 / 8.1 / 9.0 [TBD] > -------------------------------------------------- > > Key: JBIDE-18450 > URL: https://issues.jboss.org/browse/JBIDE-18450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, target-platform > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > From Andre: > {quote} > I'd argue that since OpenShift is using git our users would benefit from > any improvement in EGit. So big +1 for me! > > You mean +1 for 4.2.0/8.0.0 ? > > If so, do you think you can make extensive testing of this newer EGit > > and evaluate how well it integrates in JBT/JBDS before Thursday ? > yeah, worth it imho (if max agrees). I'll do that. > {quote} > -- http://lists.jboss.org/pipermail/jbosstools-dev/2014-September/009369.html -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18450) Include EGit 3.5.0 in JBDS 8.0.1 / 8.1 / 9.0 [TBD]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18450?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18450: ------------------------------------- Fix Version/s: (was: 4.2.1.Final) > Include EGit 3.5.0 in JBDS 8.0.1 / 8.1 / 9.0 [TBD] > -------------------------------------------------- > > Key: JBIDE-18450 > URL: https://issues.jboss.org/browse/JBIDE-18450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, target-platform > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > From Andre: > {quote} > I'd argue that since OpenShift is using git our users would benefit from > any improvement in EGit. So big +1 for me! > > You mean +1 for 4.2.0/8.0.0 ? > > If so, do you think you can make extensive testing of this newer EGit > > and evaluate how well it integrates in JBT/JBDS before Thursday ? > yeah, worth it imho (if max agrees). I'll do that. > {quote} > -- http://lists.jboss.org/pipermail/jbosstools-dev/2014-September/009369.html -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14818: ------------------------------------------ moved from maintenance to upstream 4.3.x > Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: server_adapter_editor > Fix For: 4.3.x > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Fix Version/s: 4.3.x (was: 4.2.1.Final) > Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: server_adapter_editor > Fix For: 4.3.x > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18827?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18827: ------------------------------------- Sprint: Sprint 20141112 (was: Sprint 20141112, Sprint 20141113) > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-18827 > URL: https://issues.jboss.org/browse/JBIDE-18827 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: Eclipse plugin > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.3.x > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11903) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11903: ------------------------------------------ merged and pushed to upstream/jbosstools-4.2.x (as discussed with [~mlabuda] > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-11903 > URL: https://issues.jboss.org/browse/JBIDE-11903 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta2 > Environment: Eclipse plugin > Reporter: Nam Duong > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.2.1.Final > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11903) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11903: ------------------------------------- Fix Version/s: (was: 4.3.x) > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-11903 > URL: https://issues.jboss.org/browse/JBIDE-11903 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta2 > Environment: Eclipse plugin > Reporter: Nam Duong > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.2.1.Final > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 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 November 2014