mirror of https://github.com/apache/maven.git
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@293455 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
805a5952eb
commit
fb18d2800d
|
@ -91,15 +91,19 @@ there is a strong defined lifecycle that a software system goes thru from the in
|
|||
henning
|
||||
1) (most important) quick project setup, no complicated build.xml
|
||||
files, just a POM and go
|
||||
|
||||
|
||||
2) all developers in a project use the same jar dependencies due to
|
||||
centralized POM.
|
||||
|
||||
|
||||
3) getting a number of reports and metrics for a project "for free"
|
||||
|
||||
|
||||
4) reduce the size of source distributions, because jars can be pulled
|
||||
from a central location
|
||||
|
||||
|
||||
roberto castro
|
||||
Hi Jason, the main benefits of using Maven in the company I work are: the fact Maven generates every artifact with its version in the artifact's name, it helps identify then even when configuring the artifacts dependencies; the other benefit is the Remote Repository, where all dependencies and artifacts of my sistems are deployed.
|
||||
Using the Remote Repository it is not necessary any more to save jar files in CVS, in orther to garantee that, during the compilation of a system, it will use the jar file saved in CVS.
|
||||
I think the generation of the system Web Site is another benefit of using Maven.
|
||||
Regards,
|
||||
|
||||
+-----+
|
||||
|
|
|
@ -294,9 +294,11 @@ m2 package
|
|||
|
||||
+----+
|
||||
|
||||
If you again take a look at the POM for this project you will notice the <<<packaging>>> element is set to <<<jar>>>.
|
||||
This is how Maven knows to produce a JAR file from the above command. You can now take a look in the the
|
||||
<<<${basedir}/target>>> directory and you will see the generated JAR file.
|
||||
If you take a look at the POM for this project you will notice the <<<packaging>>> element is set to <<<jar>>>.
|
||||
This is how Maven knows to produce a JAR file from the above command and we'll talk more about this later.
|
||||
You can now take a look in the the <<<${basedir}/target>>> directory and you will see the generated JAR file.
|
||||
|
||||
|
||||
|
||||
+----+
|
||||
|
||||
|
@ -526,4 +528,27 @@ What expressions are available for use in the mojos?
|
|||
<jdcasey> they're (a) listed in the expression evaluator, (b) available as POM properties, (c) available as system properties, or (d) available reflectively from the api rooted in one of the four or five data objects
|
||||
<jdcasey> yup, I think we need that
|
||||
|
||||
note from andy
|
||||
|
||||
Jason,
|
||||
|
||||
Follow up to our irc chat about suggesting that windows m2 users move their
|
||||
repos to a location without embedded spaces. I think it would be helpful to
|
||||
people if we were to place a notification about this in a prominent place
|
||||
on the M2 site and in the getting started guide. Parting of the marketing
|
||||
chat could be "Windows M2 Users Prepare for surefire and Java compiler
|
||||
forking by moving your M2 repository to a file system location that doesn't
|
||||
contain embedded spaces!"
|
||||
|
||||
The default user.home on windows is c:\documents and settings\<username>\
|
||||
|
||||
The repo location can be changed in the settings.xml file located at
|
||||
${user.home}/.m2/settings.xml
|
||||
|
||||
I've pasted an example of a trivial modified settings.xml file below.
|
||||
|
||||
<settings>
|
||||
<localRepository>F:\m2-repository\repository</localRepository>
|
||||
</settings>
|
||||
|
||||
+-----+
|
||||
|
|
Loading…
Reference in New Issue