Index: xdocs/navigation-pdf.xml
===================================================================
RCS file: /home/cvspublic/maven/xdocs/navigation-pdf.xml,v
retrieving revision 1.8
diff -u -r1.8 navigation-pdf.xml
--- xdocs/navigation-pdf.xml 23 Jul 2004 04:52:09 -0000 1.8
+++ xdocs/navigation-pdf.xml 23 Jul 2004 17:05:39 -0000
@@ -51,7 +51,7 @@
To do anything with Maven, you will still need to set up a - project.xml file with the information you need to do + project.xml file with the information you need to do the Maven tasks you are using.
@@ -58,7 +58,7 @@
If you were using Ant, you'd probably run
The process for Maven should be simpler unless the project is being really unhelpful.
If there is no
You shouldn't expect to have to define any properties outside what the project has provided and you have
- already defined to get Maven running, as only the standard Mavne plugin properties are being used, and you
+ already defined to get Maven running, as only the standard Maven plugin properties are being used, and you
know how they behave.
If there is a
Part of the misconception comes from claims that building the site or building 30 projects
takes a lot of CPU and memory. Well, this would happen in Ant too if it were attempted!
- This area is also a focus for future development so generating these types of parts of the build
+ This area is also a focus for future development so that generating these parts of the build
are much faster.
ant -projecthelp, and if that didn't help,
- just run "ant" and hope the defualt goal is what you wanted.
+ just run "ant" and hope the default target is what you wanted.
A build.properties.sample file may have been provided so you'd copy that and edit it to see if that
helped. Then you'd fix individual problems as they came up.
- If everything goes wrong and you can't find the right goal or what property it's expecting, you dig into
+ If everything goes wrong and you can't find the right target or what property it's expecting, you dig into
build.xml and look at what it is attempting.
maven.xml file, then you know the build hasn't been customised so you can rely on
a few things working.
@@ -57,11 +57,11 @@
maven.xml file, then the build has been customised. You can still rely on the
above goals doing what they advertise, but they might not be the recommended way of building that
Index: xdocs/ant-guide/qna/hooks.xml
===================================================================
RCS file: /home/cvspublic/maven/xdocs/ant-guide/qna/hooks.xml,v
retrieving revision 1.2
diff -u -r1.2 hooks.xml
--- xdocs/ant-guide/qna/hooks.xml 23 Jul 2004 04:40:07 -0000 1.2
+++ xdocs/ant-guide/qna/hooks.xml 23 Jul 2004 17:02:30 -0000
@@ -41,7 +41,8 @@
So, here is a sample maven.xml file that demonstrates how this would be achieved:
- Go the JIRA administration page
+ Go to the JIRA administration page
for the Maven plugin you have just released (Note that you need to be a JIRA administrator for this project) and
release the version. Also make sure to add a new version for the following
development version. This is required so that issue creators/plugin developers can assign a "fix for" version
@@ -107,7 +107,6 @@
These versions can go beyond 10: eg 1.13.
A third version increment is optional and signifies minor updates. These may also be deployed as
snapshots or users may just be asked to build out of CVS to acquire these fixes.
- eg. 1.0.1 - use less whitespace in output HTML.
Q: Why would I want to given all the pain it will take?
+Q: Why would I want to, given all the pain it will take?
A: Several possible answers... :-) Pick yours:
Because, making a release is honorific and you'll be thanked for it!