Databases
StackOverflow2013
Postsdbo
POGradle dependencyManagement
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGradle dependencyManagement
    primarykey
    data
    text
    <p>I am migrating Maven project to Gradle. I needed manage dependencies so tryed resolutionStrategy like so:</p> <pre><code> def dependencyVersions = [ 'org.slf4j:slf4j-api' : '1.7.2', 'javax.inject:javax.inject' : '1', 'com.google.code.findbugs:annotations' : '2.0.1', 'com.typesafe:config' : '1.0.0', 'ch.qos.logback:logback-classic' : '1.0.9', 'com.google.guava:guava' : '14.0', 'com.google.inject:guice' : '3.0', 'com.google.inject.extensions:guice-multibindings' : '3.0', 'com.google.code.gson:gson' : '2.2.2', 'joda-time:joda-time' : '2.1', 'com.thoughtworks.paranamer:paranamer' : '2.5.2', 'org.codehaus.groovy:groovy-all' : '2.0.6', 'commons-validator:commons-validator': '1.4.0', 'org.apache.shiro:shiro-core' : '1.2.1', 'junit:junit-dep' : '4.10', 'org.mockito:mockito-core' : '1.9.5', 'org.hamcrest:hamcrest-core': '1.3', 'org.hamcrest:hamcrest-library': '1.3', 'org.unitils:unitils-core': '3.3' ] configurations.all { resolutionStrategy { eachDependency { DependencyResolveDetails details -&gt; def version = dependencyVersions["$details.requested.group:$details.requested.name"] if (version != null) details.useVersion version } } } </code></pre> <p>but now when I try to Gradle install (into local Maven repository) I am getting this error:</p> <pre><code>Execution failed for task ':counter-module:install'. </code></pre> <blockquote> <p>Could not publish configuration 'archives' Unable to initialize POM pom-default.xml: Failed to validate POM for project lt.counter at /home/workspace/counter/counter-module/build/poms/pom-default.xml</p> </blockquote>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USIowA
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGradle dependencyManagement
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGradle dependencyManagement
      1. USJosh Gagnon
      1. VTFavorite
    3. VO
      singulars
      1. POGradle dependencyManagement
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI believe you're looking for this: http://stackoverflow.com/questions/9547170/in-gradle-how-do-i-declare-common-dependencies-in-a-single-place It was the third item when searching stackoverflow for the exact text of your question title...
      singulars
      1. POGradle dependencyManagement
      1. USJosh Gagnon
    2. COBut this way does not force to use exact version you want, if I am using dependency version N, and my other dependency use that dependency version N-1 I will get conflict. I need to force all my dependencies use N version.
      singulars
      1. POGradle dependencyManagement
      1. USIowA
    3. COAh, I see. Yes, the map technique is really more for convenience and DRY. If you can't trust your devs (and who can? :P) you'll want dependency resolution, as you are trying. Unfortunately I don't have firsthand experience with that.
      singulars
      1. POGradle dependencyManagement
      1. USJosh Gagnon
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload