[JBoss JIRA] (JBIDE-12931) Finish button should be disabled when server not selected
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12931:
-----------------------------------------
Summary: Finish button should be disabled when server not selected
Key: JBIDE-12931
URL: https://issues.jboss.org/browse/JBIDE-12931
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Archives
Affects Versions: 4.0.0.Beta1
Reporter: Jaroslav Jankovič
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
There is no need for Finish button in Archive Publish Dialog to be enabled, when no server is selected. It should be disabled.
--
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-12896) ConcurrentModificationException in CDICoreBuilder when importing existing application
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-12896:
-------------------------------------
Summary: ConcurrentModificationException in CDICoreBuilder when importing existing application
Key: JBIDE-12896
URL: https://issues.jboss.org/browse/JBIDE-12896
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: CDI
Affects Versions: 4.0.0.Beta1
Reporter: Xavier Coulon
Assignee: Alexey Kazakov
Priority: Critical
Fix For: 4.0.0.Beta1
While working on resolving JBIDE-12690, I got the following error:
!MESSAGE Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'jboss-richfaces-webapp'.
!STACK 0
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$KeyIterator.next(HashMap.java:828)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.copy(DefinitionContext.java:98)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.newWorkingCopy(DefinitionContext.java:340)
at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:199)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
This exception occurred when I imported an existing project (jboss-richfaces-webapp) that had been created in another workspace.
--
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-12664) Process timeout in org.jboss.ide.eclipse.archives.test after 2400s
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12664:
----------------------------------
Summary: Process timeout in org.jboss.ide.eclipse.archives.test after 2400s
Key: JBIDE-12664
URL: https://issues.jboss.org/browse/JBIDE-12664
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 4.0.0.Alpha2
Reporter: Nick Boldt
Assignee: Rob Stryker
{code}
[INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [40:03.848s]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.15.0:test (default-test) on project org.jboss.ide.eclipse.archives.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 2400 seconds -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.15.0:test (default-test) on project org.jboss.ide.eclipse.archives.test: Error while executing platform
{code}
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
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-12637) Hibernate Tools generates @SequenceGenerator with not unique name
by Nicolas Bihan (JIRA)
Nicolas Bihan created JBIDE-12637:
-------------------------------------
Summary: Hibernate Tools generates @SequenceGenerator with not unique name
Key: JBIDE-12637
URL: https://issues.jboss.org/browse/JBIDE-12637
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.0.0.Alpha1
Reporter: Nicolas Bihan
Assignee: Dmitry Geraskov
Priority: Blocker
When generating entities with EJB3 annotations with a strategy set to "sequence", Hibernate tools generates POJOs with non unique javax.persistence.SequenceGenerator name "generator". But according to the Java documentation :
bq. String name (Required) A unique generator name that can be referenced by one or more classes to be the generator for primary key values.
See [javadoc|http://docs.oracle.com/javaee/5/api/javax/persistence/SequenceGen...]
Exemple of generated code with 4.0.0 Alpha1:
{code}
@SequenceGenerator(name = "generator", sequenceName = "S_CLIENT")
@Id
@GeneratedValue(strategy = SEQUENCE, generator = "generator")
@Column(name = "CLIENT_ID", unique = true, nullable = false, precision = 22, scale = 0)
public long getClientId() {
return this.clientId;
}
{code}
[Source code|https://github.com/hibernate/hibernate-tools/blob/master/src/java/or...] can be seen here.
So looks like the //TODO comment is right and it should generate a unique name atribute. sequencename+"generator" would be a good name.
It would even be better if we could define this name in reveng.xml or/and in a DelegatingReverseEngineeringStrategy class.
--
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-11975) JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK
by Vimal Kansal (JIRA)
Vimal Kansal created JBIDE-11975:
------------------------------------
Summary: JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK
Key: JBIDE-11975
URL: https://issues.jboss.org/browse/JBIDE-11975
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Vimal Kansal
Hi,
I am using JBDS 5.0 Beta 3. I created a POJO with follwoing attributes :
String username;
String password
String loginCount;
Then I invoked conetxt menu option "Generate Hibernate/JPA annotations", it generates only @Entity annotation. Obviously there is no way for the wizard to find out which attribute should act as PK. However if I include a string "id" anywhere in "username" e.g idusername, usernameid, useridname, it assumes it to be the PK and generates @Id and @GeneratedValue annotation. I wonder if this is by design? I think a better approach would be to let the user choose on the wizard, which field he wants to mark as PK.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12704) Erroneous description in forge console update screen
by George Gastaldi (JIRA)
George Gastaldi created JBIDE-12704:
---------------------------------------
Summary: Erroneous description in forge console update screen
Key: JBIDE-12704
URL: https://issues.jboss.org/browse/JBIDE-12704
Project: Tools (JBoss Tools)
Issue Type: Task
Components: forge, updatesite
Reporter: George Gastaldi
Assignee: Koen Aers
Priority: Trivial
The current description for Forge Console when selecting to update is:
{panel}
Plugins for using Seam Forge from within Eclipse.
{panel}
It should be:
{panel}
Plugins for using JBoss Forge from within Eclipse.
{panel}
--
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