Community
Participate
Working Groups
In RC3 the default target server specified in the preferences page (checked) doesnt appears in wizard pages for example "Dynamic Web Project", "Enterprise Application Project", "EJB Project", "Connector Project", etc ... Whats doing wrong ?? Thks !
The default runtime is supposed to be your preferred runtime when creating new projects. This only brings it to the top of the runtimes list when creating a new project, and does not make it appear if it doesn't support the type of project that you are creating. For example, if you have Tomcat v3.2 as your default runtime target, it should appear at the top of the list when creating a J2EE 1.2 Web project, but will not appear at all when creating a J2EE 1.4 project (which Tomcat v3.2 does not support). I tried this on 0.7 and it worked correctly for me. Are you seeing different behaviour? If not, please close the bug. If you are, please describe in more detail.
Recently i test 0.7 with tomcat 5.5 and genornimo 1.0 and both work successful. But when build a dyna web project creating a "new" project in the wizard screen appears an errors : Errors during build. Errors running builder "Component Structural Dependency Resolver" on project foo. Resource /foo/.deployables does not exist. is correct ?? exist any bug reported for this ??? (In reply to comment #1) > The default runtime is supposed to be your preferred runtime when creating new > projects. This only brings it to the top of the runtimes list when creating a > new project, and does not make it appear if it doesn't support the type of > project that you are creating. For example, if you have Tomcat v3.2 as your > default runtime target, it should appear at the top of the list when creating a > J2EE 1.2 Web project, but will not appear at all when creating a J2EE 1.4 > project (which Tomcat v3.2 does not support). > > I tried this on 0.7 and it worked correctly for me. Are you seeing different > behaviour? If not, please close the bug. If you are, please describe in more detail.
I beleive this bug is a dup of one already opened. Transferring to wst.common since the original problem is resolved.
The .deployables should be going away in 1.0 *** This bug has been marked as a duplicate of 97756 ***
This bug was moved to 'closed' state, since it is so old is is assumed its dup, invalid, or worksforme resolution is no longer in qustion and the bugzilla needs no further attention. Feel free to re-open, or open a new bug, if this semi-automatic processing was done in error in this case.
