duncangrant merged pull request #311:
URL: https://github.com/apache/brooklyn-docs/pull/311
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above t
asfgit merged pull request #1126:
URL: https://github.com/apache/brooklyn-server/pull/1126
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
ahgittin commented on a change in pull request #1126:
URL: https://github.com/apache/brooklyn-server/pull/1126#discussion_r529842552
##
File path:
karaf/init/src/main/java/org/apache/brooklyn/launcher/osgi/OsgiLauncherImpl.java
##
@@ -108,21 +136,178 @@ public void initOsgi()
duncangrant commented on a change in pull request #1126:
URL: https://github.com/apache/brooklyn-server/pull/1126#discussion_r529707791
##
File path:
karaf/init/src/main/java/org/apache/brooklyn/launcher/osgi/OsgiLauncherImpl.java
##
@@ -108,21 +136,178 @@ public void initOsgi
Thanks very much JB!
On Tue, 24 Nov 2020, 17:15 Jean-Baptiste Onofre, wrote:
> Hi guys,
>
> First of all, my apologizes: I have been quiet for way too long on the
> mailing list.
>
> I had the chance to chat with Alex today and honestly I’m very impressed
> by Brooklyn. I’m really happy to see h
Hi guys,
First of all, my apologizes: I have been quiet for way too long on the mailing
list.
I had the chance to chat with Alex today and honestly I’m very impressed by
Brooklyn. I’m really happy to see how you leverage Apache Karaf.
I’m working on some issues you encountered (and I’m also pr
duncangrant commented on a change in pull request #1126:
URL: https://github.com/apache/brooklyn-server/pull/1126#discussion_r529699668
##
File path:
karaf/init/src/main/java/org/apache/brooklyn/launcher/osgi/OsgiLauncherImpl.java
##
@@ -108,21 +136,178 @@ public void initOsgi
duncangrant commented on a change in pull request #1126:
URL: https://github.com/apache/brooklyn-server/pull/1126#discussion_r529707791
##
File path:
karaf/init/src/main/java/org/apache/brooklyn/launcher/osgi/OsgiLauncherImpl.java
##
@@ -108,21 +136,178 @@ public void initOsgi
duncangrant commented on a change in pull request #1126:
URL: https://github.com/apache/brooklyn-server/pull/1126#discussion_r529699668
##
File path:
karaf/init/src/main/java/org/apache/brooklyn/launcher/osgi/OsgiLauncherImpl.java
##
@@ -108,21 +136,178 @@ public void initOsgi
ahgittin commented on pull request #311:
URL: https://github.com/apache/brooklyn-docs/pull/311#issuecomment-733061705
documentation for https://github.com/apache/brooklyn-server/pull/1126
This is an automated message from the
ahgittin opened a new pull request #311:
URL: https://github.com/apache/brooklyn-docs/pull/311
until required startup services are available
This is an automated message from the Apache Git Service.
To respond to the message,
ahgittin opened a new pull request #1126:
URL: https://github.com/apache/brooklyn-server/pull/1126
More details will be in a docs PR which will come shortly and be advertised
here
This is an automated message from the Apache
Cheers Geoff -- helpful input.
Absolutely I think (a) should be _supported_ -- but I don't think it
should be preferred.
Blueprint authors who just write a simple yaml/BOM file shouldn't be
required to make/maintain an OSGI-INF/MANIFEST.MF. And nor do we want
to stipulate that bundles tha
Hi Alex,
I'd actually say (a) is the way to do it, using the OSGI service
dependency mechanism in some way (not *quite* sure how that is done
these days!). That would be the more "OSGI native" style of doing it,
would it not? Start levels wouldn't be what we want [1] and making all
catalog init bl
14 matches
Mail list logo