tomcat7:run with multi maven modules changes
Locked
tomcat7:run with multi maven modules changes
 
|
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 - tomcat7:run will then see the newest stuffs Note that i dont need to rebuild maven and eclipse project if i dont modify the webapp maven module, tomcat7 can automatically see the newest changes Ideally i would like to skip rebuilding everything in maven and then eclipse to see the newest changes in the other modules outside webapp module. Are there any tips to achieve this ? Thanks ! -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
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 <[hidden email]>: > 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 > - tomcat7:run will then see the newest stuffs > > Note that i dont need to rebuild maven and eclipse project if i dont > modify the webapp maven module, tomcat7 can automatically see the > newest changes > > Ideally i would like to skip rebuilding everything in maven and then > eclipse to see the newest changes in the other modules outside webapp > module. > > Are there any tips to achieve this ? > > Thanks ! > > -- > Do not pursue the past. Do not lose yourself in the future. > The past no longer is. The future has not yet come. > Looking deeply at life as it is in the very here and now, > the practitioner dwells in stability and freedom. > (Thich Nhat Hanh) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
Re: tomcat7:run with multi maven modules changes
|
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:34 PM, Olivier Lamy <[hidden email]> wrote: > 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 <[hidden email]>: > > 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 > > - tomcat7:run will then see the newest stuffs > > > > Note that i dont need to rebuild maven and eclipse project if i dont > > modify the webapp maven module, tomcat7 can automatically see the > > newest changes > > > > Ideally i would like to skip rebuilding everything in maven and then > > eclipse to see the newest changes in the other modules outside webapp > > module. > > > > Are there any tips to achieve this ? > > > > Thanks ! > > > > -- > > Do not pursue the past. Do not lose yourself in the future. > > The past no longer is. The future has not yet come. > > Looking deeply at life as it is in the very here and now, > > the practitioner dwells in stability and freedom. > > (Thich Nhat Hanh) > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [hidden email] > > For additional commands, e-mail: [hidden email] > > > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury |
Re: tomcat7:run with multi maven modules changes
|
|
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 ! Thanks a lot, i feel i can begin my fire dance now ! Anyway, i just want to report something that may not be related with this topic in case that'd be useful. I have these warnings when starting up tomcat7:run : [INFO] Scanning for projects... [WARNING] The metadata C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa che.snapshots.xml is invalid: end tag name </head> must be the same as start tag <link> from line 56 (position: TEXT seen ...arset ="utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) [WARNING] The metadata C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa che.snapshots.xml is invalid: end tag name </head> must be the same as start tag <link> from line 56 (position: TEXT seen ...arset ="utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) [WARNING] The metadata C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat-maven-plugin\2.0-SNAPSHOT\maven-metadata-apac he.snapshots.xml is invalid: end tag name </head> must be the same as start tag <link> from line 56 (position: TEXT seen ...arset= "utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) On Wed, May 9, 2012 at 1:45 AM, Jeff MAURY <[hidden email]> wrote: > 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:34 PM, Olivier Lamy <[hidden email]> wrote: > >> 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 <[hidden email]>: >> > 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 >> > - tomcat7:run will then see the newest stuffs >> > >> > Note that i dont need to rebuild maven and eclipse project if i dont >> > modify the webapp maven module, tomcat7 can automatically see the >> > newest changes >> > >> > Ideally i would like to skip rebuilding everything in maven and then >> > eclipse to see the newest changes in the other modules outside webapp >> > module. >> > >> > Are there any tips to achieve this ? >> > >> > Thanks ! >> > >> > -- >> > Do not pursue the past. Do not lose yourself in the future. >> > The past no longer is. The future has not yet come. >> > Looking deeply at life as it is in the very here and now, >> > the practitioner dwells in stability and freedom. >> > (Thich Nhat Hanh) >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [hidden email] >> > For additional commands, e-mail: [hidden email] >> > >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [hidden email] >> For additional commands, e-mail: [hidden email] >> >> > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
|
2012/5/9 Albert Kam <[hidden email]>:
> 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 ! > > Thanks a lot, i feel i can begin my fire dance now ! > > Anyway, i just want to report something that may not be related with > this topic in case that'd be useful. > I have these warnings when starting up tomcat7:run : > > [INFO] Scanning for projects... > [WARNING] The metadata > C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa > che.snapshots.xml is invalid: end tag name </head> must be the same as > start tag <link> from line 56 (position: TEXT seen ...arset > ="utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) > [WARNING] The metadata > C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa > che.snapshots.xml is invalid: end tag name </head> must be the same as > start tag <link> from line 56 (position: TEXT seen ...arset > ="utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) > [WARNING] The metadata > C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat-maven-plugin\2.0-SNAPSHOT\maven-metadata-apac > he.snapshots.xml is invalid: end tag name </head> must be the same as > start tag <link> from line 56 (position: TEXT seen ...arset= > "utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) > It looks you have bad metadata locally. Maybe a misconfigured repo manager. Delete files from C:\Users\albert\.m2\repository\org\apache\tomcat\maven\ to download all again. > > > > On Wed, May 9, 2012 at 1:45 AM, Jeff MAURY <[hidden email]> wrote: >> 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:34 PM, Olivier Lamy <[hidden email]> wrote: >> >>> 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 <[hidden email]>: >>> > 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 >>> > - tomcat7:run will then see the newest stuffs >>> > >>> > Note that i dont need to rebuild maven and eclipse project if i dont >>> > modify the webapp maven module, tomcat7 can automatically see the >>> > newest changes >>> > >>> > Ideally i would like to skip rebuilding everything in maven and then >>> > eclipse to see the newest changes in the other modules outside webapp >>> > module. >>> > >>> > Are there any tips to achieve this ? >>> > >>> > Thanks ! >>> > >>> > -- >>> > Do not pursue the past. Do not lose yourself in the future. >>> > The past no longer is. The future has not yet come. >>> > Looking deeply at life as it is in the very here and now, >>> > the practitioner dwells in stability and freedom. >>> > (Thich Nhat Hanh) >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: [hidden email] >>> > For additional commands, e-mail: [hidden email] >>> > >>> >>> >>> >>> -- >>> Olivier Lamy >>> Talend: http://coders.talend.com >>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [hidden email] >>> For additional commands, e-mail: [hidden email] >>> >>> >> >> >> -- >> Jeff MAURY >> >> >> "Legacy code" often differs from its suggested alternative by actually >> working and scaling. >> - Bjarne Stroustrup >> >> http://www.jeffmaury.com >> http://riadiscuss.jeffmaury.com >> http://www.twitter.com/jeffmaury > > > > -- > Do not pursue the past. Do not lose yourself in the future. > The past no longer is. The future has not yet come. > Looking deeply at life as it is in the very here and now, > the practitioner dwells in stability and freedom. > (Thich Nhat Hanh) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
Re: tomcat7:run with multi maven modules changes
|
|
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 <[hidden email]> wrote: > 2012/5/9 Albert Kam <[hidden email]>: >> 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 ! >> >> Thanks a lot, i feel i can begin my fire dance now ! >> >> Anyway, i just want to report something that may not be related with >> this topic in case that'd be useful. >> I have these warnings when starting up tomcat7:run : >> >> [INFO] Scanning for projects... >> [WARNING] The metadata >> C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa >> che.snapshots.xml is invalid: end tag name </head> must be the same as >> start tag <link> from line 56 (position: TEXT seen ...arset >> ="utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) >> [WARNING] The metadata >> C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa >> che.snapshots.xml is invalid: end tag name </head> must be the same as >> start tag <link> from line 56 (position: TEXT seen ...arset >> ="utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) >> [WARNING] The metadata >> C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat-maven-plugin\2.0-SNAPSHOT\maven-metadata-apac >> he.snapshots.xml is invalid: end tag name </head> must be the same as >> start tag <link> from line 56 (position: TEXT seen ...arset= >> "utf-8">\n Ext.onReady(Sonatype.init);\n </script>\n</head>... @65:8) >> > > It looks you have bad metadata locally. > Maybe a misconfigured repo manager. Delete files from > C:\Users\albert\.m2\repository\org\apache\tomcat\maven\ to download > all again. -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
«
Return to Tomcat - User
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |