jduranmaster / docbkx-tools

Automatically exported from code.google.com/p/docbkx-tools
0 stars 0 forks source link

docbkx-quickstart-archetype 2.0.13 generates project with invalid docbkx-maven-plugin version reference #76

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create a project using docbkx-quickstart-archetype ( mvn 
org.apache.maven.plugins:maven-archetype-plugin:2.0:generate 
-DarchetypeArtifactId=docbkx-quickstart-archetype 
-DarchetypeGroupId=com.agilejava.docbkx -DarchetypeVersion=2.0.13 )
2.
3.

What is the expected output? What do you see instead?
Expected is that the pom of generated project makes use of 
com.agilejava.docbkx:docbkx-maven-plugin of same version as archetype, or 
latest release (e.g. 2.0.13 in this case). Instead the archetype creates 
project which reference 2.0.10-SNAPSHOT version of docbkx-maven-plugin

What version of the product are you using? On what operating system?
2.0.13 on Windows 7 x64, Java 6 update 25 x64, Maven 3.0.3

Please provide any additional information below.

Original issue reported on code.google.com by ssla...@gmail.com on 3 Jun 2011 at 1:54

GoogleCodeExporter commented 8 years ago
Confirmed, it is hardcoded in the pom file =)

Original comment by MimilO...@gmail.com on 4 Jun 2011 at 7:27

GoogleCodeExporter commented 8 years ago
commited in r235

the plugin version is not anymore harcoded in the archetype, integration test 
has also been added

Original comment by MimilO...@gmail.com on 12 Jun 2011 at 5:54

GoogleCodeExporter commented 8 years ago
not fixed, wrong package is generated

Original comment by MimilO...@gmail.com on 12 Jun 2011 at 6:33

GoogleCodeExporter commented 8 years ago
now fixed in r236, it was due to unwanted maven resource filtering

Original comment by MimilO...@gmail.com on 12 Jun 2011 at 7:33