[JBoss JIRA] (TOOLSDOC-295) Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-295?page=com.atlassian.jira.plug... ]
Mustafa Musaji commented on TOOLSDOC-295:
-----------------------------------------
I'd also like to suggest that the point "NOTE" containing the section on using 'alternatives' may be better placed at the top of section 3.1.1 rather than in the middle.
> Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux
> ---------------------------------------------------------------------------------
>
> Key: TOOLSDOC-295
> URL: https://issues.jboss.org/browse/TOOLSDOC-295
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.0.0.CR1
>
>
> In GSG for JBDS 6 [1], section *3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux*, I see:
> {quote}
> You only need to run "alternative" as a safe guard for the right JVM.
> {quote}
> Suggest changing this to:
> {quote}
> You only need to run *alternatives* to select the correct default JDK.
> {quote}
> [1] https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0...
> Note too that the JDK referenced is now called the Oracle JDK, not the Sun JDK.
> {quote}
> 3.1.1. Installing and Configuring 32-bit *Sun* JDK 6 on Linux
> To install 32-bit *Sun* JDK 6 on Linux and configure it, you should follow the next steps:
> Download the *Sun* JDK 6 from *Sun*'s website.
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (TOOLSDOC-295) Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux
by Nick Boldt (JIRA)
Nick Boldt created TOOLSDOC-295:
-----------------------------------
Summary: Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux
Key: TOOLSDOC-295
URL: https://issues.jboss.org/browse/TOOLSDOC-295
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Getting Started Guide
Reporter: Nick Boldt
Assignee: Michelle Murray
Fix For: 4.0.0.CR1
In GSG for JBDS 6 [1], section *3.1.1. Installing and Configuring 32-bit Sun JDK 6 on Linux*, I see:
{quote}
You only need to run "alternative" as a safe guard for the right JVM.
{quote}
Suggest changing this to:
{quote}
You only need to run *alternatives* to select the correct default JDK.
{quote}
[1] https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0...
Note too that the JDK referenced is now called the Oracle JDK, not the Sun JDK.
{quote}
3.1.1. Installing and Configuring 32-bit *Sun* JDK 6 on Linux
To install 32-bit *Sun* JDK 6 on Linux and configure it, you should follow the next steps:
Download the *Sun* JDK 6 from *Sun*'s website.
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13323) integration-tests: cannot build CDI bot tests
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13323?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič commented on JBIDE-13323:
-------------------------------------------
When using default configuration (not a custom settings.xml file) everything is going fine. There is a problem with our local repository on jawa32 machine.
> integration-tests: cannot build CDI bot tests
> ---------------------------------------------
>
> Key: JBIDE-13323
> URL: https://issues.jboss.org/browse/JBIDE-13323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: QA
> Affects Versions: 4.0.0.Final
> Environment: clean (empty) .m2 repo
> Reporter: Pavol Srna
> Assignee: Jaroslav Jankovič
> Fix For: 4.0.0.Final
>
>
> {code}
> psrna@psrna-laptop:~/data/jbosstools-integration-tests/tests$ mvn verify -Dmaven.test.skip -Dswtbot.test.skip
> [INFO] Scanning for projects...
> [INFO] Computing target platform for MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.bot.test/pom.xml
> [INFO] Adding repository http://p2-reddeer.rhcloud.com/master
> [INFO] Adding repository http://p2-reddeer.rhcloud.com/master
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.bot.test/pom.xml
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving class path of MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.bot.test/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.cdi:org.jboss.tools.cdi.reddeer:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.reddeer/pom.xml
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.cdi:org.jboss.tools.cdi.reddeer:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.reddeer/pom.xml
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Loading repository 'http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO' from mirror 'target-platform-minimum' at 'http://jawa32.mw.lab.eng.brq.redhat.com:8081/nexus/content/repositories/j...'
> [INFO] Resolving class path of MavenProject: org.jboss.tools.cdi:org.jboss.tools.cdi.reddeer:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.reddeer/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.seam3.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.seam3.bot.test/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.cdi.tests:org.jboss.tools.cdi.seam3.bot.test:4.0.0-SNAPSHOT @ /home/psrna/data/jbosstools-integration-tests/tests/org.jboss.tools.cdi.seam3.bot.test/pom.xml
> [INFO] Cannot complete the request. Generating details.
> [INFO] Cannot complete the request. Generating details.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.cdi.seam3.bot.test 4.0.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.cdi.reddeer 4.0.0.qualifier requires 'bundle org.jboss.reddeer.swt 0.0.0' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.cdi.bot.test 4.0.0.qualifier depends on: bundle org.jboss.tools.cdi.reddeer 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.cdi.seam3.bot.test 4.0.0.qualifier depends on: bundle org.jboss.tools.cdi.bot.test 1.2.0
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "No solution found because the problem is unsatisfiable."]
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.bot.test 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.swt 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.jface 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.eclipse 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.cdi.reddeer 4.0.0.qualifier to bundle org.jboss.reddeer.workbench 0.0.0.", "No solution found because the problem is unsatisfiable."]
> at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77)
> at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89)
> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122)
> at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80)
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377)
> at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354)
> at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103)
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> ... 11 more
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory
by Ondrej Skutka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2439?page=com.atlassian.jira.plugin.... ]
Ondrej Skutka commented on JBDS-2439:
-------------------------------------
An easy fix is to replace the {code}./studio/jbdevstudio{code} with {code}$(dirname "$0")/studio/jbdevstudio{code}
> jbdevstudio-unity execution fails when called from different working directory
> ------------------------------------------------------------------------------
>
> Key: JBDS-2439
> URL: https://issues.jboss.org/browse/JBDS-2439
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.GA
> Reporter: Ondrej Skutka
>
> jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir.
> This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory
by Ondrej Skutka (JIRA)
Ondrej Skutka created JBDS-2439:
-----------------------------------
Summary: jbdevstudio-unity execution fails when called from different working directory
Key: JBDS-2439
URL: https://issues.jboss.org/browse/JBDS-2439
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.GA
Reporter: Ondrej Skutka
jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir.
This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13076) Marker Resolution Generators should check if IMarker exists
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13076?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13076:
----------------------------------------
Pushed the new PR to master
> Marker Resolution Generators should check if IMarker exists
> ------------------------------------------------------------
>
> Key: JBIDE-13076
> URL: https://issues.jboss.org/browse/JBIDE-13076
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: CDI, central, common/jst/core, JSF, Seam 2
> Affects Versions: 4.0.0.Beta2
> Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.Beta2-v20121107-1854-B62.jar
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha1
>
>
> When Marker Resolution Generator tries to find quick fixes for Problem Marker marker may not be exist any more. In that case we can get follow Exception:
> {code}
> org.eclipse.core.internal.resources.ResourceException: Marker id 5 not found.
> at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57)
> at org.eclipse.core.internal.resources.Marker.getType(Marker.java:195)
> at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.getProblemType(ConfigureProblemSeverityResolutionGenerator.java:140)
> at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.hasResolutions(ConfigureProblemSeverityResolutionGenerator.java:124)
> at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolution(MarkerHelpRegistry.java:191)
> at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolutions(MarkerHelpRegistry.java:160)
> at org.eclipse.ui.views.markers.MarkerField.annotateImage(MarkerField.java:76)
> at org.eclipse.ui.internal.views.markers.MarkerProblemSeverityAndMessageField.update(MarkerProblemSeverityAndMessageField.java:86)
> at org.eclipse.ui.internal.views.markers.MarkerColumnLabelProvider.update(MarkerColumnLabelProvider.java:62)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:953)
> at org.eclipse.ui.internal.views.markers.MarkersTreeViewer.doUpdateItem(MarkersTreeViewer.java:73)
> at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:113)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1033)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
> at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2753)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1923)
> at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1930)
> at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1898)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1855)
> at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
> at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533)
> at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548)
> at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1490)
> at org.eclipse.ui.internal.views.markers.UIUpdateJob.runInUIThread(UIUpdateJob.java:108)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3529)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3182)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> {code}
> I saw such exceptions only when I was working in Visual Page Editor.
> May by this is WTP related issue.
> So lets add check IMarker.exists() to hasResolutions(IMarker) methods to all our Marker Resolution Generators which work with jsp, xhtml and xml files:
> *jbosstools-javaee*
> 1. org.jboss.tools.cdi.ui.marker.CDIProblemMarkerResolutionGenerator
> 2. org.jboss.tools.seam.ui.marker.SeamProblemMarkerResolutionGenerator
> 3. org.jboss.tools.jsf.ui.marker.DisableFaceletHTMLValidatorResolutionGenerator
> 4. org.jboss.tools.jsf.web.validation.jsf2.action.JSF2ComponentResolutionGenerator
> *jbosstools-jst*
> 1. org.jboss.tools.jst.web.ui.action.JSPProblemMarkerResolutionGenerator
> *jbosstools-base*
> 1. org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-9719) Deploys Teiid artifacts to deploy folder configured in JBDS
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9719?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on JBIDE-9719:
-------------------------------------
For Designer 8.0 we implemented the changes necessary to maintain current feature set. This includes deploying VDB's and creating Data Sources through Teiid's API. VDB's get deployed as "metadata", not as standard artifacts. For Data Sources, Teiid utilizes AS7 functionality and Designer will deploy the connection profile jars to the appropriate server folder.
> Deploys Teiid artifacts to deploy folder configured in JBDS
> -----------------------------------------------------------
>
> Key: JBIDE-9719
> URL: https://issues.jboss.org/browse/JBIDE-9719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: teiid
> Reporter: Joao Viragine
> Assignee: Barry LaFond
> Fix For: 4.0.0.Alpha1-SOA
>
>
> When we deploy Teiid artifacts (like Datasources, VDB), JBDS *always* deploys the artifacts to JBoss deploy folder. It should use deploy folder configured in JBDS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months