Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/674
Looks like this has been addressed as well so closing.
---
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/674
---
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/673
---
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/673
Thanks @andreaturli, @geomacy, closing.
---
[
https://issues.apache.org/jira/browse/BROOKLYN-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244537#comment-16244537
]
Svetoslav Neykov commented on BROOKLYN-548:
---
[~tbouron] I believe that
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/860
Seems this fixes
[BROOKLYN-525](https://issues.apache.org/jira/browse/BROOKLYN-525) as well.
Worth checking by enabling the corresponding tests as done in
https://github.com/apache
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/794
:+1:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-server/pull/794
Test Framework TestNG runner
Useful for running the test framework tests as live tests on the project.
From the test included in the PR, example usage
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/392
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/392
Closing in favour of https://github.com/apache/brooklyn-server/pull/786.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/641
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/641
Fix failed to address the problem. Closing. Created an issue to track the
bug.
https://issues.apache.org/jira/browse/BROOKLYN-525
---
If your project is set up for it, you can reply to
Svetoslav Neykov created BROOKLYN-525:
-
Summary: Sensor change events fired out of order
Key: BROOKLYN-525
URL: https://issues.apache.org/jira/browse/BROOKLYN-525
Project: Brooklyn
Issue
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/786
Thanks @geomacy, fixed the typo.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/786
Added additional template variables (substitutions) as a second argument.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/786
Added more test coverage.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-server/pull/786
Freemarker DSL
Provides `$brooklyn:template(...)` evaluated against the context entity as
a freemarker template.
The main advantage of the new DSL is that it's now possible to do s
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/782
That's used for machine names which already include a bunch of other unique
tags, including a jclouds generated random number. Of course we could use a
similar strategy, it's just
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/782
Just a heads up that some downstream apps/entities embed the appId in the
name of cloud resources and having an ID with a length of 1022 will lead to
failures when trying to create them
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/781#discussion_r130041426
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/templates/customize/TemplateOptionsOption.java
---
@@ -39,8 +45,17
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/781#discussion_r129914806
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/templates/customize/TemplateOptionsOption.java
---
@@ -39,8 +45,17
;>> `org.apache.brooklyn.deploymentId` approach.
>>>
>>> For "/application's ID is not meant to be user-supplied/", that has
>>> historically been the case but why should we stick to that? What matters is
>>> that the appId is definitely u
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/767
+1, merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-dist/pull/101
If we are changing logging providers, perhaps it's the right time to look
at using logback, as was the initial plan?
Any preferences here for log4j2 vs logback?
---
If your proje
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/771
:+1: glad to see so few changes needed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/770
Tests are passing. Merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/769
Tests pass, merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/769
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/767
Looks a lot like `BrooklynJavascriptGuiLauncher`, but otherwise LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-dist/pull/100
LGTM, merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/765
:+1: somehow I've been viewing only the first commit. All good!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/765
Is it worth adding it to `/ha/states` as well, along `nodeId`? LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/745
@Graeme-Miller Brooklyn has upgraded to jclouds 2.0.2, which opens the door
to supporting default region as well.
---
If your project is set up for it, you can reply to this email and have
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-server/pull/764
Fixes tested response from /server/user
Fixes the integration test `ServerResourceIntegrationTest.testGetUser()`.
You can merge this pull request into a Git repository by running
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/753
Build succeeds after rebasing on master with the
`brooklyn-locations-container` pom.xml fix applied.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/753
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/754#discussion_r126417847
--- Diff:
rest/rest-resources/src/main/java/org/apache/brooklyn/rest/resources/PolicyConfigResource.java
---
@@ -66,7 +66,7
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-dist/pull/98
Thanks @geomacy, merging.
Lot's more entries need removing from here, can be addressed in another PR.
---
If your project is set up for it, you can reply to this email and have
Hi Duncan,
I've solved this problem before by adding a caller generated config key on the
app (now it's also possible to tag them), then iterating over the deployed
apps, looking for the key.
An alternative which I'd like to mention is creating an async deploy operation
which immediately retur
Hi Valentin,
Parameters set on the specs are later converted to config keys on the entity
which are then used for type inference and applying restrictions (can mark
parameters as required). That's why I think it would be useful to keep the
parameters passed in from yaml.
We had a similar probl
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/753
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/754
Suggest we keep the changes for `PolicyConfigApi.get(...)`, making it work
analogously to `EntityConfigApi.get(...)`. The value there can be any object,
so it needs to be encoded as JSON
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/745
Thanks @Graeme-Miller, merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/745
LGTM with the "waiting to complete" changes.
@Graeme-Miller have you retried your test, has the failure rate improved?
If no failure this is good to merge. Otherwise we need t
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-server/pull/753
[WIP] Update jclouds to 2.0.2-rc1
`azurecompute-arm` has changed considerably since `2.0.1`. `jclouds-labs`
providers usually backport all master changes to iterate quickly, free to break
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/752
Closing because will not consistently set the property. When the location
doesn't have a region set, but one is passed through `flags` (for example in
`provisioning.properties`) we wil
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/752
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-server/pull/752
Cache the default region in location config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/neykov/brooklyn-server cache-default-region
[
https://issues.apache.org/jira/browse/BROOKLYN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071992#comment-16071992
]
Svetoslav Neykov commented on BROOKLYN-524:
---
Unconfirmed workaround - pr
Svetoslav Neykov created BROOKLYN-524:
-
Summary: Windows paths treated as `bundle:resource` pairs
resulting in file not found errors
Key: BROOKLYN-524
URL: https://issues.apache.org/jira/browse/BROOKLYN-524
Svetoslav Neykov created BROOKLYN-523:
-
Summary: Unhelpful warn message "Configuration being made to
SshMachineLocation"
Key: BROOKLYN-523
URL: https://issues.apache.org/jira/browse/BR
Svetoslav Neykov created BROOKLYN-521:
-
Summary: Unhelpful message "Attempted release of unknown machine"
Key: BROOKLYN-521
URL: https://issues.apache.org/jira/browse/BROOKLYN-521
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/748
@alx I think the fix makes sense.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/748
Sounds reasonable (on first read :) ). Still seems like a hacky workflow
though. Separating the metadata and the content just so it's friendly to ad-hoc
editing is not encouraging goo
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/731
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/748
Support for the [`type:
url`](https://github.com/apache/incubator-brooklyn/pull/71) was added around
the same time we added support for [yaml catalog
items](https://github.com/apache
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/745
Fine by me to merge the PR as it already improves on the existing
functionality. Can you create another PR which targets post 2.0.1 jclouds,
handling the default region case and mark it `WIP
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/740
> for other things yes it will be surprising but someone making an OSGi
bundle relying on that converter's obscure behaviour is asking for trouble
That's everyone usin
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/737
@geomacy left my comments in
https://github.com/apache/brooklyn-server/pull/740 which includes this PR.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/745#discussion_r124042939
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/networking/creator/DefaultAzureArmNetworkCreator.java
---
@@ -64,57
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/745
* re azure jclouds 2.0.1 not having enough functionality - the changes here
(and in previous PR) will create the default network, but will not assign it to
the nodes because `ipOptions
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/745#discussion_r124042243
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/networking/creator/DefaultAzureArmNetworkCreator.java
---
@@ -64,57
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/743
LGTM
retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/740
Couldn't find where we sanitise the catalog items ID to be used for
persistence file names. If changing the naming rules for the IDs then perhaps
changing the sanitising rules wou
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/740
LGTM, but a bit nervous about not relying on `DefaultMaven2OsgiConverter`
for the version conversion. The same version string will create a maven bundle
with one OSGi version and a catalog
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/742
LGTM, also see the comments I just added to
https://github.com/apache/brooklyn-server/pull/739
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/739
The most important from above comments is that `location` (which is region
in brooklyn speak) could not be set, using the jclouds' default. Would be
useful to have that improved.
An
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/739#discussion_r123533239
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/networking/creator/DefaultAzureArmNetworkCreator.java
---
@@ -0,0
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/739#discussion_r123531214
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/networking/creator/DefaultAzureArmNetworkCreator.java
---
@@ -0,0
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/739#discussion_r123530475
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/networking/creator/DefaultAzureArmNetworkCreator.java
---
@@ -0,0
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/739#discussion_r123529723
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/networking/creator/DefaultAzureArmNetworkCreator.java
---
@@ -0,0
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/739#discussion_r123528419
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/networking/creator/DefaultAzureArmNetworkCreator.java
---
@@ -0,0
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-dist/pull/97
Builds fine for me, merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-ui/pull/46
Builds fine for me, merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/741
Builds fine for me, merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/741
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Makes sense.
> On 22.06.2017 г., at 12:27, Alex Heneveld
> wrote:
>
>
> inline
>
> On 22/06/2017 10:10, Svetoslav Neykov wrote:
>> +1 to the proposal.
>>
>> One thing I have reservations about is having a recommended version syntax
>> with
+1 to the proposal.
One thing I have reservations about is having a recommended version syntax with
other formats still supported but deprecated.
As far as I understand the recommended syntax is there so we can guarantee a
uniqueness of the OSGi versions (when the source version is unique). Inst
[
https://issues.apache.org/jira/browse/BROOKLYN-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057560#comment-16057560
]
Svetoslav Neykov commented on BROOKLYN-519:
---
To restate the problem
[
https://issues.apache.org/jira/browse/BROOKLYN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-180.
---
Resolution: Fixed
The winrm4j project switched to a pure java implementation, based
[
https://issues.apache.org/jira/browse/BROOKLYN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055934#comment-16055934
]
Svetoslav Neykov edited comment on BROOKLYN-160 at 6/20/17 3:2
[
https://issues.apache.org/jira/browse/BROOKLYN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055934#comment-16055934
]
Svetoslav Neykov commented on BROOKLYN-160:
---
There's {{EmptyWindo
[
https://issues.apache.org/jira/browse/BROOKLYN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-160.
---
Resolution: Fixed
Fix Version/s: 0.9.0
> No-op entity for Windows
[
https://issues.apache.org/jira/browse/BROOKLYN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-94.
--
Resolution: Won't Fix
Available as an external add-on to Brooklyn at
[
https://issues.apache.org/jira/browse/BROOKLYN-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055926#comment-16055926
]
Svetoslav Neykov commented on BROOKLYN-139:
---
Sounds like this is alr
[
https://issues.apache.org/jira/browse/BROOKLYN-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-80.
--
Resolution: Fixed
Fix Version/s: 0.10.0
Swagger is now at 1.5.6
> Upd
[
https://issues.apache.org/jira/browse/BROOKLYN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055908#comment-16055908
]
Svetoslav Neykov commented on BROOKLYN-65:
--
It's almost there - just
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/731
@aledsage I'm fine with not updating the code to handle multi-threaded
calls. Would be nice if you mark it explicitly as not supported it in the docs.
It's been used just fine
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/731#discussion_r122729269
--- Diff:
utils/common/src/main/java/org/apache/brooklyn/util/stream/LoggingOutputStream.java
---
@@ -0,0 +1,134 @@
+/*
+ * Licensed to the
[
https://issues.apache.org/jira/browse/BROOKLYN-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-44.
--
Resolution: Fixed
Fix Version/s: 0.11.0
Fixed with the {{Composer}} tab, giving
[
https://issues.apache.org/jira/browse/BROOKLYN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-41.
--
Resolution: Fixed
Fix Version/s: 0.12.0
Should've been fixed with
[
https://issues.apache.org/jira/browse/BROOKLYN-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053712#comment-16053712
]
Svetoslav Neykov commented on BROOKLYN-39:
--
This got an alterna
[
https://issues.apache.org/jira/browse/BROOKLYN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-13.
--
Resolution: Fixed
Fix Version/s: (was: 0.7.0)
0.11.0
We
[
https://issues.apache.org/jira/browse/BROOKLYN-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-8.
-
Resolution: Fixed
Fix Version/s: 0.11.0
Response is proper JSON now. Not sure when
[
https://issues.apache.org/jira/browse/BROOKLYN-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-7.
-
Resolution: Fixed
It's possible to att
[
https://issues.apache.org/jira/browse/BROOKLYN-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-9.
-
Resolution: Fixed
Support added in https://github.com/apache/incubator-brooklyn/pull/25
[
https://issues.apache.org/jira/browse/BROOKLYN-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053693#comment-16053693
]
Svetoslav Neykov commented on BROOKLYN-367:
---
Persisting of bun
[
https://issues.apache.org/jira/browse/BROOKLYN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-53.
--
Resolution: Fixed
Adding locations is now possible through the UI. They are persisted
[
https://issues.apache.org/jira/browse/BROOKLYN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-17.
--
Resolution: Fixed
Release 0.7.0 is out.
> Release 0.7.0
[
https://issues.apache.org/jira/browse/BROOKLYN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svetoslav Neykov resolved BROOKLYN-27.
--
Resolution: Fixed
Release 0.7.0 is out.
> IPMC vote to rele
1 - 100 of 1900 matches
Mail list logo