I am currently responsible for a "legacy" POM that copies ZIP files
from the Red Hat JBoss Fuse distro in our Nexus repository manager
to a location on a local worstation. Several ZIP files are copied
from each of the following Fuse components, ActiveMQ, Camel and CXF.
To perform the copy
I've just tried version ranges for the first time, and I hit a pothole.
Step 1: set version in dependency to: 7.14.0.c52.2. Run a build.
Step 2: change version in pom to [7.13.500.c52.2,7.13.600.c52.2).
Now, mvn dependency:whatever shows the correct resolution, but an
actual build stubbornly
Michael-
out of curiosity which stax-ex versions are located at
C:\Users\Michael CTR
Tarullo.FAA\.m2\super-pom-test-repository-62\org\jvnet\staxex\stax-ex
concerning version 2.15.1.redhat-620133
if you want to implement a specific "version rule" then you'll need to
implement
a version rule
IIRC don't version ranges only work with Major.Minor.Patch-(Qualifier or
Build) formatted version numbers, eg 3.2.1-07
On Friday 2 October 2015, Benson Margulies wrote:
> I've just tried version ranges for the first time, and I hit a pothole.
>
> Step 1: set version in