]
Max Rydahl Andersen commented on JBIDE-15332:
---------------------------------------------
Happy to see movement on this one again, but I don't grok why you need to ask all
this.
using skipTest to disable globally all downloads via the normal download plugin is just
wrong imo.
why are skipRequirements controlling download of normal maven
dependencies ?
----------------------------------------------------------------------------
Key: JBIDE-15332
URL:
https://issues.jboss.org/browse/JBIDE-15332
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.2.0.Beta1
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Priority: Minor
Labels: f2f2014
Fix For: LATER
I stumbled on [~dgolovin]'s patch for livreload at
https://github.com/jbosstools/jbosstools-livereload/pull/54/files
This is not the first time i've seen skip having to be enabled for plain normal mvn
dependencies.
skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things
done via non-maven download mechanism.
Why is this applied to mvn dependency downloads ?
The culprit for needing this line is at:
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012:
https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b...
I understand why the explicit google download plugin (why is there two versions used
btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements
are using this for download ?