Commit Graph

71 Commits

Author SHA1 Message Date
Florian Reimair
68d813fc0c Refactored TorNetworkNode 2018-11-17 18:02:49 +01:00
Manfred Karrer
136c268dbb
Merge pull request #1928 from freimair/tor8.0.3
Use tor binaries from TorBrowser 8.0.3
2018-11-16 21:07:14 -05:00
Florian Reimair
21a56cc127 worked around jitpack issue 2018-11-16 13:31:37 +01:00
Florian Reimair
3e25ee2cdd Use tor binaries from TorBrowser 8.0.3 2018-11-16 12:28:34 +01:00
Chris Beams
44c326729b
Merge pull request #1901 from devinbileck/update-gradle-witness.jar
Update gradle-witness.jar
2018-11-15 11:41:25 +01:00
Devin Bileck
286dd51b13
Update gradle-witness.jar
Built from commit
44b0391006

md5 hash ae4796f320ef3200515183fa9d3f4759
2018-11-15 11:40:46 +01:00
Florian Reimair
9e88e6eed1 Fixed netlayer and tor binary dependency issues 2018-11-13 19:51:11 +01:00
Florian Reimair
73fc35413b bumped netlayer to 0.4.7 2018-11-07 17:13:51 +01:00
Chris Beams
3c54be2d4f
Pull up remaining desktop config to root
And also relocate gradle-witness jar and config (back) to root-level
gradle/witness dir.
2018-11-04 17:37:32 +01:00
Chris Beams
c257590424
Upgrade to Gradle 4.10.2 2018-11-04 09:54:56 +01:00
Chi Nul
c3dc3c5086
Update gradle to 4.9 2018-09-05 11:19:58 +02:00
Chi Nul
9014925d1c
Move witness gradle plugin to desktop 2018-09-05 10:27:23 +02:00
Chris Beams
27cc933c4e
Verify dependency checksums with gradle-witness plugin
This performs the same function that the maven-enforcer-plugin did in
the pom removed by the previous commit, and also includes a more
comprehensive / up-to-date set of dependencies.

Note that the gradle-witness jar checked in here is one built from the
pull request in signalapp/gradle-witness#26.
2018-03-21 06:15:00 +01:00
Chris Beams
6e87bee784
Add Gradle build 2018-03-21 06:14:48 +01:00
Manfred Karrer
6b4f528f47 UpdateFX with maven build (tested only on mac) 2015-02-27 23:47:23 +01:00
Chris Beams
5f53fea190
Remove use of Gradle JavaFX plugin
As documented at [1], version 8.1.1 of the Gradle JavaFX plugin has
disappeared from bintray. This causes Travis CI build failures. Version
8.1.0 is still in place [2], but downgrading to it causes further build
errors.

This commit removes use of the plugin entirely in order to fix the CI
problem immediately. In the meantime, the Bitsquare UI must be launched
directly from within IDEA.

Resolves #221
See #66

[1]: https://bitbucket.org/shemnon/javafx-gradle/issue/46/received-status-code-401-from-server
[2]: http://dl.bintray.com/content/shemnon/javafx-gradle/org/bitbucket/shemnon/javafxplugin/gradle-javafx-plugin/
2014-10-13 11:13:43 +02:00
Chris Beams
e1889b0697
Update JavaFX Gradle plugin repository config
This commit makes the following improvements upon the stock
javafx.gradle file introduced in the previous commit:

 - Swap Maven Central for JCenter
 - Remove mavenLocal entirely
 - Update naming for clarity

See #66
2014-10-03 18:35:18 +02:00
Chris Beams
d16c2740b6
Generate native installers with Gradle JavaFX plugin
The plugin's jfx* tasks tie into the normal Gradle build lifecycle, such
that `gradle build` will now generate executables and installers
according to the OS on which the build is being run. These files are
output to the `build/distributions` directory.

Installers work as expected OS X and Linux at this point.

Windows installers do build, but a very particular configuration is
necessary on the Windows machine doing the building (this configuration
is to be documented in #109). However, even when the configuration is in
place and the MSI installer is successfully built, there is still a
fatal error at installer execution time relating to a missing
msvp100.dll file. See details at
https://bitbucket.org/shemnon/javafx-gradle/issue/43. An issue has been
created to track this from the Bitsquare side as well--see #108.

The changes made in this commit are based on on the samples at
http://bitbucket.org/shemnon/javafx-gradle and the article at
http://jaxenter.com/tutorial-a-guide-to-the-gradle-javafx-plugin-46270.html

The gradle/javafx.gradle file is copied directly from the sources in the
bitbucket repository above, as is apparently the convention (not sure
why this isn't part of the plugin itself, but that's a question to be
addressed later).

Resolves #66, #100
See #108, #109
2014-10-03 18:32:03 +02:00
Manfred Karrer
b9b7d4b3e0 Improve usability, fix bugs 2014-10-02 14:30:05 +02:00
Chris Beams
c5028c178c
Finish upgrading Gradle wrapper from 2.0 => 2.1
Commit 4d4787d updated the Gradle wrapper config from 2.0 => 2.1, but
did not actually update the wrapper properties file (forgot to run
`gradle wrapper`). This commit finishes what was started there.
2014-09-29 14:23:08 +02:00
Chris Beams
4cfc949446
Generate Gradle wrapper artifacts
See http://www.gradle.org/docs/current/userguide/gradle_wrapper.html
2014-08-28 13:56:04 +02:00