Author: brett
Date: Wed May 18 21:41:05 2005
New Revision: 170866
URL: http://svn.apache.org/viewcvs?rev=170866&view=rev
Log:
add some extra documentation, fix formatting
Modified:
maven/components/trunk/maven-site/src/site/apt/proposals/plugin-tool-refactoring.apt
maven/components/trunk/maven-site/src/site/fml/maven1.fml
Modified:
maven/components/trunk/maven-site/src/site/apt/proposals/plugin-tool-refactoring.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/proposals/plugin-tool-refactoring.apt?rev=170866&r1=170865&r2=170866&view=diff
==============================================================================
---
maven/components/trunk/maven-site/src/site/apt/proposals/plugin-tool-refactoring.apt
(original)
+++
maven/components/trunk/maven-site/src/site/apt/proposals/plugin-tool-refactoring.apt
Wed May 18 21:41:05 2005
@@ -6,13 +6,13 @@
09-Feb-2005
---
-*Abstract
+Abstract
Propose changing the structure of maven-plugin-tools to accommodate multiple
plugin languages and their needs during the descriptor, etc. generation
process. Details below.
-*Refactor Details
+Refactor Details
[[1]] Move the existing project (maven-plugin-tools) to
<<<maven-plugin-tools/maven-plugin-tools-java>>>. Adjust dependencies
on
Modified: maven/components/trunk/maven-site/src/site/fml/maven1.fml
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/fml/maven1.fml?rev=170866&r1=170865&r2=170866&view=diff
==============================================================================
--- maven/components/trunk/maven-site/src/site/fml/maven1.fml (original)
+++ maven/components/trunk/maven-site/src/site/fml/maven1.fml Wed May 18
21:41:05 2005
@@ -1,3 +1,4 @@
+<?xml version="1.0"?>
<faqs title="Information for Maven 1.0 Users">
<part id="maven1">
@@ -6,7 +7,7 @@
<answer>
<p>
Maven 2.0 will feel very different to a Maven 1.0 user - and perhaps
a little strange. But it is a lot simpler
- to work with! The key changes from Maven 1.0 are:
+ to work with, and closer to how Maven was always meant to be! The
key changes from Maven 1.0 are:
</p>
<ul>
<li>
@@ -137,6 +138,33 @@
We recommend building your Jelly plugins as thin wrappers around
Java beans that do not use Maven 1.0 API's,
which will allow easy migration to Maven 2.0.
</p>
+ </answer>
+ </faq>
+ <faq id="m1-maven-xml">
+ <question>How do I write custom scripts without a <code>maven.xml</code>
file?</question>
+ <answer>
+ <p>Taken from <a
href="http://mail-archives.apache.org/mod_mbox/maven-users/200504.mbox/[EMAIL
PROTECTED]">this post to the Maven User's List</a>:
+ </p>
+ <blockquote>
+Everything in m2 is a plugin so for doing any sort of custom work like
+that you will need to make a plugin. This 1) greatly reduces the
+complexity within m2 because we only deal with proper plugins. The
+maven.xml file in m1 was a psuedo plugin essentially and greatly
+complicated the internals and 2) it promotes the sharing of your work
+right from the get go. To start with you'll probably write a plugin that
+is only applicable to your specific requirements, or your team's work,
+but you'll see people asking for some functionality and you'll go "hey,
+I have something like that!" and hopefully people who have concrete
+solutions will generalize their solutions so they can be shared with
+others. That's what we're trying to encourage.
+ </blockquote>
+ <blockquote>
+We estimate that there's a lot of work bound up in project's maven.xml
+that is not being shared and we'd like to try and change that. We plan
+to make it dead simple to share plugins and hopefully people can use
+other project's plugins as a start for a plugin that they may need
+themselves.
+ </blockquote>
</answer>
</faq>
</part>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
