don't worry, this is just a "conflict" between pom-properties and velocity.
both use the same mechanism (${someVar}) to reference a property, which is
replaced with a certain value.
and since there no properties "jetty.version" and "wicket.version" available
during archetype creation,
maven (or velocity) shows these warnings.
i guess there is no way to prevent this (other than not using
maven-properties)?
i think it's not too good for a first experience for newcomers to start the
wicket-experience with warnings,
even though this actually has nothing to do with wicket itself...
gerolf
On 10/5/07, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]>
wrote:
>
> writing this line :
>
> mvn archetype:create -DarchetypeGroupId=org.apache.wicket
> -DarchetypeArtifactId=wicket-archetype-quickstart
> -DarchetypeVersion=1.3.0-beta3 -DgroupId=com.mycompany
> -DartifactId=myproject
>
> to create a project yields these warnings:
>
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = archetype-resources/pom.xml [line 35,column 34] :
> ${wicket.version} is not a valid reference.
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = archetype-resources/pom.xml [line 41,column 34] :
> ${wicket.version} is not a valid reference.
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = archetype-resources/pom.xml [line 64,column 34] :
> ${jetty.version} is not a valid reference.
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = archetype-resources/pom.xml [line 70,column 34] :
> ${jetty.version} is not a valid reference.
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = archetype-resources/pom.xml [line 76,column 34] :
> ${jetty.version} is not a valid reference.
>
>
> should they be taken into consideration?
>
>
> I took the command line from http://wicket.apache.org/quickstart.html
>
>
> regards Nino
>
