Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 50853 invoked from network); 18 Dec 2009 22:27:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Dec 2009 22:27:46 -0000 Received: (qmail 89977 invoked by uid 500); 18 Dec 2009 22:27:44 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 89855 invoked by uid 500); 18 Dec 2009 22:27:44 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 89845 invoked by uid 99); 18 Dec 2009 22:27:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 22:27:44 +0000 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=SPF_HELO_NEUTRAL,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 86.59.33.198 is neither permitted nor denied by domain of Roland.Asmann@adesso.at) Received: from [86.59.33.198] (HELO mail.cfc.at) (86.59.33.198) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 22:27:35 +0000 Received: from amavis by mail.cfc.at with scanned-ok (Exim 3.36 #1 (Debian)) id 1NLlI2-0000NM-00 for ; Fri, 18 Dec 2009 23:27:14 +0100 Received: from mail.cfc.at ([127.0.0.1]) by localhost (mail.cfc.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACpifyH8vhH4 for ; Fri, 18 Dec 2009 23:27:08 +0100 (CET) Received: from localhost ([127.0.0.1] helo=cfc.at ident=www-data) by mail.cfc.at with esmtp (Exim 3.36 #1 (Debian)) id 1NLlHv-0000NB-00 for ; Fri, 18 Dec 2009 23:27:07 +0100 Received: from 85.127.252.101 (SquirrelMail authenticated user asr) by cfc.at with HTTP; Fri, 18 Dec 2009 23:27:07 +0100 (CET) Message-ID: <52718.85.127.252.101.1261175227.squirrel@cfc.at> In-Reply-To: <4d71bb0f0912181403g606babc6td66ec8f900b9dc9e@mail.gmail.com> References: <4d71bb0f0912181311xd24edc8r14c66312fd3a162@mail.gmail.com> <4B2BF7F8.6050306@apache.org> <4d71bb0f0912181403g606babc6td66ec8f900b9dc9e@mail.gmail.com> Date: Fri, 18 Dec 2009 23:27:07 +0100 (CET) Subject: Re: release plugin: version change not only in POMs ? From: "Roland Asmann" To: "Maven Users List" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Checked: Checked by ClamAV on apache.org 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 copy&filter them to the root of the project (make sure this is done before the pax-plugin runs) If you use the clean-plugin, it would be a good idea to put the 2 files in the root of the project in the list of files to delete as well! 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 > �������: > >> 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-unsubscribe@maven.apache.org >> For additional commands, e-mail: users-help@maven.apache.org >> >> > > > -- > � ���������, > �������� ������ > > +7 (916) 1489766 > gptashko@cmmt.ru > http://www.cmmt.ru > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org