Try with: ant -q -Dbinary.server=https://jcenter.bintray.com/

It seems maven central (our last resort to turn to when a binary is missing) does not have the gradle tooling files. As I had it in my local cache it got resolved from there.

Probably we shall switch to jcenter as default to turn to.

On 12/29/18 8:19 PM, John McDonnell wrote:
Switched to your gradle-support branch but wasn't able to build:

BUILD FAILED
/Users/john/codebase/incubator-netbeans/nbbuild/build.xml:125: Could not
download
70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar from
http://netbeans.osuosl.org/binaries/: java.io.IOException: Could not
download
70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar to
/Users/john/.hgexternalcache/70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar:
java.io.IOException: Skipping download from
http://central.maven.org/maven2/org/gradle/gradle-tooling-api/4.10.2/gradle-tooling-api-4.10.2.jar
due to response code 404
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:249)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.fillInFile(DownloadBinaries.java:190)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.execute(DownloadBinaries.java:154)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388)
at org.apache.tools.ant.Project.executeTarget(Project.java:1361)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:834)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
Caused by: java.io.IOException: Skipping download from
http://central.maven.org/maven2/org/gradle/gradle-tooling-api/4.10.2/gradle-tooling-api-4.10.2.jar
due to response code 404
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.downloadFromServer(DownloadBinaries.java:275)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.mavenFile(DownloadBinaries.java:177)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.lambda$execute$0(DownloadBinaries.java:154)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:226)
... 18 more

Is there a step I'm missing?


John


On Sun, 30 Dec 2018 at 02:46, Scott Palmer <[email protected]> wrote:

+1  Great to see more support for Gradle.

How does this plugin compare to the existing Gradle plugin?  Would it make
sense to merge your efforts?

I would really like to see support for Gradle-based native C/C++ projects.

Scott


On Dec 29, 2018, at 6:02 PM, John McDonnell <[email protected]>
wrote:
Very cool, it'll be nice to have Gradle and Maven in NetBeans moving
forward.

 From what I see, new frameworks seem to be coming out supporting Gradle,
so
being able to have Gradle as a first class citizen along with Maven that
would be really great.


Regards

John

On Sat, 29 Dec 2018 at 19:57, Laszlo Kishalmi <[email protected]

wrote:

Dear all,

I would like to donate my Gradle works to Apache NetBeans.

Right now the code is here:
https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support

I just recently rebased it on master, so there is no conflicts. If I'd
create a PR from it that would mean 317 new files and ~35k line of code.

The current state of the plugin:

  * It Opens Gradle Projects resource efficiently
  * It is based on the ideas found in our Maven Plugin
  * It supports JavaSE and Groovy development
  * Unit Testing
  * Code Coverage
  * JPA projects
  * Spring (the little support we have for that)
  * Navigator for project task
  * Custom Task execution
  * Output processing
  * Debugging (even single methods)
  * Creating new projects

The shady side:

  * The Gradle <-> NetBeans project discovery and communication.
    Based on simple property serialization. Ugly Groovy code, well the
    deserialization Java code isn't that nice as well
  * Limited number of unittest
  * Being a sole developer there could be glitches here and there as of
    lack of wider testing.
  * Gradle is required to build the NetBeans <-> Gradle tooling
    This adds a binary

groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
    to the source distribution package, though this file is not
    distributed. So Apace might agree with that.

Introduced External Dependencies:

  * Gradle Tooling API (Apache Licensed)
      o slf4j (Apache Licensed)
  * JaCoCo Core Library (EPL 1.0)
    The whole JaCoCo project uses other libraries distributed under
    different licenses, I need to make sure that the core is EPL 1.0 only

Areas to Improve:

  * There is no support for Ergonomy
  * Module versions might be incorrectly specified, I did the best I
could
  * Add Groovy project support (could be trivial)
  * Improve Gradle <-> JDK incompatibility check.
  * Profiling
  * Compile on Save (that's an icy territory)
  * Improve project Settings
  * Whatever you think...

Future Works:

  * I also have a JavaEE support module started, I can donate somewhat
    later to the enterprise cluster.




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to