Good idea, less is good. +1.
Niclas, have you seen the problem where the plugin now during the felix
build creates a bad org.osgi.core-0.8.0-SNAPSHOT.jar bundle, by
assigning the BundleActivator itself as the implemenation in the
manifest? (Bundle-Activator: org.osgi.framework.BundleActivator)
- John
On Fri, 2006-05-26 at 18:00 +0800, Niclas Hedhman wrote:
> Hi,
>
> I think it would be good if one was allowed to use ${pom.version} for version
> attribute in Export-Package. There are two issues as far as I can see;
>
> 1. -SNAPSHOT is not allowed at all.
>
> 2. Does the package version evolve at some other rate than the bundle? And
> should one perhaps only use the first two digit groups for the package
> version.
>
>
> I also think that
>
> * <bundleSymbolicName> should default to ${pom.artifactId}
>
> * <bundleName> should default to ${pom.name}
>
> * <bundleDescription> should default to ${pom.description}
>
> * <bundleVendor> should default to ${pom.organization.name}
>
> * <bundleVersion> should default to ${pom.version} (see above).
>
> * bundleContactAddress should default to ${pom.organization.url}
>
> * <bundleUrl> and/or <bundleUpdateLocation> should default to ${pom.url}
>
> * <bundleCopyright should default to
> Copyright ${pom.inceptionYear}, ${pom.organization.name}
>
> * A whole bunch of other properties to read from file(s) in the project
> directory instead, including <exportPackage>, <excludeImport>
> Or perhaps utlize the <properties> tag in the pom main section...
>
> If that is done, then one can move the whole <plugin> section of the POM to a
> (grand)*parent pom, which I think simplifies 'standard cases', still allowing
> for the current form.
>
> Willing to do the work, but before wasting my time, I would like to get some
> feedback.
>
> WDYT?
>
>
> Cheers
> Niclas
>
