[drewmca]

The synch on demand feature for an exploded tomcat 5 deployment only seems to work for java files. if I edit velocity, JSP, css, or other web files, or even xml config files, the changes don’t seem to deploy. I can understand why config file updates might not synch, though it would be nice if they did. But web files, like html, jsp, css, etc., should just be copied over automatically on edit, since they won’t cause a restart.

As it is, I keep having to redeploy to my exploded application to push the changes out.

[support-michael]

The exploded deployment synchronization logic does not automatically discriminate between Java and other file types. It should synchronize all resources in the same manner. I’m categorizing this report as a bug and relocating it to the Bug Reports & Fixes forum.

Now can you help me isolate this problem?
I need the following information:
1. OS
2. Eclipse version
3. MyEclipse version
4. server you are deploying to
5. location of resource not being synchronized
6. other non-MyEclipse plugins installed
7. does the project contain any linked resources
8. is project inside of workspace directory or external to it
9. are you confirming that non-java resources are not deployed by physically inspecting deployment area or observing via execution of application from running instance of Tomcat5

Michael
MyEclipse Support

[Scott Anderson]

drewmca,

As it is, I keep having to redeploy to my exploded application to push the changes out.

We’ve just had a case where someone was experiencing similar behavior and it was due to a corrupted .project file. Could you email the .project file for the project you’re having trouble with to support@mye…com so we can give it a look?

–Scott
MyEclipse Support

[drewmca]

In response to your questions:
1) WinXP
2) 2.1.0
3) 2.5.1
4) Tomcat 5
5) Under webroot (*.vm, *.vsl, *.jsp, *.xml)
6) An old installation of Lomboz (not used), XML Buddy
7) No
8) outside workspace directory (it has to be)
9) Yes on both

The synchronization seems to work with Java files, though it’s not 100% guaranteed (I’m confirming this with breakpoints since I can’t decipher the class files). This project file was also created from scratch specifically because of other problems I had with it before. I created it from scratch as a MyEclipse project, then readded all of the files except .project and other .xxx eclipse files (like .myeclipse).

Thanks,

Drew

[Scott Anderson]

Drew,

This project file was also created from scratch specifically because of other problems I had with it before. I created it from scratch as a MyEclipse project, then readded all of the files except .project and other .xxx eclipse files (like .myeclipse).

This is really not recommended. I’ve received your .project file and emailed back a replacement. However, I’m now very concerned about other project meta information.

The other thing that can cause this is the Workbench setting:
Window > Preferences > Workbench > Perform build automatically on resource modification. This setting must be ‘checked’ in order for the deployer to function properly since it uses build events to trigger the file updates.

–Scott
MyEclipse Support

[drewmca]

Not sure what you mean by not recommending that. I had been having other problems and it seemed that they were related to the fact that the project wasn’t originally a myeclipse project. So I recreated a new MyEclipse project and pulled everything into it from the old project, except for metadata (the whole point of creating a new project was so that new, hopefully correct, metadata would be created as well). I didn’t know of any other way to fix the issues I had, and once I did this, they were taken care of. For example, Java code updates weren’t getting synched at all before the new project, and afterwards, they were.

As for other points, the “perform build auto…” setting is definitely checked, and I know it from both checking it and from the fact that my Java class updates are automatically compiled. Also, I updated my project file based on what you sent and it looks like files under web-root are still not getting synchronized.

[Scott Anderson]

So I recreated a new MyEclipse project and pulled everything into it from the old project, except for metadata (the whole point of creating a new project was so that new, hopefully correct, metadata would be created as well).

I’m sorry; I misunderstood you. I thought you’d created the .project file ‘by hand’, which is what I don’t recommend. Believe it or not, we’ve had users in there mucking about with the builders. 🙂 You did the right thing creating a new project and moving your source over. My mistake.

Also, I updated my project file based on what you sent and it looks like files under web-root are still not getting synchronized.

This is truly strange. We’re just not able to replicate this problem. Additionally, the builder is completely indescriminate about what it copies. It should just take any update under the web root. It may be because your project is stored outside the workspace. Please check that the MyEclipse project properties (rt-click > Properties > MyEclipse) show the correct web root. I’ll try setting up a struts project outside the workspace with the release candidate for 2.5.2 just to make sure that this still can’t be replicated. I do know that a good bit of deployer work has gone into the new release, so this might have been addressed as a side effect.

–Scott
MyEclipse Support

[drewmca]

I’ve confirmed that the web root is as expected. It’s very strange because it didn’t used to give me problems. Also, I believe that previously when I refreshed the project, it would do a context reload. That doesn’t appear to be happening either. Thought that might help.

Any target date on the 2.5.2 release?

[Scott Anderson]

Any target date on the 2.5.2 release?

The week of 8/18/2003 (this week). Due to the level of enhancements, it make be called 2.6.0, however.

–Scott
MyEclipse Support

[roeland]

I seemed to have the same problem. For each change I made, I had to redeploy the entire web project.
The reason I post, is that this is in MyEclipse 2.6.1

Thanks to this topic, however, I was able to fix it myself. I have a separate Linux machine which worked fine. Comparing the .project files revealed that the following section is missing under the ‘buildspec’ heading:

<buildCommand>
    <name>com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder</name>
    <arguments>
    </arguments>
</buildCommand>

Any idea why the .project gets mangled?

Here are my answers to the earlier questions:
1. OS
Win2K SP4
2. Eclipse version
Version: 2.1.1
Build id: 200306271545
3. MyEclipse version
Version: 2.6.1
Build id: 200308311200
4. server you are deploying to
Tomcat 5
5. location of resource not being synchronized
Any except .java, such as .jsp
6. other non-MyEclipse plugins installed
none
7. does the project contain any linked resources
no
8. is project inside of workspace directory or external to it
It’s inside the workspace
9. are you confirming that non-java resources are not deployed by physically inspecting deployment area or observing via execution of application from running instance of Tomcat5
Yes (Using the browse button in the deploy dialog)

[support-michael]

Good detective work. The missing deploymentBuild spec is interesting. It should have been added at the same time the deploymentNature was added. I’m forwarding this to development for their immediate attention. Have you seen this problem with any other project?

Michael
MyEclipse Support

[Author]

Posts