[JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration doesn't select Java 7 by default
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18700:
--------------------------------
Fix Version/s: 4.3.0.Alpha1
> EAP 6.x Configuration doesn't select Java 7 by default
> ------------------------------------------------------
>
> Key: JBIDE-18700
> URL: https://issues.jboss.org/browse/JBIDE-18700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
>
> - Create a new EAP 6.3 server
> - Create a new Dynamic Web Project
> - Select the EAP runtime
> => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer."
> !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png!
> The EAP 6 Default Configuration should have the Java 1.7 Facet set by default.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration doesn't select Java 7 by default
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18700:
-------------------------------------
We have a few options here, but not really ;) We're basically stuck and have to wait for new API =P
Our current API only has a minimum execution environment. If we move this up to java7 for eap6.x, then unfortunately java6 will no longer appear as an option to users for any eap6.x server. This obviously isn't acceptable. We should ideally have a minimim execenv, a maximum, and a default, for each server/runtime type.
The second problem is that AbstractJREComposite unfortunately fills its data during its constructor, rather than fit in with the workflow of the other widgets like RuntimeHomeComposite which are created first, and filled after the runtime working copy has been created. That should be an easy fix, though, and may open the possibility that we could ensure different default / min / max execenv depending on the inner details of a given server home.
But, since we're lacking that api, and currently only have minimums, I think we're pretty stuck here until API addition has occurred.
> EAP 6.x Configuration doesn't select Java 7 by default
> ------------------------------------------------------
>
> Key: JBIDE-18700
> URL: https://issues.jboss.org/browse/JBIDE-18700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Reporter: Fred Bricon
> Assignee: Rob Stryker
>
> - Create a new EAP 6.3 server
> - Create a new Dynamic Web Project
> - Select the EAP runtime
> => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer."
> !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png!
> The EAP 6 Default Configuration should have the Java 1.7 Facet set by default.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18708) Provide content assist on hibernate properties values in persistence.xml
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18708:
-------------------------------------
Summary: Provide content assist on hibernate properties values in persistence.xml
Key: JBIDE-18708
URL: https://issues.jboss.org/browse/JBIDE-18708
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: hibernate
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
in persistence.xml, it would be convenient to have content assist on values for Hibernate properties such as those below:
{code}
<property name="hibernate.hbm2ddl.auto" value="create-drop" />
<property name="hibernate.show_sql" value="false" />
{code}
especially the alternative values to {{create-drop}} ;-)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18696:
------------------------------------------
ok, thanks that clarifies it.
The weird part is that you cannot replicate it in OpenShift online and so can't I.
Does refreshing your connection in OpenShift Explorer (in OpenShift Explorer: pick "Refresh" in the context menu of the connection) help?
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18707) FrameworkEvent ERROR
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18707:
-------------------------------------
Summary: FrameworkEvent ERROR
Key: JBIDE-18707
URL: https://issues.jboss.org/browse/JBIDE-18707
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
This error appeared in my Error Log after I exited JBDS 8.0.0.Final:
{code}
org.osgi.framework.BundleException: Exception in org.jboss.tools.central.JBossCentralActivator.stop() of bundle org.jboss.tools.central.
at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:847)
at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:950)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:324)
at org.eclipse.osgi.container.Module.doStop(Module.java:626)
at org.eclipse.osgi.container.Module.stop(Module.java:488)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1623)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1542)
at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:248)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:145)
at org.eclipse.osgi.container.Module.doStop(Module.java:626)
at org.eclipse.osgi.container.Module.stop(Module.java:488)
at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:186)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:160)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.eclipse.swt.SWTException: Invalid thread access
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.Display.error(Display.java:1083)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:840)
at org.eclipse.swt.widgets.Display.create(Display.java:823)
at org.eclipse.swt.graphics.Device.<init>(Device.java:130)
at org.eclipse.swt.widgets.Display.<init>(Display.java:714)
at org.eclipse.swt.widgets.Display.<init>(Display.java:705)
at org.eclipse.swt.widgets.Display.getDefault(Display.java:1403)
at org.jboss.tools.central.JBossCentralActivator.stop(JBossCentralActivator.java:215)
at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:827)
at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:820)
... 13 more
Root exception:
org.eclipse.swt.SWTException: Invalid thread access
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.Display.error(Display.java:1083)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:840)
at org.eclipse.swt.widgets.Display.create(Display.java:823)
at org.eclipse.swt.graphics.Device.<init>(Device.java:130)
at org.eclipse.swt.widgets.Display.<init>(Display.java:714)
at org.eclipse.swt.widgets.Display.<init>(Display.java:705)
at org.eclipse.swt.widgets.Display.getDefault(Display.java:1403)
at org.jboss.tools.central.JBossCentralActivator.stop(JBossCentralActivator.java:215)
at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:827)
at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:820)
at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:950)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:324)
at org.eclipse.osgi.container.Module.doStop(Module.java:626)
at org.eclipse.osgi.container.Module.stop(Module.java:488)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1623)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1542)
at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:248)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:145)
at org.eclipse.osgi.container.Module.doStop(Module.java:626)
at org.eclipse.osgi.container.Module.stop(Module.java:488)
at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:186)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:160)
at java.lang.Thread.run(Thread.java:744)
{code}
Note: I exited JBDS after my laptop came back from a long week-end of hibernation, because I wanted to start using the IDE with a fresh JVM. Not sure if this can be related to the problem reported here, though.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18706) NPE wrt JPA when creating a new Java EE7/Maven project
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18706:
-------------------------------------
Summary: NPE wrt JPA when creating a new Java EE7/Maven project
Key: JBIDE-18706
URL: https://issues.jboss.org/browse/JBIDE-18706
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate, maven
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
I got the following error when creating a new Maven project using the 'wildfly-javaee7-blank-archetype' archetype:
{code}
java.lang.NullPointerException
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.defaultResourceLocation(JpaFacetInstallDelegate.java:123)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:107)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:100)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:61)
at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:35)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:154)
at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:109)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:250)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:163)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:109)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:789)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:719)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:717)
at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard$5.doCreateMavenProjects(MavenProjectWizard.java:244)
at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:46)
at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62)
at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:50)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-17545) Can't Full Publish project to WildFly (8.0 or 8.1)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17545?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17545:
-------------------------------------
Could be related to https://issues.jboss.org/browse/JBIDE-18697 which was at it's heart a permission error.
> Can't Full Publish project to WildFly (8.0 or 8.1)
> --------------------------------------------------
>
> Key: JBIDE-17545
> URL: https://issues.jboss.org/browse/JBIDE-17545
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Lincoln Baxter III
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> The following error is logged and publishing fails when attempting to Full Publish this project:
> https://github.com/forgeide/forgeide
> {code}
> Publishing failed
> Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1118502157688228046.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/forge-javassist-2.jar.
> This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp1738236936180964755.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jboss-modules-1.3.0.Final-forge.jar.
> This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> Error renaming /Users/lb3/lib/wildfly-8.1.0.Final/standalone/tmp/tmp2320075067441042997.jar to /Users/lb3/lib/wildfly-8.1.0.Final/standalone/deployments/forgeide.war/WEB-INF/lib/furnace-se-2.6.1-SNAPSHOT.jar/bootpath/jgrapht-0.8.3.jar.
> This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Chunyun Chen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Chunyun Chen edited comment on JBIDE-18696 at 10/27/14 5:47 AM:
----------------------------------------------------------------
[~adietish] Sorry for confused, my mean above is that the quickstarts are always existed after restarting Eclipse once, so every later attempt always have quickstarts.
So my means are:
1. Try to create a new application but dont see the quickstarts
2. Restart Eclipse
3. Have the quickstarts listed
4. Try to create another application
5. Also have quickstarts listed
..........................................................................
Always have the quickstarts listed after step 2, so do not need restart Eclipse to show quickstarts tree any more after step 2
..........................................................................
was (Author: cathat):
[~adietish] Sorry for confused, my mean above is that the quickstarts are always existed after restarting Eclipse once, so every later attempt always have quickstarts.
So my means are:
1. Try to create a new application but dont see the quickstarts
2. Restart Eclipse
3. Have the quickstarts listed
4. Try to create another application
5. Do have quickstarts listed
..........................................................................
Always have the quickstarts listed after step 2, so do not need restart Eclipse to show quickstarts tree any more after step 2
..........................................................................
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months