o stubbing out deploying with FTP

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@306875 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2005-10-06 20:13:14 +00:00
parent d96a8626cb
commit f0f1b99898
2 changed files with 26 additions and 5 deletions

View File

@ -0,0 +1,9 @@
------
Guide to deploying with FTP
------
Jason van Zyl
------
12 October 2005
------
Guide to deploying with FTP

View File

@ -8,6 +8,10 @@
Guide to Working with Manifests
In order to modify the manifest of the resultant JAR produced by the jar plug-in you need to create a configuration
for the jar plug-in. In this first example we'll add some entries to the manifest by specifying what we'd like
in the <<<configuration>>> element of the jar plug-in:
+----+
<project>
@ -33,6 +37,10 @@ Guide to Working with Manifests
+----+
As you see above you can use literal values or you can have values from the POM interpolated into literals
or simply use straight POM expressions. So this is what your resultant <<<MANIFEST.MF>>> will look like inside
the generated JAR:
+----+
Manifest-Version: 1.0
@ -50,6 +58,10 @@ url: http://maven.apache.org
+----+
If you need to do more then simply add some manifest entries there are more options like activating indexing of the
JAR, setting the main-class, packageName ... Here's an example of what the <<<configuration>>> element of the
JAR plug-in might look like:
+----+
<project>
@ -67,7 +79,7 @@ url: http://maven.apache.org
<manifest>
<mainClass>com.mycompany.app.App</mainClass/>
<packageName>com.mycompany.app</packageName>
<!--
<!-- options
<addClasspath>true</addClasspath>
<addExtensions/>
<classpathPrefix/>
@ -85,6 +97,10 @@ url: http://maven.apache.org
...
</project>
+----+
So this is what your resultant <<<MANIFEST.MF>>> will look like inside the generated JAR:
+----+
Manifest-Version: 1.0
@ -104,7 +120,3 @@ url: http://maven.apache.org
+----+
+----+