Dave Nice

Tycho does not handle multi-release OSGi bundles

1

I have fallen over the issue documented at https://bugs.eclipse.org/bugs/show_bug.cgi?id=542905 Eclipse and OSGi support multi-release OSGi bundles. In my case I've got a Java 9+ MANIFEST.MF that introduces package imports for...

This PR fixes issue #379 by introducing a new mojo parameter `copyrightStringFormat` allowing users to configure a different copyright string format. I considered moving the default copyright string up to...

Currently, copyright statements are always in the format: `Copyright (C) 2020 ` But my organisation requires this format: `(c) Copyright 2020.` This aspect of the tooling should be configurable by...

Position of defaultjvmserver parameter is confusing.

1

If you're packaging an existing WAR as a bundle by extending the config, you specify the defaultjvmserver within the execution config. If you create a separate module for the CICS...

For instance, pipeline resources require supporting files to be present in EBCDIC on the server. We'd need to detect the pipeline resource additional file and transcode it during build time....

(variables in attributes as introduced with CICSBT)

#14 covers non-Java based bundle parts. It would be good to build Node bundle parts which we haven't taken into account for that issue.

Support for bundle import statements. We don't think this is likely to be essential for the kind of use we're targetting.

Currently the bundlepart filename is derived from the symbolic name. However it's possible to use names that aren't valid on some filesystems.

Release 1.0.6.

1

Release 1.0.6 of the Maven plugin with latest common version 2.0.1