Hello team,
Yesterday JCenter was down for some time, due to which I was unable to start the OFBiz server (because the build was failed). Status of JCenter can be found at [1]. This is a severe issue because it may be possible during any production deployment, JCenter is down. Do we have any solution for the issue? Please let me know if I am missing anything. [1] https://status.bintray.com/ Here is stacktrace of build failure. ====================================== *> Task :compileTestJava* FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':compileTestJava'. > Could not resolve all files for configuration ':testCompileClasspath'. > Could not resolve org.mockito:mockito-core:2.+. Required by: project : > Failed to list versions for org.mockito:mockito-core. > Unable to load Maven meta-data from https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> . > Could not HEAD ' https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> '. > jcenter.bintray.com > Failed to list versions for org.mockito:mockito-core. > Unable to load Maven meta-data from https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> . > Could not HEAD ' https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> '. > jcenter.bintray.com * Try: Run with *--stacktrace* option to get the stack trace. Run with *--info* or *--debug* option to get more log output. Run with *--scan* to get full insights. * Get more help at *https://help.gradle.org <https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q>* *BUILD FAILED* in 1m 14s ====================================== - Best Regards, Swapnil M Mane, www.hotwax.co |
Adding one or more additional repositories in build.gradle (at the moment
we have only jcenter()) can be a solution. Jacopo On Fri, Mar 22, 2019 at 8:41 AM Swapnil M Mane < [hidden email]> wrote: > Hello team, > > Yesterday JCenter was down for some time, due to which I was unable to > start the OFBiz server (because the build was failed). > Status of JCenter can be found at [1]. > > This is a severe issue because it may be possible during any production > deployment, JCenter is down. Do we have any solution for the issue? > Please let me know if I am missing anything. > > [1] https://status.bintray.com/ > > Here is stacktrace of build failure. > ====================================== > *> Task :compileTestJava* FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':compileTestJava'. > > Could not resolve all files for configuration ':testCompileClasspath'. > > Could not resolve org.mockito:mockito-core:2.+. > Required by: > project : > > Failed to list versions for org.mockito:mockito-core. > > Unable to load Maven meta-data from > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > . > > Could not HEAD ' > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > '. > > jcenter.bintray.com > > Failed to list versions for org.mockito:mockito-core. > > Unable to load Maven meta-data from > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > . > > Could not HEAD ' > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > '. > > jcenter.bintray.com > > * Try: > Run with *--stacktrace* option to get the stack trace. Run with *--info* or > *--debug* option to get more log output. Run with *--scan* to get full > insights. > > * Get more help at *https://help.gradle.org > < > https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q > >* > > *BUILD FAILED* in 1m 14s > ====================================== > > - Best Regards, > Swapnil M Mane, > www.hotwax.co > |
In reply to this post by Swapnil Mane
Whatever repository you choose, there is always the risk of going down.
To mitigate this risk, you can (after deploying the system) use the - -offline flag when running gradle. Alternatively you can simply run the java - jar command. On Fri, Mar 22, 2019, 10:41 AM Swapnil M Mane < [hidden email]> wrote: > Hello team, > > Yesterday JCenter was down for some time, due to which I was unable to > start the OFBiz server (because the build was failed). > Status of JCenter can be found at [1]. > > This is a severe issue because it may be possible during any production > deployment, JCenter is down. Do we have any solution for the issue? > Please let me know if I am missing anything. > > [1] https://status.bintray.com/ > > Here is stacktrace of build failure. > ====================================== > *> Task :compileTestJava* FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':compileTestJava'. > > Could not resolve all files for configuration ':testCompileClasspath'. > > Could not resolve org.mockito:mockito-core:2.+. > Required by: > project : > > Failed to list versions for org.mockito:mockito-core. > > Unable to load Maven meta-data from > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > . > > Could not HEAD ' > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > '. > > jcenter.bintray.com > > Failed to list versions for org.mockito:mockito-core. > > Unable to load Maven meta-data from > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > . > > Could not HEAD ' > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > < > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > '. > > jcenter.bintray.com > > * Try: > Run with *--stacktrace* option to get the stack trace. Run with *--info* or > *--debug* option to get more log output. Run with *--scan* to get full > insights. > > * Get more help at *https://help.gradle.org > < > https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q > >* > > *BUILD FAILED* in 1m 14s > ====================================== > > - Best Regards, > Swapnil M Mane, > www.hotwax.co > |
In reply to this post by Swapnil Mane
Hi,
I think the Jacopo's suggest will be a good improvement. The last years I told with a Herve Boutemy (hboutemy, maven-pmc) that explain me why it's better to use maven central :) . But historically we resolved all jar dependencies on jcenter and personally I didn't check yet if all jar resolution done with jcenter are also present on maven central. Nicolas On 22/03/2019 08:40, Swapnil M Mane wrote: > Hello team, > > Yesterday JCenter was down for some time, due to which I was unable to > start the OFBiz server (because the build was failed). > Status of JCenter can be found at [1]. > > This is a severe issue because it may be possible during any production > deployment, JCenter is down. Do we have any solution for the issue? > Please let me know if I am missing anything. > > [1] https://status.bintray.com/ > > Here is stacktrace of build failure. > ====================================== > *> Task :compileTestJava* FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':compileTestJava'. >> Could not resolve all files for configuration ':testCompileClasspath'. > > Could not resolve org.mockito:mockito-core:2.+. > Required by: > project : > > Failed to list versions for org.mockito:mockito-core. > > Unable to load Maven meta-data from > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> > . > > Could not HEAD ' > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> > '. > > jcenter.bintray.com > > Failed to list versions for org.mockito:mockito-core. > > Unable to load Maven meta-data from > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> > . > > Could not HEAD ' > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> > '. > > jcenter.bintray.com > > * Try: > Run with *--stacktrace* option to get the stack trace. Run with *--info* or > *--debug* option to get more log output. Run with *--scan* to get full > insights. > > * Get more help at *https://help.gradle.org > <https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q>* > > *BUILD FAILED* in 1m 14s > ====================================== > > - Best Regards, > Swapnil M Mane, > www.hotwax.co > |
In reply to this post by taher
Just to clarify, I was suggesting that we could add more repositories, not
replace Jcenter with another one: the redundancy would mitigate the risk of unavailability. Jacopo On Fri, Mar 22, 2019 at 6:07 PM Taher Alkhateeb <[hidden email]> wrote: > Whatever repository you choose, there is always the risk of going down. > > To mitigate this risk, you can (after deploying the system) use the - > -offline flag when running gradle. Alternatively you can simply run the > java - jar command. > > On Fri, Mar 22, 2019, 10:41 AM Swapnil M Mane < > [hidden email]> wrote: > > > Hello team, > > > > Yesterday JCenter was down for some time, due to which I was unable to > > start the OFBiz server (because the build was failed). > > Status of JCenter can be found at [1]. > > > > This is a severe issue because it may be possible during any production > > deployment, JCenter is down. Do we have any solution for the issue? > > Please let me know if I am missing anything. > > > > [1] https://status.bintray.com/ > > > > Here is stacktrace of build failure. > > ====================================== > > *> Task :compileTestJava* FAILED > > > > FAILURE: Build failed with an exception. > > > > * What went wrong: > > Execution failed for task ':compileTestJava'. > > > Could not resolve all files for configuration ':testCompileClasspath'. > > > Could not resolve org.mockito:mockito-core:2.+. > > Required by: > > project : > > > Failed to list versions for org.mockito:mockito-core. > > > Unable to load Maven meta-data from > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > < > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > . > > > Could not HEAD ' > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > < > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > '. > > > jcenter.bintray.com > > > Failed to list versions for org.mockito:mockito-core. > > > Unable to load Maven meta-data from > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > < > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > . > > > Could not HEAD ' > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > < > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > '. > > > jcenter.bintray.com > > > > * Try: > > Run with *--stacktrace* option to get the stack trace. Run with *--info* > or > > *--debug* option to get more log output. Run with *--scan* to get full > > insights. > > > > * Get more help at *https://help.gradle.org > > < > > > https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q > > >* > > > > *BUILD FAILED* in 1m 14s > > ====================================== > > > > - Best Regards, > > Swapnil M Mane, > > www.hotwax.co > > > |
Ahh I get it now.
In that case the challenge might be making sure the naming and transitive dependencies are equivalent on both sides. Maybe another solution is to create two files, one for maven and the other for jcenter each with its own unique set of dependencies that can be tested and ensured correct behavior. This way differences in names or transitive dependencies are not an issue. On Sat, Mar 23, 2019, 5:09 PM Jacopo Cappellato < [hidden email]> wrote: > Just to clarify, I was suggesting that we could add more repositories, not > replace Jcenter with another one: the redundancy would mitigate the risk of > unavailability. > > Jacopo > > On Fri, Mar 22, 2019 at 6:07 PM Taher Alkhateeb < > [hidden email]> > wrote: > > > Whatever repository you choose, there is always the risk of going down. > > > > To mitigate this risk, you can (after deploying the system) use the - > > -offline flag when running gradle. Alternatively you can simply run the > > java - jar command. > > > > On Fri, Mar 22, 2019, 10:41 AM Swapnil M Mane < > > [hidden email]> wrote: > > > > > Hello team, > > > > > > Yesterday JCenter was down for some time, due to which I was unable to > > > start the OFBiz server (because the build was failed). > > > Status of JCenter can be found at [1]. > > > > > > This is a severe issue because it may be possible during any production > > > deployment, JCenter is down. Do we have any solution for the issue? > > > Please let me know if I am missing anything. > > > > > > [1] https://status.bintray.com/ > > > > > > Here is stacktrace of build failure. > > > ====================================== > > > *> Task :compileTestJava* FAILED > > > > > > FAILURE: Build failed with an exception. > > > > > > * What went wrong: > > > Execution failed for task ':compileTestJava'. > > > > Could not resolve all files for configuration > ':testCompileClasspath'. > > > > Could not resolve org.mockito:mockito-core:2.+. > > > Required by: > > > project : > > > > Failed to list versions for org.mockito:mockito-core. > > > > Unable to load Maven meta-data from > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > < > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > . > > > > Could not HEAD ' > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > < > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > '. > > > > jcenter.bintray.com > > > > Failed to list versions for org.mockito:mockito-core. > > > > Unable to load Maven meta-data from > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > < > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > . > > > > Could not HEAD ' > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > < > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > '. > > > > jcenter.bintray.com > > > > > > * Try: > > > Run with *--stacktrace* option to get the stack trace. Run with > *--info* > > or > > > *--debug* option to get more log output. Run with *--scan* to get full > > > insights. > > > > > > * Get more help at *https://help.gradle.org > > > < > > > > > > https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q > > > >* > > > > > > *BUILD FAILED* in 1m 14s > > > ====================================== > > > > > > - Best Regards, > > > Swapnil M Mane, > > > www.hotwax.co > > > > > > |
Thank you so much Jacopo, Taher, Nicolas for your kind inputs.
+1 for adding more repositories (maven seems good to me). - Best Regards, Swapnil M Mane, www.hotwax.co On Sat, Mar 23, 2019 at 9:34 PM Taher Alkhateeb <[hidden email]> wrote: > Ahh I get it now. > > In that case the challenge might be making sure the naming and transitive > dependencies are equivalent on both sides. > > Maybe another solution is to create two files, one for maven and the other > for jcenter each with its own unique set of dependencies that can be tested > and ensured correct behavior. This way differences in names or transitive > dependencies are not an issue. > > On Sat, Mar 23, 2019, 5:09 PM Jacopo Cappellato < > [hidden email]> wrote: > > > Just to clarify, I was suggesting that we could add more repositories, > not > > replace Jcenter with another one: the redundancy would mitigate the risk > of > > unavailability. > > > > Jacopo > > > > On Fri, Mar 22, 2019 at 6:07 PM Taher Alkhateeb < > > [hidden email]> > > wrote: > > > > > Whatever repository you choose, there is always the risk of going down. > > > > > > To mitigate this risk, you can (after deploying the system) use the - > > > -offline flag when running gradle. Alternatively you can simply run the > > > java - jar command. > > > > > > On Fri, Mar 22, 2019, 10:41 AM Swapnil M Mane < > > > [hidden email]> wrote: > > > > > > > Hello team, > > > > > > > > Yesterday JCenter was down for some time, due to which I was unable > to > > > > start the OFBiz server (because the build was failed). > > > > Status of JCenter can be found at [1]. > > > > > > > > This is a severe issue because it may be possible during any > production > > > > deployment, JCenter is down. Do we have any solution for the issue? > > > > Please let me know if I am missing anything. > > > > > > > > [1] https://status.bintray.com/ > > > > > > > > Here is stacktrace of build failure. > > > > ====================================== > > > > *> Task :compileTestJava* FAILED > > > > > > > > FAILURE: Build failed with an exception. > > > > > > > > * What went wrong: > > > > Execution failed for task ':compileTestJava'. > > > > > Could not resolve all files for configuration > > ':testCompileClasspath'. > > > > > Could not resolve org.mockito:mockito-core:2.+. > > > > Required by: > > > > project : > > > > > Failed to list versions for org.mockito:mockito-core. > > > > > Unable to load Maven meta-data from > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > . > > > > > Could not HEAD ' > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > '. > > > > > jcenter.bintray.com > > > > > Failed to list versions for org.mockito:mockito-core. > > > > > Unable to load Maven meta-data from > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > . > > > > > Could not HEAD ' > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > '. > > > > > jcenter.bintray.com > > > > > > > > * Try: > > > > Run with *--stacktrace* option to get the stack trace. Run with > > *--info* > > > or > > > > *--debug* option to get more log output. Run with *--scan* to get > full > > > > insights. > > > > > > > > * Get more help at *https://help.gradle.org > > > > < > > > > > > > > > > https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q > > > > >* > > > > > > > > *BUILD FAILED* in 1m 14s > > > > ====================================== > > > > > > > > - Best Regards, > > > > Swapnil M Mane, > > > > www.hotwax.co > > > > > > > > > > |
Administrator
|
In reply to this post by Nicolas Malin-2
Le 22/03/2019 à 21:44, Nicolas Malin a écrit :
> The last years I told with a Herve Boutemy (hboutemy, maven-pmc) that explain me why it's better to use maven central Sorry to resurrect this, but it would have been wise, isn't? More to come about Bintray... Jacques |
Administrator
|
I created https://issues.apache.org/jira/browse/OFBIZ-12192 for that
Le 03/03/2021 à 08:10, Jacques Le Roux a écrit : > Le 22/03/2019 à 21:44, Nicolas Malin a écrit : >> The last years I told with a Herve Boutemy (hboutemy, maven-pmc) that explain me why it's better to use maven central > > Sorry to resurrect this, but it would have been wise, isn't? > > More to come about Bintray... > > Jacques > |
Free forum by Nabble | Edit this page |