[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13346:
----------------------------------------
Release Notes Text:
Cause: If the Deployment assembly preference for projects referenced directories that does not exist an error was unnecessarily logged as an error with a full stack trace.
Consequence: A user having a project where not all directories are present during the build cycle could see this error and think it was a bug even when it has no impact on his project.
Fix: Server tools do no longer log the error, as it is not a critical error.
Result: There are no more logging of this special case and users should not get a long list of these errors on every build cycle.
was:
Cause: We logged errors in a situation where the error was not critical.
Consequence: A user (in very specific circumstances) may receive an error in their error log when it is not necessary to log such an error.
Fix: Do not log the error, as it is not critical.
Result: The user no longer sees the error.
> 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] (JBDS-2365) ESB projects cannot be deployed using Server Add/Remove
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2365?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2365:
----------------------------------
Release Notes Text:
Cause: as.core (Server tools) did not list ESB 4.11 and 4.12 as a compatible runtime/facet to use together with AS and EAP servers.
Consequence: When using ESB tooling the wizards to create ESB 4.11 and 4.12 projects the projects were not possible to deploy to the server because the project was considered incompatible with the servers.
Fix: The list of compatible facets/runtimes now list ESB 4.11 and 4.12 for the AS and EAP server's. JBIDE-13328 includes additional fixing to make it possible for the esb project to manage this without updates to the server core.
Result: ESB 4.11 and 4.12 projects can be deployed using the server adapter without errors/warnings.
was:
Cause: as.core did not list ESB 4.11 and 4.12 as a compatible runtime/facet to use together with AS and EAP servers.
Consequence: When using ESB tooling the wizards to create ESB 4.11 and 4.12 projects the projects were not possible to deploy to the server because the project was considered incompatible with the servers.
Fix: The list of compatible facets/runtimes now list ESB 4.11 and 4.12 for the AS and EAP server's. JBIDE-13328 includes additional fixing to make it possible for the esb project to manage this without updates to the server core.
Result: ESB 4.11 and 4.12 projects can be deployed using the server adapter without errors/warnings.
> ESB projects cannot be deployed using Server Add/Remove
> -------------------------------------------------------
>
> Key: JBDS-2365
> URL: https://issues.jboss.org/browse/JBDS-2365
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Jeremy Davis
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 6.0.0.CR1, 6.0.1.GA
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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] (JBDS-2365) ESB projects cannot be deployed using Server Add/Remove
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2365?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2365:
--------------------------------------
Release Notes Text:
Cause: as.core did not list ESB 4.11 and 4.12 as a compatible runtime/facet to use together with AS and EAP servers.
Consequence: When using ESB tooling the wizards to create ESB 4.11 and 4.12 projects the projects were not possible to deploy to the server because the project was considered incompatible with the servers.
Fix: The list of compatible facets/runtimes now list ESB 4.11 and 4.12 for the AS and EAP server's. JBIDE-13328 includes additional fixing to make it possible for the esb project to manage this without updates to the server core.
Result: ESB 4.11 and 4.12 projects can be deployed using the server adapter without errors/warnings.
was:
Cause: as.core plugin did not know what ESB 4.11 or 4.12 was, so would not detect those runtimes
Consequence: as.core plugin did not know what ESB 4.11 or 4.12 was, so would not detect those runtimes
Fix: make as.core plugin know what ESB 4.11 & 4.12 are, so could detect those runtimes
Result: ESB 4.11 and 4.12 projects can be deployed using JBDS.
> ESB projects cannot be deployed using Server Add/Remove
> -------------------------------------------------------
>
> Key: JBDS-2365
> URL: https://issues.jboss.org/browse/JBDS-2365
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Jeremy Davis
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 6.0.0.CR1, 6.0.1.GA
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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-13769) Cannot import OpenShift maven project twice: "Could not import project null"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13769?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13769:
-------------------------------------
Attachment: could-not-maven-import-null.png
> Cannot import OpenShift maven project twice: "Could not import project null"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-13769
> URL: https://issues.jboss.org/browse/JBIDE-13769
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: could-not-maven-import-null.png
>
>
> You cannot import an OpenShift java/maven project twice since the project name has to be unique within the very same Eclipse workspace. The OpenShift import wizard errors while importing and reports that it could not import the maven project *null*.
> !could-not-maven-import-null.png!
> We cannot change the wizard to error before importing since we have to clone the application repo and look into the pom to find out about the name clash.
> Nevertheless, we should fix the lacking error message that's missing the project name.
--
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-13769) Cannot import OpenShift maven project twice: "Could not import project null"
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13769:
----------------------------------------
Summary: Cannot import OpenShift maven project twice: "Could not import project null"
Key: JBIDE-13769
URL: https://issues.jboss.org/browse/JBIDE-13769
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 4.1.x
You cannot import an OpenShift java/maven project twice since the project name has to be unique within the very same Eclipse workspace. The OpenShift import wizard errors while importing and reports that it could not import the maven project *null*.
!could-not-maven-import-null.png!
We cannot change the wizard to error before importing since we have to clone the application repo and look into the pom to find out about the name clash.
Nevertheless, we should fix the lacking error message that's missing the project name.
--
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] (JBDS-2438) include EAP 6.0.1 in JBDS 6.0.1 installer
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2438?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2438:
---------------------------------------
[~nickboldt] Regarding, "Do RN need to be this verbose?": this style ensures devs provide all the information needed for sufficiently detailed and coherent release notes to be created. While it might not appear necessary for simple JIRAs such as this, it is very helpful in more complicated ones. FYI: I edit and restructure the text into something less turgid before it goes out in the final release notes document.
> include EAP 6.0.1 in JBDS 6.0.1 installer
> -----------------------------------------
>
> Key: JBDS-2438
> URL: https://issues.jboss.org/browse/JBDS-2438
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 6.0.1.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 6.0.1.GA
>
> Attachments: JBDS2438.patch.txt, JBDS2438.patch2.txt
>
>
> EAP 6.0.1 is out. Time to update the installer to include the latest n' greatest EAP 6.
--
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-13413) jQuery Mobile Widget Palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13413:
----------------------------------
Attachment: jQueryMobile.png
> jQuery Mobile Widget Palette
> ----------------------------
>
> Key: JBIDE-13413
> URL: https://issues.jboss.org/browse/JBIDE-13413
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.x
>
> Attachments: CSS-Preview.png, Dialog.png, DialogWizBan.png, Images.zip, jQueryMobile.png, jQueryMobile.png, jQueryMobile.png, jQueryMobile.png, Listview.png, ListviewWizBan.png, NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewCheckboxWizard.png, NewCheckboxWizard.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, PaletteThinLines.png, Palette_1.png, Palette_2.png, Palette_3.png, withwithoutpreview.bmml, withwithoutpreview.png
>
>
> http://jquerymobile.com/test/
> See my proposal regarding the content of jQuery Mobile palette below.
> Also I have an idea to add a live preview into each wizard.
> We could try to add a browser to the wizard which will show how the widget is going to look.
> !jQueryMobile.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
[JBoss JIRA] (JBDS-2486) Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2486:
----------------------------------
This change breaks out Central connectors too:
{code:title=when installing into JBDS 7.0.0.Alpha1 from 7.0-development site}
Problems occurred while performing installation: The following connectors are not available:
Google Plugin + Web Toolkit (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/),
Google Web Toolkit Designer (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/)
The following connectors are not available:
Google Plugin + Web Toolkit (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/),
Google Web Toolkit Designer (id=com.google.gwt.eclipse.sdkbundle.e42.feature.feature.group, site=https://devstudio.jboss.com/updates/7.0-development/central/core/)
{code}
> Investigate use of GWT/GPE 3.2.0.v201302131858-rel-r42 in Central
> -----------------------------------------------------------------
>
> Key: JBDS-2486
> URL: https://issues.jboss.org/browse/JBDS-2486
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, central
> Affects Versions: 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 7.0.0.Alpha2
>
>
> New 3.2.0 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013...
> https://devstudio.jboss.com/updates/requirements/gwt/3.2.0.v201302131858-...
> New composites:
> http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/
> https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.1/
> Note that at least one IU had been renamed:
> OLD: com.google.gwt.eclipse.sdkbundle.e42.feature
> NEW: com.google.gwt.eclipse.sdkbundle.feature
--
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