Thanks, I’ll take a look
One of these days I was going to attempt a port of an incremental build system
we developed to Maven.
Some concepts include a post compile artifact byte code analyzer and comparator
that classifies the nature of change to help optimize away (in some cases) the
dependent
.
If I'm not wrong
http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml
should
return all versions while it returns only 2 .
On Mon, Mar 10, 2014 at 4:37 PM, Mauri, Richard richard.ma...@sap.com
wrote:
I am still having trouble.
It certainly should be easy to reproducee
Yes Wayne, I rm -rf ~/.m2/repository
Your questioning implies my test case is not reproducible for you; really
On 3/10/14, 9:19 AM, Wayne Fay wayne...@gmail.com wrote:
I am still having trouble.
It certainly should be easy to reproducee no?
It is a trivial settings.xml and pom.xml and
I am still having trouble.
It certainly should be easy to reproducee no?
It is a trivial settings.xml and pom.xml and mvn dependency:tree goal
Thanks for helping, but please keep at it :-)
On 3/10/14, 6:15 AM, Wayne Fay wayne...@gmail.com wrote:
Where did this repo.maven.apache.org url come
Using mvm 3.1.1 with a pom.xml with a dependency on log4j version [1.2.8]
- it will not resolve
Similar for required versions up to and including [1.2.15]
It¹s not an option for us to just go to the later log4j like [1.2.17]
What¹s going on here?
If we request an open ended 1.2.8 then it
