Aha, now the warning is gone. The cause was the old snapshot
repository and pluginRepository i was still using.
Thank you !
On Wed, May 9, 2012 at 1:33 PM, Olivier Lamy wrote:
> 2012/5/9 Albert Kam :
>> After the advices, i took a peek on the the eclipse maven run
>> configuration that i use to l
2012/5/9 Albert Kam :
> After the advices, i took a peek on the the eclipse maven run
> configuration that i use to launch tomcat7:run, and i notice the
> checkbox : "Resolve Workspace Artifacts".
> Ticking that checkbox, and re-run the tomcat7:run works great now,
> which can see the other modules
After the advices, i took a peek on the the eclipse maven run
configuration that i use to launch tomcat7:run, and i notice the
checkbox : "Resolve Workspace Artifacts".
Ticking that checkbox, and re-run the tomcat7:run works great now,
which can see the other modules' changes without rebuilding !
You need to write a M2E connector for a Maven MOJO that processes your
projects files. I don't think this is the case for the tomcat7:run goal and
it should work out of of the box in Eclipse. Just need to add a Maven lunch
configuration with the proper goal.
Regards
Jeff
On Tue, May 8, 2012 at 5
I imagine you use tomcat7:run "inside" eclipse.
Do that work outside eclipse ?
Perso I don't have any issues as I use only command line and
furthermore I don't use eclipse :-).
I imagine there is some m2e connector to write
2012/5/8 Albert Kam :
> I notice that i have to repeat these steps so
I notice that i have to repeat these steps so that tomcat7:run will
see the newest stuffs from other maven modules :
- rebuild all of my mvn modules (including my webapp module on which
my tomcat7:run-ed, and other dependencies module)
- clean my eclipse java project, rebuilding everything
- tomcat
