[bnd] 03/04: Update bnd.pod for new release. Mention new or different commands.
Markus Koschany
apo-guest at moszumanska.debian.org
Mon May 18 19:33:37 UTC 2015
This is an automated email from the git hooks/post-receive script.
apo-guest pushed a commit to branch master
in repository bnd.
commit d0a7ba064aa2e0f18b3d353d85f4347e2a28991f
Author: Markus Koschany <apo at gambaru.de>
Date: Mon May 18 19:42:11 2015 +0200
Update bnd.pod for new release. Mention new or different commands.
Remove Authors paragraph since all copyright holders are already credited in
debian/copyright.
---
debian/bnd.pod | 116 +++++++++++++++++++++++++++----------------------------
debian/changelog | 3 ++
2 files changed, 61 insertions(+), 58 deletions(-)
diff --git a/debian/bnd.pod b/debian/bnd.pod
index 933010d..518b0e3 100644
--- a/debian/bnd.pod
+++ b/debian/bnd.pod
@@ -17,17 +17,17 @@ The bnd tool helps you create and diagnose OSGi bundles. The key functions are:
* Show the manifest and JAR contents of a bundle
* Wrap a JAR so that it becomes a bundle
* Create a Bundle from a specification and a class path
- * Verify the validity of the manifest entries
+ * Verify the validity of the manifest entries
=head1 GENERAL OPTIONS
=over
-=item -failok
+=item --failok
-Same as the property -failok. The current run will create a JAR file even if there were errors.
+Same as the property --failok. The current run will create a JAR file even if there were errors.
-=item -exceptions
+=item --exceptions
Will print the exception when the software has ran into a bad exception and bails out. Normally only a message is printed. For debugging or diagnostic reasons, the exception stack trace can be very helpful.
@@ -37,65 +37,65 @@ Will print the exception when the software has ran into a bad exception and bail
=over
-=item print ( -verify | -manifest | -list | - all ) * E<lt>fileE<gt>.jar +
-
-The print function will take a list of JAR file and print one or more aspect of the JAF riles. The following aspects can be added.
-
- * -verify - Verify the JAR for consistency with the specification
- The print will exit with an error if the verify fails.
- * -manifest - Show the manifest
- * -list - List the entries in the JAR file
- * -all - Do all (this is the default.
-
-C<bnd print -verify *.jar>
-
-=item buildx ( -classpath LIST | -eclipse <lt>fileE<gt> | -noeclipse | -output E<lt>fileE<gt> ) * E<lt>fileE<gt>.bnd +
-
-The build function will assemble a bundle from the bnd specification. The default name of the output bundle is the name of the bnd file with a .jar extension.
-
- * -classpath - A list of JAR files and/or directories that should
- be placed on the class path before the calculation starts.
- * -eclipse - Parse the file as an Eclipse .classpath file, use
- the information to create an Eclipse's project class path.
- If this option is used, the default .classpath file is not read
- * -noeclipse - Do not parse the .classpath file of an Eclipse
- project.
- * -output - Override the default output name of the bundle or the
- directory. If the output is a directory, the name will be
- derived from the bnd file name.
-
-C<bnd build -classpath bin -noeclipse -output test.jar xyz.bnd>
-
-=item wrap ( -classpath (<lt>fileE<gt>(','<lt>fileE<gt>)*)-output <lt>fileE|dir<gt> | -properties <lt>fileE<gt> ) *
--ignoremanifest? <lt>fileE<gt>.jar *
-
-The wrap command takes an existing JAR file and guesses the manifest headers that will make this JAR useful for an OSGi Service Platform. If the output file is not overridden, the name of the input file is used with a .bar extension. The default bnd file for the header calculation is:
-
- Export-Package: *
- Import-Package: <packages inside the target jar>
-
-If the target bundle has a manifest, the headers are merged with the properties.
-
-The defaults can be overridden with a specific properties file.
-
- * -output - Set the output file or directory
- * -classpath - Sets the classpath as a comma separated list
- * -properties - Use a special property file for the manifest
- calculation.
- * -ignoremanifest - Do not include the manifest headers from
- the target bundle
-
-C<bnd wrap -classpath osgi.jar *.jar>
+Available commands:
+
+ baseline - Compare a newer bundle to a baselined bundle and provide
+ versioning advice
+ bnd - The swiss army tool for OSGi
+ build - Build a project. This will create the jars defined in the
+ bnd.bnd and sub-builders.
+ buildx - Build project, is deprecated but here for backward
+ compatibility
+ bump - Bumps the version of a project
+ clean - Clean a project
+ convert - Converter to different formats
+ create - Create jar, used to support backward compatible java jar
+ commands
+ debug - Show a lot of info about the project you're in
+ deliverables - Show all deliverables from this workspace. with their
+ current version and path.
+ diff - Diff jars
+ digest - Digests a number of files
+ do - Execute a file based on its extension. Supported
+ extensions are: bnd (build), bndrun (run), and jar (print)
+ eclipse - Show info about the current directory's eclipse project
+ extract - Extract files from a JAR file, equivalent jar command
+ x[vf] (syntax supported)
+ grep - Grep the manifest of bundles/jar files.
+ info - Show key project variables
+ macro - Show macro value
+ maven - Maven bundle command
+ package - Package a bnd or bndrun file into a single jar that
+ executes with java -jar <>.jar
+ print - Printout the JAR
+ project - Execute a Project action, or if no parms given, show
+ information about the project
+ release - Release this project
+ repo - Manage the repositories
+ run - Run a project in the OSGi launcher
+ runtests - Run OSGi tests and create report
+ schema - Highly specialized function to create an overview of
+ package deltas in ees
+ select - Helps finding information in a set of JARs by filtering on
+ manifest data and printing out selected information.
+ settings - Set bnd/jpm global variables
+ source - Merge a binary jar with its sources. It is possible to
+ specify source path
+ syntax - Access the internal bnd database of keywords and options
+ test - Test a project according to an OSGi test
+ type - List files int a JAR file, equivalent jar command t[vf]
+ (syntax supported)
+ verify - Verify jars
+ version - Show version information about bnd
+ view - View a resource from a JAR file.
+ wrap - Wrap a jar
+ xref - Show a cross references for all classes in a set of jars.
=back
=head1 SEE ALSO
-L<http://www.aqute.biz/Code/Bnd>
-
-=head1 AUTHOR
+L<https://github.com/bndtools/bnd>
-Ludovic Claude <ludovic.claude at laposte.net>
-Damien Raude-Morvan <drazzib at debian.org>
diff --git a/debian/changelog b/debian/changelog
index d9c13ac..14640a7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -40,6 +40,9 @@ bnd (2.1.0-1) experimental; urgency=medium
- Remove biz.aQute.resolve in clean target.
- Fix all obsolete tmp paths. Files are now in generated.
* wrap-and-sort -sa.
+ * Update bnd.pod for new release. Mention new or different commands.
+ Remove Authors paragraph since all copyright holders are already credited
+ in debian/copyright.
-- Markus Koschany <apo at gambaru.de> Sun, 17 May 2015 23:36:37 +0200
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/bnd.git
More information about the pkg-java-commits
mailing list