Home » Language IDEs » ServerTools (WTP) » Dynamic Web project is not a Java project?
| Dynamic Web project is not a Java project? [message #174660] |
Mon, 17 July 2006 13:37  |
Eclipse User |
|
|
|
Originally posted by: Alex.Savitsky.tdsecurities.com
Some of our team members have started to use WST for our development, and
we've run into some issues:
1. If I want to use any of the WST features on an existing pre-WST
project, I have to manually hack the .* files (changing the project nature
by hand and such). Furthermore, I have to keep these changes on my local
PC, not being able to store it in the source control, because ...
2. If another team member who doesn't have WST checks out my WST project,
they are left out with a project that has neither the WST nor the Java
nature - i.e., a project that can't even be compiled without some manual
* hacking!
Am I missing something there? Are WST and Java project totally
incompatible? After all, a Web project is still a Java project with maybe
some additional info thrown in (content folder, content root, etc).
Currently, the way it's set up, there's simply no way to gradually adopt
WST in our environment - it's an "all or nothing" proposition. Quite a
pain, if you ask me, as WST by itself is a nice tool...
Alex
|
|
|
| Re: Dynamic Web project is not a Java project? [message #174676 is a reply to message #174660] |
Mon, 17 July 2006 14:12  |
|
Alex wrote:
> Some of our team members have started to use WST for our development,
> and we've run into some issues:
>
> 1. If I want to use any of the WST features on an existing pre-WST
> project, I have to manually hack the .* files (changing the project
> nature by hand and such). Furthermore, I have to keep these changes on
> my local PC, not being able to store it in the source control, because ...
>
> 2. If another team member who doesn't have WST checks out my WST
> project, they are left out with a project that has neither the WST nor
> the Java nature - i.e., a project that can't even be compiled without
> some manual * hacking!
I'm assuming you meant WTP as a whole instead of WST, but it sounds
like you didn't commit the .* files into your source control
repository originally. In particular, the .project and .classpath
files are essential for other team members to be able to check out
those projects and have the Java functionality that should be there.
--
- Nitin
_
Nitin Dahyabhai
Eclipse Web Tools Platform
|
|
|
| Re: Dynamic Web project is not a Java project? [message #174685 is a reply to message #174676] |
Mon, 17 July 2006 15:34 |
| Eclipse User |
|
|
|
Originally posted by: Alex.Savitsky.tdsecurities.com
Nitin Dahyabhai wrote:
> Alex wrote:
>> Some of our team members have started to use WST for our development,
>> and we've run into some issues:
>>
>> 1. If I want to use any of the WST features on an existing pre-WST
>> project, I have to manually hack the .* files (changing the project
>> nature by hand and such). Furthermore, I have to keep these changes on
>> my local PC, not being able to store it in the source control, because ...
>>
>> 2. If another team member who doesn't have WST checks out my WST
>> project, they are left out with a project that has neither the WST nor
>> the Java nature - i.e., a project that can't even be compiled without
>> some manual * hacking!
> I'm assuming you meant WTP as a whole instead of WST, but it sounds
> like you didn't commit the .* files into your source control
> repository originally. In particular, the .project and .classpath
> files are essential for other team members to be able to check out
> those projects and have the Java functionality that should be there.
Yes, I meant the WTP as a whole.
It turned out that some of our team members were using WTP 1.0, which
didn't have the Java nature for web projects. Upgrading to 1.5 kinda fixed
the problem - the WTP project is now being properly recognized as a Java
project, albeit with a bunch of broken library references (I guess that's
as good as it gets, though).
However, I'm still not sure what is the best way to convert existing
projects to WTP. As we're not allowed to change the project names in CVS
we have to manually change the .classpath and .project, and to add entries
in the .settings folder. It would be nice if there'd be a "Convert to
Dynamic Web project" option for plain Java projects - just like one
existing for Sysdeo, Spring IDE, AspectJ, etc.
|
|
|
| Re: Dynamic Web project is not a Java project? [message #176379 is a reply to message #174685] |
Mon, 07 August 2006 17:49 |
| Eclipse User |
|
|
|
Originally posted by: dbaker.wesleyan.nojunk.edu
Alex wrote:
<snip>
> However, I'm still not sure what is the best way to convert existing
> projects to WTP. As we're not allowed to change the project names in CVS
> we have to manually change the .classpath and .project, and to add
> entries in the .settings folder. It would be nice if there'd be a
> "Convert to Dynamic Web project" option for plain Java projects - just
> like one existing for Sysdeo, Spring IDE, AspectJ, etc.
So is there any definitive answer in regard to converting an existing
project to WTP? Please point me in the right direction if there is a
resource for such information! Thanks!
Doug Baker
|
|
|
Goto Forum:
Current Time: Fri Apr 26 16:25:59 GMT 2024
Powered by FUDForum. Page generated in 0.03823 seconds |
] 
Search
Help
Register
Login
Home
