September 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4555) Unknown category error in Red Hat Central

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4555?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-4555 at 9/21/17 10:21 AM: --------------------------------------------------------------- [~nickboldt], I can live with it. If the referenced categories don't exist, what are the consequences? I guess the connectors won't be displayed in the right categories in Central, right? But that doesn't seem to be the case. !categories.png! was (Author: mmalina): [~nickboldt], I can live with it. If the referenced categories don't exist, what are the consequences? I guess the connectors won't be displayed in the right categories in Central, right? But that doesn't seem to be the case. > Unknown category error in Red Hat Central > ----------------------------------------- > > Key: JBDS-4555 > URL: https://issues.jboss.org/browse/JBDS-4555 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 11.1.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > Attachments: categories.png > > > I installed devstudio 11.1.0.AM2 B1060 and went to central's Updates/Software tab and immediately got these errors: > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.soa' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24803. --------------------------------- I think this is good enough for now. Closing. > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.1.AM2 > > > JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-867. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24803: --------------------------------------- It turns out that our assumptions about DV 6.3 were not 100 % accurate. DV 6.3 actually either installs in a new folder - then it's a complete install including EAP 6.4. Or it installs into a 6.4 folder. But if you point it to an existing directory which is not an eap 6.4 installation, it will give you an error. So assume you want to install DV into /tmp. In our Download dialog, you will set Install Folder to /tmp. Then it will download the 900MB DV 6.3 installer and when it starts, the install path will be pre-filled for you to say /tmp. But the installer will not accept it - it either wants a non-existing directory that it will create for you or a directory containing eap 6.4. OK, so what if I entered the desired target directory in our Download dialog - say /tmp/dv-6.3? What won't work (probably) either - our tooling will tell you that this directory does not exist and will be created for you. But if it's indeed created before the jar installer of dv 6.3 is started, then the installer will complain that eap 6.4 is missing in that folder. I'm not sure what we could do here. We could automatically add a subfolder to the target path when starting the jar installer. But that may be undesirable if the user already enters something like /tmp/dv-6.3. Or we could skip the creation of the folder in this case, that would probably work. But I would say that it's not worth the effort and we can just leave it as is for now - it still works, but you will usually have to change the install folder in the installer. Now what about DV 6.2 where it requires an installation of EAP 6.4? The dialog says: "It is strongly recommended you first install EAP 6.4 before proceeding." Well, this is not strictly correct - it's not recommended, it's required - I am not allowed to proceed without it. But I guess I'm nitpicking. It's not a big deal. {quote} What happens if you download dv 6.2 (that requires path to existing eap 6.4) and you already have it configured in runtime detection? Variant a): You already have this exact path in 'paths to search for runtimes' {quote} Answer: You will get an error: "Unable to initialize some runtime paths." I guess it's kind of expected. > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.1.AM2 > > > JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-867. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24280) Support JVM converted types by Jolokia in JolokiaMBeanServerConnection

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24280?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-24280. -------------------------------- verified - 4.5.1.AM2 > Support JVM converted types by Jolokia in JolokiaMBeanServerConnection > ---------------------------------------------------------------------- > > Key: JBIDE-24280 > URL: https://issues.jboss.org/browse/JBIDE-24280 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.5.1.AM1 > > Attachments: propertyToCheck.png > > > currently if you are trying to invoke methods/get attributes of (returning) type Integer or Date, there is a ClassCastException > i should be the case for all types converted by Jolokia/Json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4555) Unknown category error in Red Hat Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4555?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4555 at 9/21/17 10:09 AM: ------------------------------------------------------------ nightly may not have the IS content in it. AM2 should have the IS discovery jar, which contains the old namespace. If this really bothers you I could manually edit the plugin jar to fix the namespace. :D But we might also get a 11.1.0.Beta from Paul which we can use to verify everything is fixed before our 11.1.0.GA. If we get a beta, we can use that; if not I can manually replace the jars. was (Author: nickboldt): nightly may not have the IS content in it. AM2 should have the IS discovery jar, which contains the old namespace. If this really bothers you I could manually edit the plugin jar to fix the namespace. :D > Unknown category error in Red Hat Central > ----------------------------------------- > > Key: JBDS-4555 > URL: https://issues.jboss.org/browse/JBDS-4555 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 11.1.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > I installed devstudio 11.1.0.AM2 B1060 and went to central's Updates/Software tab and immediately got these errors: > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.soa' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4555) Unknown category error in Red Hat Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4555?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4555: ---------------------------------- nightly may not have the IS content in it. AM2 should have the IS discovery jar, which contains the old namespace. If this really bothers you I could manually edit the plugin jar to fix the namespace. :D > Unknown category error in Red Hat Central > ----------------------------------------- > > Key: JBDS-4555 > URL: https://issues.jboss.org/browse/JBDS-4555 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 11.1.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > I installed devstudio 11.1.0.AM2 B1060 and went to central's Updates/Software tab and immediately got these errors: > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.soa' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25013) Refactor integration tests for use with RedDeer 2.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25013?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25013: ------------------------------------ I've merged both https://github.com/jbosstools/jbosstools-integration-tests/pull/1880 and its prereq, https://github.com/jbosstools/jbosstools-server/pull/540 Building now: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=786 https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=1419 > Refactor integration tests for use with RedDeer 2.0 > --------------------------------------------------- > > Key: JBIDE-25013 > URL: https://issues.jboss.org/browse/JBIDE-25013 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.5.1.AM3 > > > A number of integration-tests plugins require reddeer 1.2 and need to be migrated to use 2.0. > {code}** [1] ./plugins/org.jboss.tools.seam.reddeer/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [2] ./tests/org.jboss.tools.central.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [3] ./tests/org.jboss.tools.dummy.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [4] ./tests/org.jboss.tools.eclipsecs.ui.test/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [5] ./tests/org.jboss.tools.examples.ui.bot.test/META-INF/MANIFEST.MF ** > 9:Require-Bundle: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [6] ./tests/org.jboss.tools.freemarker.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [7] ./tests/org.jboss.tools.jsf.ui.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [8] ./tests/org.jboss.tools.maven.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [9] ./tests/org.jboss.tools.openshift.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24939: ------------------------------------ Jobs and parent poms updated to use latest TPs. https://github.com/jbdevstudio/jbdevstudio-ci/commit/f8495d2a559cffd52c6b... > update target platform & Central to Oxygen.1 > -------------------------------------------- > > Key: JBIDE-24939 > URL: https://issues.jboss.org/browse/JBIDE-24939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions_sorted_no_featurejars_no_sources.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff.txt, p2diff.considerversions.txt, p2diff.ignoreversions.txt > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25088) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25088?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-25088. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-25088 > URL: https://issues.jboss.org/browse/JBIDE-25088 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [central-update]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25088) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25088?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25088: ------------------------------------ bump up to parent pom version = 4.5.1.AM3-SNAPSHOT > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-25088 > URL: https://issues.jboss.org/browse/JBIDE-25088 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [central-update]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017