January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21526) Deploy from existing project git constraints are too stringent

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21526?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21526. ----------------------------------- Resolution: Done > Deploy from existing project git constraints are too stringent > -------------------------------------------------------------- > > Key: JBIDE-21526 > URL: https://issues.jboss.org/browse/JBIDE-21526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > > There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying: > - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted > - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21494) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21494?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-21494. ------------------------------------------ Resolution: Done > For JBIDE 4.3.1.Beta2: Code Freeze + Branch [VPE] > ------------------------------------------------- > > Key: JBIDE-21494 > URL: https://issues.jboss.org/browse/JBIDE-21494 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta2 > > > For JBIDE 4.3.1.Beta2 [VPE]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta2x > git push origin jbosstools-4.3.1.Beta2x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and > * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21340) Deploy from existing project git constraints are too stringent

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21340?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21340. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > Deploy from existing project git constraints are too stringent > -------------------------------------------------------------- > > Key: JBIDE-21340 > URL: https://issues.jboss.org/browse/JBIDE-21340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta2 > > > There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying: > - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted > - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21526) Deploy from existing project git constraints are too stringent

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21526: ------------------------------------- Summary: Deploy from existing project git constraints are too stringent Key: JBIDE-21526 URL: https://issues.jboss.org/browse/JBIDE-21526 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Fred Bricon Assignee: Andre Dietisheim Fix For: 4.3.1.Beta2 There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying: - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21347. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta2 > > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt commented on JBTIS-471: ------------------------------------------ OK, I changed the Neon version to 1.1.0 - HAPPY NOW??? ;) Just to clarify: Mars is still 1.0.5 > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21349) Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21349?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21349. --------------------------------- > Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21349 > URL: https://issues.jboss.org/browse/JBIDE-21349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.Beta2 > > Attachments: browse-workspace.png > > > how to reproduce: > # EXEC: File > New > Server > OpenShift 3 > # ASSERT: connection page shows up > # EXEC: provide connection and hit Next > # ASSERT: you get to the server settings page > # EXEC: hit "Workspace..." to the right of "Source Path" > !browse-workspace.png! > Result: > You get a file-chooser that defaults to the workspace and lets you choose files/directories > Expected Result: > You should get a dialog where you can pick a workspace project -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21525) context menu of openshift is not using global commands like delete or properties

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21525?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21525. ----------------------------------- Resolution: Done > context menu of openshift is not using global commands like delete or properties > -------------------------------------------------------------------------------- > > Key: JBIDE-21525 > URL: https://issues.jboss.org/browse/JBIDE-21525 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Delete Project, resource etc. should use the normal Delete command. It seems we've created custom commands and UI for it instead of just using the default Delete command as used in other context menus. > Similar we dont seem to use standard Properties > see https://wiki.eclipse.org/Menu_Contributions/Problems_View_Example on how to use org.eclipse.ui.edit.delete etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21525) context menu of openshift is not using global commands like delete or properties

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21525: ------------------------------------- Summary: context menu of openshift is not using global commands like delete or properties Key: JBIDE-21525 URL: https://issues.jboss.org/browse/JBIDE-21525 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 4.3.1.Beta2 Delete Project, resource etc. should use the normal Delete command. It seems we've created custom commands and UI for it instead of just using the default Delete command as used in other context menus. Similar we dont seem to use standard Properties see https://wiki.eclipse.org/Menu_Contributions/Problems_View_Example on how to use org.eclipse.ui.edit.delete etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20603) context menu of openshift is not using global commands like delete or properties

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20603?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20603. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > context menu of openshift is not using global commands like delete or properties > -------------------------------------------------------------------------------- > > Key: JBIDE-20603 > URL: https://issues.jboss.org/browse/JBIDE-20603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Delete Project, resource etc. should use the normal Delete command. It seems we've created custom commands and UI for it instead of just using the default Delete command as used in other context menus. > Similar we dont seem to use standard Properties > see https://wiki.eclipse.org/Menu_Contributions/Problems_View_Example on how to use org.eclipse.ui.edit.delete etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016