Details
-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 3.2, 3.3
-
Fix Version/s: None
-
Component/s: ICECORE-Components
-
Labels:None
-
Environment:Tomcat 6 and 7.
-
Workaround Exists:Yes
-
Workaround Description:Rename the icefaces-3.3.0.jar manually to icefaces.jar.
Description
Just spent about six hours trying to figure out why a new developer machine setup of our jsf project doesn't work.
The expectation is to see the jsf page, the results on the other hand is we see the actual xhtml of the jsf page.
After comparing a similar project I remembered that a while ago I had to change the file name on icefaces jar maven name from icefaces-x.x.x.jar to icefaces.jar.
After making this change everything started working again.
We added logging to the logging.properties file to try to find the problem. But there were no log whatsoever to indicate the problem.
It will be great if either you guys fix that dependency on the jar name or modify the maven build so that the final name of the jar file doesn't include the version, so other developers don't spend hours trying to figure this out.
this issue doesn't apply to the ace, compat and push jar files
The expectation is to see the jsf page, the results on the other hand is we see the actual xhtml of the jsf page.
After comparing a similar project I remembered that a while ago I had to change the file name on icefaces jar maven name from icefaces-x.x.x.jar to icefaces.jar.
After making this change everything started working again.
We added logging to the logging.properties file to try to find the problem. But there were no log whatsoever to indicate the problem.
It will be great if either you guys fix that dependency on the jar name or modify the maven build so that the final name of the jar file doesn't include the version, so other developers don't spend hours trying to figure this out.
this issue doesn't apply to the ace, compat and push jar files
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion