Re: Making First Contact

One thing to think about I have noted in a comment here: https://issues.apache.org/jira/browse/BROOKLYN-575?focusedCommentId=16393594=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16393594 Something to think about for this proposal - we should avoid thinking that the

[jira] [Commented] (BROOKLYN-575) GSOC: New Brooklyn UI

[ https://issues.apache.org/jira/browse/BROOKLYN-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393594#comment-16393594 ] Geoff Macartney commented on BROOKLYN-575: -- Something to think about for this proposal  - we

[jira] [Commented] (BROOKLYN-577) GSoC: Modernise Brooklyn's authentication system

[ https://issues.apache.org/jira/browse/BROOKLYN-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393448#comment-16393448 ] Senuri De Silva commented on BROOKLYN-577: -- Hi!, I'm Senuri De Silva, 3^rd^ year undergraduate

[jira] [Comment Edited] (BROOKLYN-577) GSoC: Modernise Brooklyn's authentication system

[ https://issues.apache.org/jira/browse/BROOKLYN-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393448#comment-16393448 ] Senuri De Silva edited comment on BROOKLYN-577 at 3/9/18 7:46 PM: -- Hi!,

Re: Making First Contact

Thank you so much John and Thomas for your time and wishes. Thomas, I really appreciate your feedback. Those are great suggestions to add to my proposal. I will think over them and update my proposal accordingly. Many thanks, Mert 2018-03-09 17:34 GMT+03:00 Thomas Bouron

Re: Making First Contact

Another thing to consider (I meant to add it to the list but send my email too quickly): you plan to use Brace for the YAML editor. Any reason for that? What about browsers compatibility? That's it for me, I let you think about it :) Best. On Fri, 9 Mar 2018 at 14:29 Thomas Bouron

Re: Making First Contact

Hi Mert. Thanks for sharing your proposal, that looks really good! I quite like that you went the extra-mile to make a quick prototype (which also looks good BTW) May I suggest few things that you could add to improve your proposal: - you want to use React + Redux stack but what about other

Re: [PROPOSAL] Deprecated JBoss 7 entity

I ended up creating 2 PRs: - for JBoss 7: https://github.com/apache/brooklyn-library/pull/149 - for JBoss 6: https://github.com/apache/brooklyn-library/pull/150 (as it is even older than 7) Best. On Fri, 9 Mar 2018 at 11:23 Aled Sage wrote: > +1 to deprecating it

[GitHub] brooklyn-library pull request #150: Deprecate JBoss 6 entity

GitHub user tbouron opened a pull request: https://github.com/apache/brooklyn-library/pull/150 Deprecate JBoss 6 entity Same reason with #149, but this version is even older You can merge this pull request into a Git repository by running: $ git pull

[GitHub] brooklyn-library pull request #149: Deprecate JBoss 7 entity

GitHub user tbouron opened a pull request: https://github.com/apache/brooklyn-library/pull/149 Deprecate JBoss 7 entity As the title, this deprecates JBoss 7, mainly because it is EOF. See discussion here:

[jira] [Commented] (BROOKLYN-585) Bundle not re-installed on change when using brooklyn.library's URL

[ https://issues.apache.org/jira/browse/BROOKLYN-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392739#comment-16392739 ] Aled Sage commented on BROOKLYN-585: How much do we care about this use-case? The use of a nested

[jira] [Commented] (BROOKLYN-585) Bundle not re-installed on change when using brooklyn.library's URL

[ https://issues.apache.org/jira/browse/BROOKLYN-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392737#comment-16392737 ] Aled Sage commented on BROOKLYN-585: This is because of

[jira] [Created] (BROOKLYN-585) Bundle not re-installed on change when using brooklyn.library's URL

Aled Sage created BROOKLYN-585: -- Summary: Bundle not re-installed on change when using brooklyn.library's URL Key: BROOKLYN-585 URL: https://issues.apache.org/jira/browse/BROOKLYN-585 Project: Brooklyn

Re: [PROPOSAL] Deprecated JBoss 7 entity

+1 to deprecating it Thomas. Alex, I agree with you in general. In this case, we don't particularly care about a yaml equivalent of jboss 7 because it's so old. We would like a yaml blueprint for wildfly [1] in the community at some point. I thought that someone had done that in the past, but

Re: [PROPOSAL] Deprecated JBoss 7 entity

go for it. is there a yaml entity in the community we can point people to as part of the deprecation? wherever possible i'd like to replace the system-specific java entities like jboss with yaml equivalents in the community (ie outside apache brooklyn). --a On 09/03/2018 10:28, Thomas

[PROPOSAL] Deprecated JBoss 7 entity

Hi Brooklyners I made a PR yesterday[1] (which as been merged, thanks Geoff) to fix an issue with JBoss 7 entity. As it turns out, JBoss 7 is now EOL and does not work with java 7u171 onward. This is due to the `jboss-module.jar` not being compatible with the newest versions of Java. The patch I