[
https://issues.apache.org/jira/browse/MJAR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588355#comment-15588355
]
Marco Peters commented on MJAR-163:
-----------------------------------
I have a similar problem. Till now I've used 2.5 but wanted to switch to 3.0.2.
In the previous version I've used useDefaultManifestFile in the configuration.
I was able to add this into the plugin configuration of the parent pom and all
child modules used this configuration.
Now I have to use manifestFile but this fails in the parent pom. So I would
have to declare this configuration in each module. Which is pretty redundant.
So I have to stick to 2.5.
> maven jar plugin fails if bundle plugin defined in type 'pom'
> -------------------------------------------------------------
>
> Key: MJAR-163
> URL: https://issues.apache.org/jira/browse/MJAR-163
> Project: Maven JAR Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Eric Charles
> Attachments: pom.xml
>
>
> I have the same issue as the one posted here:
> http://markmail.org/message/mjsn2xozkcesethl
> Running 'mvn install' on the attached pom give:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:2.4:jar (jar) on project test:
> Error assembling JAR: Manifest file:
> /Users/eric/wrk/spc/aos/test/target/osgi/MANIFEST.MF does not exist. -> [Help
> 1]
> Yes, no class to process in a pom, but I would expect maven-jar-plugin to
> play nice (ignore the abscence of osgi/... file) in such a case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
