Then configure the resource-plugin specially for this file of yours:
- put the file in src/main/config (or something like that)
- have the resource-plugin copyfilter it to target/config (or something,
anything but target/classes I would say)
- configure the pax-plugin to read from the location
This helped me! Thanks a lot!
19 декабря 2009 г. 14:45 пользователь Anders Hammar and...@hammar.netнаписал:
Your plugin binding binds the resources plugin as configured to the Maven
lifecycle. But you're executing
mvn resources:copy-resources
which isn't executing the lifecycle (it justs
I've inserted the following configuration to my pom.xml (taken from here
http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html
):
plugin
artifactIdmaven-resources-plugin/artifactId
version2.4.1/version
executions
execution
Your plugin binding binds the resources plugin as configured to the Maven
lifecycle. But you're executing
mvn resources:copy-resources
which isn't executing the lifecycle (it justs executed the copy-resources
goal). Try
mvn install
instead!
If you need to be able to run mvn
Hello.
Recently I've got acquainted with the release plugin. I started using it, it
works great but I am missing one feature. The problem is the following: the
version that is specified in a POM is used not only in this POM but also in
another place in a plain-text format. Actually it is used in
You should try to go about this in another way. Instead of having the
version explicitly in text files, you should filter these files using
the Resources Plugin. See
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
As for the example of the manifest file, you should
Sorry for the mess but actually this is not directly the MANIFEST file. It
is a file used by other plugin to create the MANIFEST file. I am talking
about the pax plugin and osgi.bnd file which must reside in the root of the
maven project along with the pom.xml. This file is a not resource, it is
Hi,
Sorry, didn't read the mail good enough and made some errors in my
previous reply!
- Put your files in src/main/config with the variables configured
- Have the resource-plugin copyfilter them to the root of the project
(make sure this is done before the pax-plugin runs)
If you use the
