June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3787: ----------------------------- Target Release: (was: ) > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, new_and_notworthy, user-docs > Fix For: 10.0.0.GA > > Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3787: -------------------------------- Fix Version/s: 10.0.0.GA > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, new_and_notworthy, user-docs > Fix For: 10.0.0.GA > > Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22553) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Aerogear]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22553?page=com.atlassian.jira.plugi... ] Ilya Buziuk closed JBIDE-22553. ------------------------------- Resolution: Done > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Aerogear] > ----------------------------------------------------------- > > Key: JBIDE-22553 > URL: https://issues.jboss.org/browse/JBIDE-22553 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Aerogear]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22553) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Aerogear]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22553?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22553: ------------------------------------- Updates in master: - parent to 4.4.0.Alpha1-SNAPSHOT - aerogear to 1.3.1-SNAPSHOT - cordova to 1.4.1-SNAPSHOT - cordovasim to 3.8.1-SNAPSHOT - feedhenry to 1.2.1-SNAPSHOT > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Aerogear] > ----------------------------------------------------------- > > Key: JBIDE-22553 > URL: https://issues.jboss.org/browse/JBIDE-22553 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Aerogear]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22553) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Aerogear]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22553?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-22553: ----------------------------------- Assignee: Ilya Buziuk > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Aerogear] > ----------------------------------------------------------- > > Key: JBIDE-22553 > URL: https://issues.jboss.org/browse/JBIDE-22553 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Aerogear]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22514) Unable to build the workspace

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22514?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22514: --------------------------------------------- [~jamezp] you should be able to remove yourself from watcher list - but anyway, I've removed you now ;) > Unable to build the workspace > ----------------------------- > > Key: JBIDE-22514 > URL: https://issues.jboss.org/browse/JBIDE-22514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Environment: Eclipse > Reporter: Megha Kesharwani > Assignee: Viacheslav Kabanovich > Priority: Trivial > Fix For: 4.2.0.Final > > Attachments: .log > > > I am using eclipse Kepler with plugins JBOSS(wildfly-8.2.0.Final) and ClearCase, while building the workspace i am getting the following error "ENTRY org.eclipse.core.jobs 4 2 2016-06-02 11:07:19.724 > !MESSAGE An internal error occurred during: "Building workspace". > !STACK 0 > java.lang.StackOverflowError" > Attached logs. > We have tried the following solutions: > 1. We tried increasing the memory size in eclipse.ini file as below but it doesn't seems to work: > --launcher.XXMaxPermSize > 1024M > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 1024m > --launcher.appendVmargs > -vm "C:\Program Files\Java\jre7" > -Dosgi.requiredJavaVersion=1.7 > -Xms2048m > -Xmx2048m > 2. When the RAM was checked using task manager eclipse was taking 365MB of memory. > Please guide us some other workaround to resolve the issue. > thanks, > Megha -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3883) "Download & install" button is enabled during detection after going back and forth again

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3883?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3883: -------------------------------- Sprint: devex #115 May 2016 > "Download & install" button is enabled during detection after going back and forth again > ---------------------------------------------------------------------------------------- > > Key: JBDS-3883 > URL: https://issues.jboss.org/browse/JBDS-3883 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.1.Alpha1 > > > Normally, the user cannot proceed with the installation on the confirm page until component detection has finished. If after that they click back and continue again, the detection is launched again, but it allows the user to continue anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3940) use new logo in icon for Development Suite installer .exe

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3940?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3940: ----------------------------------- Sprint: devex #115 May 2016 Assignee: Denis Golovin (was: Catherine Robson) > use new logo in icon for Development Suite installer .exe > --------------------------------------------------------- > > Key: JBDS-3940 > URL: https://issues.jboss.org/browse/JBDS-3940 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: dpinstaller-new-icon-and-properties-2.png, dpinstaller-new-icon-and-properties.png, icons.png, RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3803) Add JavaVM version detection and validation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3803?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3803: ------------------------------------- [~jrichter1], you are correct about new regexp, because java 9 version has different format - 9-ea. I just decided do not add it right now, because DevStudio doesn't work with Java 9. In DevSuite it just goes the path when Java is not detected and requires to install OpenJDK 8. > Add JavaVM version detection and validation > ------------------------------------------- > > Key: JBDS-3803 > URL: https://issues.jboss.org/browse/JBDS-3803 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22591) Saving new username/pw during prompt for pw while starting cdk fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22591?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22591: ----------------------------------- Assignee: Rob Stryker > Saving new username/pw during prompt for pw while starting cdk fails > --------------------------------------------------------------------- > > Key: JBIDE-22591 > URL: https://issues.jboss.org/browse/JBIDE-22591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Alpha1 > > > When the server is in a project rather than in memory, persisting changes to the server (ie changing its username) will fail because the scheduling rule for starting the server does not include the ability to modify projects. This scenario will need to be identified (is server in memory or project) and a workspace job will need to be scheduled to properly persist the changes. > java.lang.IllegalArgumentException: Attempted to beginRule: L/Servers/Container Development Environment.server, does not match outer scope rule: Container Development Environment > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134) > at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85) > at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:307) > at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:121) > at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2188) > at org.eclipse.core.internal.resources.File.setContents(File.java:334) > at org.eclipse.core.internal.resources.File.setContents(File.java:434) > at org.eclipse.wst.server.core.internal.Base.saveToFile(Base.java:251) > at org.eclipse.wst.server.core.internal.Server.saveToFile(Server.java:471) > at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:264) > at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:466) > at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:434) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.CDKServer.getPassword(CDKServer.java:124) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:158) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016