ferris-journal-gui
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>org.ferris</groupId>
<artifactId>ferris-journal-gui</artifactId>
<version>0.0.3</version>
</dependency>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<!--
| PARENT
-->
<parent>
<artifactId>ferris-standard-project</artifactId>
<groupId>org.ferris</groupId>
<version>0.0.4</version>
</parent>
<!--
| ARTIFACT INFO
-->
<name>Ferris Journal: GUI</name>
<groupId>org.ferris</groupId>
<artifactId>ferris-journal-gui</artifactId>
<version>0.0.3</version>
<!--
| VERSION INFO
-->
<inceptionYear>March 15, 2008</inceptionYear>
<description>
Ferris Journal GUI provides a GUI based journal application which uses
ferris-journal-jws and ferris-journal-ejb.
</description>
<!--
| SCM INFO (REQUIRED FOR RELEASE PLUGIN
-->
<url>http://ferris.sourceforge.net/journal-gui/</url>
<scm>
<connection>scm:cvs:pserver:anonymous@ferris.cvs.sourceforge.net:/cvsroot/ferris:ferris-journal-gui</connection>
<tag>ferris-journal-gui-0_0_3</tag>
<developerConnection>scm:cvs:ext:mjremijan@ferris.cvs.sourceforge.net:/cvsroot/ferris:ferris-journal-gui</developerConnection>
<url>http://ferris.cvs.sourceforge.net/viewvc/ferris/ferris-journal-gui</url>
</scm>
<!--
| BUILD
-->
<build>
<resources>
<!--
| FILTERED
-->
<resource>
<filtering>true</filtering>
<directory>src/main/resources</directory>
<includes>
<include>FerrisStrings.properties</include>
</includes>
</resource>
<!--
| NON-FILTERED
-->
<resource>
<filtering>false</filtering>
<directory>src/main/resources</directory>
<excludes>
<exclude>FerrisStrings.properties</exclude>
</excludes>
</resource>
</resources>
<plugins>
<!--
| Jar Plugin
|
| This plugin provides the capability to build and sign jars.
|
| Binds by default to the lifecycle phase: package.
|
| Configured here to create an additional artifact which contains
| the full Class-Path in the manifest for a stand-alone distribution.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<addMavenDescriptor>false</addMavenDescriptor>
</archive>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<classifier>standalone</classifier>
<archive>
<addMavenDescriptor>false</addMavenDescriptor>
<manifest>
<addClasspath>true</addClasspath>
<classpathPrefix>lib</classpathPrefix>
<mainClass>org.ferris.journal.gui.main.Main</mainClass>
</manifest>
</archive>
</configuration>
</execution>
</executions>
</plugin>
<!--
| Site Plugin
|
| Tell the build process I want to use the site plugin and I
| want to attach it to the default lifecycle prepare-package
| phase. By attaching this to the prepare-package phase, I
| can get the site build before the assembly creates the "bin"
| and "src" distributions of this project.
|
| @see ferris-parent-pom pom.xml pluginManagement
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>site</goal>
</goals>
<phase>prepare-package</phase>
</execution>
</executions>
</plugin>
<!--
| Assembly Plugin
|
| The Assembly Plugin for Maven is primarily intended to allow
| users to aggregate the project output along with its
| dependencies, modules, site documentation, and other files
| into a single distributable archive.
|
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>ferris-bin-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<skipAssembly>true</skipAssembly>
</configuration>
</execution>
<execution>
<id>journal-gui-bin-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptors>
<descriptor>src/main/assemblies/journal-gui-bin-assembly.xml</descriptor>
</descriptors>
</configuration>
</execution>
</executions>
</plugin>
<!--
| WebStart Plugin
|
| The Webstart Maven Plugin generates application bundles that can
| be deployed via Web Start. The plugin can be used to prepare
| standalone Web Start applications or Web Start applications
| bundled in WAR files (with or without Sun's Download Servlet).
| It handles the generation of JNLP files and optional version.xml
| files, using Velocity templates. It also handles the selection
| and preparation of the dependencies, performing signing,
| unsigning and Pack200 compression when required.
|
| Bound here to the lifecycle phase: package
-->
<plugin>
<groupId>org.codehaus.mojo.webstart</groupId>
<artifactId>webstart-maven-plugin</artifactId>
<version>1.0-alpha-2</version>
<executions>
<execution>
<id>jnlp-webstart</id>
<phase>package</phase>
<goals>
<goal>jnlp-inline</goal>
</goals>
<configuration>
<!--
Set to true to exclude all transitive dependencies.
Default is false.
-->
<excludeTransitive>false</excludeTransitive>
<!-- The path where the libraries are stored within the jnlp structure. not required. by default the libraries are within the working directory -->
<libPath>lib</libPath>
<jnlp>
<outputFile>journal.jnlp</outputFile>
<mainClass>org.ferris.journal.gui.main.Main</mainClass>
</jnlp>
<sign>
<!-- access the keystore -->
<keystore>${basedir}/src/main/keystore/MyKeystore</keystore>
<keypass>MyFerrisJournalGui</keypass> <!-- we need to override passwords easily from the command line. ${keypass} -->
<storepass>MyFerrisJournalGui</storepass> <!-- ${storepass} -->
<alias>MyFerrisJournalGui</alias>
<keyalg>RSA</keyalg>
<!-- only required for generating the keystore
<dnameCn>ferris.dnsalias.net</dnameCn>
<dnameOu>Research and Development</dnameOu>
<dnameO>ferris.dnsalias.net</dnameO>
<dnameL>St. Louis</dnameL>
<dnameSt>Missouri</dnameSt>
<dnameC>MO</dnameC>
<validity>1000</validity>
-->
<!-- verify that the signing operation succeeded -->
<verify>true</verify>
<!-- keystore management -->
<keystoreConfig>
<!-- delete the keystore? -->
<delete>false</delete>
<!-- generate the keystore? -->
<gen>false</gen>
</keystoreConfig>
</sign>
<!-- BUILDING PROCESS
<pack200>true</pack200>
<gzip>true</gzip>
<outputJarVersions>true</outputJarVersions>
-->
<verbose>false</verbose>
</configuration>
</execution>
</executions>
</plugin>
<!--
| AntRun Plugin
|
| This plugin provides the ability to run Ant tasks from within
| Maven 2. You can even embed your Ant scripts in the POM!
|
| Bound here to the lifecycle phase: package
|
| Configured here to unzip the zip file created by the JNLP plugin.
| The zip file is unzipped into the "site" directory so it can
| be included with the projects website documentation.
-->
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>unzip-jnlp-file</id>
<phase>package</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<tasks>
<echo message="Unzip JNLP file '${project.artifactId}-${project.version}.zip' to '${project.reporting.outputDirectory}' " />
<mkdir dir="${project.reporting.outputDirectory}" />
<unzip src="${project.build.directory}/${project.artifactId}-${project.version}.zip" dest="${project.reporting.outputDirectory}" />
</tasks>
</configuration>
</execution>
</executions>
</plugin>
<!--
If I need to regenerate the Java Web Service client files,
this is the plugin to do it.
Set maven goal as "clean axistools:wsdl2java"
CONFIGURATION
sourceDirectory - src/main/wsdl
outputDirectory - target/generated-sources/wsdl
packageSpace - com.company.wsdl
serverSide - true/false
verbose - true/false
noImports - true/false
timeout - int
debug - true/false
noWrapped - true/false
skeletonDeploy -
NStoPkg - name=value
fileNStoPkg - file of properties
deployScope - Application, Request, Session
all - true/false
typeMappingVersion - 1.1/1.2
factory - custom class
nsInclude - namespace
nsExclude - namespace
helperGen - true/false
username -
password -
testCases - true/false
runTestCasesAsUnitTests - true/false
allElements - true/false
subPackageByFileName - true/false
multiple url specification
-->
<!--
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>axistools-maven-plugin</artifactId>
<version>1.3</version>
<configuration>
<sourceDirectory>src/main/wsdl</sourceDirectory>
<packageSpace>org.ferris.journal.jws</packageSpace>
<subPackageByFileName>true</subPackageByFileName>
</configuration>
<dependencies>
<dependency>
<groupId>axis</groupId>
<artifactId>axis</artifactId>
<version>1.3</version>
</dependency>
</dependencies>
<executions>
<execution>
<goals>
<goal>wsdl2java</goal>
</goals>
</execution>
</executions>
</plugin>
-->
</plugins>
</build>
<!--
| DEPENDENCIES
-->
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.7</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.13</version>
</dependency>
<dependency>
<groupId>axis</groupId>
<artifactId>axis</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>org.ferris</groupId>
<artifactId>ferris-swing</artifactId>
<version>0.0.3</version>
</dependency>
<dependency>
<groupId>commons-codec</groupId>
<artifactId>commons-codec</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>org.ferris</groupId>
<artifactId>ferris-crypto</artifactId>
<version>0.0.1</version>
</dependency>
<dependency>
<groupId>org.ferris</groupId>
<artifactId>ferris-constraint</artifactId>
<version>0.0.1</version>
</dependency>
<dependency>
<groupId>org.swinglabs</groupId>
<artifactId>swingx</artifactId>
<version>1.6</version>
</dependency>
<dependency>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>2.3</version>
</dependency>
<dependency>
<groupId>org.ferris</groupId>
<artifactId>ferris-util</artifactId>
<version>0.0.2</version>
</dependency>
</dependencies>
</project>