September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-13663) Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13663?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13663: ------------------------------------------ This issue went unvalid when we added a commit dialog when pushing: JBIDE-10541. We're not automatically committing any more, we always let the user decide what files he wants to add/commit and push. > Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13663 > URL: https://issues.jboss.org/browse/JBIDE-13663 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Fix For: 4.2.x > > Attachments: push-local-commit.png > > > usecase: > EXECUTE: Create openshift project > EXECUTE: Make sure all is committed and Pushed. > EXECUTE: Edit an existing committed file - commit it. > EXECUTE: Add a "xyz.log" file that is not to be committed. > EXECUTE: Publish to server. > ASSERT: no message about dirty changes, everything should be committed. Only message about push is missing. > EXECUTE: Wait for publish to finish. > ASSERT: "xyz.log" should *not* be pushed nor committed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18248) Upgrade .adoc files after upgrade to asciidoctor 1.5.0

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-18248: ------------------------------------- Summary: Upgrade .adoc files after upgrade to asciidoctor 1.5.0 Key: JBIDE-18248 URL: https://issues.jboss.org/browse/JBIDE-18248 Project: Tools (JBoss Tools) Issue Type: Task Components: website Affects Versions: 4.2.0.Beta3 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.0.CR1 tl;dr: replace {+} with {`} to render HTML {<pre>} blocks see discussion on http://discuss.asciidoctor.org/An-important-syntax-change-coming-in-1-5-0... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18186) XMLMemento cannot parse a file where first node is a comment

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18186?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18186: ------------------------------------- I don't think such a UI interaction case exists. Sorry. > XMLMemento cannot parse a file where first node is a comment > ------------------------------------------------------------ > > Key: JBIDE-18186 > URL: https://issues.jboss.org/browse/JBIDE-18186 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > The class XMLMemento, originally taken from upstream eclipse, is unable to parse a xml input stream if the first node is not an Element. This restriction should be worked around. This is a patch needed by astools for solving /JBIDE-18130 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18239: --------------------------------------------- it is TP for the updatesite created. It ensures we list the actual updatesite where things was fetched from and the exact IU and versions. For stuff already in jbosstools we don't need this since already part of build. I'm not looking to replace or change the use of the TP - i'm suggesting the creation of the update site(s) could be done so we do not need to list the exact versions of JBoss Tools provided content. > Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18239 > URL: https://issues.jboss.org/browse/JBIDE-18239 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, discovery, updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.). > We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG. > These would be produced as new zips using the JBT aggregate builder: > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ > Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15517) Explorer: There's currently no way to see that an appliaction is scaled

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15517?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15517: ------------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Explorer: There's currently no way to see that an appliaction is scaled > ----------------------------------------------------------------------- > > Key: JBIDE-15517 > URL: https://issues.jboss.org/browse/JBIDE-15517 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.x > > > There's currently no way for the user to see that an application is scaled. > We should show this to the user via decorations in the OpenShift Explorer and also in the application details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15495) Server Adapter: publish locks the whole workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15495: ------------------------------------- Assignee: (was: Andre Dietisheim) > Server Adapter: publish locks the whole workspace > ------------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Labels: server_adapter > Fix For: 4.2.x > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15495) Server Adapter: publish locks the whole workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15495: ------------------------------------- Issue Type: Enhancement (was: Feature Request) > Server Adapter: publish locks the whole workspace > ------------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: server_adapter > Fix For: 4.2.x > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16509) Application wizard: Embedded cartridges should get verified when I select "Enable Scaling" AFTER I selected them

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16509?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16509: ------------------------------------- Summary: Application wizard: Embedded cartridges should get verified when I select "Enable Scaling" AFTER I selected them (was: Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them) > Application wizard: Embedded cartridges should get verified when I select "Enable Scaling" AFTER I selected them > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16509 > URL: https://issues.jboss.org/browse/JBIDE-16509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Priority: Minor > Labels: application_wizard > Fix For: 4.2.x > > > We currently only check the validity of embedded cartridges when you check/uncheck them. Since there are cartridges which are not valid in scaled apps (ex. phpmyadmin), we should also check the embedded cartridges when one hits the "Enable Scaling" checkbox. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13862) Server adapter wizard: When creating adapter manually, the deploying project should be added automatically

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13862: ------------------------------------- Summary: Server adapter wizard: When creating adapter manually, the deploying project should be added automatically (was: server adapter wizard: When creating adapter manually, the deploying project should be added automatically) > Server adapter wizard: When creating adapter manually, the deploying project should be added automatically > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13862 > URL: https://issues.jboss.org/browse/JBIDE-13862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Priority: Minor > Labels: server_adapter_wizard > Fix For: 4.2.x > > Attachments: server.png, server1.png, server2.png > > > Deploying project is automatically added to OpenShift Server adapter after application import: > * after application import contains the deploying project: !server.png|thumbnail! > When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project: > * !server2.png|thumbnail! *->* !server1.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14322) Application wizard: Displays wrong cloning location when merging into existing project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14322?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14322: ------------------------------------- Summary: Application wizard: Displays wrong cloning location when merging into existing project (was: Application wizard: displays wrong cloning location) > Application wizard: Displays wrong cloning location when merging into existing project > -------------------------------------------------------------------------------------- > > Key: JBIDE-14322 > URL: https://issues.jboss.org/browse/JBIDE-14322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Stefan Bunciak > Labels: application_wizard > Fix For: 4.2.x > > Attachments: clonning.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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