+1 Dan
On Jul 9, 2014, at 4:31 AM, Guillaume Nodet <gno...@apache.org> wrote: > I'm starting a vote to release the spi-fly 1.0.1 bundles: > org.apache.aries.spifly.core-internal > org.apache.aries.spifly.dynamic.bundle > org.apache.aries.spifly.static.bundle > org.apache.aries.spifly.static.tool > org.apache.aries.spifly.weaver-internal > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachearies-1006/org/apache/aries/spifly/ > Change log: Upgrade all modules to the released parent Change parent > version to 2.0.0-SNAPSHOT [ARIES-1192] Upgrade to maven-bundle-plugin > 2.4.1-SNAPSHOT [ARIES-1185] SPI Fly does not work with Java 8 Define the > versioning plugin as an execution in the parent pom. It can thus be removed > from ALL the other poms. Fix spi-fly tests spy fly build with java6, maven > 3.2.1 [ARIES-1006] Upgrade to the "new" parent pom and OSGi 4.3.1 Convert > file to use unix line delimiters. [ARIES-1156] SPI-Fly static tool does not > work with Require-Capability bundles [ARIES-1156] SPI Fly fix syntax errors > with static tool Manifest generation [SPI Fly] Fix for NPE. Additional > example that shows a single bundle being a provider and consumer at the > same time. Add Aries Versioning Plugin for the bundles in this project. > > Please review and vote, > > Cheers, > Guillaume -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
