[FELIX-3772] maven-bundle-plugin does not scan blueprint in workspace outside default location

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: maven-bundle-plugin-2.3.7
• Fix Version/s: maven-bundle-plugin-2.4.0
• Component/s: Maven Bundle Plugin
• Environment: Windows 7, Maven 3.0.4
• Assignee: Unassigned
• Reporter: Rigas Grigoropoulos
• Created: 21/Nov/12 10:16
• Updated: 12/Jun/13 23:46
• Resolved: 22/Nov/12 01:27

Description

maven-bundle-plugin will not scan blueprint xml files in the workspace during a Maven build, unless the blueprint file is located at OSGI-INF/blueprint/ and an instruction "Bundle-Blueprint: OSGI-INF/blueprint" is provided.

The bug is in org.apache.felix.bundleplugin.BlueprintPlugin and in method analyzeJar.
Original code:

String bpHeader = analyzer.getProperty( "Bundle-Blueprint", "OSGI-INF/blueprint" );
Map<String, Map<String, String>> map = Processor.parseHeader( bpHeader, null );
for ( String root : map.keySet() )
{
Jar jar = analyzer.getJar();
Map<String, Resource> dir = jar.getDirectories().get( root );
if ( dir == null || dir.isEmpty() )

{ Resource resource = jar.getResource( root ); if ( resource != null ) process( analyzer, root, resource, headers ); return false; }

This code reads a custom location from the Bundle-Blueprint instruction, locates the resource in the classpath and does the processing, but then just returns false.
Changing as follows fixes the problem:
if ( resource != null )
process( analyzer, root, resource, headers );
continue;