maven-central

How does the Central Repository sort version numbers?

半世苍凉 提交于 2019-12-02 19:37:37
问题 I maintain an open source project and publish its releases to The Central Repository. I just published oshi-core-2.6 . The versioning in my pom.xml for that release reads: <groupId>com.github.dblock</groupId> <artifactId>oshi-core</artifactId> <version>2.6</version> My code requires Java 8 due to the Date/Time functions. To support a user's request, just prior to this release, I released a Java 7 compatible version using the threeten backport, with the following in its pom.xml : <groupId>com

Gradle only downloads .aar.asc from Maven Central

情到浓时终转凉″ 提交于 2019-12-02 10:09:58
I freshly deployed an Android library named TypedPreferences . I used it in another Android project for some days. Suddenly, it stopped working - dependencies cannot be found any longer. I noticed that Gradle only downloads one file when I clean the project: Download http://repo1.maven.org/maven2/info/metadude/android/typed-preferences/ \ 1.0.0/typed-preferences-1.0.0.aar.asc These are build files of my pet project: build.gradle : // Top-level build file where you can add configuration // options common to all sub-projects/modules. buildscript { repositories { mavenCentral() } dependencies {

How does the Central Repository sort version numbers?

蹲街弑〆低调 提交于 2019-12-02 07:40:55
I maintain an open source project and publish its releases to The Central Repository . I just published oshi-core-2.6 . The versioning in my pom.xml for that release reads: <groupId>com.github.dblock</groupId> <artifactId>oshi-core</artifactId> <version>2.6</version> My code requires Java 8 due to the Date/Time functions. To support a user's request, just prior to this release, I released a Java 7 compatible version using the threeten backport, with the following in its pom.xml : <groupId>com.github.dblock</groupId> <artifactId>oshi-core</artifactId> <version>2.6-m-java7</version> How Version

Maven build gets connection reset when downloading artifacts

蹲街弑〆低调 提交于 2019-12-01 05:58:29
We have a maven build that runs in jenkins in amazon ec2 instances. The total build takes 20-30min and roughly every other run it fails because it cant download artifacts from maven central. This is the failing part of the log: [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration

Gradle error “Attribute ”xxx“ has already been defined” in Android Studio

喜你入骨 提交于 2019-11-28 05:16:27
I created a project in Android Studio and added a few dependencies using Maven Central and when I try to compile, I run into this type of errors: Error:Gradle: Attribute "titleTextStyle" has already been defined Error:Gradle: Attribute "subtitleTextStyle" has already been defined [...] And so on... Here is my build.gradle file: buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:0.5.+' } } apply plugin: 'android' repositories { mavenCentral() } android { compileSdkVersion 18 buildToolsVersion "17.0.0" defaultConfig { minSdkVersion 8

What is included in JCenter repository in Gradle?

匆匆过客 提交于 2019-11-28 03:52:26
From Gradle 1.7 there is new Public repository JCenter. repositories { jcenter() } So I want to ask if all jars from Maven Central are parts of this repo? And if not from what is JCenter repo consists of? And is JCenter more reliable from Maven Central as downtime? Rene Groeschke jcenter() is similar to mavenCentral() . Have a look at https://bintray.com/bintray/jcenter for more details. The jCenter guys claim that they have a better performance than Maven Central. As mentioned in https://bintray.com/bintray/jcenter : JCenter is the place to find and share popular Apache Maven packages for use

Removing an artifact from Maven Central

帅比萌擦擦* 提交于 2019-11-27 21:57:43
I just sync'd an artifact to Maven Central from oss.sonatype.org. Immediately after doing so, a problem was discovered (of course). I haven't announced the new artifact yet, it is very unlikely that anyone is using it yet, so I'd like to take it down before anyone starts using the broken version. How can I remove a broken artifact from Maven Central? Can't be done. It's A Rule. But if you want to try, contact the Sonatype people who support oss.sonatype.org. So you generally push a new, higher, version with the fix, and tell everyone to use it. If you accidentally distributed an artifact which

Gradle Could not HEAD https://..pom > peer not authenticated

半腔热情 提交于 2019-11-27 07:36:47
When you upgrade from gradle 2.0 to 2.1, you may see following error. Could not HEAD 'https://jcenter.bintray.com/de/undercouch/gradle-download-task/1.0/gradle-download-task-1.0.pom'. > peer not authenticated To be fair, this error is not due to gradle. It is problem of how java handles ssl connections. I am using following java version. java -version java version "1.7.0_40" Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode) You can use following answer to import security certificate your java installation. I do not care about

Gradle error “Attribute ”xxx“ has already been defined” in Android Studio

痴心易碎 提交于 2019-11-27 05:33:55
问题 I created a project in Android Studio and added a few dependencies using Maven Central and when I try to compile, I run into this type of errors: Error:Gradle: Attribute "titleTextStyle" has already been defined Error:Gradle: Attribute "subtitleTextStyle" has already been defined [...] And so on... Here is my build.gradle file: buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:0.5.+' } } apply plugin: 'android' repositories { mavenCentral()

Gradle 0.9.+/0.9.2 error: Unable to load class 'com.android.builder.testing.api.DeviceProvider'

跟風遠走 提交于 2019-11-27 01:57:34
This morning, all Android Studio projects started failing Gradle sync/build/clean with: > Could not create plugin of type 'AppPlugin'. The stacktrace looks like: * Exception is: org.gradle.api.GradleScriptException: A problem occurred evaluating project ':Project'. at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:54) at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:177) at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:38) at