[JBoss JIRA] (JBIDE-19079) SWTException when creating JPA 2.0 project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19079?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19079:
------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> SWTException when creating JPA 2.0 project
> ------------------------------------------
>
> Key: JBIDE-19079
> URL: https://issues.jboss.org/browse/JBIDE-19079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.3.0.CR1
>
>
> This is the produced stacktrace:
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
> at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:903)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.refreshTree(KnownConfigurationsProvider.java:91)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.access$0(KnownConfigurationsProvider.java:85)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider$KnownConfigurationsVisitor.visit(KnownConfigurationsProvider.java:163)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.resourceChanged(KnownConfigurationsProvider.java:141)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19795:
-------------------------------------
[~akazakov], I would probably write a blog next week
> Bower support
> -------------
>
> Key: JBIDE-19795
> URL: https://issues.jboss.org/browse/JBIDE-19795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: javascript
> Affects Versions: 4.3.0.Alpha2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta2
>
>
> Need to have initial [Bower|http://bower.io/] tools support:
> *The gist*
> Bower tooling should initially support several bower API commands :
> |Command||Description|
> | *bower init* |creates a *bower.json* file|
> |*bower install <package>*|installs packages to *bower_components* folder|
> |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory|
> |*bower update* |updates installed packages to their newest version according to *bower.json*|
> Basically, the main idea of the implementation is the following:
> Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*
> Native bower tools must be preinstalled
> *The main questions & proposals:*
> 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.)
> 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature?
> 3. Implementation details:
> - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* )
> - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17710) error importing kitchensink angularjs quickstart when no jboss-eap runtime available
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17710?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-17710:
------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> error importing kitchensink angularjs quickstart when no jboss-eap runtime available
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17710
> URL: https://issues.jboss.org/browse/JBIDE-17710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Beta2
> Environment: Linux 64 (Fedora 18), JDK 1.8
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.3.0.CR1
>
> Attachments: config-jboss-maven.png, error-quickstart-kitchensink-angularjs.png, install-jpa2-NPE.txt, jbds8b3a-jdk8-quickstart-angularjs-launch-no-NPE-thrown-simpler-settings.xml.png, jbds8b3a-jdk8-quickstart-angularjs-launch-no-server-runtime-found-imports-fine-only-1-warning-compiles-ok.png, jbds8b3a-jdk8-quickstart-angularjs-launch-no-server-runtime-found.png, jbds8b3a-jdk8-quickstart-angularjs-launch-NPE-thrown.log.txt, settings.xml
>
>
> 1. install JBDS 8.0.0.Beta2-v20140617-2058-B166 from update site into Eclipse 4.4.0.R Luna JEE bundle.
> 2. Install Arquillian from JBoss Central EA site (using -D flags above)
> 3. launch kitchensink-angularjs quickstart.
> 4. Get NPE installing JPA 2.0
> 5. Get numerous import problems in MemberRegistrationTest.java and other source files; quickfixes don't work.
> Also had the same issues with JBT 4.2.0.Beta2, so it doesn't seem this is a JBDS only issue.
> !error-quickstart-kitchensink-angularjs.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months