[JBoss JIRA] (JBDS-3719) Initial search for an existing JBDS is present but disabled
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3719?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3719:
-----------------------------------
OK, so then there is no need for that horrible glob pattern that limits the search to the depth of 4.
> Initial search for an existing JBDS is present but disabled
> -----------------------------------------------------------
>
> Key: JBDS-3719
> URL: https://issues.jboss.org/browse/JBDS-3719
> 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: 10.0.0.Alpha1
>
>
> The installer calls the functionality to search for an existing JBDS when the confirm page loads, but the method has a built-in check that just interrupts it. Meaning - checking an existing installation will only proceed if a folder was selected by the user, the initial search will not.
> Is this by design? If it is there is no point in initiating the search automatically.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21967) Cannot create server adapter if there is a running build on a project although there are more projects
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21967?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21967:
---------------------------------------
Or we could show everything, but preselect the selected service and load its (meta)data only for it. If user choose different service, (meta)data will be downloaded "on demand" (in that precisely moment). But if that would be a problem I am ok with Fred's proposal.
> Cannot create server adapter if there is a running build on a project although there are more projects
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21967
> URL: https://issues.jboss.org/browse/JBIDE-21967
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When I am having several projects and some of them has already running application, I am not able to create a new server adapter for OpenShift 3 application if there is a project with running build. Once build finish, it is possible to create a project but while there is any project with not completed build (and therefore application image is not there yet) user is blocked from creating a new server adapter. This is related to JBIDE-21731 - once this issue will be fixed, it should keep in mind to allow users proceed with creation of server adapters on other projects.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-16444) Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16444?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16444.
---------------------------------
Verified in JBDS 9.1.0.GA build ID B477.
> Connection wizard: save accepted certificates in the Eclipse preferences and allow users to inspect/revoke them
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16444
> URL: https://issues.jboss.org/browse/JBIDE-16444
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: accept-certificate.png
>
>
> In JBIDE-14768 we introduced a dialog that allows users to accept/refuse untrusted SSL certificates.
> !accept-certificate.png!
> The authorization is currently stored for the current Eclipse session. We should store those authorizations in the Eclipse preferences and add a preferences page which shows these and allows users to revoke the given authorizations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-11129) Switch application Properties view to 'Tabbed Properties' view
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11129?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-11129.
---------------------------------
Verified in JBDS 9.1.0.GA build ID B477.
> Switch application Properties view to 'Tabbed Properties' view
> --------------------------------------------------------------
>
> Key: JBIDE-11129
> URL: https://issues.jboss.org/browse/JBIDE-11129
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Jeff Cantrill
> Labels: properties
> Fix For: 4.3.1.CR1
>
> Attachments: appprops.png, appselection.png
>
>
> Switch application Properties view to 'Tabbed Properties' view to support hypertext links in the application properties (accessible via OpenShift Console view):
> * !appprops.png|thumbnail!
> like in the Existing application selection dialog
> * !appselection.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21981) Error during rsync
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21981:
----------------------------------
Sprint: devex #4 March 2016 (was: devex #4 March 2016, devex #5 April 2016)
> Error during rsync
> ------------------
>
> Key: JBIDE-21981
> URL: https://issues.jboss.org/browse/JBIDE-21981
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy
> OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
> rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
> error: exit status 23
> {code}
> The content of the {{.../deploy}} directory was:
> {code}
> drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./
> drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../
> -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt
> drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/
> -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed
> -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying
> -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar
> -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed
> -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21981) Error during rsync
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21981.
---------------------------------
Ok, in this case I am closing this one as verified in JBDS 9.1.0.GA B477.
> Error during rsync
> ------------------
>
> Key: JBIDE-21981
> URL: https://issues.jboss.org/browse/JBIDE-21981
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy
> OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
> rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
> error: exit status 23
> {code}
> The content of the {{.../deploy}} directory was:
> {code}
> drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./
> drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../
> -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt
> drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/
> -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed
> -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying
> -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar
> -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed
> -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22105) Update AERI Server to 2.0
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22105?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22105:
-------------------------------------
fair enough. It's as good a motive as another
> Update AERI Server to 2.0
> -------------------------
>
> Key: JBIDE-22105
> URL: https://issues.jboss.org/browse/JBIDE-22105
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aeri
> Reporter: Marcel Bruch
> Priority: Minor
>
> I'd like to roll out an update of the aeri server.
> Notable changes on for Eclipse clients:
> This update changes the sever responses send back to clients on submission of a problem report. The response format is compatible with the Eclipse AERI integration 1.100+
> No breaking changes.
> Most notable changes on the server's web-site:
> * The UI changed from AngularJS to Vaadin
> * Improved JIRA integration.
> * Improved customization of email digests and bug creation templates
> * Fine-grained control over server-responses
> * Auto-Actions for automated problem state transitions on problem state changes (e.g., _number-of-reporters > 100 && status=open --> Set Severity to major._ or _If new error reports arrived in with bundle.version > 1.2.3 --> set status=reopen.
> Details will be announced separately.
> In this bug I'm looking for a process *how* to perform an server-update for JBoss Tools.
> I'd like to know who needs to be involved in case of major/minor updates? Is some testing / approval from QE required before an update can go live?
> My proposed way of doing a major update:
> * Copy the current database.
> * Set up a sandbox instance running on the copied database
> * Create a JIRA issue for the planned update.
> * After approval by QE switch testing instance to production
> FWIW, I don't plan to announce minor bugfixes and minor improvements (e.g., to duplicate detection) as long as they do have user-observable impact or lead to significant changes in the UI and workflows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years