So how do I use my documentation-producing plugin in its own documentation without a variable version number?
See http://github.com/khuxtable/docbkx-wrapper-plugin/blob/master/pom.xml for an example. It's in the "site" profile near the bottom. -K On May 17, 2010, at 12:48 PM, Kalpak Gadre wrote: > Yes variable version names are not allowed as of Maven 3. I believe the > reason will be deploying into repositories, as pom with version as some > properties instead of a proper version could get deployed. > > A quick fix is to configure Eclipse to use external installation of Maven 2. > But remember that variable versions will not be supported in the future > releases. I personally use version number derived out of properties for our > Continuous Integration server to generate the tick part of version > (1.0.0.[123]). I haven't personally found a solution yet using Maven 3. > > Thanks, > > Kalpak > > >> >> >> Hi, >> >> >> >> At first, thanks for your attention and time to read. >> >> >> >> In our enterprise applications we use MyEclipse 8.5 with >> M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2 >> we >> could specify a variable for the application version in the parent pom, so >> that >> in the child poms we could able to specify the version by the same variable. >> That helps us saving our time for updating version number in each project >> upgrade and for reusability. >> >> >> >> I hope I can clearly demonstrate the problem as the >> following piece of code for pom.xml’s. >> >> Now the problem is in maven3 (m2eclipse) it gives a warning >> that says “version must be a constant instead of a variable”. I have been >> trying lots of variations such as moving out the<version> tag or >> swapping the expressions between<projectVersion> and<version> >> tags or the other suggestions from the different forum sites, etc.. However, >> the solution never comes up.. Maybe I am doing something wrong, but could not >> find out yet. >> >> >> >> Any help would be appreciated, >> >> Many thanks in advance, >> >> Bariscan >> >> >> >> BTW, you can check the case from here: >> >> >> >> PARENT: >> >> <project >> >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/maven-v4_0_0.xsd"; >> >> xmlns="http://maven.apache.org/POM/4.0.0"; >> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> >> >> <modelVersion>4.0.0</modelVersion> >> >> <groupId>com.gg.n3gservices</groupId> >> >> <artifactId>n3gservices</artifactId> >> >> <name>n3gservices Maven >> Main</name> >> >> <packaging>pom</packaging> >> >> <description>Version Alias: >> MemberProfitLocalService</description> >> >> <version>${projectVersion}</version> >> >> <properties> >> >> >> <projectVersion>2.4</projectVersion> >> >> </properties> >> >> >> >> Child; >> >> <project >> >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/maven-v4_0_0.xsd"; >> >> xmlns="http://maven.apache.org/POM/4.0.0"; >> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> >> >> <modelVersion>4.0.0</modelVersion> >> >> <groupId>com.gg.n3gservices</groupId> >> >> <artifactId>n3gservicesBugfix</artifactId> >> >> <name>n3gservices Bugfix</name> >> >> <parent> >> >> >> <artifactId>n3gservices</artifactId> >> >> >> <groupId>com.gg.n3gservices</groupId> >> >> >> <relativePath>../n3gservices/pom.xml</relativePath> >> >> >> <version>${projectVersion}</version> >> >> </parent> >> >> <version>${projectVersion}</version> >> >> >> _________________________________________________________________ >> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. >> https://signup.live.com/signup.aspx?id=60969 >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
