|maven result with strictMavenVersions : invalid version numbers in maven-metadata.xml [message #1728022]
||Wed, 30 March 2016 10:22
| German Vega
Registered: December 2015
I am trying to use the aggregator to produce a maven mirror of a p2 update site.
Every things work ok, but I would like to have strict maven versions, as discussed in bug 314992. This is important for me, as I would like the maven users of the repository to use version ranges, instead of specific version numbers.
Everything seems to work, I have the good repository layout and file naming convention :
However, the version numbers in the file maven-metadata.xml are not correct, and this produces errors on my build :
<?xml version="1.0" encoding="ASCII"?>
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://maven.apache.org/METADATA/1.0.0">
Notice that they use major.minor.third.qualifier and not major.minor.third-qualifier
I attach a minimal b3 model with my use case, to see if you can reproduce the problem.
Just for information, my use-case is to produce a maven repository to be able to build standalone applications that depend on eclipse/UML2 using maven. I am using b3 as downloaded from the 4.4 update site
Powered by FUDForum
. Page generated in 0.02263 seconds