facebook

deployment problems in Tomcat

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #266546 Reply

    Hello,

    Im have two running projects atm, One java project and one webproject. I got some difficulties with deploying my webapp to tomcat 5.5.

    Problem 1 : My classes are compiled (default) in workspace directory “/<projectname>/target/eclipse-classes”
    I have a deployment to a tomcat 5.5 installation Everything works except for the class files. So I change my output folder to “/<projectname>/src/main/webapp/WEB-INF/classes”. This works fine but when i restart MyEclipse the output folder is set back to “/<projectname>/target/eclipse-classes”. This is very anoying. Any ideas?

    Problem 2 : If I alter my buildpath (add source folder) of my Java project, this works fine. But again when I restart MyEclipse this specific source folder is removed again.

    Conclusion: Why is it that these settings arent saved in the.classpath file after restart?

    Thanx for your help,

    Jeroen

    #266582

    Riyad Kalla
    Member

    Problem 1 : My classes are compiled (default) in workspace directory “/<projectname>/target/eclipse-classes”
    I have a deployment to a tomcat 5.5 installation Everything works except for the class files. So I change my output folder to “/<projectname>/src/main/webapp/WEB-INF/classes”. This works fine but when i restart MyEclipse the output folder is set back to “/<projectname>/target/eclipse-classes”. This is very anoying. Any ideas?

    That is strange. Try closing the projects after making the change and then shutting down and restarting using the -clean command line argument. Maybe a stale cache information somewhere causing the reversion.

    Conclusion: Why is it that these settings arent saved in the.classpath file after restart?

    They definately should be. After you make the change and check the .classpath file, do you see the changes, or are they not there? ALso check your log file for errors, maybe you have a permission problem and the changes cannot be written to the file (<workspace dir>\.metadata\.log). Sometimes aggressive SCMs can do this, like ClearCase or VSS

    #266633

    @support-rkalla wrote:

    That is strange. Try closing the projects after making the change and then shutting down and restarting using the -clean command line argument. Maybe a stale cache information somewhere causing the reversion.

    I did the thing you asked me to but…. No result.

    They definately should be. After you make the change and check the .classpath file, do you see the changes, or are they not there? ALso check your log file for errors, maybe you have a permission problem and the changes cannot be written to the file (<workspace dir>\.metadata\.log). Sometimes aggressive SCMs can do this, like ClearCase or VSS

    The .classPath file is altered all the changes are done. When i close project and reopen it, it changes again back to the wrong values.
    My Question: is the directory “/<projectname>/target/eclipse-classes” someting that is standard in MyEclipse? Maybe i can look for some some third party addons who may cause this problem.

    #266642

    Riyad Kalla
    Member

    No that’s not a standard output location set by MyEclipse. For web projects it’s /<project>/WebRoot/WEB-INF. I have no idea what is going on here besides possible roll-back debing done by your source control plugin (if you have one).

    Something to try is to create a brand new project, change it’s output path and restart, see if it sticks.

    #266671

    I’ve found the problem. It was a Maven plugin that is written internally here. It ( does more but also this “feauture”) sets the output path to the target directory. Thank you for your help, and I’ll handle it internally here.

    #266694

    Riyad Kalla
    Member

    Great catch, thanks for digging in and finding that.

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: deployment problems in Tomcat

You must be logged in to post in the forum log in