January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-157) JBT documentation should not contain JBDS references

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-157?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-157: ------------------------------------------ This issue has been resolved in JBT 4.0.0 Getting Started Guide so marking as resolved. > JBT documentation should not contain JBDS references > ---------------------------------------------------- > > Key: TOOLSDOC-157 > URL: https://issues.jboss.org/browse/TOOLSDOC-157 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 3.2.0.Final > Reporter: Jiri Peterka > Assignee: Isaac Rooskov > Fix For: Future > > > JBT documentation should not contain JBDS installation instructions and other product references > http://docs.jboss.org/tools/3.2.0.Beta1/en/GettingStartedGuide/html_singl... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-157) JBT documentation should not contain JBDS references

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-157?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-157. -------------------------------------- Resolution: Done > JBT documentation should not contain JBDS references > ---------------------------------------------------- > > Key: TOOLSDOC-157 > URL: https://issues.jboss.org/browse/TOOLSDOC-157 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 3.2.0.Final > Reporter: Jiri Peterka > Assignee: Isaac Rooskov > Fix For: Future > > > JBT documentation should not contain JBDS installation instructions and other product references > http://docs.jboss.org/tools/3.2.0.Beta1/en/GettingStartedGuide/html_singl... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11411) OpenShift server adapter: Warn user when the deployments folder is changed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11411?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11411: ------------------------------------- Hey andre, can you "set the stage" here with some examples for me? A use case, with setup, and what we want to happen instead? Thanks. > OpenShift server adapter: Warn user when the deployments folder is changed > -------------------------------------------------------------------------- > > Key: JBIDE-11411 > URL: https://issues.jboss.org/browse/JBIDE-11411 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.x > > > As Max comment: > We could warn the user if the deployments folder is not deployments (or even better look for .openshift/config/standalone.xml setting if the apptype is JBoss and only validate then) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11411) OpenShift server adapter: Warn user when the deployments folder is changed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11411?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-11411: ----------------------------------- Assignee: Andre Dietisheim (was: Rob Stryker) > OpenShift server adapter: Warn user when the deployments folder is changed > -------------------------------------------------------------------------- > > Key: JBIDE-11411 > URL: https://issues.jboss.org/browse/JBIDE-11411 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > > As Max comment: > We could warn the user if the deployments folder is not deployments (or even better look for .openshift/config/standalone.xml setting if the apptype is JBoss and only validate then) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-291) Update screenshots for JBoss Tools Getting Started Guide installation chapter

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-291?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-291. -------------------------------------- Fix Version/s: 4.0.0.Final Resolution: Done Changes were live at 10th Jan 2013. > Update screenshots for JBoss Tools Getting Started Guide installation chapter > ----------------------------------------------------------------------------- > > Key: TOOLSDOC-291 > URL: https://issues.jboss.org/browse/TOOLSDOC-291 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 3.3.0.Beta1 > Reporter: Michelle Murray > Assignee: Isaac Rooskov > Fix For: 4.0.0.Final > > > About: JBoss Tools, Getting Started Guide, 3.3.0Beta1 > Issue: Existing screenshots for installing JBoss Tools are outdated for Eclipse 4.2.0 SR1, namely Figures 1.1-1.9. And the text relating to the 'Restart Eclipse' dialog (Fig1.8) needs updating as the buttons are now Yes and No. > Workaround: > * Replace figures 1.1-1.9. > * [1.1, After Fig1.8, P1, L1] Click the Restart Now buttton ... > Click the Yes button ... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-291) Update screenshots for JBoss Tools Getting Started Guide installation chapter

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-291?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-291: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-documentation/pull/12 > Update screenshots for JBoss Tools Getting Started Guide installation chapter > ----------------------------------------------------------------------------- > > Key: TOOLSDOC-291 > URL: https://issues.jboss.org/browse/TOOLSDOC-291 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 3.3.0.Beta1 > Reporter: Michelle Murray > Assignee: Isaac Rooskov > > About: JBoss Tools, Getting Started Guide, 3.3.0Beta1 > Issue: Existing screenshots for installing JBoss Tools are outdated for Eclipse 4.2.0 SR1, namely Figures 1.1-1.9. And the text relating to the 'Restart Eclipse' dialog (Fig1.8) needs updating as the buttons are now Yes and No. > Workaround: > * Replace figures 1.1-1.9. > * [1.1, After Fig1.8, P1, L1] Click the Restart Now buttton ... > Click the Yes button ... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13348: ------------------------------------- When will there be a new 3.3.x build to test against? I've committed the following to 3.3.x: Author: rob.stryker(a)jboss.com Date: 2013-01-09 07:01:36 -0500 (Wed, 09 Jan 2013) New Revision: 44650 It looks like it adds a complete method, but really it's an identical clone of the method above it. I preferred to copy-paste the entire method (only a few lines) rather than have one point to the other, due to fears of somehow initiating infinite loops. (ie, foo(IServer s) { foo((IServerAttributes)s); } ) This should replace the missing method. > Cannot deploy BPEL project > -------------------------- > > Key: JBIDE-13348 > URL: https://issues.jboss.org/browse/JBIDE-13348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, SOA Tooling > Affects Versions: 3.3.2 > Reporter: Andrej Podhradsky > Assignee: Rob Stryker > Priority: Blocker > > After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server. > See JBDS-2437 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-293) http://docs.jboss.org/tools/nightly/trunk/ gives 404 Not Found

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-293?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-293: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-documentation/pull/23, https://github.com/jbosstools/jbosstools-documentation/pull/25, https://github.com/jbosstools/jbosstools-documentation/pull/26 (was: https://github.com/jbosstools/jbosstools-documentation/pull/23, https://github.com/jbosstools/jbosstools-documentation/pull/25) > http://docs.jboss.org/tools/nightly/trunk/ gives 404 Not Found > -------------------------------------------------------------- > > Key: TOOLSDOC-293 > URL: https://issues.jboss.org/browse/TOOLSDOC-293 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Affects Versions: 4.0.0.CR1 > Reporter: Pavol Srna > Assignee: Michelle Murray > Priority: Critical > Fix For: 4.0.0.CR1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13346: -------------------------------- Priority: Minor (was: Major) > DirectoryScanner fails on non-existing folders > ---------------------------------------------- > > Key: JBIDE-13346 > URL: https://issues.jboss.org/browse/JBIDE-13346 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives, JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: Windows XP/Windows 7 > Eclipse 4.3M4 > Reporter: Jesper Skov > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: org.eclipse.wst.common.component > > > DirectoryScanner can be made to fail on non-existing folders. > In our setup, these folders are possibly picked up from the Deployment Assembly settings. > The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse. > But it seems the Archive DirectoryScanner runs before our builder. > The stack trace looks like this: > > {code} > java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552) > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588) > at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13346: ------------------------------------- Is the attached stack trace from an error log entry? Looking at the codebase, it seems it's a logged warning. It seems it should have no real effect on anything. When you try to publish, are you noticing all required resources? Or not? Looking at teh code, a new root folder is created every time on request (not cached), so even with the error being logged, it seems we should just supress the error in this situation if everything else is working ok. Can you verify the rest of the behavior is working properly? Just that a warning is logged when it doesn't need to be? > DirectoryScanner fails on non-existing folders > ---------------------------------------------- > > Key: JBIDE-13346 > URL: https://issues.jboss.org/browse/JBIDE-13346 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Windows XP/Windows 7 > Eclipse 4.3M4 > Reporter: Jesper Skov > Assignee: Rob Stryker > Attachments: org.eclipse.wst.common.component > > > DirectoryScanner can be made to fail on non-existing folders. > In our setup, these folders are possibly picked up from the Deployment Assembly settings. > The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse. > But it seems the Archive DirectoryScanner runs before our builder. > The stack trace looks like this: > > {code} > java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552) > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588) > at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 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 January 2013