The project that I had troubles with began from the wicket-phonebook
codebase about 2 years ago. So my pom had most of the things that
were in the wicket-phonebook pom. The pom at the following url was
very similar to what I had:
http://wicket-stuff.svn.sourceforge.net/viewvc/wicket-stuff/branches/wicket-1.3.x/wicket-phonebook/pom.xml?revision=3819&view=markup
I've removed most of the plugins and all of the reporting plugins. I
also removed the sourceDirectory and testSourceDirectory. I wonder if
that was the culprit. Here is what my build section looks like now:
<build>
<resources>
<resource>
<filtering>false</filtering>
<directory>src/main/resources</directory>
</resource>
<resource>
<filtering>false</filtering>
<directory>src/main/java</directory>
<includes>
<include>**</include>
</includes>
<excludes>
<exclude>**/*.java</exclude>
</excludes>
</resource>
</resources>
<testResources>
<testResource>
<filtering>false</filtering>
<directory>src/test/java</directory>
<includes>
<include>**</include>
</includes>
<excludes>
<exclude>**/*.java</exclude>
</excludes>
</testResource>
</testResources>
<plugins>
<plugin>
<inherited>true</inherited>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.6</source>
<target>1.6</target>
<optimise>true</optimise>
<debug>true</debug>
</configuration>
</plugin>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<downloadSources>true</downloadSources>
</configuration>
</plugin>
</plugins>
</build>
<properties>
<wicket.version>1.3.4</wicket.version>
<jetty.version>6.1.4</jetty.version>
</properties>
It now runs without problem and I can debug, change html or java files
and it works as expected.
Tauren
On Sun, Jan 18, 2009 at 12:05 AM, noon <[email protected]> wrote:
>
> Which plugins you removed?
>
>
> tauren wrote:
>>
>> That seems consistent with the problem I was having. I removed
>> several plugins from the pom and got things working. Like you, for
>> now I'm leaving adding those plugins back in until another day.
>>
>> Thanks,
>> Tauren
>>
>>
>> On Thu, Jan 15, 2009 at 11:59 PM, noon <[email protected]> wrote:
>>>
>>> No, I didn't mean the "default output folder". For some reason, Maven
>>> added
>>> also the "target/classes" folder as a source folder. I noticed also that
>>> this was done only if I had a custom Maven plugin in the project (one of
>>> our
>>> plugins), even if I used the quickstart Maven artifact. If I removed that
>>> plugin from the pom.xml, everything worked ok. As a workaround, I have to
>>> delete the "target/classes" folder from the source list... I'll solve
>>> this
>>> problem of ours later...
>>>
>>> Good if you got your project working... :)
>>>
>>>
>>>
>>> tauren wrote:
>>>>
>>>> Noon,
>>>>
>>>> Do you mean the "Default output folder" in Properties-->Java Build
>>>> Path-->Source tab? If so, what did you change it to? I can't just
>>>> delete it as Eclipse says that it is required.
>>>>
>>>> Anyway, it is of no consequence any more. It seems that I got things
>>>> working. I decided to try to start with a basic wicket quickstart
>>>> from maven archetype, enable Maven dependency management on it, and
>>>> debugged it. The quickstart worked just fine and I could edit html
>>>> files and they would refresh without stopping the server.
>>>>
>>>> So I compared my project's pom with the quickstart one. My project's
>>>> pom was modeled after another project's pom. There was a lot of extra
>>>> stuff that I didn't need, so I removed it. After making my pom very
>>>> close to the quickstart pom, and then debugging, my project too would
>>>> refresh html files. Yay!
>>>>
>>>> I may follow up on this later as I start to add additional plugins and
>>>> settings that I removed back into my pom. But at least I'll now be
>>>> able to test things one at a time and isolate what caused the problem.
>>>>
>>>> So thanks everyone for the help!
>>>>
>>>> Tauren
>>>>
>>>> ----
>>>>
>>>> PS - Just in case anyone is trying to do this in the future, here are
>>>> the steps I took to get the wicket quickstart working within eclipse
>>>> with maven and m2eclipse:
>>>>
>>>> First make sure eclipse, maven, and m2eclipse are installed...
>>>>
>>>> Command line:
>>>> cd workspace
>>>> mvn archetype:create -DarchetypeGroupId=org.apache.wicket
>>>> -DarchetypeArtifactId=wicket-archetype-quickstart
>>>> -DarchetypeVersion=1.4-rc1 -DgroupId=test -DartifactId=mytest
>>>> cd mytest
>>>> mvn eclipse:eclipse
>>>>
>>>> Eclipse:
>>>> File->Import
>>>> Select General->Existing projects into Workspace
>>>> Next
>>>> Select root directory "workspace/mytest"
>>>> Finish
>>>> Right click onto "mytest" project
>>>> Select Maven->Enable Dependency Management
>>>> Right click onto src/test/java/test/Start.java
>>>> Select Debug As -> Java Application
>>>>
>>>> Web browser:
>>>> http://localhost:8080/
>>>>
>>>> In Eclipse, edit HomePage.html, save.
>>>> Refresh browser, changes are there...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jan 15, 2009 at 10:50 PM, noon <[email protected]> wrote:
>>>>>
>>>>> I had to remove the "target/classes" folder from the java source paths
>>>>> which
>>>>> Maven Eclipse plugin adds (project properties ==> java build path).
>>>>> After
>>>>> this, the markup files refreshed as expected.
>>>>>
>>>>>
>>>>> Tauren Mills-2 wrote:
>>>>>>
>>>>>> Thanks Igor, but I already looked there and the only thing listed in
>>>>>> filtered resources is *.launch.
>>>>>>
>>>>>> Any other ideas?
>>>>>>
>>>>>> Tauren
>>>>>>
>>>>>> On Thu, Jan 15, 2009 at 4:05 PM, Igor Vaynberg
>>>>>> <[email protected]>
>>>>>> wrote:
>>>>>>> open the preferences window
>>>>>>> in the search box type "filter"
>>>>>>> this will show you java/compiler/building panel with
>>>>>>> FilteredREsources: textbox, remove *.html
>>>>>>>
>>>>>>> -igor
>>>>>>>
>>>>>>> On Thu, Jan 15, 2009 at 4:03 PM, Tauren Mills <[email protected]>
>>>>>>> wrote:
>>>>>>>> Martijn,
>>>>>>>>
>>>>>>>> Thanks. But any clue how or where I do that? I've been poking
>>>>>>>> around
>>>>>>>> the preferences in eclipse and haven't found it.
>>>>>>>>
>>>>>>>> Tauren
>>>>>>>>
>>>>>>>> On Thu, Jan 15, 2009 at 3:51 PM, Martijn Dashorst
>>>>>>>> <[email protected]> wrote:
>>>>>>>>> iirc you have to turn off eclipse's filtering of html files (which
>>>>>>>>> is
>>>>>>>>> turned off default because of javadoc html which usually doesn't
>>>>>>>>> want
>>>>>>>>> to be packaged inside your war/jar)
>>>>>>>>>
>>>>>>>>> Martijn
>>>>>>>>>
>>>>>>>>> On Fri, Jan 16, 2009 at 12:31 AM, Tauren Mills <[email protected]>
>>>>>>>>> wrote:
>>>>>>>>>> Are there any wicket/eclipse/maven/m2eclipse users out there? I'm
>>>>>>>>>> trying to get my development environment working properly and need
>>>>>>>>>> your help.
>>>>>>>>>>
>>>>>>>>>> Up until now, I've been developing WIcket applications in Eclipse
>>>>>>>>>> and
>>>>>>>>>> have not been using maven. As long as my web.xml is set to
>>>>>>>>>> development rather than deployment mode, changes I made to HTML
>>>>>>>>>> files
>>>>>>>>>> while debugging were immediately applied.
>>>>>>>>>>
>>>>>>>>>> Not anymore... I am now managing my projects with maven, having
>>>>>>>>>> just
>>>>>>>>>> added a pom file to my project. I'm using the m2eclipse plugin in
>>>>>>>>>> Eclipse and enabled dependency management on my project.
>>>>>>>>>> Unfortunately, now my HTML file changes aren't being recognized
>>>>>>>>>> any
>>>>>>>>>> longer even with development mode turned on. I have to stop and
>>>>>>>>>> start
>>>>>>>>>> the app to see the HTML changes.
>>>>>>>>>>
>>>>>>>>>> My project's maven properties show these goals to invoke on
>>>>>>>>>> resource
>>>>>>>>>> changes: process-resources resources:testResources.
>>>>>>>>>>
>>>>>>>>>> My pom includes:
>>>>>>>>>>
>>>>>>>>>> <build>
>>>>>>>>>> <sourceDirectory>src/main/java</sourceDirectory>
>>>>>>>>>> <testSourceDirectory>src/test/java</testSourceDirectory>
>>>>>>>>>> <resources>
>>>>>>>>>> <resource>
>>>>>>>>>> <filtering>false</filtering>
>>>>>>>>>> <directory>src/main/resources</directory>
>>>>>>>>>> <includes>
>>>>>>>>>> <include>**</include>
>>>>>>>>>> </includes>
>>>>>>>>>> </resource>
>>>>>>>>>> <resource>
>>>>>>>>>> <filtering>false</filtering>
>>>>>>>>>> <directory>src/main/java</directory>
>>>>>>>>>> <includes>
>>>>>>>>>> <include>**</include>
>>>>>>>>>> </includes>
>>>>>>>>>> <excludes>
>>>>>>>>>> <exclude>**/*.java</exclude>
>>>>>>>>>> </excludes>
>>>>>>>>>> </resource>
>>>>>>>>>> </resources>
>>>>>>>>>> ...
>>>>>>>>>> </build>
>>>>>>>>>>
>>>>>>>>>> So, I'm wondering, does eclipse not think that a resource has been
>>>>>>>>>> changed because the HTML files are within src/main/java instead of
>>>>>>>>>> src/main/resources? If I change my CSS files, which are in
>>>>>>>>>> /src/main/webapp, the changes are reflected with a browser
>>>>>>>>>> refresh.
>>>>>>>>>> But if I change an HTML file, it is not.
>>>>>>>>>>
>>>>>>>>>> How do I configure this to work right? Everything else seems to
>>>>>>>>>> be
>>>>>>>>>> working right, just not HTML refreshing.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Tauren
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Become a Wicket expert, learn from the best:
>>>>>>>>> http://wicketinaction.com
>>>>>>>>> Apache Wicket 1.3.5 is released
>>>>>>>>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>> For additional commands, e-mail: [email protected]
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Wicket-Eclipse-Maven-m2eclipse---HTML-files-not-refreshing-tp21489401p21493513.html
>>>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Wicket-Eclipse-Maven-m2eclipse---HTML-files-not-refreshing-tp21489401p21494207.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Wicket-Eclipse-Maven-m2eclipse---HTML-files-not-refreshing-tp21489401p21525164.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
