Hi Geoff, all,
For using vagrant, Iuliana said:
"Successfully started unpacked and started
apache-brooklyn-1.0.0-rc3-vagrant.zip. All nodes were correctly created."
Geoff, did your steps match the vagrant instructions at
http://brooklyn.apache.org/v/latest/start/running.html?
*Iuliana*
My current appraisal of the RC is:
verify_brooklyn_rc.sh looks ok, tail of output (tidied):
[✓] Build from sources successful
~/brooklyn_releases/apache-brooklyn-1.0.0-rc3 ~/brooklyn_releases
---
Additional steps requiring manual intervention (execute in
kemitix commented on issue #44: Don't install openjdk
URL: https://github.com/apache/brooklyn/pull/44#issuecomment-589262910
@geomacy I think we want to be going forward, and using the updated maven
3.6.3 image, which this PR allows. The PR to roll-back to maven 3.5.4 by
@tbouron was added
geomacy edited a comment on issue #44: Don't install openjdk
URL: https://github.com/apache/brooklyn/pull/44#issuecomment-589242354
> Hi Geoff, I believe this is an alternative solution to the problem
@tbouron was fixing. Applying both would result in openjdk not being available.
Paul
>
geomacy commented on issue #44: Don't install openjdk
URL: https://github.com/apache/brooklyn/pull/44#issuecomment-589242354
> Hi Geoff, I believe this is an alternative solution to the problem
@tbouron was fixing. Applying both would result in openjdk not being available.
Paul
> […](#)
Note that's different from the situation with the Docker image above. If we
are distributing source with a Dockerfile, I'd really expect that to "Just
Work". I'm tending towards thinking this will mean a -1 from me - open to
debate the matter though, what do you all think?
Geoff
On Thu, 20 Feb 2
Hi Paul,
>Given Debian Buster, the current version doesn't provide a Java 8 JRE, the
> Debian package of Apache Brooklyn won't work on that version.
> Getting this to work would require the user to install a system-wide JRE 8
> on their machine.
That's perfectly OK, we require a Java 8 runtime b
+1 (binding)
I don't think Paul's reported issue above is a blocker - but I do think we
should address this soon.
I've run some tests on mac using tar.gz and deployed some apps to aws and
gce. All worked as expected so I'm happy for the release to go ahead.
Duncan
On Thu, 20 Feb 2020 at 16:03,
Hi,
I think I've pinned down my errors to my machine having openjdk-11-jre
installed.
Given Debian Buster, the current version doesn't provide a Java 8 JRE, the
Debian package of Apache Brooklyn won't work on that version.
Getting this to work would require the user to install a system-wide JRE
Hi,
Trying to test the RC3 deb package on Debian 10 (Buster).
I'm not able to start the 'brooklyn' service properly when installed from
the Debian package.
sudo dpkg -i apache-brooklyn-1.0.0-rc3.deb
sudo service brooklyn start
Apache Brooklyn never completes startup, but doesn't die either. Por
+1 from me
Tested apache-brooklyn-1.0.0-rc3-bin.tar.gz on macOs running Catalina 10.15.3.
Successfully deployed all blueprints in the quick launch on AWS eu-west-1.
Successfully started unpacked and started
apache-brooklyn-1.0.0-rc3-vagrant.zip. All nodes were correctly created.
Iuliana Cosmina
+1 from me
Tested apache-brooklyn-1.0.0-rc3-bin.zip on macOS running Mohave 10.14.6
Successfully deployed sample 1 server template successfully on AWS us-east-1
Successfully deployed sample 4 resilient bash web cluster template on AWS
us-east-1
John Campbell
Software Engineer
Cloudsoft | Brin
kemitix commented on issue #44: Don't install openjdk
URL: https://github.com/apache/brooklyn/pull/44#issuecomment-588926688
Hi Geoff,
I believe this is an alternative solution to the problem @tbouron was
fixing.
Applying both would result in openjdk not being available.
geomacy commented on a change in pull request #44: Don't install openjdk
URL: https://github.com/apache/brooklyn/pull/44#discussion_r381904448
##
File path: Dockerfile
##
@@ -19,9 +19,6 @@
# and PhantomJS
FROM maven:3.6.3-jdk-8
-# Install the non-headless JRE as some te
14 matches
Mail list logo
