TODO - Antonio Alvarado Hernández on Diigo

This plugin for Maven 2 is based on the BND tool from Peter Kriens
works is by treating your project as a big collection of classes
77 more annotations...
- The way you create a bundle with BND is to tell it the content of the bundle's
  JAR file as a subset of the available classes
- wraps BND to make it work specifically with the Maven 2 project structure
- plug-in automatically computes bundle capabilities and requirements
- Assume that we have a simple bundle project that has a pubic API package an
  several implementation packages
- the <Export-Package>
  instruction specifies that the bundle
  
  exports
  the Log Service package
  , even though this package is not contained in
  the bundle project
- <Export-Package> instruction tells the plugin which of the
  available packages to copy into the bundle and export
- <Export-Package> and <Private-Package>
  instructions tell the plugin about the contents of the resulting bundle JAR file
- <Private-Package> instruction indicates which of the available
  packages to copy into the bundle but not export
- If the two sets overlap, as they do in the case, then the export takes
  precedence
- they will assume default values which are described below
- manifest - create an OSGi manifest for the current project
- One specific behavior to highlight is that the plugin generates the
  Import-Package bundle manifest header based on the contents of the
  bundle
- BND recognizes three types of instructions
- Manifest headers - Any instruction that starts with a capital letter
  will appear in the resulting bundle's manifest file
- Variables - Any instruction starting with a lowercase letter is assumed
  to be a variable in the form of a name-value pair, such as version=3.0
- Directives - Any instruction starting with a '-' character is
  considered to be a directive that informs BND to perform some special pro
- ant - create an Ant build script to rebuild the bundle
- These packages are copied into the resulting bundle JAR file
- <Export-Package> instruction is a list of packages for the bundle
  to export
- it is possible to include classes into your bundle that are not associated with
  source files in your project
- can be specified with package patterns using the '*' wildcard
- it is possible to exclude packages using negation by starting the package
  pattern with '!'
- non-negated patterns indicate which of the available packages to include in the
  bundle
- list of package patterns is ordered and earlier patterns are applied before
  later patterns
- package patterns can include both directives and attributes
- BND will also determine package versions by examining the source JAR file or
  from packageinfo files in the package directory
- <Private-Package> instruction is similar in every way to the
  <Export-Package> instruction, except for the fact that these
  packages will not be exported
- <Include-Resource> instruction is a list of arbitrary resources
  that should be copied into the bundle JAR file
- For the <Include-Resource> instruction, actual file paths are
  relative to the pom.xml
- file copy destinations are relative to the root of the resulting bundle JAR file
- a specific resource must be placed into a subdirectory of the bundle jar, then
  use the assignment form, where the first path is the the destination
  path (including file name if the resource is a file) and the second path is the
  resource to copy
- inline form requires a ZIP or JAR file, which will be completely
  expanded in the bundle JAR
- If a resource clause is specified inside of "{ ... }" brackets, then variable
  substitution will be performed on the resource
- By default the bundle plugin converts the project's Maven resource directories
  into a single <Include-Resource> instruction
- you specify your own <Include-Resource> instruction, this will
  replace the generated one
- To include the generated list of Maven resources in your own
  <Include-Resource> instruction just add
  {maven-resources} to the list and it will be expanded automatically
- The <Import-Package> instruction is a list of packages that are
  required by the bundle's contained packages
- efault for this header is "*", resulting in importing all referred packages
- package patterns work in the same way as for <Export-Package>
- To use this plugin, very little information is required by BND
- the plugin tries to set reasonable defaults for various instructions
- <Bundle-SymbolicName> is computed using the shared Maven2OsgiConverter component
- <Export-Package> is now assumed to be the set of packages in your
  local Java sources, excluding the default package '.' and any packages
  containing 'impl' or 'internal'
- <Private-Package> is now assumed to be the set of packages in
  your local Java sources
- <Import-Package> is assumed to be "*", which imports
  everything referred to by the bundle content, but not contained in the bundle
- <Include-Resource> is generated from the project's Maven
  resources
- <Bundle-Version> is assumed to be "${pom.version}" with
  '-' character separator of the qualifier replaced with a '.' character
- <Bundle-Name> is assumed to be "${pom.name}".
- <Bundle-Description> is assumed to be
  "${pom.description}".
- <Bundle-License> is assumed to be "${pom.licenses}".
- <Bundle-Vendor> is assumed to be
  "${pom.organization.name}".
- <Bundle-DocURL> is assumed to be
  "${pom.organization.url}".
- it hard-codes Bundle-ManifestVersion to be '2'
- it generates imports for every export to ensure package substitutability, which
  is very important when working with collaborating services
- downloading and installing the latest version of the Maven2 runtime
- install - adds the current bundle project to the local OBR
- you first need to add the plugin and some appropriate plugin configuration to
  your bundle project's POM
- (2) the plugin and configuration must be specified
- (1) the <packaging> specifier must be "bundle"
- the <Export-Package> instruction specifies that the bundle
  exports the Log Service package
- the plugin will copy the Log Service package into the resulting bundle JAR file
- The resulting bundle JAR file has the following content
- If you want to keep your project packaging type (for example "jar") but would
  like to add OSGi metadata
  you can use the manifest goal to generate a bundle
  manifest
- maven-jar-plugin can then be used to
  add this manifest to the final artifact
- If you want to use packaging types other than "jar" and "bundle" then you also
  need to enable support
  for them in the bundleplugin configuration
- Command-line execution of a goal is performed as follows
- bundleall - build OSGi bundle jars for all transitive
  dependencies
- install-file - adds a local bundle file to the local OBR
- deploy - adds the current bundle project to a remote OBR
- deploy-file - adds a local bundle file to a remote OBR
- clean - cleans the local OBR, removing missing bundles
- remote-clean - cleans a remote OBR, removing missing bundles
- The default goal bundle will be initialized by setting the
  <packaging> entry to "bundle".
- The Maven Bundle Plugin supports embedding of selected project dependencies
  inside the bundle by using the <Embed-Dependency> instruction
- plugin uses the <Embed-Dependency> instruction to transform the
  project dependencies into <Include-Resource> and
  <Bundle-ClassPath> clauses
- are then appended to the current set of instructions and passed onto BND
- If you want the embedded dependencies to be at the start or middle of
  <Include-Resource> or <Bundle-ClassPath> then you
  can use {maven-dependencies}, which will automatically expand to the
  relevant clauses

Antonio Alvarado Hernández's Library tagged TODO → View Popular

Tornado Web Server

TracWikiPrintPlugin - Trac Hacks - Plugins Macros etc. - Trac

The Shalma Project

WhatIsLibpurple – Pidgin – Trac

Instructables - Make, How To, and DIY

PEP 0263 -- Defining Python Source Code Encodings

PEP 20 -- The Zen of Python

PEP 8 -- Style Guide for Python Code

Web Design Practices

WIRE (Web Information Retrieval Environment)::Center for Web Research

Papervision3D

Tellumar Kampiva: CDargs

InBase, Inc

MindfulData, Inc

Yet Another Python Templating Utility (YAPTU) « ActiveState Code

Templating - PythonInfo Wiki

Hibernate DAO using Java 5 Generics | Nilesh D Kapadia

OSGi Alliance | Main / OSGi Alliance

jersey: Home

Apache Felix - Apache Felix Maven Bundle Plugin (BND)

Selected Tags

Related Tags

Sponsored Links

Top Contributors

Groups interested in TODO

Web Performance

Web2.0

GetThingsDone