[
https://issues.apache.org/jira/browse/FELIX-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990744#comment-12990744
]
Simon Chemouil edited comment on FELIX-2819 at 2/4/11 9:14 PM:
---------------------------------------------------------------
By the way, if you're not doing it already (or for people who might read this
issue), here's the cleanest workaround :
{code:XML}
<project ...>
<build>
<!-- A lot of stuff may go here-->
<resources>
<!-- You have to keep this only if you want to keep the
default Maven layout as well-->
<resource>
<directory>src/main/resources</directory>
</resource>
<!-- Here's the magic stuff: include everything except
Java and hidden files (eg, .svn directories) -->
<resource>
<directory>${project.build.sourceDirectory}</directory>
<excludes>
<exclude>**/*.java</exclude>
<exclude>**/.*</exclude>
</excludes>
</resource>
<!-- Alternatively, you may want to include only
packageinfo files (if so, remove the previous
<resource/> block that is a superset of this one)
-->
<resource>
<directory>${project.build.sourceDirectory}</directory>
<includes>
<include>**/packageinfo</include>
</includes>
</resource>
</resources>
<!-- A lot more stuff, including maven-bundle-plugin if you
don't use pluginManagement in a parent POM -->
</build>
</project>
{code}
On our project we put the "include all resources that are in src/" rule in a
parent POM... Of course, it would still be nice if maven-bundle-plugin would
manage bnd-related files out-of-the-box.
Hope this helps,
Simon
was (Author: magnet):
By the way, if you're not doing it already (or for people who might read
this issue), here's the cleanest workaround :
<project ...>
<build>
<!-- A lot of stuff may go here-->
<resources>
<!-- You have to keep this only if you want to keep the
default Maven layout as well-->
<resource>
<directory>src/main/resources</directory>
</resource>
<!-- Here's the magic stuff: include everything except
Java and hidden files (eg, .svn directories) -->
<resource>
<directory>${project.build.sourceDirectory}</directory>
<excludes>
<exclude>**/*.java</exclude>
<exclude>**/.*</exclude>
</excludes>
</resource>
<!-- Alternatively, you may want to include only
packageinfo files (if so, remove the previous
<resource/> block that is a superset of this one)
-->
<resource>
<directory>${project.build.sourceDirectory}</directory>
<includes>
<include>**/packageinfo</include>
</includes>
</resource>
</resources>
<!-- A lot more stuff, including maven-bundle-plugin if you
don't use pluginManagement in a parent POM -->
</build>
</project>
On our project we put the "include all resources that are in src/" rule in a
parent POM... Of course, it would still be nice if maven-bundle-plugin would
manage bnd-related files out-of-the-box.
Hope this helps,
Simon
> packageinfo files in src/main/java are ignored
> ----------------------------------------------
>
> Key: FELIX-2819
> URL: https://issues.apache.org/jira/browse/FELIX-2819
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Alasdair Nottingham
>
> The bnd tool can pick up the package version from a packageinfo file if it is
> stored next to the java files.
> The maven-bundle-plugin will only include them in the jar, and make them
> visible to bnd if they are in the src/main/resources directory. I would like
> to use these files for specifying versions, rather than putting it in the
> pom. This allows me to specify the version once in this file even if it is
> repackaged in a different jar later.
> The problem is I have to put the files into src/main/resources which
> significantly reduces the chance of updating them when a change is made.
> Could the maven-bundle-plugin be updated to put the packageinfo files from
> src/main/java into the jar before calling bnd?
> Thanks
> Alasdair
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
