4 ms·

Care to explain why?

• pjmlp 6y ago
  Because it ties the source code to the origin of the dependencies, forces code rewrites that don't scale across all dependencies and aren't enterprise friendly for using internal IT vetoed repositories. Just because a dependency changed location I should not be obliged to touch a single character of the source code.
  • brabel 6y ago
    In the case of Groovy that OP mentioned, that's wrong. This is what it looks like in Groovy[1]: @Grab(group='org.springframework', module='spring-orm', version='3.2.5.RELEASE') import org.springframework.jdbc.core.JdbcTemplate This provides the dependency's coordinates... but not where it comes from. You can define where it comes from by configuring Repositories (normally done by modifying the M2 settings file). This is how Java has always done it in Maven and Gradle, even Ant long time ago. And this works really well! Never seen anyone complaining about how that works. [1] http://docs.groovy-lang.org/latest/html/documentation/grape.html http://docs.groovy-lang.org/latest/html/documentation/grape....
    • pjmlp 6y ago
      I am the OP and you forgot this little detail, @GrabResolver(name='restlet', root='http://maven.restlet.org/')
      • brabel 6y ago
        No I didn't. This is if you WANT TO use a particular repo. Read the docs and you'll understand that.
        • pjmlp 6y ago
          Which breaks the script when that repo is no longer available.