February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23536: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, release, release-eng > Fix For: 4.4.3.Final > > Attachments: run.log > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23510: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.AM2) > [devdoc] document sources in target platform zip & use of PDE Source Lookup feature > ----------------------------------------------------------------------------------- > > Key: JBIDE-23510 > URL: https://issues.jboss.org/browse/JBIDE-23510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1 > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to build a targetplatform with all the sources - done in JBIDE-23481. > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use the PDE Source Lookup plugin > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve sources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4233 at 2/7/17 11:16 PM: ----------------------------------------------------------- Target platform jobs migrated: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... However, there are currently two problems: a) JBQA-13417 :: can't deploy to nexus - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... b) JBQA-13418 and JBIDE-23285 :: need shared folder for p2diff - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... was (Author: nickboldt): Target platform jobs migrated: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... However, there are currently two problems: a) JBQA-13417 :: can't deploy to nexus - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... b) JBQA-13418 :: need shared folder for p2diff - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: CCI-installed-plugins-Jenkins-1.609.3-1_list.txt > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[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/7/17 11:15 PM: ------------------------------------------------------------- Had a look at all the runtimes shared between jobs, since we'll be migrating them to CCI Jenkins and need a new way to house that shared config (JBQA-13418). Here's the current list of *8.8G* of runtimes we use (or _used_ - oldest file is jboss-as-distribution-6.0.0.Final.zip from dec 28 2010) for testing. Can any of these be safely deleted, [~mmalina] [~psrna] [~rob.stryker] ? {code} 10.x.zip apache-tomcat-6.0.39.zip apache-tomcat-6.0.41.zip apache-tomcat-7.0.56.zip apache-tomcat-8.0.8.zip db2jcc4.jar eap6.zip eap7.zip earlyaccess.properties GateIn-3.4.0.Final-jbossas5.zip GateIn-3.5.0.Final-jbossas7.zip h2-1.4.178.jar hibernate-distribution-3.5.3-Final-dist.zip hibernate-distribution-3.6.10.Final-dist.zip hibernate-release-4.3.11.Final.zip hsqldb-2.2.9.zip ide-config.properties index.ser IzPack-install-4.3.5.jar jbds-seamfp-patch.zip jboss-3.2.8.SP1.zip jboss-4.0.5.GA.zip jboss-4.2.3.GA-jdk6.zip jboss-5.0.1.GA-jdk6.zip jboss-5.0.1.GA.zip jboss-5.1.0.GA-jdk6.zip jboss-5.1.0.GA.zip jboss-as-7.0.2.Final.zip jboss-as-7.1.1.Final.zip jboss-as-distribution-6.0.0.Final.zip jboss-as-distribution-6.1.0.Final.zip jboss-eap-4.3.0.GA_CP10.zip jboss-eap-5.1.2.zip jboss-eap-6.0.1.zip jboss-eap-6.1.0.Alpha.zip jboss-eap-6.1.1.zip jboss-eap-6.1.2.zip jboss-eap-6.2.0.zip jboss-eap-6.2.4-full-build.zip jboss-eap-6.2.x-patched.zip jboss-eap-6.3.0.zip jboss-eap-6.3.x-patched.zip jboss-eap-6.4.0.zip jboss-eap-6.4-CVE-2015-7501.zip jboss-eap-7.0.0.zip jboss-eap-fp-4.3.0.CP03-FP01.zip jboss-eap-noauth-4.3.0.GA_CP03.zip jboss-eap-noauth-5.2.0.zip jboss-portal-2.7.2-bundled.zip JBossPortletBridge-2.3.1.Final.zip jboss-seam-2.0.1.GA.zip jboss-seam-2.1.1.GA.zip jboss-seam-2.1.2.zip jboss-seam-2.2.0.GA.zip jboss-seam-2.2.1.Final.zip jboss-seam-distribution-2.3.0.Final-dist.zip jconn4-26666.jar mockito-1.9.5.zip mysql-connector-java-5.1.21-bin.jar ojdbc6.jar poi-src-2.5.1-final-20040804.zip postgresql-9.1-902.jdbc4.jar rhds-seam-gen-patch.zip sakila.h2.db saxonhe9-2-1-5j.zip soa-4.3.0.GA_CP05.zip soa-p-5.3.0.GA.zip sqljdbc4.jar wildfly-8.0.0.Final.zip wildfly-8.1.0.Final.zip wildfly-8.2.0.Final.zip wildfly-9.0.1.Final.zip wildfly-10.0.0.CR2.zip wildfly-10.0.0.Final.zip wildfly-10.1.0.Final.zip {code} was (Author: nickboldt): Had a look at all the runtimes shared between jobs, since we'll be migrating them to CCI Jenkins and need a new way to house that shared config (JBQA-13418). Here's the current list of runtimes we use(d) for testing. Can any of these be safely deleted, [~mmalina] [~psrna] [~rob.stryker] ? {code} 10.x.zip apache-tomcat-6.0.39.zip apache-tomcat-6.0.41.zip apache-tomcat-7.0.56.zip apache-tomcat-8.0.8.zip db2jcc4.jar eap6.zip eap7.zip earlyaccess.properties GateIn-3.4.0.Final-jbossas5.zip GateIn-3.5.0.Final-jbossas7.zip h2-1.4.178.jar hibernate-distribution-3.5.3-Final-dist.zip hibernate-distribution-3.6.10.Final-dist.zip hibernate-release-4.3.11.Final.zip hsqldb-2.2.9.zip ide-config.properties index.ser IzPack-install-4.3.5.jar jbds-seamfp-patch.zip jboss-3.2.8.SP1.zip jboss-4.0.5.GA.zip jboss-4.2.3.GA-jdk6.zip jboss-5.0.1.GA-jdk6.zip jboss-5.0.1.GA.zip jboss-5.1.0.GA-jdk6.zip jboss-5.1.0.GA.zip jboss-as-7.0.2.Final.zip jboss-as-7.1.1.Final.zip jboss-as-distribution-6.0.0.Final.zip jboss-as-distribution-6.1.0.Final.zip jboss-eap-4.3.0.GA_CP10.zip jboss-eap-5.1.2.zip jboss-eap-6.0.1.zip jboss-eap-6.1.0.Alpha.zip jboss-eap-6.1.1.zip jboss-eap-6.1.2.zip jboss-eap-6.2.0.zip jboss-eap-6.2.4-full-build.zip jboss-eap-6.2.x-patched.zip jboss-eap-6.3.0.zip jboss-eap-6.3.x-patched.zip jboss-eap-6.4.0.zip jboss-eap-6.4-CVE-2015-7501.zip jboss-eap-7.0.0.zip jboss-eap-fp-4.3.0.CP03-FP01.zip jboss-eap-noauth-4.3.0.GA_CP03.zip jboss-eap-noauth-5.2.0.zip jboss-portal-2.7.2-bundled.zip JBossPortletBridge-2.3.1.Final.zip jboss-seam-2.0.1.GA.zip jboss-seam-2.1.1.GA.zip jboss-seam-2.1.2.zip jboss-seam-2.2.0.GA.zip jboss-seam-2.2.1.Final.zip jboss-seam-distribution-2.3.0.Final-dist.zip jconn4-26666.jar mockito-1.9.5.zip mysql-connector-java-5.1.21-bin.jar ojdbc6.jar poi-src-2.5.1-final-20040804.zip postgresql-9.1-902.jdbc4.jar rhds-seam-gen-patch.zip sakila.h2.db saxonhe9-2-1-5j.zip soa-4.3.0.GA_CP05.zip soa-p-5.3.0.GA.zip sqljdbc4.jar wildfly-8.0.0.Final.zip wildfly-8.1.0.Final.zip wildfly-8.2.0.Final.zip wildfly-9.0.1.Final.zip wildfly-10.0.0.CR2.zip wildfly-10.0.0.Final.zip wildfly-10.1.0.Final.zip {code} > 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

1
0
0 / 0

[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: ------------------------------------ Had a look at all the runtimes shared between jobs, since we'll be migrating them to CCI Jenkins and need a new way to house that shared config (JBQA-13418). Here's the current list of runtimes we use(d) for testing. Can any of these be safely deleted, [~mmalina] [~psrna] [~rob.stryker] ? {code} 10.x.zip apache-tomcat-6.0.39.zip apache-tomcat-6.0.41.zip apache-tomcat-7.0.56.zip apache-tomcat-8.0.8.zip db2jcc4.jar eap6.zip eap7.zip earlyaccess.properties GateIn-3.4.0.Final-jbossas5.zip GateIn-3.5.0.Final-jbossas7.zip h2-1.4.178.jar hibernate-distribution-3.5.3-Final-dist.zip hibernate-distribution-3.6.10.Final-dist.zip hibernate-release-4.3.11.Final.zip hsqldb-2.2.9.zip ide-config.properties index.ser IzPack-install-4.3.5.jar jbds-seamfp-patch.zip jboss-3.2.8.SP1.zip jboss-4.0.5.GA.zip jboss-4.2.3.GA-jdk6.zip jboss-5.0.1.GA-jdk6.zip jboss-5.0.1.GA.zip jboss-5.1.0.GA-jdk6.zip jboss-5.1.0.GA.zip jboss-as-7.0.2.Final.zip jboss-as-7.1.1.Final.zip jboss-as-distribution-6.0.0.Final.zip jboss-as-distribution-6.1.0.Final.zip jboss-eap-4.3.0.GA_CP10.zip jboss-eap-5.1.2.zip jboss-eap-6.0.1.zip jboss-eap-6.1.0.Alpha.zip jboss-eap-6.1.1.zip jboss-eap-6.1.2.zip jboss-eap-6.2.0.zip jboss-eap-6.2.4-full-build.zip jboss-eap-6.2.x-patched.zip jboss-eap-6.3.0.zip jboss-eap-6.3.x-patched.zip jboss-eap-6.4.0.zip jboss-eap-6.4-CVE-2015-7501.zip jboss-eap-7.0.0.zip jboss-eap-fp-4.3.0.CP03-FP01.zip jboss-eap-noauth-4.3.0.GA_CP03.zip jboss-eap-noauth-5.2.0.zip jboss-portal-2.7.2-bundled.zip JBossPortletBridge-2.3.1.Final.zip jboss-seam-2.0.1.GA.zip jboss-seam-2.1.1.GA.zip jboss-seam-2.1.2.zip jboss-seam-2.2.0.GA.zip jboss-seam-2.2.1.Final.zip jboss-seam-distribution-2.3.0.Final-dist.zip jconn4-26666.jar mockito-1.9.5.zip mysql-connector-java-5.1.21-bin.jar ojdbc6.jar poi-src-2.5.1-final-20040804.zip postgresql-9.1-902.jdbc4.jar rhds-seam-gen-patch.zip sakila.h2.db saxonhe9-2-1-5j.zip soa-4.3.0.GA_CP05.zip soa-p-5.3.0.GA.zip sqljdbc4.jar wildfly-8.0.0.Final.zip wildfly-8.1.0.Final.zip wildfly-8.2.0.Final.zip wildfly-9.0.1.Final.zip wildfly-10.0.0.CR2.zip wildfly-10.0.0.Final.zip wildfly-10.1.0.Final.zip {code} > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4233: ---------------------------------- Target platform jobs migrated: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... However, there are currently two problems: a) JBQA-13417 :: can't deploy to nexus - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... b) JBQA-13418 :: need shared folder for p2diff - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: CCI-installed-plugins-Jenkins-1.609.3-1_list.txt > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23625) Duplicate nodes in JMX tree makes tree hard to navigate

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23625: -------------------------------- Summary: Duplicate nodes in JMX tree makes tree hard to navigate (was: JMX: jmx tree is not very usable) > Duplicate nodes in JMX tree makes tree hard to navigate > ------------------------------------------------------- > > Key: JBIDE-23625 > URL: https://issues.jboss.org/browse/JBIDE-23625 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM1 > > Attachments: image-2016-12-02-16-47-59-519.png > > > steps to reproduce: > # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project > # EXEC: create a server adapter for it > # ASSERT: your server adapter now has a JMX child node > # EXEC: double click it and wait until all MBeans are loaded > # EXEC: now try to see if you can find your deployment > Result: > You get a listing of tons of beans. > !mbeans.png! > Your deployment is a child bean of jboss.as, named by the war that was created: > !image-2016-12-02-16-47-59-519.png|thumbnail! > Rather painfull to find a listing of your deployments in this way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-398) Deselected connection after deleted tag [EBZ#499919]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-398?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-398: ------------------------------ Sprint: devex #127 February 2017 > Deselected connection after deleted tag [EBZ#499919] > ---------------------------------------------------- > > Key: ERT-398 > URL: https://issues.jboss.org/browse/ERT-398 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Priority: Minor > Labels: Docker, bzira > > Steps to reproduce: > 1. Pull any image. > 2. Add tag to this image. > 3. Click on added tag in Docker Explorer. > 4. Delete in Docker Images tab this newly created tag. > 5. Tag is deleted, but connection is deselected, so the Docker Images tab is empty. > I suggest in this case to select connection or images in Docker explorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-398) Deselected connection after deleted tag [EBZ#499919]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-398?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-398: --------------------------------- Assignee: Jeff Johnston > Deselected connection after deleted tag [EBZ#499919] > ---------------------------------------------------- > > Key: ERT-398 > URL: https://issues.jboss.org/browse/ERT-398 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Priority: Minor > Labels: Docker, bzira > > Steps to reproduce: > 1. Pull any image. > 2. Add tag to this image. > 3. Click on added tag in Docker Explorer. > 4. Delete in Docker Images tab this newly created tag. > 5. Tag is deleted, but connection is deselected, so the Docker Images tab is empty. > I suggest in this case to select connection or images in Docker explorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4274) Fix marketplace categories for devstudio and jbosstools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4274?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4274: ----------------------------- Description: 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} was: 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: {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 "General Purpose Tools" and "IDE", and use "Web, XML, Java EE and OSGi Enterprise Development" and "Mobile and Device Development" instead? Or include "Linux Tools" since we have Docker/Vagrant stuff? For Integration Stack, we could drop "IDE" and "Tools" and use instead "Database Persistence", "Web Services", "Business Intelligence, Reporting and Charting" ? What do you think? Here's the current full list of categories. {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} > 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

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 February 2017