[JBoss JIRA] (JBIDE-12784) IllegalArgumentException after importing HTML5 project from JBoss Central
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-12784:
--------------------------------------
Summary: IllegalArgumentException after importing HTML5 project from JBoss Central
Key: JBIDE-12784
URL: https://issues.jboss.org/browse/JBIDE-12784
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate, project-examples
Affects Versions: 4.0.0.Alpha2
Reporter: Stefan Bunciak
Assignee: Dmitry Geraskov
Fix For: 4.0.0.Beta1
{code}duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)){code}
Stack trace:
{code}
java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5))
at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95)
at org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource.addResourceModelListener(JpaXmlResource.java:264)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:579)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:552)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1683)
at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:254)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1668)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1860)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1852)
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:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1835)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1646)
at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1638)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:684)
at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:670)
at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
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, 3 months
[JBoss JIRA] (JBDS-2366) Improve libs import for EAP 6
by William Siqueira (JIRA)
William Siqueira created JBDS-2366:
--------------------------------------
Summary: Improve libs import for EAP 6
Key: JBDS-2366
URL: https://issues.jboss.org/browse/JBDS-2366
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: libmanagement, servers
Affects Versions: 5.0.0.GA
Environment: JBDS 4.x
EAP 6/AS 7
Reporter: William Siqueira
In previous version of EAP, we could create a LIB and all our JARs files to the application build path, so we didn't have problem with imports. in EAP 6(AS 7), we have the modules new concept.
The problem is that when migrating from older EAP version to EAP 6, we have to create modules to represent our libs and when setting a server to your project, it is not bringing our custom modules which our application is dependent.
What is needed is a way to select which modules will be in the project classpath whn adding a server lib to the project or perhaps automatically import all modules based on the jboss-deployment-structure.xml descriptor.
--
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, 3 months
[JBoss JIRA] (JBIDE-12911) CLONE - Review error handling code in as plugins
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-12911:
-------------------------------------
Summary: CLONE - Review error handling code in as plugins
Key: JBIDE-12911
URL: https://issues.jboss.org/browse/JBIDE-12911
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Please review the error handling code in JBossAS plugin. I replaced a lot of e.printStackTrace() (in JBIDE-8434) by proper logging. I might have missed some, in some cases more handling is needed, some might not be correct.
--
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, 3 months
[JBoss JIRA] (JBIDE-12831) GWT/Errai Archetype Description
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-12831:
-----------------------------------
Summary: GWT/Errai Archetype Description
Key: JBIDE-12831
URL: https://issues.jboss.org/browse/JBIDE-12831
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
Current description under the title has the phrase "Make sure you read the..." and this is not repeated in the Description field - these should be synced up and the suggestion to make sure to read the readme should be BIGGER since there are additional steps prior to deployment.
--
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, 3 months