On 9/25/06, David Leangen <[EMAIL PROTECTED]> wrote: > > Oh, this is a cool plugin! Thanks for pointing this out! > > A few questions... > > If I have some default values, can I declare these in a parent POM, or > some kind of config file? In maven any pom.xml that has <parent> declaration will inherit all the properties / settings / depedencies / etcs to the child project.
> > There are some manifest entries that are not processed by the plugin, so > it seems. Is there a reason for this, or have they just not yet been > implemented. The following supported properties are: * osgi-BundleCategory to declare bundle category. * osgi-nativeCode to declare native code. * osgi-ExportPackage to declare export package. * osgi-ImportPackage to *override* the import entry generation. * osgi-DynamicImportPackage to declare dynamic import package. * osgi-BundleActivator to declare bundle activator. * osgi-UpdateLocation to declare url to update bundle. * osgi-RequiredExecutionEnvironment to declare required execution environment. * osgi-Localization to declare supported bundle localization. * osgi-RequiredBundle to declare required bundle. * osgi-FragmentHost to declare fragment host. * osgi-ManifestVersion to override the manifest version information (default value = 2) * osgi-URL to declare bundle url Default values: * Description is taken from pom project description value. * Name is taken from pom project name value. * Vendor is taken from pom project organisation value. * Version is taken from pom project version value. * Doc url is taken from pom project url. * Contact address is taken from pom project url. * Bundle symbolic name is contructed from pom group id + "." + artifact Id. * Bundle src is taken from pom scm declaration. > > > Thanks! You're welcome. Regards, efy _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
