Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@mmiklavc does that mean we can go back to 3.0.1? Or should?
---
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
GitHub user justinleet opened a pull request:
https://github.com/apache/metron/pull/685
METRON-1087: Adjust license headers to be comments instead of Javadoc
## Contributor Comments
This does three things:
1. Changes Javadoc to just plain comment.
2. Fixes headers that
GitHub user merrimanr opened a pull request:
https://github.com/apache/metron/pull/684
DO NOT MERGE: METRON-1086: Create a Blockly-based user interface for Stellar
## Contributor Comments
This PR is a first look at the Blockly/Stellar integration with a working
example. This
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
Ok, I decided to try yet another combo here. I set the plugin version back
to 3.0.1 and re-installed the archetype. Now I get a new file
`~/.m2/repository/archetype-catalog.xml` with the archetype
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
So another wrinkle here - when running the archetype plugin from a
non-project (separate, clean) directory, it's going to default to 3.0.1. I'm
trying this up in full dev right now and running into
Github user james-sirota commented on the issue:
https://github.com/apache/metron/pull/683
+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
GitHub user merrimanr opened a pull request:
https://github.com/apache/metron/pull/683
METRON-1084: Management UI web server license should be Apache
## Contributor Comments
Minor license correction.
## Pull Request Checklist
Thank you for submitting a
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/680
Sounds great, @dlyle65535 !
---
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 dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
Oh yeah, thanks for clarifying, @anandsubbu - I'm not going to change the
'happy path' logic, so when the UI is up, it will work the way it did prior.
---
If your project is set up for it, you
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/680
Hi @dlyle65535 can it be a two step validation as follows:
a) We first verify if we are able to hit the storm URL, if that fails ->
then we mark the service as stopped.
b) If the storm
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/678
---
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 feature is
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/679
---
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 feature is
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
I'm starting to think the best approach would to assume the service is
stopped if we can't get to the ui (which we kind of do anyway because of how
status works).
Anybody absolutely hate
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/680
@dlyle65535 Thanks for the update. That's pretty surprising, it seems like
this should take care of it. Ping me when there's some new info, and I'll hop
back on this review.
---
If your
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
Thanks @justinleet - I'm going to hold off on this, @anandsubbu did some
additional testing and it didn't actually solve the problem. :(
---
If your project is set up for it, you can reply to
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/680
+1 by inspection
---
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,
16 matches
Mail list logo
