Google Code Upload Maven Plugin 0.9 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Google Code Upload Maven Plugin 0.9 (Default branch)
# 1  
Old 01-12-2009
Google Code Upload Maven Plugin 0.9 (Default branch)

Google Code Upload Maven Plugin is a Maven plugin that allows Maven users to upload files in their target directory to the Google Code download file repository of their Google Code project. While all download properties can be specified, the gcupload-maven-plugin is also able to infer a sensible set of properties (e.g. summary, labels) from the information given in the Maven project. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Ubuntu

My Google voice plugin problem.

I am encountering problem in Google microphone while voice chat. Voice input is almost no, although I've installed Adobe flash plugin. Please Help! (0 Replies)
Discussion started by: nixhead
0 Replies
Login or Register to Ask a Question
MAVEN(1)							   User Commands							  MAVEN(1)

NAME
Maven - Installs all POMs for the package into /usr/share/maven-repo. SYNOPSIS
mh_installpoms [option]... DESCRIPTION
Reads the file debian/$package.poms and installs each POM file listed in the .poms file. OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: name of the Debian package which will contain those POM files -k --keep-pom-version: keep the original version of the POM but convert all other versions in dependencies and plugins. If there is a parent POM, keeps its version except when the parent is already registered in the Maven repository -e<version>, --set-version=<version>: set the version for the POM, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules -u<rules> --published-rules=<rules>: path to the file containing the extra rules to publish in the property debian.mavenRules in the cleaned POM. Optional, the default location is debian/maven.pub- lishedRules -i<rules> --ignore-rules=<rules>: path to the file containing the rules used to remove certain dependencies from the cleaned POM Optional, the default location is debian/maven.ignoreRules -c<rules> --clean-ignore-rules=<rules>: path to the file containing the rules use to remove certain dependencies from the cleaned POM, in addition to the ignore rules specified previously. This is useful in situations such as when the Maven clean target requires more dependencies or plugins to ignore than the build target. All rules defined in clean-ignore-rules will be added to the existing rules in ignore-rules. Optional, the default location is debian/maven.cleanIgnoreRules -s --no-rules: don't apply any rules for converting versions, do not even convert versions to the default 'debian' version --no-publish-used-rule: don't publish the rule used to transform a POM's own attributes in debian.mavenRules --keep-elements=<elem1,elem2>: keep the elements listed here even if they are normally removed by the clean operation. Such elements are build,reports,reporting,prerequisites,profiles. -m<repo root>--maven-repo=<repo root>: location of the Maven repository, used to force the versions of the Maven plugins used in the current POM file with the versions found in the repository -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results See also: mh_installpom(1), mh_cleanpom(1) Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)