Problem with republish not getting triggered [message #652886] |
Mon, 07 February 2011 08:18  |
Eclipse User |
|
|
|
I have a most annoying situation in Eclipse / Tomcat.
The situation i am used to is this:
- Change a Java code file
- Save the file
- Right click project and build
If the Tomcat server is not running its status changes from synchronised to republish
If the Tomcat server is running a republish automatically happens within a few seconds.
Just the way i want it.
Unfortunately i had a disk crash and i have had to switch to a different laptop and re-install everything. The new situation i'm working in is this:
- Change a Java code file
- Save the file
- Right click project and build
No effect on the server wether its running or not.
The weird thing is that i can only trigger a republish with this sequence of actions:
- Change a Java code file
- Save the file
- Right click project and build
- Change a Java code file again, even a dummy change like add a space
- Save the file
Then, and only then, is there an effect.
If the server is not running the status changes from synchronised to republish.
If it is running the status also cahnges from synchronised to republish but the actual republish does not occer.
The weird part being that even the rebuild does not trigger the republish, only the second edit and save of the code file.
I have installed:
Version: Helios Service Release 1 Build id: 20100917-0705
Tomcat: Version 6.0.30
When examining the server settings there is a section called "Publishing" , i have that set to "Automatically republish after a build event" with interval of 0 (zero) seconds
Anyone got any idea what's going on and what setting or log files i might examine to get it working back with a simple automatic republish after each build.
|
|
|
Re: Problem with republish not getting triggered [message #652949 is a reply to message #652886] |
Mon, 07 February 2011 12:32   |
Eclipse User |
|
|
|
On 2/7/2011 8:18 AM, Erik wrote:
> I have a most annoying situation in Eclipse / Tomcat.
>
> The situation i am used to is this:
> - Change a Java code file
> - Save the file
> - Right click project and build
>
> If the Tomcat server is not running its status changes from synchronised
> to republish
> If the Tomcat server is running a republish automatically happens within
> a few seconds.
> Just the way i want it.
>
> Unfortunately i had a disk crash and i have had to switch to a different
> laptop and re-install everything. The new situation i'm working in is this:
>
> - Change a Java code file
> - Save the file
> - Right click project and build
>
> No effect on the server wether its running or not.
>
> The weird thing is that i can only trigger a republish with this
> sequence of actions:
>
> - Change a Java code file
> - Save the file
> - Right click project and build
> - Change a Java code file again, even a dummy change like add a space
> - Save the file
>
> Then, and only then, is there an effect.
> If the server is not running the status changes from synchronised to
> republish.
> If it is running the status also cahnges from synchronised to republish
> but the actual republish does not occer.
> The weird part being that even the rebuild does not trigger the
> republish, only the second edit and save of the code file.
>
>
> I have installed:
> Version: Helios Service Release 1 Build id: 20100917-0705
> Tomcat: Version 6.0.30
> When examining the server settings there is a section called
> "Publishing" , i have that set to "Automatically republish after a build
> event" with interval of 0 (zero) seconds
>
> Anyone got any idea what's going on and what setting or log files i
> might examine to get it working back with a simple automatic republish
> after each build.
Just to make sure, is Project -> Build Automatically still enabled? In
case it helps, right-clicking on the server in the Servers view and
selecting "Clean..." will force a "full" publish for that server.
Cheers,
Larry
|
|
|
|
|
|
|
|
|
Re: Problem with republish not getting triggered [message #723791 is a reply to message #723362] |
Fri, 09 September 2011 09:49  |
Eclipse User |
|
|
|
On 9/8/2011 8:18 AM, soysus wrote:
> I guess is too late, but I had the same problem today. I hope this helps
> somebody:
>
> What worked for me was to change the configuration on
> ".settings/org.eclipse.wst.common.component", it seems a file that says
> to wpt how to behave..
>
> I added the following lines in it:
>
>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="src/main/java"/>
> <wb-resource deploy-path="/WEB-INF/classes"
> source-path="src/main/resources"/>
>
>
> What made it look something like this:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="[MyProjectName]">
> <property name="context-root" value="[MyProjectRoot]"/>
> <wb-resource deploy-path="/" source-path="src/main/webapp"/>
> <wb-resource deploy-path="/" source-path="src/main/webapp"/>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="src/main/java"/>
> <wb-resource deploy-path="/WEB-INF/classes"
> source-path="src/main/resources"/>
> <property name="java-output-path" value="/target/classes"/>
> </wb-module>
> </project-modules>
>
The source-paths suggest that this might be a maven project. If so, it
would represent a bug in the maven support that failed to include these
extra entries automatically. If this is reproducible behavior, you may
want to file a bug against the maven plug-ins involved.
I'm not sure why there would be two entries for "src/main/webapp". It
probably wouldn't hurt to remove one.
Cheers,
Larry
|
|
|
Powered by
FUDForum. Page generated in 0.24813 seconds