You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Chad La Joie <la...@itumi.biz> on 2011/04/02 00:37:23 UTC
Understanding Lifecycles, Phases, and Goals.
Can some one confirm that my understanding of lifecycles, phases, and
goals is correct?
Maven has three lifecycles: clean, default (build), and site. These are
defined by Maven core and can not be changed by plugins.
Each lifecycle is made up of a fixed, ordered list, of phases. The
phases in each lifecycle are also defined by Maven core and can not be
changed by plugins.
Goals, defined in various plugins, are attached to specific phases in
order to create the actual "executable" lifecycle.
Each particular project packaging type (e.g., POM, JAR, WAR) comes with
a default set of goals attached to various lifecycle phases.
Note, I'm looking for technical specificity here so if any of the above
statements aren't exactly correct I'd like to know.
Thanks.
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Assembling webapp only, but not make WAR file
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 04/04/2011 12:08 PM, Wayne Fay wrote:
>> The answer is : mvn prepare-packagewar:exploded
>>
>> Thanks Asmann for your instruction :x
> It took 5 emails to figure out that you really just wanted an exploded
> war to deploy to an App Server during testing.
>
> In the future, instead of asking someone to help you implement the
> solution you've imagined, you should just tell the list what problem
> you are trying to solve, and then let someone tell you the right
> solution to implement.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Best advice this month!!!
Should be a requirement for all new users to prefix their first question
with a standard preamble:
Development target: standalone app, webapp under [tomcat, jboss,
websphere, ....], applet,plug-in....
Language:
Maven Version:
Development IDE: Eclipse, Netbeans,
CI server: Hudson,...., none
Maven Repo: Nexus, Artifactory, none (My advice if, none, get one
and come back if you still have a problem)
Project team size: x people
Number of deliverable artifacts: x
Overall goal: (trying to set up a release strategy, etc., etc.,)
Specific task and problem: Want to get Maven to automatically decide
when to make a new release version. Maven never seems to be able to
figure out when my code is working to spec.
Probably not a bad thing for the second and subsequent post as well.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Assembling webapp only, but not make WAR file
Posted by Wayne Fay <wa...@gmail.com>.
> The answer is : mvn prepare-packagewar:exploded
>
> Thanks Asmann for your instruction :x
It took 5 emails to figure out that you really just wanted an exploded
war to deploy to an App Server during testing.
In the future, instead of asking someone to help you implement the
solution you've imagined, you should just tell the list what problem
you are trying to solve, and then let someone tell you the right
solution to implement.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Assembling webapp only, but not make WAR file
Posted by "Asmann, Roland" <Ro...@adesso.at>.
Be carefull though, if you change anything in one of the other modules,
you *must* run a mvn install to make them available in your WAR!
Roland
On 04.04.2011 11:39, Nguyen Tien Luong wrote:
> Yeah, it is :x
>
> The answer is : mvn prepare-packagewar:exploded
>
>
> Thanks Asmann for your instruction :x
>
> Luong
>
>
> ________________________________
> From: "Asmann, Roland" <Ro...@adesso.at>
> To: "users@maven.apache.org" <us...@maven.apache.org>
> Sent: Mon, 4 April, 2011 11:26:39
> Subject: Re: Assembling webapp only, but not make WAR file
>
> I believe you should try the war:exploded, this should do what you want...
>
>
> On 04.04.2011 11:13, Nguyen Tien Luong wrote:
> > In fact when I have all files I need in target, I will copy directly to
> > Application Server for testing.
> >
> > Sometime I modified only some JSP files, and if for testing I have to
> > generate a
> > new WAR file, it's painful T_T
> >
> > So there is no solution for my problem then ?
> >
> > Luong
> >
> >
> >
> > ________________________________
> > From: "Asmann, Roland" <Ro...@adesso.at>
> > To: "users@maven.apache.org" <us...@maven.apache.org>
> > Sent: Mon, 4 April, 2011 11:06:07
> > Subject: Re: Assembling webapp only, but not make WAR file
> >
> > Multi-module might be a problem. Because that way the other modules will
> > not get installed either! If you do have them in your repository, Maven
> > *should* copy them into the target-dir though, but they will be older
> > versions.
> >
> > A question: why don't you want the WAR to be packaged?
> >
> >
> > On 04.04.2011 10:54, Nguyen Tien Luong wrote:
> > > Thanks for your reply :x
> > >
> > > Is prepare-package that you want to mention ?
> > >
> > > I have multi-module project, and that the webapp depends on for example
> > > project-a that has its .java files and also depends on another artifact
> > > (jar)
> > >
> > > What I want is after execute an maven'lifecycle, I have in target of
> > > webapp (or
> > > somewhere else) the dependency of project-a, .class files of projects-a
> > > and also
> > > files of webapp
> > >
> > > When I do mvn prepare-package for the webapp, I did not copy the
> files of
> > > project-a in the webapp target's folder.
> > >
> > > I did somethings wrong or it is the way maven doing?
> > >
> > > Luong
> > >
> > >
> > >
> > > ________________________________
> > > From: "Asmann, Roland" <Ro...@adesso.at>
> > > To: "users@maven.apache.org" <us...@maven.apache.org>
> > > Sent: Mon, 4 April, 2011 10:32:35
> > > Subject: Re: Assembling webapp only, but not make WAR file
> > >
> > > Check the life-cycle phases and choose one that is just *before*
> > 'package'.
> > >
> > >
> > > On 04.04.2011 10:26, Nguyen Tien Luong wrote:
> > > > Here is the backtrace of MVN INSTALL
> > > >
> > > >
> > > >
> > > > [INFO] [war:war]
> > > > [INFO] Packaging webapp
> > > > [INFO] Assembling webapp[webapp] in [C:\Documents and
> > > > Settings\webapp\target\webapp]
> > > > [INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
> > > > version=1.2, type=jar}] has changed (was Dependency
> > > {groupId=javax.servlet,
> > > > artifactId=jstl, version=1.2, type=jar}).
> > > > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > > > artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has
> > > changed
> > > > (was Dependency {groupId=com.jcp.ui.framework,
> > > > artifactId=ui-modules-api-jcp-mock, ve
> > > > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > > > artifactId=jcp-logger, version=0.3, type=jar}] has changed (was
> > > Dependency
> > > > {groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3,
> > > > type=jar}).
> > > > [INFO] Processing war project
> > > > [INFO] Copying webapp resources[C:\Documents and
> > > > Settings\webapp\target\webapp]
> > > > [INFO] Webapp assembled in[45999 msecs]
> > > > [INFO] Building war: C:\Documents and
> > > > Settings\webapp\target\webapp\target\baseline-webapp.war
> > > > [INFO] [install:install]
> > > > [INFO] Installing C:\Documents and
> > > > Settings\webapp\target\webapp\target\webapp.war to
> > > > D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
> > > >
> > > >
> > > >
> > > >
> > > > For some reason, I want just that maven do the Assembling (copy
> .class
> > > > files,
> > > > jar files .... to TARGET ) but not making the WAR file.
> > > >
> > > > Is that possbile ?
> > > >
> > > > Thanks
> > > >
> > > > Luong
> > > >
> > > >
> > > >
> > >
> > > --
> > > Roland Asmann
> > > Senior Software Engineer
> > >
> > > adesso Austria GmbH
> > > Floridotower 26. Stock T +43 1 2198790-27
> > > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> > > A-1210 Wien M +43 664 88657566
> > > E roland.asmann@adesso.at
> > > W www.adesso.at
> > >
> > > -------------------------------------------------------------
> > > >>> business. people. technology. <<<
> > > -------------------------------------------------------------
> > >
> > >
> > >
> >
> > --
> > Roland Asmann
> > Senior Software Engineer
> >
> > adesso Austria GmbH
> > Floridotower 26. Stock T +43 1 2198790-27
> > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> > A-1210 Wien M +43 664 88657566
> > E roland.asmann@adesso.at
> > W www.adesso.at
> >
> > -------------------------------------------------------------
> > >>> business. people. technology. <<<
> > -------------------------------------------------------------
> >
> >
> >
>
> --
> Roland Asmann
> Senior Software Engineer
>
> adesso Austria GmbH
> Floridotower 26. Stock T +43 1 2198790-27
> Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> A-1210 Wien M +43 664 88657566
> E roland.asmann@adesso.at
> W www.adesso.at
>
> -------------------------------------------------------------
> >>> business. people. technology. <<<
> -------------------------------------------------------------
>
>
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
Re: Assembling webapp only, but not make WAR file
Posted by Nguyen Tien Luong <ti...@yahoo.com>.
Yeah, it is :x
The answer is : mvn prepare-packagewar:exploded
Thanks Asmann for your instruction :x
Luong
________________________________
From: "Asmann, Roland" <Ro...@adesso.at>
To: "users@maven.apache.org" <us...@maven.apache.org>
Sent: Mon, 4 April, 2011 11:26:39
Subject: Re: Assembling webapp only, but not make WAR file
I believe you should try the war:exploded, this should do what you want...
On 04.04.2011 11:13, Nguyen Tien Luong wrote:
> In fact when I have all files I need in target, I will copy directly to
> Application Server for testing.
>
> Sometime I modified only some JSP files, and if for testing I have to
> generate a
> new WAR file, it's painful T_T
>
> So there is no solution for my problem then ?
>
> Luong
>
>
>
> ________________________________
> From: "Asmann, Roland" <Ro...@adesso.at>
> To: "users@maven.apache.org" <us...@maven.apache.org>
> Sent: Mon, 4 April, 2011 11:06:07
> Subject: Re: Assembling webapp only, but not make WAR file
>
> Multi-module might be a problem. Because that way the other modules will
> not get installed either! If you do have them in your repository, Maven
> *should* copy them into the target-dir though, but they will be older
> versions.
>
> A question: why don't you want the WAR to be packaged?
>
>
> On 04.04.2011 10:54, Nguyen Tien Luong wrote:
> > Thanks for your reply :x
> >
> > Is prepare-package that you want to mention ?
> >
> > I have multi-module project, and that the webapp depends on for example
> > project-a that has its .java files and also depends on another artifact
> > (jar)
> >
> > What I want is after execute an maven'lifecycle, I have in target of
> > webapp (or
> > somewhere else) the dependency of project-a, .class files of projects-a
> > and also
> > files of webapp
> >
> > When I do mvn prepare-package for the webapp, I did not copy the files of
> > project-a in the webapp target's folder.
> >
> > I did somethings wrong or it is the way maven doing?
> >
> > Luong
> >
> >
> >
> > ________________________________
> > From: "Asmann, Roland" <Ro...@adesso.at>
> > To: "users@maven.apache.org" <us...@maven.apache.org>
> > Sent: Mon, 4 April, 2011 10:32:35
> > Subject: Re: Assembling webapp only, but not make WAR file
> >
> > Check the life-cycle phases and choose one that is just *before*
> 'package'.
> >
> >
> > On 04.04.2011 10:26, Nguyen Tien Luong wrote:
> > > Here is the backtrace of MVN INSTALL
> > >
> > >
> > >
> > > [INFO] [war:war]
> > > [INFO] Packaging webapp
> > > [INFO] Assembling webapp[webapp] in [C:\Documents and
> > > Settings\webapp\target\webapp]
> > > [INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
> > > version=1.2, type=jar}] has changed (was Dependency
> > {groupId=javax.servlet,
> > > artifactId=jstl, version=1.2, type=jar}).
> > > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > > artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has
> > changed
> > > (was Dependency {groupId=com.jcp.ui.framework,
> > > artifactId=ui-modules-api-jcp-mock, ve
> > > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > > artifactId=jcp-logger, version=0.3, type=jar}] has changed (was
> > Dependency
> > > {groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3,
> > > type=jar}).
> > > [INFO] Processing war project
> > > [INFO] Copying webapp resources[C:\Documents and
> > > Settings\webapp\target\webapp]
> > > [INFO] Webapp assembled in[45999 msecs]
> > > [INFO] Building war: C:\Documents and
> > > Settings\webapp\target\webapp\target\baseline-webapp.war
> > > [INFO] [install:install]
> > > [INFO] Installing C:\Documents and
> > > Settings\webapp\target\webapp\target\webapp.war to
> > > D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
> > >
> > >
> > >
> > >
> > > For some reason, I want just that maven do the Assembling (copy .class
> > > files,
> > > jar files .... to TARGET ) but not making the WAR file.
> > >
> > > Is that possbile ?
> > >
> > > Thanks
> > >
> > > Luong
> > >
> > >
> > >
> >
> > --
> > Roland Asmann
> > Senior Software Engineer
> >
> > adesso Austria GmbH
> > Floridotower 26. Stock T +43 1 2198790-27
> > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> > A-1210 Wien M +43 664 88657566
> > E roland.asmann@adesso.at
> > W www.adesso.at
> >
> > -------------------------------------------------------------
> > >>> business. people. technology. <<<
> > -------------------------------------------------------------
> >
> >
> >
>
> --
> Roland Asmann
> Senior Software Engineer
>
> adesso Austria GmbH
> Floridotower 26. Stock T +43 1 2198790-27
> Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> A-1210 Wien M +43 664 88657566
> E roland.asmann@adesso.at
> W www.adesso.at
>
> -------------------------------------------------------------
> >>> business. people. technology. <<<
> -------------------------------------------------------------
>
>
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
Re: Assembling webapp only, but not make WAR file
Posted by "Asmann, Roland" <Ro...@adesso.at>.
I believe you should try the war:exploded, this should do what you want...
On 04.04.2011 11:13, Nguyen Tien Luong wrote:
> In fact when I have all files I need in target, I will copy directly to
> Application Server for testing.
>
> Sometime I modified only some JSP files, and if for testing I have to
> generate a
> new WAR file, it's painful T_T
>
> So there is no solution for my problem then ?
>
> Luong
>
>
>
> ________________________________
> From: "Asmann, Roland" <Ro...@adesso.at>
> To: "users@maven.apache.org" <us...@maven.apache.org>
> Sent: Mon, 4 April, 2011 11:06:07
> Subject: Re: Assembling webapp only, but not make WAR file
>
> Multi-module might be a problem. Because that way the other modules will
> not get installed either! If you do have them in your repository, Maven
> *should* copy them into the target-dir though, but they will be older
> versions.
>
> A question: why don't you want the WAR to be packaged?
>
>
> On 04.04.2011 10:54, Nguyen Tien Luong wrote:
> > Thanks for your reply :x
> >
> > Is prepare-package that you want to mention ?
> >
> > I have multi-module project, and that the webapp depends on for example
> > project-a that has its .java files and also depends on another artifact
> > (jar)
> >
> > What I want is after execute an maven'lifecycle, I have in target of
> > webapp (or
> > somewhere else) the dependency of project-a, .class files of projects-a
> > and also
> > files of webapp
> >
> > When I do mvn prepare-package for the webapp, I did not copy the files of
> > project-a in the webapp target's folder.
> >
> > I did somethings wrong or it is the way maven doing?
> >
> > Luong
> >
> >
> >
> > ________________________________
> > From: "Asmann, Roland" <Ro...@adesso.at>
> > To: "users@maven.apache.org" <us...@maven.apache.org>
> > Sent: Mon, 4 April, 2011 10:32:35
> > Subject: Re: Assembling webapp only, but not make WAR file
> >
> > Check the life-cycle phases and choose one that is just *before*
> 'package'.
> >
> >
> > On 04.04.2011 10:26, Nguyen Tien Luong wrote:
> > > Here is the backtrace of MVN INSTALL
> > >
> > >
> > >
> > > [INFO] [war:war]
> > > [INFO] Packaging webapp
> > > [INFO] Assembling webapp[webapp] in [C:\Documents and
> > > Settings\webapp\target\webapp]
> > > [INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
> > > version=1.2, type=jar}] has changed (was Dependency
> > {groupId=javax.servlet,
> > > artifactId=jstl, version=1.2, type=jar}).
> > > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > > artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has
> > changed
> > > (was Dependency {groupId=com.jcp.ui.framework,
> > > artifactId=ui-modules-api-jcp-mock, ve
> > > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > > artifactId=jcp-logger, version=0.3, type=jar}] has changed (was
> > Dependency
> > > {groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3,
> > > type=jar}).
> > > [INFO] Processing war project
> > > [INFO] Copying webapp resources[C:\Documents and
> > > Settings\webapp\target\webapp]
> > > [INFO] Webapp assembled in[45999 msecs]
> > > [INFO] Building war: C:\Documents and
> > > Settings\webapp\target\webapp\target\baseline-webapp.war
> > > [INFO] [install:install]
> > > [INFO] Installing C:\Documents and
> > > Settings\webapp\target\webapp\target\webapp.war to
> > > D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
> > >
> > >
> > >
> > >
> > > For some reason, I want just that maven do the Assembling (copy .class
> > > files,
> > > jar files .... to TARGET ) but not making the WAR file.
> > >
> > > Is that possbile ?
> > >
> > > Thanks
> > >
> > > Luong
> > >
> > >
> > >
> >
> > --
> > Roland Asmann
> > Senior Software Engineer
> >
> > adesso Austria GmbH
> > Floridotower 26. Stock T +43 1 2198790-27
> > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> > A-1210 Wien M +43 664 88657566
> > E roland.asmann@adesso.at
> > W www.adesso.at
> >
> > -------------------------------------------------------------
> > >>> business. people. technology. <<<
> > -------------------------------------------------------------
> >
> >
> >
>
> --
> Roland Asmann
> Senior Software Engineer
>
> adesso Austria GmbH
> Floridotower 26. Stock T +43 1 2198790-27
> Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> A-1210 Wien M +43 664 88657566
> E roland.asmann@adesso.at
> W www.adesso.at
>
> -------------------------------------------------------------
> >>> business. people. technology. <<<
> -------------------------------------------------------------
>
>
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
Re: Assembling webapp only, but not make WAR file
Posted by Nguyen Tien Luong <ti...@yahoo.com>.
In fact when I have all files I need in target, I will copy directly to
Application Server for testing.
Sometime I modified only some JSP files, and if for testing I have to generate a
new WAR file, it's painful T_T
So there is no solution for my problem then ?
Luong
________________________________
From: "Asmann, Roland" <Ro...@adesso.at>
To: "users@maven.apache.org" <us...@maven.apache.org>
Sent: Mon, 4 April, 2011 11:06:07
Subject: Re: Assembling webapp only, but not make WAR file
Multi-module might be a problem. Because that way the other modules will
not get installed either! If you do have them in your repository, Maven
*should* copy them into the target-dir though, but they will be older
versions.
A question: why don't you want the WAR to be packaged?
On 04.04.2011 10:54, Nguyen Tien Luong wrote:
> Thanks for your reply :x
>
> Is prepare-package that you want to mention ?
>
> I have multi-module project, and that the webapp depends on for example
> project-a that has its .java files and also depends on another artifact
> (jar)
>
> What I want is after execute an maven'lifecycle, I have in target of
> webapp (or
> somewhere else) the dependency of project-a, .class files of projects-a
> and also
> files of webapp
>
> When I do mvn prepare-package for the webapp, I did not copy the files of
> project-a in the webapp target's folder.
>
> I did somethings wrong or it is the way maven doing?
>
> Luong
>
>
>
> ________________________________
> From: "Asmann, Roland" <Ro...@adesso.at>
> To: "users@maven.apache.org" <us...@maven.apache.org>
> Sent: Mon, 4 April, 2011 10:32:35
> Subject: Re: Assembling webapp only, but not make WAR file
>
> Check the life-cycle phases and choose one that is just *before* 'package'.
>
>
> On 04.04.2011 10:26, Nguyen Tien Luong wrote:
> > Here is the backtrace of MVN INSTALL
> >
> >
> >
> > [INFO] [war:war]
> > [INFO] Packaging webapp
> > [INFO] Assembling webapp[webapp] in [C:\Documents and
> > Settings\webapp\target\webapp]
> > [INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
> > version=1.2, type=jar}] has changed (was Dependency
> {groupId=javax.servlet,
> > artifactId=jstl, version=1.2, type=jar}).
> > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has
> changed
> > (was Dependency {groupId=com.jcp.ui.framework,
> > artifactId=ui-modules-api-jcp-mock, ve
> > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > artifactId=jcp-logger, version=0.3, type=jar}] has changed (was
> Dependency
> > {groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3,
> > type=jar}).
> > [INFO] Processing war project
> > [INFO] Copying webapp resources[C:\Documents and
> > Settings\webapp\target\webapp]
> > [INFO] Webapp assembled in[45999 msecs]
> > [INFO] Building war: C:\Documents and
> > Settings\webapp\target\webapp\target\baseline-webapp.war
> > [INFO] [install:install]
> > [INFO] Installing C:\Documents and
> > Settings\webapp\target\webapp\target\webapp.war to
> > D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
> >
> >
> >
> >
> > For some reason, I want just that maven do the Assembling (copy .class
> > files,
> > jar files .... to TARGET ) but not making the WAR file.
> >
> > Is that possbile ?
> >
> > Thanks
> >
> > Luong
> >
> >
> >
>
> --
> Roland Asmann
> Senior Software Engineer
>
> adesso Austria GmbH
> Floridotower 26. Stock T +43 1 2198790-27
> Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> A-1210 Wien M +43 664 88657566
> E roland.asmann@adesso.at
> W www.adesso.at
>
> -------------------------------------------------------------
> >>> business. people. technology. <<<
> -------------------------------------------------------------
>
>
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
Re: Assembling webapp only, but not make WAR file
Posted by "Asmann, Roland" <Ro...@adesso.at>.
Multi-module might be a problem. Because that way the other modules will
not get installed either! If you do have them in your repository, Maven
*should* copy them into the target-dir though, but they will be older
versions.
A question: why don't you want the WAR to be packaged?
On 04.04.2011 10:54, Nguyen Tien Luong wrote:
> Thanks for your reply :x
>
> Is prepare-package that you want to mention ?
>
> I have multi-module project, and that the webapp depends on for example
> project-a that has its .java files and also depends on another artifact
> (jar)
>
> What I want is after execute an maven'lifecycle, I have in target of
> webapp (or
> somewhere else) the dependency of project-a, .class files of projects-a
> and also
> files of webapp
>
> When I do mvn prepare-package for the webapp, I did not copy the files of
> project-a in the webapp target's folder.
>
> I did somethings wrong or it is the way maven doing?
>
> Luong
>
>
>
> ________________________________
> From: "Asmann, Roland" <Ro...@adesso.at>
> To: "users@maven.apache.org" <us...@maven.apache.org>
> Sent: Mon, 4 April, 2011 10:32:35
> Subject: Re: Assembling webapp only, but not make WAR file
>
> Check the life-cycle phases and choose one that is just *before* 'package'.
>
>
> On 04.04.2011 10:26, Nguyen Tien Luong wrote:
> > Here is the backtrace of MVN INSTALL
> >
> >
> >
> > [INFO] [war:war]
> > [INFO] Packaging webapp
> > [INFO] Assembling webapp[webapp] in [C:\Documents and
> > Settings\webapp\target\webapp]
> > [INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
> > version=1.2, type=jar}] has changed (was Dependency
> {groupId=javax.servlet,
> > artifactId=jstl, version=1.2, type=jar}).
> > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has
> changed
> > (was Dependency {groupId=com.jcp.ui.framework,
> > artifactId=ui-modules-api-jcp-mock, ve
> > [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> > artifactId=jcp-logger, version=0.3, type=jar}] has changed (was
> Dependency
> > {groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3,
> > type=jar}).
> > [INFO] Processing war project
> > [INFO] Copying webapp resources[C:\Documents and
> > Settings\webapp\target\webapp]
> > [INFO] Webapp assembled in[45999 msecs]
> > [INFO] Building war: C:\Documents and
> > Settings\webapp\target\webapp\target\baseline-webapp.war
> > [INFO] [install:install]
> > [INFO] Installing C:\Documents and
> > Settings\webapp\target\webapp\target\webapp.war to
> > D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
> >
> >
> >
> >
> > For some reason, I want just that maven do the Assembling (copy .class
> > files,
> > jar files .... to TARGET ) but not making the WAR file.
> >
> > Is that possbile ?
> >
> > Thanks
> >
> > Luong
> >
> >
> >
>
> --
> Roland Asmann
> Senior Software Engineer
>
> adesso Austria GmbH
> Floridotower 26. Stock T +43 1 2198790-27
> Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> A-1210 Wien M +43 664 88657566
> E roland.asmann@adesso.at
> W www.adesso.at
>
> -------------------------------------------------------------
> >>> business. people. technology. <<<
> -------------------------------------------------------------
>
>
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
Re: Assembling webapp only, but not make WAR file
Posted by Nguyen Tien Luong <ti...@yahoo.com>.
Thanks for your reply :x
Is prepare-package that you want to mention ?
I have multi-module project, and that the webapp depends on for example
project-a that has its .java files and also depends on another artifact (jar)
What I want is after execute an maven'lifecycle, I have in target of webapp (or
somewhere else) the dependency of project-a, .class files of projects-a and also
files of webapp
When I do mvn prepare-package for the webapp, I did not copy the files of
project-a in the webapp target's folder.
I did somethings wrong or it is the way maven doing?
Luong
________________________________
From: "Asmann, Roland" <Ro...@adesso.at>
To: "users@maven.apache.org" <us...@maven.apache.org>
Sent: Mon, 4 April, 2011 10:32:35
Subject: Re: Assembling webapp only, but not make WAR file
Check the life-cycle phases and choose one that is just *before* 'package'.
On 04.04.2011 10:26, Nguyen Tien Luong wrote:
> Here is the backtrace of MVN INSTALL
>
>
>
> [INFO] [war:war]
> [INFO] Packaging webapp
> [INFO] Assembling webapp[webapp] in [C:\Documents and
> Settings\webapp\target\webapp]
> [INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
> version=1.2, type=jar}] has changed (was Dependency {groupId=javax.servlet,
> artifactId=jstl, version=1.2, type=jar}).
> [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has changed
> (was Dependency {groupId=com.jcp.ui.framework,
> artifactId=ui-modules-api-jcp-mock, ve
> [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> artifactId=jcp-logger, version=0.3, type=jar}] has changed (was Dependency
> {groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3,
> type=jar}).
> [INFO] Processing war project
> [INFO] Copying webapp resources[C:\Documents and
> Settings\webapp\target\webapp]
> [INFO] Webapp assembled in[45999 msecs]
> [INFO] Building war: C:\Documents and
> Settings\webapp\target\webapp\target\baseline-webapp.war
> [INFO] [install:install]
> [INFO] Installing C:\Documents and
> Settings\webapp\target\webapp\target\webapp.war to
> D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
>
>
>
>
> For some reason, I want just that maven do the Assembling (copy .class
> files,
> jar files .... to TARGET ) but not making the WAR file.
>
> Is that possbile ?
>
> Thanks
>
> Luong
>
>
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
Re: Assembling webapp only, but not make WAR file
Posted by "Asmann, Roland" <Ro...@adesso.at>.
Check the life-cycle phases and choose one that is just *before* 'package'.
On 04.04.2011 10:26, Nguyen Tien Luong wrote:
> Here is the backtrace of MVN INSTALL
>
>
>
> [INFO] [war:war]
> [INFO] Packaging webapp
> [INFO] Assembling webapp[webapp] in [C:\Documents and
> Settings\webapp\target\webapp]
> [INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
> version=1.2, type=jar}] has changed (was Dependency {groupId=javax.servlet,
> artifactId=jstl, version=1.2, type=jar}).
> [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has changed
> (was Dependency {groupId=com.jcp.ui.framework,
> artifactId=ui-modules-api-jcp-mock, ve
> [INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
> artifactId=jcp-logger, version=0.3, type=jar}] has changed (was Dependency
> {groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3,
> type=jar}).
> [INFO] Processing war project
> [INFO] Copying webapp resources[C:\Documents and
> Settings\webapp\target\webapp]
> [INFO] Webapp assembled in[45999 msecs]
> [INFO] Building war: C:\Documents and
> Settings\webapp\target\webapp\target\baseline-webapp.war
> [INFO] [install:install]
> [INFO] Installing C:\Documents and
> Settings\webapp\target\webapp\target\webapp.war to
> D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
>
>
>
>
> For some reason, I want just that maven do the Assembling (copy .class
> files,
> jar files .... to TARGET ) but not making the WAR file.
>
> Is that possbile ?
>
> Thanks
>
> Luong
>
>
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
Assembling webapp only, but not make WAR file
Posted by Nguyen Tien Luong <ti...@yahoo.com>.
Here is the backtrace of MVN INSTALL
[INFO] [war:war]
[INFO] Packaging webapp
[INFO] Assembling webapp[webapp] in [C:\Documents and
Settings\webapp\target\webapp]
[INFO] Dependency[Dependency {groupId=javax.servlet, artifactId=jstl,
version=1.2, type=jar}] has changed (was Dependency {groupId=javax.servlet,
artifactId=jstl, version=1.2, type=jar}).
[INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
artifactId=ui-modules-api-jcp-mock, version=14.0-194, type=jar}] has changed
(was Dependency {groupId=com.jcp.ui.framework,
artifactId=ui-modules-api-jcp-mock, ve
[INFO] Dependency[Dependency {groupId=com.jcp.ui.framework,
artifactId=jcp-logger, version=0.3, type=jar}] has changed (was Dependency
{groupId=com.jcp.ui.framework, artifactId=jcp-logger, version=0.3, type=jar}).
[INFO] Processing war project
[INFO] Copying webapp resources[C:\Documents and Settings\webapp\target\webapp]
[INFO] Webapp assembled in[45999 msecs]
[INFO] Building war: C:\Documents and
Settings\webapp\target\webapp\target\baseline-webapp.war
[INFO] [install:install]
[INFO] Installing C:\Documents and
Settings\webapp\target\webapp\target\webapp.war to
D:\m2repo\com\webapp\0.0.1\webapp-0.0.1.war
For some reason, I want just that maven do the Assembling (copy .class files,
jar files .... to TARGET ) but not making the WAR file.
Is that possbile ?
Thanks
Luong
Re: Understanding Lifecycles, Phases, and Goals.
Posted by Manfred Moser <ma...@mosabuam.com>.
>> > Each lifecycle is made up of a fixed, ordered list, of phases. The
>> > phases in each lifecycle are also defined by Maven core and can not be
>> > changed by plugins.
>>
>> Not correct. They can be changed. E.g the maven android plugin changes
>> it..
>>
>
> I'm quite sure he is correct. The ordered list of phases for the three
> lifecycles in Maven core cannot be changed.
I am pretty sure they can be changed. I kind of remember references to
that. But I might be wrong. However a plugin can definitely change what
happens in each lifecycle phase.
>>> > Goals, defined in various plugins, are attached to specific phases in
>> > order to create the actual "executable" lifecycle.
>>
>> Yes.. this is defined in the super pom.
>>
>
> No, it's not defined in the super POM. Some bindings are defined by the
> packaging type that you declare in your project. Others you add yourself
> in
> your pom under build/plugins.
Correct. Sorry for the mix up. Some executions are defined on the super
pom but only for performing a release. But the super pom defines a lot of
plugin versions and therefore indirectly packaging types.. and then we are
back to your point ;-)
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Understanding Lifecycles, Phases, and Goals.
Posted by Chad La Joie <la...@itumi.biz>.
On 4/2/11 3:48 AM, Anders Hammar wrote:
>>> Each lifecycle is made up of a fixed, ordered list, of phases. The
>>> phases in each lifecycle are also defined by Maven core and can not be
>>> changed by plugins.
>>
>> Not correct. They can be changed. E.g the maven android plugin changes it..
>>
>
> I'm quite sure he is correct. The ordered list of phases for the three
> lifecycles in Maven core cannot be changed.
Yes, upon further reading this does appear to be correct. Plugins can
create *new* lifecycles but the docs do not indicate an ability to
change Maven's clean, default, and site lifecycles.
>>> Goals, defined in various plugins, are attached to specific phases in
>>> order to create the actual "executable" lifecycle.
>>
>> Yes.. this is defined in the super pom.
>>
>
> No, it's not defined in the super POM. Some bindings are defined by the
> packaging type that you declare in your project. Others you add yourself in
> your pom under build/plugins.
Again, from the further information I've been able to dig up this
appears to be true as well. It looks like the super POM has a plugin
management section, setting the version of various plugins, but does not
in fact attach any plugins to any phase of the standard lifecycles.
Thanks to both Manfred and Anders for the discussion on this.
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Understanding Lifecycles, Phases, and Goals.
Posted by Manfred Moser <ma...@mosabuam.com>.
>> > Each lifecycle is made up of a fixed, ordered list, of phases. The
>> > phases in each lifecycle are also defined by Maven core and can not be
>> > changed by plugins.
>>
>> Not correct. They can be changed. E.g the maven android plugin changes
>> it..
>>
>
> I'm quite sure he is correct. The ordered list of phases for the three
> lifecycles in Maven core cannot be changed.
I am pretty sure they can be changed. I kind of remember references to
that. But I might be wrong. However a plugin can definitely change what
happens in each lifecycle phase.
>>> > Goals, defined in various plugins, are attached to specific phases in
>> > order to create the actual "executable" lifecycle.
>>
>> Yes.. this is defined in the super pom.
>>
>
> No, it's not defined in the super POM. Some bindings are defined by the
> packaging type that you declare in your project. Others you add yourself
> in
> your pom under build/plugins.
Correct. Sorry for the mix up. Some executions are defined on the super
pom but only for performing a release. But the super pom defines a lot of
plugin versions and therefore indirectly packaging types.. and then we are
back to your point ;-)
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Understanding Lifecycles, Phases, and Goals.
Posted by Anders Hammar <an...@hammar.net>.
> > Each lifecycle is made up of a fixed, ordered list, of phases. The
> > phases in each lifecycle are also defined by Maven core and can not be
> > changed by plugins.
>
> Not correct. They can be changed. E.g the maven android plugin changes it..
>
I'm quite sure he is correct. The ordered list of phases for the three
lifecycles in Maven core cannot be changed.
>
> > Goals, defined in various plugins, are attached to specific phases in
> > order to create the actual "executable" lifecycle.
>
> Yes.. this is defined in the super pom.
>
No, it's not defined in the super POM. Some bindings are defined by the
packaging type that you declare in your project. Others you add yourself in
your pom under build/plugins.
/Anders
Re: Understanding Lifecycles, Phases, and Goals.
Posted by Manfred Moser <ma...@mosabuam.com>.
> Can some one confirm that my understanding of lifecycles, phases, and
> goals is correct?
>
> Maven has three lifecycles: clean, default (build), and site. These are
> defined by Maven core and can not be changed by plugins.
the stock maven does..
> Each lifecycle is made up of a fixed, ordered list, of phases. The
> phases in each lifecycle are also defined by Maven core and can not be
> changed by plugins.
Not correct. They can be changed. E.g the maven android plugin changes it..
> Goals, defined in various plugins, are attached to specific phases in
> order to create the actual "executable" lifecycle.
Yes.. this is defined in the super pom.
> Each particular project packaging type (e.g., POM, JAR, WAR) comes with
> a default set of goals attached to various lifecycle phases.
>
> Note, I'm looking for technical specificity here so if any of the above
> statements aren't exactly correct I'd like to know.
Check out the maven books for more info..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Understanding Lifecycles, Phases, and Goals.
Posted by Justin Edelson <ju...@justinedelson.com>.
Only addition I'd suggest is that new lifecycles and packaging types can be defined in plugins.
Justin
On Apr 1, 2011, at 6:37 PM, Chad La Joie <la...@itumi.biz> wrote:
> Can some one confirm that my understanding of lifecycles, phases, and
> goals is correct?
>
> Maven has three lifecycles: clean, default (build), and site. These are
> defined by Maven core and can not be changed by plugins.
>
> Each lifecycle is made up of a fixed, ordered list, of phases. The
> phases in each lifecycle are also defined by Maven core and can not be
> changed by plugins.
>
> Goals, defined in various plugins, are attached to specific phases in
> order to create the actual "executable" lifecycle.
>
> Each particular project packaging type (e.g., POM, JAR, WAR) comes with
> a default set of goals attached to various lifecycle phases.
>
> Note, I'm looking for technical specificity here so if any of the above
> statements aren't exactly correct I'd like to know.
>
> Thanks.
>
> --
> Chad La Joie
> http://itumi.biz
> trusted identities, delivered
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org