[JBoss JIRA] (JBDS-3869) DevSuite Installer should check/warn if Hyper-V is already enabled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3869:
--------------------------------
Sprint: devex #127 February 2017 (was: devex #126 January 2017)
> DevSuite Installer should check/warn if Hyper-V is already enabled
> ------------------------------------------------------------------
>
> Key: JBDS-3869
> URL: https://issues.jboss.org/browse/JBDS-3869
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 10 Pro, 64 bit.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> The platform installer should check and warn if Hyper-V is already enabled on Windows systems.
> Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4253) Show warning for virtualbox component if virtualization is not enabled or cannot be detected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4253?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4253:
--------------------------------
Sprint: devex #127 February 2017 (was: devex #126 January 2017)
> Show warning for virtualbox component if virtualization is not enabled or cannot be detected
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-4253
> URL: https://issues.jboss.org/browse/JBDS-4253
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
>
> Current implementation shows errors and warning under item selected for installation.
> See confirmation page error message for virtualbox Installer [here|https://github.com/redhat-developer-tooling/developer-platform-insta...].
> Confirmation page controller should run Virtualization detection along with installed components detection and show warning under virtualbox item if it is detected or selected for install.
> If Virtualization firmware status cannot be detected (windows 7) message should say:
> * Make sure hardware virtualization is enabled on your platform if supported to improve performance.
> if Hardware Virtualization is Disabled:
> * Please enable hardware virtualization for your platform to improve performance
> If Hardware Virtualization is Enabled, no message is required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4159:
--------------------------------
Sprint: devex #127 February 2017 (was: devex #126 January 2017)
> On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4159
> URL: https://issues.jboss.org/browse/JBDS-4159
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases.
> here is the error:
> {noformat}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
> Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
> Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4038) Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4038?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4038:
--------------------------------
Sprint: devex #127 February 2017 (was: devex #126 January 2017)
> Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-4038
> URL: https://issues.jboss.org/browse/JBDS-4038
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Environment: Windows 7 Pro, x86_64, SP1
> Reporter: Ondrej Dockal
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.3.0.AM2
>
>
> Default installation on Non-ASCII path fails to install/configure CDK.
> Error from install log file:
> Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute command vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem"
> Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute options {
> "env": {
> "ALLUSERSPROFILE": "C:\\ProgramData",
> "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming",
> "CommonProgramFiles": "C:\\Program Files\\Common Files",
> "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files",
> "CommonProgramW6432": "C:\\Program Files\\Common Files",
> "COMPUTERNAME": "SOME-PC",
> "ComSpec": "C:\\Windows\\system32\\cmd.exe",
> "FP_NO_HOST_CHECK": "NO",
> "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q",
> "HOMEDRIVE": "C:",
> "HOMEPATH": "\\Users\\jbossqa",
> "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local",
> "LOGONSERVER": "\\\\SOME-PC",
> "NUMBER_OF_PROCESSORS": "2",
> "OS": "Windows_NT",
> "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;c:\\DevelopmentÅ uite\\cdk\\bin;c:\\DevelopmentÅ uite\\vagrant\\bin;c:\\DevelopmentÅ uite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;;c:\\DevelopmentŠuite\\vagrant\\bin;c:\\DevelopmentŠuite\\cygwin\\bin;C:\\DevelopmentŠuite\\virtualbox\\",
> "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC",
> "PROCESSOR_ARCHITECTURE": "AMD64",
> "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel",
> "PROCESSOR_LEVEL": "6",
> "PROCESSOR_REVISION": "3c01",
> "ProgramData": "C:\\ProgramData",
> "ProgramFiles": "C:\\Program Files",
> "ProgramFiles(x86)": "C:\\Program Files (x86)",
> "ProgramW6432": "C:\\Program Files",
> "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\",
> "PUBLIC": "C:\\Users\\Public",
> "SESSIONNAME": "Console",
> "SystemDrive": "C:",
> "SystemRoot": "C:\\Windows",
> "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp",
> "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp",
> "USERDOMAIN": "Some-PC",
> "USERNAME": "jbossqa",
> "USERPROFILE": "C:\\Users\\jbossqa",
> "VAGRANT_DETECTED_OS": "cygwin",
> "windir": "C:\\Windows",
> "windows_tracing_flags": "3",
> "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log",
> "__COMPAT_LAYER": "VistaSetup"
> },
> "cwd": "c:\\DevelopmentŠuite\\cdk\\boxes"
> }
> Thu, 01 Sep 2016 11:19:25 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem"
> <internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError)
> from <internal:gem_prelude>:1:in `<compiled>'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4246) Implement minishift cdk-setup in devsuite installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4246?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4246:
--------------------------------
Sprint: devex #127 February 2017 (was: devex #126 January 2017)
> Implement minishift cdk-setup in devsuite installer
> ---------------------------------------------------
>
> Key: JBDS-4246
> URL: https://issues.jboss.org/browse/JBDS-4246
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Environment: Windows, mac OS, Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.3.0.AM2
>
>
> Instead of downloading three resources from three different URL's installer will need to download only one and run with 'cdk-setup' parameter during installation:
> 1. copy minishift to $\{target.folder\}/cdk/bin
> 2. remove ~/.minishift
> 3.1. run for virtualbox setup $\{target.folder\}/cdk/bin/minishift.exe setup-cdk --default-vm-driver=virtualbox
> 3.2. run for hyper-v setup $\{target.folder\}/cdk/bin/minishift.exe setup-cdk
> 4. find location of oc.exe in ~/.minishift/cache/** and add it to PATH
> 5. add $\{target.folder\}/cdk/bin to PATH
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23285 at 2/8/17 1:37 PM:
------------------------------------------------------------
{code}
13:17:01 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-4.3.0) @ org.jboss.tools.as.itests ---
13:17:02 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-4.3.0.GA_CP10.zip
13:17:20 [INFO]
13:17:20 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-5.1.2) @ org.jboss.tools.as.itests ---
13:17:20 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-5.1.2.zip
13:17:25 [INFO]
13:17:25 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.0.1) @ org.jboss.tools.as.itests ---
13:17:25 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.0.1.zip
13:17:28 [INFO]
13:17:28 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.1.2) @ org.jboss.tools.as.itests ---
13:17:31 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.2.zip
13:17:33 [INFO]
13:17:33 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.2.4) @ org.jboss.tools.as.itests ---
13:17:36 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.2.4-full-build.zip
13:17:38 [INFO]
13:17:38 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.3.0) @ org.jboss.tools.as.itests ---
13:17:39 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.3.0.zip
13:17:41 [INFO]
13:17:41 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-7.0.0) @ org.jboss.tools.as.itests ---
13:17:45 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-7.0.0.zip{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
So... the cache folder is still being used. Property _download.cache.directory_ is used by http://maven-download-plugin.github.io/maven-download-plugin/docsite/1.2....
was (Author: nickboldt):
{code}
13:17:01 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-4.3.0) @ org.jboss.tools.as.itests ---
13:17:02 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-4.3.0.GA_CP10.zip
13:17:20 [INFO]
13:17:20 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-5.1.2) @ org.jboss.tools.as.itests ---
13:17:20 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-5.1.2.zip
13:17:25 [INFO]
13:17:25 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.0.1) @ org.jboss.tools.as.itests ---
13:17:25 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.0.1.zip
13:17:28 [INFO]
13:17:28 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.1.2) @ org.jboss.tools.as.itests ---
13:17:31 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.2.zip
13:17:33 [INFO]
13:17:33 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.2.4) @ org.jboss.tools.as.itests ---
13:17:36 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.2.4-full-build.zip
13:17:38 [INFO]
13:17:38 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.3.0) @ org.jboss.tools.as.itests ---
13:17:39 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.3.0.zip
13:17:41 [INFO]
13:17:41 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-7.0.0) @ org.jboss.tools.as.itests ---
13:17:45 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-7.0.0.zip{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
So... the cache folder is still being used.
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.4.3.Final
>
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23285:
------------------------------------
{code}
13:17:01 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-4.3.0) @ org.jboss.tools.as.itests ---
13:17:02 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-4.3.0.GA_CP10.zip
13:17:20 [INFO]
13:17:20 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-5.1.2) @ org.jboss.tools.as.itests ---
13:17:20 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-5.1.2.zip
13:17:25 [INFO]
13:17:25 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.0.1) @ org.jboss.tools.as.itests ---
13:17:25 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.0.1.zip
13:17:28 [INFO]
13:17:28 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.1.2) @ org.jboss.tools.as.itests ---
13:17:31 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.2.zip
13:17:33 [INFO]
13:17:33 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.2.4) @ org.jboss.tools.as.itests ---
13:17:36 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.2.4-full-build.zip
13:17:38 [INFO]
13:17:38 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-6.3.0) @ org.jboss.tools.as.itests ---
13:17:39 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.3.0.zip
13:17:41 [INFO]
13:17:41 [INFO] --- download-maven-plugin:1.2.0:wget (install-eap-7.0.0) @ org.jboss.tools.as.itests ---
13:17:45 [INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-7.0.0.zip{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
So... the cache folder is still being used.
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.4.3.Final
>
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4274) Fix marketplace categories for devstudio and jbosstools
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-4274?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBDS-4274:
----------------------------------
I'd still like to see 'Tools' as an IS category since it's something a user would likely search for. Let me run this past the IS folk and see what they think for their top 5.
> Fix marketplace categories for devstudio and jbosstools
> -------------------------------------------------------
>
> Key: JBDS-4274
> URL: https://issues.jboss.org/browse/JBDS-4274
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 10.3.0.GA
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 10.3.0.GA
>
>
> After a recent change to the Eclipse Marketplace, we can only select up to 5 categories. This affects how we're discovered when someone searches for Marketplace listings.
> Here's what we currently use for JBoss Tools:
> {code}Application Server
> Database Development
> General Purpose Tools
> IDE
> J2EE Development Platform{code}
> And here's what we have for Devstudio - the same 5 categories:
> {code}Application Server
> Database Development
> General Purpose Tools
> IDE
> J2EE Development Platform{code}
> And for Devstudio IS:
> {code}
> Database Development
> IDE
> SOA Development
> Tools{code}
> Maybe we want to remove
> {code}General Purpose Tools, and
> IDE{code}
> and use instead:
> {code}Web, XML, Java EE and OSGi Enterprise Development, and
> Mobile and Device Development{code}
> Or should we include {code}Linux Tools{code} since we have
> Docker/Vagrant stuff now too?
> For Integration Stack, we could drop "IDE" and "Tools" and use instead:
> {code}
> Business Intelligence, Reporting and Charting
> Database Development
> Database Persistence
> SOA Development
> Web Services{code}
> What do you think?
> Here's the current full list of categories from which to choose:
> {code}Application Development Frameworks
> Application Management
> Application Server
> BIRT
> Build and Deploy
> Business Intelligence, Reporting and Charting
> Code Management
> Collaboration
> Database
> Database Development
> Database Persistence
> Documentation
> Eclipse Kura
> Eclipse SmartHome
> EclipseRT Target Platform Components
> Editor
> Entertainment
> General Purpose Tools
> Graphics
> IDE
> Internet of Things (IoT)
> J2EE Development Platform
> J2ME
> Languages
> Linux Tools
> Logging
> Mobile and Device Development
> Modeling
> Modeling Tools
> Mylyn Connectors
> Network
> Other
> Process
> Profiling
> Programming Languages
> Reporting
> Rich Client Applications
> SCM
> Search
> SOA Development
> Source Code Analyzer
> Systems Development
> Team Development
> Testing
> Tools
> UI
> UML
> Web
> Web Services
> Web, XML, Java EE and OSGi Enterprise Development
> XML{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month