3:21 p.m.
Alexey Kazakov created JBIDE-12823:
--------------------------------------
Summary: Compilation error in JSF project
Key: JBIDE-12823
URL: https://issues.jboss.org/browse/JBIDE-12823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Beta1
1. Open Eclipse
2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project
wizard
3. FAILURE: User.java has compilation errors since javax.* can't be found.
4. Clean/re-build the project. Compilation errors are gone.
5. Create one more JSF project. Now there are no errors.
6. Close Eclipse. Open it again. Steps 2-5 are reproducible again.
Not sure that's a bug of JSF Tools. Maybe it's an upstream bug.
--
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
5:21 p.m.
[
https://issues.jboss.org/browse/JBIDE-12823?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-12823:
-----------------------------------------------
Sometimes, new project has no runtime. That happens, because we add runtime in a job,
while another job, started by Java script plugin (ConvertJob), configures the new project.
I checked in debug mode the failing sequence of events:
(1) Project is created initially without runtime;
(2) Java script's ConvertJob starts and creates working copy of the new project;
(3) Our RuntimeJob starts and adds runtime to the new project (if ConvertJob is suspended
in debugger, one can make sure in Studio that the new project has the runtime);
(4) ConvertJob commits changes to the new project, and since its working copy has no
runtime, it is removed.
If event (3) happens before (2) or after (4), then the runtime is set to the project.
Compilation error in JSF project
--------------------------------
Key: JBIDE-12823
URL: https://issues.jboss.org/browse/JBIDE-12823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Beta1
1. Open Eclipse
2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project
wizard
3. FAILURE: User.java has compilation errors since javax.* can't be found.
4. Clean/re-build the project. Compilation errors are gone.
5. Create one more JSF project. Now there are no errors.
6. Close Eclipse. Open it again. Steps 2-5 are reproducible again.
Not sure that's a bug of JSF Tools. Maybe it's an upstream bug.
--
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
5:32 p.m.
[
https://issues.jboss.org/browse/JBIDE-12823?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich edited comment on JBIDE-12823 at 10/10/12 6:31 PM:
-------------------------------------------------------------------------
To fix the problem, we should set runtime to data model before project creation rather
than to the project after it is created. To prevent a deadlock, we should run the creation
operation in the same mode as New Dynamic Web project wizard does it (fork=true,
cancelable=false), we did exactly opposite.
was (Author: scabanovich):
To fix the problem we should set runtime to data model rather then to the project
after it is created. To prevent a deadlock, we should run the creation operation in the
same mode as New Dynamic Web project wizard does it (fork=true, cancelable=false), we did
exactly opposite.
Compilation error in JSF project
--------------------------------
Key: JBIDE-12823
URL: https://issues.jboss.org/browse/JBIDE-12823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Beta1
1. Open Eclipse
2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project
wizard
3. FAILURE: User.java has compilation errors since javax.* can't be found.
4. Clean/re-build the project. Compilation errors are gone.
5. Create one more JSF project. Now there are no errors.
6. Close Eclipse. Open it again. Steps 2-5 are reproducible again.
Not sure that's a bug of JSF Tools. Maybe it's an upstream bug.
--
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
5:32 p.m.
[
https://issues.jboss.org/browse/JBIDE-12823?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-12823:
-----------------------------------------------
To fix the problem we should set runtime to data model rather then to the project after it
is created. To prevent a deadlock, we should run the creation operation in the same mode
as New Dynamic Web project wizard does it (fork=true, cancelable=false), we did exactly
opposite.
Compilation error in JSF project
--------------------------------
Key: JBIDE-12823
URL: https://issues.jboss.org/browse/JBIDE-12823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Beta1
1. Open Eclipse
2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project
wizard
3. FAILURE: User.java has compilation errors since javax.* can't be found.
4. Clean/re-build the project. Compilation errors are gone.
5. Create one more JSF project. Now there are no errors.
6. Close Eclipse. Open it again. Steps 2-5 are reproducible again.
Not sure that's a bug of JSF Tools. Maybe it's an upstream bug.
--
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
5:34 p.m.
[
https://issues.jboss.org/browse/JBIDE-12823?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich reassigned JBIDE-12823:
---------------------------------------------
Assignee: Alexey Kazakov (was: Viacheslav Kabanovich)
Alexey, please verify.
Compilation error in JSF project
--------------------------------
Key: JBIDE-12823
URL: https://issues.jboss.org/browse/JBIDE-12823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.0.0.Beta1
1. Open Eclipse
2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project
wizard
3. FAILURE: User.java has compilation errors since javax.* can't be found.
4. Clean/re-build the project. Compilation errors are gone.
5. Create one more JSF project. Now there are no errors.
6. Close Eclipse. Open it again. Steps 2-5 are reproducible again.
Not sure that's a bug of JSF Tools. Maybe it's an upstream bug.
--
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
1:32 p.m.
[
https://issues.jboss.org/browse/JBIDE-12823?page=com.atlassian.jira.plugi...
]
Alexey Kazakov resolved JBIDE-12823.
------------------------------------
Assignee: Viacheslav Kabanovich (was: Alexey Kazakov)
Resolution: Done
fixed
Compilation error in JSF project
--------------------------------
Key: JBIDE-12823
URL: https://issues.jboss.org/browse/JBIDE-12823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Beta1
1. Open Eclipse
2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project
wizard
3. FAILURE: User.java has compilation errors since javax.* can't be found.
4. Clean/re-build the project. Compilation errors are gone.
5. Create one more JSF project. Now there are no errors.
6. Close Eclipse. Open it again. Steps 2-5 are reproducible again.
Not sure that's a bug of JSF Tools. Maybe it's an upstream bug.
--
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
4:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-12823?page=com.atlassian.jira.plugi...
]
Vlado Pakan closed JBIDE-12823.
-------------------------------
Verified with JBT 4.0.0.Beta1-v20121013-1726-B25.
Compilation error in JSF project
--------------------------------
Key: JBIDE-12823
URL: https://issues.jboss.org/browse/JBIDE-12823
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Beta1
1. Open Eclipse
2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project
wizard
3. FAILURE: User.java has compilation errors since javax.* can't be found.
4. Clean/re-build the project. Compilation errors are gone.
5. Create one more JSF project. Now there are no errors.
6. Close Eclipse. Open it again. Steps 2-5 are reproducible again.
Not sure that's a bug of JSF Tools. Maybe it's an upstream bug.
--
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
4373
days inactive
4380
days old
jbosstools-issues@lists.jboss.org
6 comments
3 participants
participants (3)
-
Alexey Kazakov (JIRA) -
Viacheslav Kabanovich (JIRA)
-
Vlado Pakan (JIRA)