[JBoss JIRA] (JBIDE-11903) Explorer: add Application start/stop/restart
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-11903:
-------------------------------
Sprint: Sprint 20141112, Sprint 20141113 (was: Sprint 20141112)
> 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
> 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, 5 months
[JBoss JIRA] (JBIDE-15936) Application wizard: should only show gear sizes appropriate for the selected domain
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15936?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15936:
-------------------------------
Sprint: Sprint 20141112, Sprint 20141113 (was: Sprint 20141112)
> Application wizard: should only show gear sizes appropriate for the selected domain
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-15936
> URL: https://issues.jboss.org/browse/JBIDE-15936
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Labels: application_wizard
> Fix For: 4.2.x
>
>
> in the openshift application wizard, I selected a domain. The gear profile field shows three sizes but only small is allowed for the domain I have. If I am a user who doesn't know this I might select medium but then only after three pages of wizard, when trying to create app, does it tell me:
> {noformat}Could not create application "MyApp"
> Could not request https://openshift.redhat.com/broker/rest/domain/myjbdsdomain/applications...: App gear sizes: medium is not valid for this domain. Allowed sizes: small.{noformat}
> If I click Back to change the gear profile, all of the info is removed from the wizard and I have to input it all again. Frustrating. See JBIDE-14002.
> The openshift application wizard could be improved to only show appropriate gear sizes for the selected domain.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-17550:
-------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint 20141113 (was: Sprint 20141112, Sprint to CR1 Release)
> When Install/Update button pressed no progress reported about installation preparation
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-17550
> URL: https://issues.jboss.org/browse/JBIDE-17550
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Labels: f2f2014
> Fix For: 4.3.0.Alpha1
>
>
> When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls
> {code}
> computeInstallableUnits(monitor.newChild(50));
> {code}
> and
> {code}resolveInstall(monitor.newChild(50));{code}
> which can take considerable amount of time.
> I think progress for Preparation to install requested features should be visible in eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-17696:
-------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint 20141113 (was: Sprint 20141112, Sprint to CR1 Release)
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (JBDS-3012) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3012?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3012:
-----------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint 20141113 (was: Sprint 20141112, Sprint to CR1 Release)
> JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3012
> URL: https://issues.jboss.org/browse/JBDS-3012
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, updatesite
> Affects Versions: 7.1.1.GA
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Fix For: 7.1.x
>
>
> We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert:
> {code}One or more certificates rejected. Cannot proceed with installation.{code}
> Full details: https://community.jboss.org/message/866868
> *Platform details:*
> {code}
> Debian Jessie 64 bit
> $ uname -a:
> Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux
> $ java -version
> java version "1.7.0_51"
> OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2)
> OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
> {code}
> Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :)
> [0] http://www.debian.org/releases/jessie/
> [1] http://www.debian.org/releases/
> [2] http://www.debian.org/releases/wheezy/
> [3] https://release.debian.org/
> *Steps to repro on the above platform:*
> 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru
> 3. Install failed with an error re certificates not being trusted
> 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows:
> !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061
> !MESSAGE One or more certificates rejected. Cannot proceed with installation.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (JBDS-3018) Install screen moves to bottom left corner of the screen
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3018?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3018:
-----------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint 20141113 (was: Sprint 20141112, Sprint to CR1 Release)
> Install screen moves to bottom left corner of the screen
> --------------------------------------------------------
>
> Key: JBDS-3018
> URL: https://issues.jboss.org/browse/JBDS-3018
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 7.1.1.GA
> Environment: java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> OSX 10.9.2
> One monitor
> No additional software for windows management
> Reporter: Arun Gupta
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.0.x, 9.0.x
>
> Attachments: Screen Shot 2014-04-21 at 9.07.53 PM.png
>
>
> I started the install as
> java -jar ~/Downloads/jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> Install screen (step 1 of 9) popped up in the middle and then right away went in the bottom left corner of the screen as shown in attachment.
> This does not seem right.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2635:
-----------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint 20141113 (was: Sprint 20141112, Sprint to CR1 Release)
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha1
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months