[
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