July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-661) JBDS RN: Ensure this issue is included in Known or Resolved issues

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-661?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-661. -------------------------------- Resolution: Done This is available as part of the query and listed specifically since it is a customer case: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > JBDS RN: Ensure this issue is included in Known or Resolved issues > ------------------------------------------------------------------ > > Key: TOOLSDOC-661 > URL: https://issues.jboss.org/browse/TOOLSDOC-661 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Ensure https://issues.jboss.org/browse/JBDS-3470 is included in RN for all versions of JBDS 9.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Misha Ali reassigned JBIDE-20401: --------------------------------- Assignee: Max Rydahl Andersen (was: Misha Ali) > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-20401: ----------------------------------- Agree with not repeating the effort and linking to the docs. It sounds like this should be assigned to whoever is in charge of the overall linking in the JBT docs, not myself. > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-467) Pull in graphiti 0.13.0 into JBTIS TP from JBoss mirror

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-467?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-467: ----------------------------- Description: *Reason:* Fuse Tooling needs the latest graphiti (0.13.0). It will be available in Eclipse Mars SR1. Until then - take it from a local JBoss mirror. *Project page/sources:* *Version:* 4.3.0.Beta1d *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/0.13.0... *Include Sources:* Yes *Affected JBoss Tools components:* Fuse Tooling, SwitchYard, BPMN2 *Include in JBDS:* Yes (JBDSIS) *Type of dependency:* distribution *List of bundles added/removed:* {code} < org.eclipse.graphiti.feature.feature.jar [0.12.0.v20150603-0807] < org.eclipse.graphiti.export.feature.feature.group [0.12.0.v20150603-0807] < org.eclipse.graphiti.ui [0.12.0.v20150603-0807] < org.eclipse.graphiti [0.12.0.v20150603-0807] < org.eclipse.graphiti.feature.feature.group [0.12.0.v20150603-0807] < org.eclipse.graphiti.export.batik [0.12.0.v20150603-0807] < org.eclipse.graphiti.mm [0.12.0.v20150603-0807] < org.eclipse.graphiti.export.feature.feature.jar [0.12.0.v20150603-0807] < org.eclipse.graphiti.pattern [0.12.0.v20150603-0807] > org.eclipse.graphiti.feature.feature.jar [0.13.0.v20150720-0642] > org.eclipse.graphiti.ui [0.13.0.v20150720-0642] > org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20150720-0642] > org.eclipse.graphiti.pattern [0.13.0.v20150720-0642] > org.eclipse.graphiti.mm [0.13.0.v20150720-0642] > org.eclipse.graphiti [0.13.0.v20150720-0642] > org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20150720-0642] > org.eclipse.graphiti.feature.feature.group [0.13.0.v20150720-0642] > org.eclipse.graphiti.export.batik [0.13.0.v20150720-0642] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 9 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 9 unique IUs {code} was: *Reason:* Fuse Tooling needs the latest graphiti (0.13.0). It will be available in Eclipse Mars SR1. Until then - take it from a local JBoss mirror. *Project page/sources:* *Version:* 4.3.0.Beta1d *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/0.13.0... *Include Sources:* Yes *Affected JBoss Tools components:* Fuse Tooling, SwitchYard, BPMN2 *Include in JBDS:* Yes (JBDSIS) *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} > Pull in graphiti 0.13.0 into JBTIS TP from JBoss mirror > ------------------------------------------------------- > > Key: JBTIS-467 > URL: https://issues.jboss.org/browse/JBTIS-467 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Beta1c-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* Fuse Tooling needs the latest graphiti (0.13.0). It will be available in Eclipse Mars SR1. Until then - take it from a local JBoss mirror. > *Project page/sources:* > *Version:* 4.3.0.Beta1d > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/0.13.0... > *Include Sources:* Yes > *Affected JBoss Tools components:* Fuse Tooling, SwitchYard, BPMN2 > *Include in JBDS:* Yes (JBDSIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > < org.eclipse.graphiti.feature.feature.jar [0.12.0.v20150603-0807] > < org.eclipse.graphiti.export.feature.feature.group [0.12.0.v20150603-0807] > < org.eclipse.graphiti.ui [0.12.0.v20150603-0807] > < org.eclipse.graphiti [0.12.0.v20150603-0807] > < org.eclipse.graphiti.feature.feature.group [0.12.0.v20150603-0807] > < org.eclipse.graphiti.export.batik [0.12.0.v20150603-0807] > < org.eclipse.graphiti.mm [0.12.0.v20150603-0807] > < org.eclipse.graphiti.export.feature.feature.jar [0.12.0.v20150603-0807] > < org.eclipse.graphiti.pattern [0.12.0.v20150603-0807] > > org.eclipse.graphiti.feature.feature.jar [0.13.0.v20150720-0642] > > org.eclipse.graphiti.ui [0.13.0.v20150720-0642] > > org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20150720-0642] > > org.eclipse.graphiti.pattern [0.13.0.v20150720-0642] > > org.eclipse.graphiti.mm [0.13.0.v20150720-0642] > > org.eclipse.graphiti [0.13.0.v20150720-0642] > > org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20150720-0642] > > org.eclipse.graphiti.feature.feature.group [0.13.0.v20150720-0642] > > org.eclipse.graphiti.export.batik [0.13.0.v20150720-0642] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 9 unique IUs > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 9 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-662) Add edited Advanced Install Task instructions to related docs

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-662?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-662: ------------------------------------ No permissions yet, Max is away for a while. Will remind him when he returns from PTO to give us permissions. > Add edited Advanced Install Task instructions to related docs > ------------------------------------------------------------- > > Key: TOOLSDOC-662 > URL: https://issues.jboss.org/browse/TOOLSDOC-662 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Add edited Advanced Install Task instructions to following related docs: > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/cu... > 2. https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20406) New and Noteworthy should list supported OpenShift v3 scenarios for 4.3.0.Beta2

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20406?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-20406: ----------------------------------- The JBT New and Noteworthy content is not generated by the docs team (although I'd love to be invited to edit the text before release). I'm not sure who writes this up, but I think [~akazakov] or Max (who I can't tag here for some reason) can point us to the correct assignee. > New and Noteworthy should list supported OpenShift v3 scenarios for 4.3.0.Beta2 > ------------------------------------------------------------------------------- > > Key: JBIDE-20406 > URL: https://issues.jboss.org/browse/JBIDE-20406 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Assignee: Misha Ali > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Beta2.html > We should list the scenarios that we are able to support in the N&N. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-467) Pull in graphiti 0.13.0 into JBTIS TP from JBoss mirror

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-467?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-467: ----------------------------- Description: *Reason:* Fuse Tooling needs the latest graphiti (0.13.0). It will be available in Eclipse Mars SR1. Until then - take it from a local JBoss mirror. *Project page/sources:* *Version:* 4.3.0.Beta1d *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/0.13.0... *Include Sources:* Yes *Affected JBoss Tools components:* Fuse Tooling, SwitchYard, BPMN2 *Include in JBDS:* Yes (JBDSIS) *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} was: Fuse Tooling needs the latest graphiti (0.13.0). It will be available in Eclipse Mars SR1. Until then - take it from a local JBoss mirror. > Pull in graphiti 0.13.0 into JBTIS TP from JBoss mirror > ------------------------------------------------------- > > Key: JBTIS-467 > URL: https://issues.jboss.org/browse/JBTIS-467 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Beta1c-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* Fuse Tooling needs the latest graphiti (0.13.0). It will be available in Eclipse Mars SR1. Until then - take it from a local JBoss mirror. > *Project page/sources:* > *Version:* 4.3.0.Beta1d > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/0.13.0... > *Include Sources:* Yes > *Affected JBoss Tools components:* Fuse Tooling, SwitchYard, BPMN2 > *Include in JBDS:* Yes (JBDSIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3119: ----------------------------------- I've found the problem with the above situation, and opened a bugzilla for it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=473971 Overall, seems unrelated to this issue, but I'm getting desperate and just throwing all xml stuff in teh same bucket ;) > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBDS-3119 > URL: https://issues.jboss.org/browse/JBDS-3119 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, server > Affects Versions: 8.0.0.Beta3 > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3119: ----------------------------------- I'm not sure this is related either, but it's possing me off, so I'm grouping it with the other xml schema validation stuff. The following XML successfully validates: {code} <?xml version="1.0" encoding="UTF-8"?> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint.xsd"> </blueprint> {code} The following fails to validate: {code} <?xml version="1.0" encoding="UTF-8"?> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint.xsd"> </blueprint> {code} The only difference is the addition of http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd in the schemaLocation field. > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBDS-3119 > URL: https://issues.jboss.org/browse/JBDS-3119 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, server > Affects Versions: 8.0.0.Beta3 > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19940) Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s)

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19940?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-19940 at 7/30/15 5:15 PM: ---------------------------------------------------------------- I did some investigation. This exception is thrown when you run code which was compiled with higher java version. Possible major/minor value : ||major||minor||Java platform version|| |45|3|1.1| |46|0|1.2| |47|0|1.3| |48|0|1.4| |49|0|1.5| |50|0|1.6| |51|0|1.7| |52|0|1.8| So it is really make sens to react on this exception just like we did for "org.osgi.framework.BundleException: Could not resolve module:" But probably we should show different message in this case was (Author: dazarov): I did some investigation. This exception is thrown when you run code which was compiled with higher java version. Possible major/minor value : ||major||minor||Java platform version|| |45|3|1.0| |45|3|1.1| |46|0|1.2| |47|0|1.3| |48|0|1.4| |49|0|1.5| |50|0|1.6| |51|0|1.7| |52|0|1.8| So it is really make sens to react on this exception just like we did for "org.osgi.framework.BundleException: Could not resolve module:" But probably we should show different message in this case > Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s) > ------------------------------------------------------------------------ > > Key: JBIDE-19940 > URL: https://issues.jboss.org/browse/JBIDE-19940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.CR1 > > > When testing JBIDE-19500 (warn/inform users running on non-compatilbe JVMs they are loosing out on features) on some old workspaces I got a situation when Eclipse didn't report a usual error saying "Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))" but I got UnsupportedClassVersionErrors like: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/jboss/tools/usage/event/UsageEventType : Unsupported major.minor version 52.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:272) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:588) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:540) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:527) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327) > at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.initializeUsageReporting(ForgeCorePlugin.java:48) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.start(ForgeCorePlugin.java:44) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764) > {code} > Maybe it's because I was running JBT from my dev eclipse environment and Eclipse used some cashed Require-Capability's of load plugins and we won't have such problems in real world when problematic plugins are installed/updated but not modified in dev environment. > But anyway, this is worth investigation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2015