Author: dennisl Date: Wed Aug 23 13:55:36 2006 New Revision: 434174 URL: http://svn.apache.org/viewvc?rev=434174&view=rev Log: o Set EOL style to native.
Modified: maven/plugins/trunk/maven-antrun-plugin/src/site/apt/examples/classpaths.apt (contents, props changed) maven/plugins/trunk/maven-antrun-plugin/src/site/apt/index.apt (contents, props changed) maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml (contents, props changed) Modified: maven/plugins/trunk/maven-antrun-plugin/src/site/apt/examples/classpaths.apt URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-antrun-plugin/src/site/apt/examples/classpaths.apt?rev=434174&r1=434173&r2=434174&view=diff ============================================================================== --- maven/plugins/trunk/maven-antrun-plugin/src/site/apt/examples/classpaths.apt (original) +++ maven/plugins/trunk/maven-antrun-plugin/src/site/apt/examples/classpaths.apt Wed Aug 23 13:55:36 2006 @@ -1,141 +1,141 @@ - ------ - Using the classpaths - ------ - Carlos Sanchez, Franz Allan Valencia See - ------ - 27 July 2006 - ------ - -~~ Copyright 2006 The Apache Software Foundation. -~~ -~~ Licensed under the Apache License, Version 2.0 (the "License"); -~~ you may not use this file except in compliance with the License. -~~ You may obtain a copy of the License at -~~ -~~ http://www.apache.org/licenses/LICENSE-2.0 -~~ -~~ Unless required by applicable law or agreed to in writing, software -~~ distributed under the License is distributed on an "AS IS" BASIS, -~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -~~ See the License for the specific language governing permissions and -~~ limitations under the License. - -~~ NOTE: For help with the syntax of this file, see: -~~ http://maven.apache.org/guides/mini/guide-apt-format.html - -Referencing the Maven Classpaths - - You can use these classpath references: - - * <<<maven.compile.classpath>>> - - * <<<maven.runtime.classpath>>> - - * <<<maven.test.classpath>>> - - * <<<maven.plugin.classpath>>> - - - For example, to display maven's classpaths using antrun, we can do this - ------- -<project> - <modelVersion>4.0.0</modelVersion> - <artifactId>my-test-app</artifactId> - <groupId>my-test-group</groupId> - <version>1.0-SNAPSHOT</version> - - <build> - <plugins> - - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-antrun-plugin</artifactId> - <executions> - <execution> - <id>compile</id> - <phase>compile</phase> - <configuration> - <tasks> - <property name="compile_classpath" refid="maven.compile.classpath"/> - <property name="runtime_classpath" refid="maven.runtime.classpath"/> - <property name="test_classpath" refid="maven.test.classpath"/> - <property name="plugin_classpath" refid="maven.plugin.classpath"/> - - <echo message="compile classpath: ${compile_classpath}"/> - <echo message="runtime classpath: ${runtime_classpath}"/> - <echo message="test classpath: ${test_classpath}"/> - <echo message="plugin classpath: ${plugin_classpath}"/> - </tasks> - </configuration> - <goals> - <goal>run</goal> - </goals> - </execution> - </executions> - </plugin> - </plugins> - </build> -</project> - ------- - - or alternatively, we can use an external <<<build.xml>>>. - ------- -<project> - <modelVersion>4.0.0</modelVersion> - <artifactId>my-test-app</artifactId> - <groupId>my-test-group</groupId> - <version>1.0-SNAPSHOT</version> - - <build> - <plugins> - - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-antrun-plugin</artifactId> - <executions> - <execution> - <id>compile</id> - <phase>compile</phase> - <configuration> - <tasks> - <property name="compile_classpath" refid="maven.compile.classpath"/> - <property name="runtime_classpath" refid="maven.runtime.classpath"/> - <property name="test_classpath" refid="maven.test.classpath"/> - <property name="plugin_classpath" refid="maven.plugin.classpath"/> - - <ant antfile="${basedir}/build.xml"> - <target name="test"/> - </ant> - </tasks> - </configuration> - <goals> - <goal>run</goal> - </goals> - </execution> - </executions> - </plugin> - </plugins> - </build> -</project> ------- - - The <<<build.xml>>>: - ------- -<?xml version="1.0"?> -<project name="test6"> - - <target name="test"> - - <echo message="compile classpath: ${compile_classpath}"/> - <echo message="runtime classpath: ${runtime_classpath}"/> - <echo message="test classpath: ${test_classpath}"/> - <echo message="plugin classpath: ${plugin_classpath}"/> - - </target> - -</project> ------- + ------ + Using the classpaths + ------ + Carlos Sanchez, Franz Allan Valencia See + ------ + 27 July 2006 + ------ + +~~ Copyright 2006 The Apache Software Foundation. +~~ +~~ Licensed under the Apache License, Version 2.0 (the "License"); +~~ you may not use this file except in compliance with the License. +~~ You may obtain a copy of the License at +~~ +~~ http://www.apache.org/licenses/LICENSE-2.0 +~~ +~~ Unless required by applicable law or agreed to in writing, software +~~ distributed under the License is distributed on an "AS IS" BASIS, +~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +~~ See the License for the specific language governing permissions and +~~ limitations under the License. + +~~ NOTE: For help with the syntax of this file, see: +~~ http://maven.apache.org/guides/mini/guide-apt-format.html + +Referencing the Maven Classpaths + + You can use these classpath references: + + * <<<maven.compile.classpath>>> + + * <<<maven.runtime.classpath>>> + + * <<<maven.test.classpath>>> + + * <<<maven.plugin.classpath>>> + + + For example, to display maven's classpaths using antrun, we can do this + +------ +<project> + <modelVersion>4.0.0</modelVersion> + <artifactId>my-test-app</artifactId> + <groupId>my-test-group</groupId> + <version>1.0-SNAPSHOT</version> + + <build> + <plugins> + + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-antrun-plugin</artifactId> + <executions> + <execution> + <id>compile</id> + <phase>compile</phase> + <configuration> + <tasks> + <property name="compile_classpath" refid="maven.compile.classpath"/> + <property name="runtime_classpath" refid="maven.runtime.classpath"/> + <property name="test_classpath" refid="maven.test.classpath"/> + <property name="plugin_classpath" refid="maven.plugin.classpath"/> + + <echo message="compile classpath: ${compile_classpath}"/> + <echo message="runtime classpath: ${runtime_classpath}"/> + <echo message="test classpath: ${test_classpath}"/> + <echo message="plugin classpath: ${plugin_classpath}"/> + </tasks> + </configuration> + <goals> + <goal>run</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> +</project> + +------ + + or alternatively, we can use an external <<<build.xml>>>. + +------ +<project> + <modelVersion>4.0.0</modelVersion> + <artifactId>my-test-app</artifactId> + <groupId>my-test-group</groupId> + <version>1.0-SNAPSHOT</version> + + <build> + <plugins> + + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-antrun-plugin</artifactId> + <executions> + <execution> + <id>compile</id> + <phase>compile</phase> + <configuration> + <tasks> + <property name="compile_classpath" refid="maven.compile.classpath"/> + <property name="runtime_classpath" refid="maven.runtime.classpath"/> + <property name="test_classpath" refid="maven.test.classpath"/> + <property name="plugin_classpath" refid="maven.plugin.classpath"/> + + <ant antfile="${basedir}/build.xml"> + <target name="test"/> + </ant> + </tasks> + </configuration> + <goals> + <goal>run</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> +</project> +------ + + The <<<build.xml>>>: + +------ +<?xml version="1.0"?> +<project name="test6"> + + <target name="test"> + + <echo message="compile classpath: ${compile_classpath}"/> + <echo message="runtime classpath: ${runtime_classpath}"/> + <echo message="test classpath: ${test_classpath}"/> + <echo message="plugin classpath: ${plugin_classpath}"/> + + </target> + +</project> +------ Propchange: maven/plugins/trunk/maven-antrun-plugin/src/site/apt/examples/classpaths.apt ------------------------------------------------------------------------------ svn:eol-style = native Modified: maven/plugins/trunk/maven-antrun-plugin/src/site/apt/index.apt URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-antrun-plugin/src/site/apt/index.apt?rev=434174&r1=434173&r2=434174&view=diff ============================================================================== --- maven/plugins/trunk/maven-antrun-plugin/src/site/apt/index.apt (original) +++ maven/plugins/trunk/maven-antrun-plugin/src/site/apt/index.apt Wed Aug 23 13:55:36 2006 @@ -1,57 +1,57 @@ - ------ - Introduction - ------ - Kenney Westerhof, Franz Allan Valencia See - ------ - 26 July 2006 - ------ - -~~ Copyright 2006 The Apache Software Foundation. -~~ -~~ Licensed under the Apache License, Version 2.0 (the "License"); -~~ you may not use this file except in compliance with the License. -~~ You may obtain a copy of the License at -~~ -~~ http://www.apache.org/licenses/LICENSE-2.0 -~~ -~~ Unless required by applicable law or agreed to in writing, software -~~ distributed under the License is distributed on an "AS IS" BASIS, -~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -~~ See the License for the specific language governing permissions and -~~ limitations under the License. - -~~ NOTE: For help with the syntax of this file, see: -~~ http://maven.apache.org/guides/mini/guide-apt-format.html - -Maven AntRun Plugin - - This plugin provides the ability to run Ant tasks from within Maven2. You can - even embed your ant scripts in the POM! - - It is <not> the intention of this plugin to provide a means of polluting the - POM, so it's encouraged to move all your Ant tasks to a <<<build.xml>>> file - and just call it from the POM using Ant's - {{{http://ant.apache.org/manual/CoreTasks/ant.html}\<ant/\> task}}. - - One of the main purpose of this plugin is to facilitate the migration from Ant - based projects to Maven 2. Some projects may not currently unable to migrate - because they depend on custom build functionality that Maven2 doesn't provide - by default. - -* Goals Overview - - General Information about the goals. - - * {{{run-mojo.html}antrun:run}} runs ant tasks for maven2. - -* Usage - - Instructions on how to use the Maven AntRun Plugin can be found - {{{usage.html}here}}. - -* Examples - - To provide you with better understanding on some usages of the Maven AntRun - Plugin, you can take a look into the following examples: - - * {{{examples/classpaths.html}Referencing the Maven Classpaths}} + ------ + Introduction + ------ + Kenney Westerhof, Franz Allan Valencia See + ------ + 26 July 2006 + ------ + +~~ Copyright 2006 The Apache Software Foundation. +~~ +~~ Licensed under the Apache License, Version 2.0 (the "License"); +~~ you may not use this file except in compliance with the License. +~~ You may obtain a copy of the License at +~~ +~~ http://www.apache.org/licenses/LICENSE-2.0 +~~ +~~ Unless required by applicable law or agreed to in writing, software +~~ distributed under the License is distributed on an "AS IS" BASIS, +~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +~~ See the License for the specific language governing permissions and +~~ limitations under the License. + +~~ NOTE: For help with the syntax of this file, see: +~~ http://maven.apache.org/guides/mini/guide-apt-format.html + +Maven AntRun Plugin + + This plugin provides the ability to run Ant tasks from within Maven2. You can + even embed your ant scripts in the POM! + + It is <not> the intention of this plugin to provide a means of polluting the + POM, so it's encouraged to move all your Ant tasks to a <<<build.xml>>> file + and just call it from the POM using Ant's + {{{http://ant.apache.org/manual/CoreTasks/ant.html}\<ant/\> task}}. + + One of the main purpose of this plugin is to facilitate the migration from Ant + based projects to Maven 2. Some projects may not currently unable to migrate + because they depend on custom build functionality that Maven2 doesn't provide + by default. + +* Goals Overview + + General Information about the goals. + + * {{{run-mojo.html}antrun:run}} runs ant tasks for maven2. + +* Usage + + Instructions on how to use the Maven AntRun Plugin can be found + {{{usage.html}here}}. + +* Examples + + To provide you with better understanding on some usages of the Maven AntRun + Plugin, you can take a look into the following examples: + + * {{{examples/classpaths.html}Referencing the Maven Classpaths}} Propchange: maven/plugins/trunk/maven-antrun-plugin/src/site/apt/index.apt ------------------------------------------------------------------------------ svn:eol-style = native Modified: maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml?rev=434174&r1=434173&r2=434174&view=diff ============================================================================== --- maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml (original) +++ maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml Wed Aug 23 13:55:36 2006 @@ -1,34 +1,34 @@ -<?xml version="1.0"?> - -<!-- - ~ Copyright 2006 The Apache Software Foundation. - ~ - ~ Licensed under the Apache License, Version 2.0 (the "License"); - ~ you may not use this file except in compliance with the License. - ~ You may obtain a copy of the License at - ~ - ~ http://www.apache.org/licenses/LICENSE-2.0 - ~ - ~ Unless required by applicable law or agreed to in writing, software - ~ distributed under the License is distributed on an "AS IS" BASIS, - ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - ~ See the License for the specific language governing permissions and - ~ limitations under the License. - --> - -<faqs id="FAQ" title="Frequently Asked Questions"> - <part id="General"> - <faq id="Why use antrun and not the ant program itself?"> - <question>Why use antrun and not the ant program itself?</question> - <answer> - <p>Maven has certain benefits over Ant. And for your ant projects to take - advantage of these, you can use maven as your porject management tool and - use its maven-antrun-plugin to build your ant projects. </p> - <p>Furthermore, if you wish to migrate from ant to maven, you can use - this plugin first, then gradually convert your ant expressions into their - corresponding maven expressions.</p> - </answer> - </faq> - </part> -</faqs> - +<?xml version="1.0"?> + +<!-- + ~ Copyright 2006 The Apache Software Foundation. + ~ + ~ Licensed under the Apache License, Version 2.0 (the "License"); + ~ you may not use this file except in compliance with the License. + ~ You may obtain a copy of the License at + ~ + ~ http://www.apache.org/licenses/LICENSE-2.0 + ~ + ~ Unless required by applicable law or agreed to in writing, software + ~ distributed under the License is distributed on an "AS IS" BASIS, + ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + ~ See the License for the specific language governing permissions and + ~ limitations under the License. + --> + +<faqs id="FAQ" title="Frequently Asked Questions"> + <part id="General"> + <faq id="Why use antrun and not the ant program itself?"> + <question>Why use antrun and not the ant program itself?</question> + <answer> + <p>Maven has certain benefits over Ant. And for your ant projects to take + advantage of these, you can use maven as your porject management tool and + use its maven-antrun-plugin to build your ant projects. </p> + <p>Furthermore, if you wish to migrate from ant to maven, you can use + this plugin first, then gradually convert your ant expressions into their + corresponding maven expressions.</p> + </answer> + </faq> + </part> +</faqs> + Propchange: maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml ------------------------------------------------------------------------------ svn:eol-style = native