Hi,
Are there any opposition to using explicitly dependency version numbers?
Occasionally, I would get errors like the below:
Failed to collect dependencies at junit:junit:jar:[4.10,4.10]
Caused by: org.eclipse.aether.resolution.VersionRangeResolutionException: No
versions available for junit:juni
There is a filter in the root pom.xml to only include these types inside the
jars during package time:
So essentially, all of the jars from *-res projects will be empty.
I think this was residual setting when we were still in incubator where we were
debating if resources should be included.
Are t
+1
> so I was planning to update
-Original Message-
From: Chen, Pei [mailto:pei.c...@childrens.harvard.edu]
Sent: Friday, May 02, 2014 12:27 PM
To: dev@ctakes.apache.org
Subject: Explict version numbers instead of ranges in pom.xml
Hi,
Are there any opposition to using explicitly depend
I am all for adding resources to the resource jars. It makes it very
difficult to write code/tests that use other modules when the resources
can't be resolved using normal maven dependencies.
On Fri, May 2, 2014 at 12:30 PM, Chen, Pei
wrote:
> There is a filter in the root pom.xml to only inclu
