[JBoss JIRA] Created: (JBIDE-9823) Properties are displayed twice for Archetype-based project examples
by Fred Bricon (JIRA)
Properties are displayed twice for Archetype-based project examples
-------------------------------------------------------------------
Key: JBIDE-9823
URL: https://issues.jboss.org/browse/JBIDE-9823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, project-examples
Affects Versions: 3.3.0.M3
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Minor
Fix For: 3.3.0.M4
When creating a project from the jboss-javaee6-webapp6 project example (Maven Archetype) the name property is displayed twice in the properties table.
It's set the first time when calling setArchetype(archetype) in ArchetypeExamplesWizardPage.createControl(), then a second time, by when loadArchetypeDescriptor() is called by MavenProjectWizardArchetypeParametersPage.setVisible()
Setting archetypeChanged = false; in ArchetypeExamplesWizardPage.createControl() seemingly fixes the issue, but I'm concerned as loadArchetypeDescriptor() doesn't get called that way. Will try overriding setArchetype() instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9821) Wrong workflow when creating new example projects from Maven Archetypes
by Fred Bricon (JIRA)
Wrong workflow when creating new example projects from Maven Archetypes
-----------------------------------------------------------------------
Key: JBIDE-9821
URL: https://issues.jboss.org/browse/JBIDE-9821
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, project-examples
Affects Versions: 3.3.0.M3
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 3.3.0.M4
If a user creates a Maven Archetype-based project example using the default example name (ex: jboss-javaee6-webapp6), then he can not create a 2nd example under a different name. A dialog box pops up and ask to overwrite (i.e delete) the existing jboss-javaee6-webapp6 project.
If the user answers yes, he loses his project, if he answers no, the project creation halts.
For archetype based projects, where the generated project name can be set by the user, the ImportMavenArchetypeProjectExample should not prevent the user from creating several projects based on the same example. The maven archetype wizard page has a built-in check that will prevent duplicate projects.
IMHO deleting project examples where the project name is variable doesn't make sense (as opposed to regular examples where the name cannot be changed)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9111) Deadlock when creating a new JSF project
by Fred Bricon (JIRA)
Deadlock when creating a new JSF project
----------------------------------------
Key: JBIDE-9111
URL: https://issues.jboss.org/browse/JBIDE-9111
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M1
Environment: Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /usr/java/jdk1.6.0_24/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.38.6-27.fc15.x86_64", arch: "amd64", family: "unix"
Eclipse Indigo Java EE RC3 20110602-0820
JBoss tools plugins installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/
Reporter: Fred Bricon
Assignee: Alexey Kazakov
Priority: Critical
After installing the JBT plugins from the nightly update site on a Eclipse JavaEE Indigo RC3,
I created a new JSF project. The creation hanged indefinitely after clicking on finish. See attached threaddump
Seems like an upstream issue to me.
I couldn't not reproduce it after killing eclipse and restarting.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (JBIDE-9846) XHTML Syntax Validation goes into infinite loop in fillInStackTrace()
by Victor Rubezhny (Created) (JIRA)
XHTML Syntax Validation goes into infinite loop in fillInStackTrace()
---------------------------------------------------------------------
Key: JBIDE-9846
URL: https://issues.jboss.org/browse/JBIDE-9846
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M4
Environment: Verified in Ubuntu 32b and 64b, Mac OSX.
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 3.3.0.M4
Attachments: XHTMLSyntaxValidationInfinite.png
In some cases XHTML Syntax Validator goes into an infinite loop in native fillInStackTrace() method.
STEPS TO REPRODUCE:
===================
EXECUTE: Create an XHTML page in some JSF, Seam or CDI project
EXECUTE: Fill it with the following content:
{code}
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
</
{code}
EXECUTE: Save the page.
ASSERT: See in Progress View that validation tasks finished after save operation.
FAIL: "XHTML Syntax Validation" task is never comes to finish. CPU has high load (near to 100%)
When paused in Degug session, you may see that one of the worker threads is stuck in Throwable.fillInStackTrace() native method.
--
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
14 years, 5 months