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 copy&filter it to target/config (or something, anything but target/classes I would say) - configure the pax-plugin to read from the location used in the step above
I presume here that the pax-plugin can read its configuration from a specific (configurable) location... If not, I guess you're screwed... Roland > 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 > not > going to the jar at all. It is like a config file for the pax plugin. And > it > is a text file. > > I read the info in the link about the resources plugin - it is exactly > what > I need but without packing this file to the resulting jar and it must not > go > to the target directory during the build process. > > 19 ÄÅËÁÂÒÑ 2009 Ç. 0:45 ÐÏÌØÚÏ×ÁÔÅÌØ Dennis Lundberg > <denn...@apache.org>ÎÁÐÉÓÁÌ: > >> 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 let the JAR Plugin >> handle the version in there instead of managing it yourself. See >> >> >> http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html >> >> and >> >> http://maven.apache.org/shared/maven-archiver/index.html >> >> >> Grigory Ptashko wrote: >> > 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 the >> MANIFEST.MF >> > in the special header. So when I perform a release the release version >> have >> > the new version, the trunk version gets the new y-SNAPSHOT version but >> that >> > MANIFEST.MF file has old version x-SNAPSHOT which becomes wrong both >> in >> > trunk and in the release. >> > >> > What I want is two steps to be executed while release:perform (phrases >> in >> > quotes are taken from here >> > >> http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html >> > ): >> > >> > >> > - The first is after the step "Change the version in the poms from >> > x-SNAPSHOT to a new version (you will be prompted for the versions >> to >> use)": >> > the same transformation must be done with the text file that I >> specify. >> > - The second is after the step "Bump the version in the POMs to a >> new >> > value y-SNAPSHOT (these values will also be prompted for)": the >> same >> > transformation must be done with text file that I specify. >> > >> > >> > How can I achieve this? >> > >> > Thank you. >> > >> >> >> -- >> Dennis Lundberg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > ó Õ×ÁÖÅÎÉÅÍ, > çÒÉÇÏÒÉÊ ðÔÁÛËÏ > > +7 (916) 1489766 > gptas...@cmmt.ru > http://www.cmmt.ru > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
