[JBoss JIRA] (JBIDE-20500) manage projects cannot edit projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20500?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-20500.
---------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.x)
Assignee: Fred Bricon
Resolution: Out of Date
The "manage projects" link is no longer enabled on projects, only connections, so this makes this issue irrelevant now.
> manage projects cannot edit projects
> ------------------------------------
>
> Key: JBIDE-20500
> URL: https://issues.jboss.org/browse/JBIDE-20500
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> Create project, put name etc.
> Press Finish
> Right click on Project and click Manage Project...
> ASSERT: dialog comes up with the project I selected as the one being managed (it does not)
> ASSERT: I can actually edit/manage the project (I can only add/remove)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-20723) OpenShift 3 application is created even though Cancel button was clicked
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20723?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20723:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> OpenShift 3 application is created even though Cancel button was clicked
> ------------------------------------------------------------------------
>
> Key: JBIDE-20723
> URL: https://issues.jboss.org/browse/JBIDE-20723
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.4.x
>
>
> Once the Finish button in New OpenShift Application wizard is clicked a new application is created no matter what. Even if I click on a Cancel button next to the progress bar of creation process, it looks at first like the process stopped, but it still continues and in few moments a shell with created resources is shown. Can we do something about this? Otherwise cancel button just stop eclipse job and progress bar but it does not do anything more behind it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19604:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> Save Password in New Openshift Application Wizard is annoying
> -------------------------------------------------------------
>
> Key: JBIDE-19604
> URL: https://issues.jboss.org/browse/JBIDE-19604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, x86_64, Open JDK 7
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
> Fix For: 4.4.x
>
> Attachments: openshif-save-password.mp4
>
>
> Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-21657:
---------------------------------------
Is it really something we want to keep? I would say building pr, printing out p2 diff with current aggregated repository and marking pr with success/failure should be enough for decision to push/not to push.
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21654) add aeri for jboss tools
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21654?page=com.atlassian.jira.plugi... ]
Marcel Bruch commented on JBIDE-21654:
--------------------------------------
server configuration has been updated to accept/express interest in all error reports that mention *at least one* class from the following package prefixes in their stacktrace:
"requiredPackages": [
"org.jboss.*",
"com.jboss.*",
"org.fusesource.*",
"org.hibernate.*",
"org.mozilla.xpcom.*",
"org.mozilla.xulrunner.*",
"org.drools.*",
"org.jbpm.*",
"org.guvnor.*",
"org.kie.*",
"org.switchyard.*"
],
Note that I removed the 3rd package level in all prefixes - except mozilla.
Since server configurations are cached on the Eclipse client for a week by default, please delete the cached server-config file manually from $workspace/.metadata/.plugins/org.eclipse.epp.logging.aeri.ide/org.jboss.tools/server-config.json
> add aeri for jboss tools
> ------------------------
>
> Key: JBIDE-21654
> URL: https://issues.jboss.org/browse/JBIDE-21654
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: usage
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> We have the possibility to get at test environment for error reporting for JBoss Tools.
> For that we need Mars.2 (pre-Mars.2 will not work) and the latest aeri.
> Thus we can't add it by default to i.e. usage (unless we want to force upgrade everyone), but we can at least include it in the default set.
> In Neon we can add to usage.
> jira here is to capture this + implement the extension point.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21523) Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21523?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-21523.
---------------------------------
Resolution: Done
Was applied in master a while ago
> Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21523
> URL: https://issues.jboss.org/browse/JBIDE-21523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Fred Bricon
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
> 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, 2 months
[JBoss JIRA] (JBIDE-21139) OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21139?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-21139.
---------------------------------
Assignee: Viacheslav Kabanovich
Resolution: Done
This has been fixed along with JBIDE-20719
> OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21139
> URL: https://issues.jboss.org/browse/JBIDE-21139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, explorer, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: connection.png
>
>
> After editing a connection which was without credentials (e.g. token was not stored in secure storage and eclipse got restarted) and there is tree item informing about such an error, editing the connection does not refresh connection item in OpenShift explorer view and it is necessary to refresh it via context menu of the connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months