Felix Meschberger wrote:
On the other hand, I assume that 99% of the projects do not specify
resources other than the default and most of the time those should be
copied. Hence, it might as well be left as is. And hanlding "missing
resources" is fixed, so we might just go ahead :-)
Well, we can certainly move forward with the current default and wait
until we get more feedback. In the long run, it probably makes the most
sense to just have the plugin copy the resource section of the pom to
the Include-Resource instruction, but it is not something that needs to
slow us down at present.
-> richard
Regards
Felix
-> richard
>
>> maven-bundle-plugin: Failures if src or parts of it are missing
>> ---------------------------------------------------------------
>>
>> Key: FELIXM2-10
>> URL: http://issues.apache.org/jira/browse/FELIXM2-10
>> Project: Felix M2 Plugin
>> Issue Type: Bug
>> Reporter: Felix Meschberger
>> Assigned To: Richard S. Hall
>> Attachments: FELIXM2-10.diff
>>
>>
>> When using the maven-bundle-plugin to build bundles from existing
jar files, three issues exist:
>> * If nothing is copied into the project output directory
(target/classes), the folder does not exist and the
BundlePlugin.getClassPath fails for the line "new Jar(".",
outputDirectory)"
>> * If no resources exist, an exception is logged for the missing
src/main/resources folder. I suggest to only place a default
Include-Resources header if the src/main/resources folder exists.
>> * If no maven build phase generates output the target folder
does not exist at the time the BundlePluing.execute method tries to
write the JAR File.
>> I will attach a patch for the three issues.
>>
>
>
