-
1. Re: Can't set "scope = project" in visual page editor options
maxandersen Feb 12, 2010 9:35 AM (in response to dipteros)Hi Robert,
Sorry, but I'm not following what you mean.
Could you open a jira with screenshots/more detailed steps ?
What does it mean it works only for the page (what page ?) and not for the whole project (the preview is only showing one file with it includes so not sure what you mean by "whole project") ?
/max
-
2. Re: Can't set "scope = project" in visual page editor options
mareshkau Feb 12, 2010 2:55 PM (in response to dipteros)1 of 1 people found this helpfulRobert talk about Page Design Options Dialog in Visual Page Editor.
I have tried set scope to Project on absolute path and it works for all pages in project.
-
3. Re: Can't set "scope = project" in visual page editor options
dipteros Feb 14, 2010 3:24 PM (in response to mareshkau)Yes, Maxim that is my problem. Thank you for answering my question.
Do you have the newest milestone of JBoss Tools 3.1.0.CR1 and eclipse Galieleo 3.5.0.
Because this problem occured after the update to JBoss Tools 3.1.0.CR1.
-
4. Re: Can't set "scope = project" in visual page editor options
dgolovin Feb 23, 2010 2:04 PM (in response to dipteros) -
5. Re: Can't set "scope = project" in visual page editor options
maxandersen Feb 24, 2010 5:17 AM (in response to dgolovin)Yes, just have to wait a bit longer to get hudson to build it1 of 1 people found this helpful -
6. Re: Can't set "scope = project" in visual page editor options
dipteros Mar 1, 2010 5:58 AM (in response to dgolovin)Got the new 3.1.0.CR2.
And this message pops up.
I configured my project using Add JSF Capabilities
http://community.jboss.org/wiki/JBosstoolsVisualEditorFAQ.
And now it works .
I don't kwow why i had to do it again, but i am sorry for stealing your time.
thanks to all of you
Robert Sander
-
7. Re: Can't set "scope = project" in visual page editor options
maxandersen Mar 1, 2010 6:08 AM (in response to dipteros)did you create the project with a previous/older version of JBoss Tools ? (i.e. 3.0.x?) then it would not have added the nature and builder that allows us to pick up classpath changes and that is why the dialog shows up.