maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: effective practice for web application development using maven
Date Sun, 17 Mar 2013 10:35:27 GMT
AFAIK, currently only jszip-maven-plugin responds to changes in the
dependencies in your pom files.

All the others require ^C, up arrow, enter

On Saturday, 16 March 2013, maven apache wrote:

> Thanks all you guys for the ideas.
>
> And it seems that the tomcat-maven-plugin is rather simple. And I prefer to
> it.
>
> However I can not found any docs about how to make it auto-scan the change
> of the dependency project. Do I miss anything?
>
> 2013/3/12 Stephen Connolly <stephen.alan.connolly@gmail.com>
>
> > You can work around that by creating a profile called e.g. run
> >
> > in the root pom you just do
> >
> > <profiles>
> > <profile>
> > <id>run</id>
> > <build>
> >   <defaultGoals>test-compile</defaultGoals>
> >   <properties>
> >     <skipTests>true</skipTests>
> >   </properties>
> > </build>
> > </profile>
> > </profiles>
> >
> > and then in the webapp pom you do
> >
> > <profiles>
> > <profile>
> > <id>run</id>
> > <build>
> > <plugins>
> > <groupId>org.eclipse.jetty</groupId>
> > <artifactId>jetty-maven-plugin</artifactId>
> > <executions>
> > <execution>
> > <id>run</id>
> > <phase>test-compile</phase>
> > <goals>
> > <goal>run</goal>
> > </goals>
> > </execution>
> > </executions>
> > </plugins>
> > </build>
> > </profile>
> > </profiles>
> >
> > And then
> >
> > $ mvn -Prun
> >
> > and bob's your uncle...
> >
> > OK not as handy as my -DrunModule=
> >
> > but it does work (though I ususally go as far as verify when doing those
> > tricks in the cases where I cannot use jszip-maven-plugin because I
> haven't
> > ported all the jetty features)
> >
> >
> > On 12 March 2013 10:39, Thomas Broyer <t.broyer@gmail.com> wrote:
> >
> > > On Tue, Mar 12, 2013 at 11:07 AM, Stephen Connolly <
> > > stephen.alan.connolly@gmail.com> wrote:
> > >
> > > > I don't think that is an issue any more with org.eclipse.jetty's
> maven
> > > > plugin
> > > >
> > >
> > > Running "mvn org.eclipse.jetty:jetty-maven-plugin:9.0.0.v20130308:run"
> at
> > > the root of a multi-module still launches Jetty on the root project
> (the
> > > one with packaging=pom), and there's no way to ignore modules depending
> > on
> > > their packaging (like tomcat-maven-plugin's ignorePackaging or
> > > jszip-maven-plugin's runPackages, only considering packaging=war
> modules
> > by
> > > default) or targeting a specific module (like jszip-maven-plugin's
> > > runModule, which is a *great* idea BTW).
> > >
> > >
> > > >
> > > >
> > > > On 12 March 2013 09:29, Thomas Broyer <t.broyer@gmail.com> wrote:
> > > >
> > > > > On Tue, Mar 12, 2013 at 8:24 AM, maven apache <
> > apachemaven0@gmail.com
> > > > > >wrote:
> > > > >
> > > > > > Hi everyone:
> > > > > >
> > > > > > I am using maven3 as my J2EE application build tool.
> > > > > >
> > > > > > Now I meet some problem during my development --- I found it
is
> so
> > > > > > inflexible to do the test or debug in the multiple modules.
> > > > > >
> > > > > > For example, I have a parent maven project whose pom.xml is
like
> > > this:
> > > > > >
> > > > > >     <modules>
> > > > > >         <module>app-common</module>
> > > > > >         <module>app-webapp</module>
> > > > > >     </modules>
> > > > > >
> > > > > > And the app-common/pom.xml:
> > > > > >
> > > > > > <package>jar</package>
> > > > > >
> > > > > >
> > > > > > the app-webapp/pom.xml:
> > > > > >
> > > > > >             <package>war</package>
> > > > > >             <dependency>
> > > > > >                 <groupId>> http://xn--nna.ma.xn--bwa-xxb.je/>
<
> > > http://xn--nna.ma.xn--bwa-xxb.je/>
> > >
> >
>


-- 
Sent from my phone

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message