Converting a project to a dynamic web project [message #135727] |
Tue, 30 August 2005 17:48 |
Eclipse User |
|
|
|
Originally posted by: brian.bonner.nospam.paraware.com
I've modified the .project/.classpath and .runtime files of an existing
java project to correspond to a "fresh" new Dynamice webproject. When I
did this, it complained that the JavaSource directory was declared
twice. It was appearing in the lib tab of the project properties->java
build path as well as in the source tab (it shouldn't be in the lib tab).
To resolve this, I deleted the project from the workspace and then
imported it from an existing project. This cleared up the problem.
Has anyone else experienced this--has a bug been logged for this behavior?
Brian
|
|
|
Re: Converting a project to a dynamic web project [message #135819 is a reply to message #135727] |
Wed, 31 August 2005 00:14 |
Eclipse User |
|
|
|
Originally posted by: laurentd75___no.sp_am.yahoo.fr
Hi Brian,
I wouldn't call this behaviour a bug... You were trying to change a
project's nature, and it is normal that WTP should make complaints, cause
your changes were not sufficient for it to recognize your project as a Web
project..
Namely, you would need to edit the .project file (to add builders and
natures appropriate to a Web project), then edited or created the
..wtpmodules file, and also edited the .classpath and added a .runtime file
to associate a server runtime to your Web project.
The easier option in your case would have been to create a new Web project
from scratch, then just copied the Java source files and other files from
your old Java project into the new one...
Brian Bonner wrote:
> I've modified the .project/.classpath and .runtime files of an existing
> java project to correspond to a "fresh" new Dynamice webproject. When I
> did this, it complained that the JavaSource directory was declared
> twice. It was appearing in the lib tab of the project properties->java
> build path as well as in the source tab (it shouldn't be in the lib tab).
>
> To resolve this, I deleted the project from the workspace and then
> imported it from an existing project. This cleared up the problem.
>
> Has anyone else experienced this--has a bug been logged for this behavior?
>
> Brian
|
|
|
Powered by
FUDForum. Page generated in 0.02209 seconds