[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ]
Michelle Murray resolved JBIDE-13346.
-------------------------------------
Resolution: Done
Resetting resolution after reopening to edit release notes text
> 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, 1 month
[JBoss JIRA] (JBIDE-13779) About Dialog - What version of Eclipse am I running?
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-13779:
-----------------------------------
Summary: About Dialog - What version of Eclipse am I running?
Key: JBIDE-13779
URL: https://issues.jboss.org/browse/JBIDE-13779
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
Priority: Minor
How does someone answer the following question:
What version of Eclipse is "inside" JBoss Developer Studio?
Ideally, the string of "Eclipse Juno 4.2.1" and its build-id would be listed underneath the JBDS version, build id and build date.
--
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, 1 month
[JBoss JIRA] (JBIDE-13727) Enable generation of tests for Seam components
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13727?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13727:
-----------------------------------
Fix Version/s: 4.1.x
> Enable generation of tests for Seam components
> ----------------------------------------------
>
> Key: JBIDE-13727
> URL: https://issues.jboss.org/browse/JBIDE-13727
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Seam 2
> Affects Versions: 4.0.0.Final
> Environment: JBDS 6.0.0.GA
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.1.x
>
>
> Currently the test generation for Seam Action, Form is disabled (but not properly - see JBIDE-13596) because of previous Seam version (I guess 2.3.0.Final). In latest Seam version test can be already generated by seam-gen and are even valid and usable.
> JBDS should enable and support this functionality again.
--
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, 1 month
[JBoss JIRA] (JBIDE-13775) Add option 'Add references to JS/CSS' to Mobile Palette wizards
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13775?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13775:
-----------------------------------
Description:
Checkbox 'Add references to JS/CSS' at the bottom of each wizard.
Default state is true. Last choice is saved and applied to any Mobile Palette wizard.
!scr2.png!
was:
Checkbox 'Add references to JS/CSS' at the bottom of each wizard.
Default state is true. Last choice is saved and applied to any Mobile Palette wizard.
!scr.png!
> Add option 'Add references to JS/CSS' to Mobile Palette wizards
> ---------------------------------------------------------------
>
> Key: JBIDE-13775
> URL: https://issues.jboss.org/browse/JBIDE-13775
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
> Attachments: scr.png, scr2.png
>
>
> Checkbox 'Add references to JS/CSS' at the bottom of each wizard.
> Default state is true. Last choice is saved and applied to any Mobile Palette wizard.
> !scr2.png!
--
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, 1 month