[jira] [Commented] (EAGLE-1059) fix a bug in policy prototype resource
[ https://issues.apache.org/jira/browse/EAGLE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114017#comment-16114017 ] ASF GitHub Bot commented on EAGLE-1059: --- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/965 OK > fix a bug in policy prototype resource > -- > > Key: EAGLE-1059 > URL: https://issues.apache.org/jira/browse/EAGLE-1059 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > When a PolicyEntity(or policy prototype) is exported as a policy on a site, > the partitionSpec of the new policy is not updated, which results in a wrong > policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] eagle issue #965: EAGLE-1059: fix a bug in PolicyResource.java
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/965 OK --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-1059) fix a bug in policy prototype resource
[ https://issues.apache.org/jira/browse/EAGLE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114011#comment-16114011 ] ASF GitHub Bot commented on EAGLE-1059: --- Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/965 @haoch No. I put this feature in v0.5.1 > fix a bug in policy prototype resource > -- > > Key: EAGLE-1059 > URL: https://issues.apache.org/jira/browse/EAGLE-1059 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > When a PolicyEntity(or policy prototype) is exported as a policy on a site, > the partitionSpec of the new policy is not updated, which results in a wrong > policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] eagle issue #965: EAGLE-1059: fix a bug in PolicyResource.java
Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/965 @haoch No. I put this feature in v0.5.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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Closed] (EAGLE-1029) Wrong groupSpec is generated when more than one alert engine topology
[ https://issues.apache.org/jira/browse/EAGLE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-1029. Resolution: Fixed > Wrong groupSpec is generated when more than one alert engine topology > -- > > Key: EAGLE-1029 > URL: https://issues.apache.org/jira/browse/EAGLE-1029 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Critical > Fix For: v0.5.0 > > > According to the schedule info returned by /rest/metadata/schedulestates > In alertSpecs, new policies are assigned to alertBolt 9, 18, 19, 1, 12 of the > second alert engine topology. While in groupSpecs, the worker queue(alert > bolts) allocated for each policy is not [ 9, 18, 19, 1, 12]. Actually, it > adds all working queues, including those of other alert engine topology -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-809) Hide Kafka sink configuration used by alert engine
[ https://issues.apache.org/jira/browse/EAGLE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-809: Affects Version/s: (was: v0.5.1) v0.5.0 > Hide Kafka sink configuration used by alert engine > -- > > Key: EAGLE-809 > URL: https://issues.apache.org/jira/browse/EAGLE-809 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > * Hide Kafka topic creation used by alert engine > * Hide Kafka broker list used by alert engine -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-809) Hide Kafka sink configuration used by alert engine
[ https://issues.apache.org/jira/browse/EAGLE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-809: Affects Version/s: (was: v0.5.0) v0.5.1 > Hide Kafka sink configuration used by alert engine > -- > > Key: EAGLE-809 > URL: https://issues.apache.org/jira/browse/EAGLE-809 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > * Hide Kafka topic creation used by alert engine > * Hide Kafka broker list used by alert engine -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (EAGLE-1060) remove SNAPSHOT from version
[
https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh resolved EAGLE-1060.
---
Resolution: Fixed
> remove SNAPSHOT from version
>
>
> Key: EAGLE-1060
> URL: https://issues.apache.org/jira/browse/EAGLE-1060
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> As pointed out by Hao
> {quote}
> The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
> change to 0.5.0 instead.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-1029) Wrong groupSpec is generated when more than one alert engine topology
[ https://issues.apache.org/jira/browse/EAGLE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-1029: - Affects Version/s: (was: v0.5.1) v0.5.0 > Wrong groupSpec is generated when more than one alert engine topology > -- > > Key: EAGLE-1029 > URL: https://issues.apache.org/jira/browse/EAGLE-1029 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Critical > Fix For: v0.5.0 > > > According to the schedule info returned by /rest/metadata/schedulestates > In alertSpecs, new policies are assigned to alertBolt 9, 18, 19, 1, 12 of the > second alert engine topology. While in groupSpecs, the worker queue(alert > bolts) allocated for each policy is not [ 9, 18, 19, 1, 12]. Actually, it > adds all working queues, including those of other alert engine topology -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1029) Wrong groupSpec is generated when more than one alert engine topology
[ https://issues.apache.org/jira/browse/EAGLE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-1029: - Fix Version/s: v0.5.0 > Wrong groupSpec is generated when more than one alert engine topology > -- > > Key: EAGLE-1029 > URL: https://issues.apache.org/jira/browse/EAGLE-1029 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Critical > Fix For: v0.5.0 > > > According to the schedule info returned by /rest/metadata/schedulestates > In alertSpecs, new policies are assigned to alertBolt 9, 18, 19, 1, 12 of the > second alert engine topology. While in groupSpecs, the worker queue(alert > bolts) allocated for each policy is not [ 9, 18, 19, 1, 12]. Actually, it > adds all working queues, including those of other alert engine topology -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1029) Wrong groupSpec is generated when more than one alert engine topology
[ https://issues.apache.org/jira/browse/EAGLE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-1029: - Affects Version/s: (was: v0.5.0) v0.5.1 > Wrong groupSpec is generated when more than one alert engine topology > -- > > Key: EAGLE-1029 > URL: https://issues.apache.org/jira/browse/EAGLE-1029 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Critical > > According to the schedule info returned by /rest/metadata/schedulestates > In alertSpecs, new policies are assigned to alertBolt 9, 18, 19, 1, 12 of the > second alert engine topology. While in groupSpecs, the worker queue(alert > bolts) allocated for each policy is not [ 9, 18, 19, 1, 12]. Actually, it > adds all working queues, including those of other alert engine topology -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1031) add intervalMin setting in the metric preview page
[
https://issues.apache.org/jira/browse/EAGLE-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-1031:
-
Affects Version/s: (was: v0.5.0)
v0.5.1
> add intervalMin setting in the metric preview page
> ---
>
> Key: EAGLE-1031
> URL: https://issues.apache.org/jira/browse/EAGLE-1031
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.1
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> By default, the intervalMin is calculated by
> {code}
> intervalMin = 5min, |queryEndTime - queryStartTime| <= 6h
> 15min, |queryEndTime - queryStartTime| <= 24h
> 30min, |queryEndTime - queryStartTime| <= 7d
> 60min, |queryEndTime - queryStartTime| <= 14d
> 1day, |queryEndTime - queryStartTime| > 14d
> {code}
> In some cases, users want to view metric in minute level. Eagle should
> support to customize this parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-1044) Support policy import using a policy prototype
[ https://issues.apache.org/jira/browse/EAGLE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-1044: - Affects Version/s: v0.5.1 > Support policy import using a policy prototype > -- > > Key: EAGLE-1044 > URL: https://issues.apache.org/jira/browse/EAGLE-1044 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Critical > > This new feature is to facilitate policy management among multiple sites. > With a single policy prototype, it can be imported into different sites. > * add a new entity PolicyEntity in the metadata database > * provides RESTful APIs to query/delete/update a policy template > * easy to onboard policies on a new site -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1038) Support alertDuplication customization for each policy
[ https://issues.apache.org/jira/browse/EAGLE-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-1038: - Affects Version/s: (was: v0.6.0) v0.5.1 > Support alertDuplication customization for each policy > --- > > Key: EAGLE-1038 > URL: https://issues.apache.org/jira/browse/EAGLE-1038 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > Requirements > * compatible with old versions > * enable alertDuplication check for each policy > * optimize DefaultDeduplicator -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1041) Support policy processing pipeline
[
https://issues.apache.org/jira/browse/EAGLE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-1041:
-
Affects Version/s: (was: v0.5.0)
v0.5.1
> Support policy processing pipeline
> --
>
> Key: EAGLE-1041
> URL: https://issues.apache.org/jira/browse/EAGLE-1041
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.1
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> In some cases, like increment or decrement pattern, data need to be processed
> in more than one stage. For example, alert if the metric value increases by
> N. Two steps to get the right alert.
> 1. sort & filter events which meet the filter conditions.
> 2. define data change pattern.
> Here is a sample policy
> {code}
> fromHADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"]#window.externalTime(timestamp,1min)
> select * group by site,host,component, metric insert into temp;
> from every
> a=HADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"],
> b=HADOOP_JMX_METRIC_STREAM_SANDBOX[b.component==a.component and
> b.metric==a.metric and b.host==a.host and b.value>a.value and a.value>100]
> select b.site,b.host,b.component, b.metric, b.value as newNumOfMissingBlocks,
> a.value as oldNumOfMissingBlocks, (b.value-a.value) as
> increastedNumOfMissingBlocks insert into
> HADOOP_JMX_METRIC_STREAM_SANDBOX_MISS_BLOCKS_LARGER_OUT;
> {code}
> There are two queries in this policy. The first one with the time window
> condition tells Eagle to sort the original events. The second one defines the
> data pattern. As the constraint of Siddhi syntax
> (https://docs.wso2.com/display/CEP420/SiddhiQL+Guide+3.1#SiddhiQLGuide3.1-Pattern),
> the filtering of input events does not work.
> Luckily, if we put the output stream of the first query as the input stream
> of the second query, it works. That's the problem this ticket tries to solve.
> Ideally, the right policy can be written as
> {code}
> fromHADOOP_JMX_METRIC_STREAM_SANDBOX[metric=="hadoop.namenode.dfs.missingblocks"]#window.externalTime(timestamp,1min)
> select * group by site,host,component, metric insert into MISSING_BLOCK_OUT;
> from every a=MISSING_BLOCK_OUT[metric=="hadoop.namenode.dfs.missingblocks"],
> b=MISSING_BLOCK_OUT[b.component==a.component and b.metric==a.metric and
> b.host==a.host and b.value>a.value and a.value>100]
> select b.site,b.host,b.component, b.metric, b.value as newNumOfMissingBlocks,
> a.value as oldNumOfMissingBlocks, (b.value-a.value) as
> increastedNumOfMissingBlocks insert into
> HADOOP_JMX_METRIC_STREAM_SANDBOX_MISS_BLOCKS_LARGER_OUT;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (EAGLE-1051) Check if a publisher can be deleted
[ https://issues.apache.org/jira/browse/EAGLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen resolved EAGLE-1051. -- Resolution: Fixed > Check if a publisher can be deleted > > > Key: EAGLE-1051 > URL: https://issues.apache.org/jira/browse/EAGLE-1051 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > A publisher can be deleted only when there are no policies using it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1051) Check if a publisher can be deleted
[ https://issues.apache.org/jira/browse/EAGLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-1051: - Fix Version/s: v0.5.0 > Check if a publisher can be deleted > > > Key: EAGLE-1051 > URL: https://issues.apache.org/jira/browse/EAGLE-1051 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > A publisher can be deleted only when there are no policies using it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1055) Improve policy prototype apis
[
https://issues.apache.org/jira/browse/EAGLE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-1055:
-
Affects Version/s: (was: v0.6.0)
v0.5.1
Fix Version/s: v0.5.1
> Improve policy prototype apis
> --
>
> Key: EAGLE-1055
> URL: https://issues.apache.org/jira/browse/EAGLE-1055
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.1
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.1
>
>
> 1. create a policy prototype from a policy
> {code}
> API: POST /rest/policyProto/create?needPolicyCreated=true
> Payload: PolicyEntity (policyDefinition + alertPublishmentIds)
> public class PolicyEntity {
> String name; // auto created
> PolicyDefinition definition;
> List alertPublishmentIds = new ArrayList<>();
> }
> {code}
> 2. create a policy prototype by policy name
> {code}
> API: POST /rest/policyProto/create/{policyId}
> {code}
> 3. create policies for site from a list of policy protoypes
> {code}
> API: POST /rest/policyProto/export/{site}
> Payload: List
> {code}
> 4. create policies for site from a list of prototypes
> {code}
> API: POST /rest/policyProto/exportByName/{site}
> Payload: List
> {code}
> 5. delete a prototype
> {code}
> API: DELETE /rest/policyProto/{uuid}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (EAGLE-1051) Check if a publisher can be deleted
[ https://issues.apache.org/jira/browse/EAGLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113965#comment-16113965 ] ASF GitHub Bot commented on EAGLE-1051: --- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/959 @qingwen220 should it be included in `v0.5.0` release? > Check if a publisher can be deleted > > > Key: EAGLE-1051 > URL: https://issues.apache.org/jira/browse/EAGLE-1051 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > A publisher can be deleted only when there are no policies using it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-1059) fix a bug in policy prototype resource
[ https://issues.apache.org/jira/browse/EAGLE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113963#comment-16113963 ] ASF GitHub Bot commented on EAGLE-1059: --- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/965 Should it be included in v0.5.0 release? > fix a bug in policy prototype resource > -- > > Key: EAGLE-1059 > URL: https://issues.apache.org/jira/browse/EAGLE-1059 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.1 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > When a PolicyEntity(or policy prototype) is exported as a policy on a site, > the partitionSpec of the new policy is not updated, which results in a wrong > policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] eagle issue #959: EAGLE-1051: update removePolicy
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/959 @qingwen220 should it be included in `v0.5.0` release? --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] eagle issue #965: EAGLE-1059: fix a bug in PolicyResource.java
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/965 Should it be included in v0.5.0 release? --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-1060) remove SNAPSHOT from version
[
https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113962#comment-16113962
]
ASF GitHub Bot commented on EAGLE-1060:
---
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/966
LGTM
> remove SNAPSHOT from version
>
>
> Key: EAGLE-1060
> URL: https://issues.apache.org/jira/browse/EAGLE-1060
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> As pointed out by Hao
> {quote}
> The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
> change to 0.5.0 instead.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] eagle issue #966: [EAGLE-1060] updating version to 0.5.0
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/966 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 the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-1060) remove SNAPSHOT from version
[
https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113960#comment-16113960
]
ASF GitHub Bot commented on EAGLE-1060:
---
GitHub user jhsenjaliya opened a pull request:
https://github.com/apache/eagle/pull/966
[EAGLE-1060] updating version to 0.5.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jhsenjaliya/eagle EAGLE-1060
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/eagle/pull/966.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #966
commit 88001711bfbf0134ee7e37f12eee33fd9a9f9c27
Author: Jay
Date: 2017-08-04T05:30:49Z
udpating version to 0.5.0
> remove SNAPSHOT from version
>
>
> Key: EAGLE-1060
> URL: https://issues.apache.org/jira/browse/EAGLE-1060
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> As pointed out by Hao
> {quote}
> The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
> change to 0.5.0 instead.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] eagle pull request #966: [EAGLE-1060] updating version to 0.5.0
GitHub user jhsenjaliya opened a pull request: https://github.com/apache/eagle/pull/966 [EAGLE-1060] updating version to 0.5.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jhsenjaliya/eagle EAGLE-1060 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/966.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #966 commit 88001711bfbf0134ee7e37f12eee33fd9a9f9c27 Author: Jay Date: 2017-08-04T05:30:49Z udpating version to 0.5.0 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-1060) remove SNAPSHOT from version
[
https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113939#comment-16113939
]
Hao Chen commented on EAGLE-1060:
-
http://www.mojohaus.org/versions-maven-plugin/examples/set.html
> remove SNAPSHOT from version
>
>
> Key: EAGLE-1060
> URL: https://issues.apache.org/jira/browse/EAGLE-1060
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> As pointed out by Hao
> {quote}
> The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
> change to 0.5.0 instead.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-1060) remove SNAPSHOT from version
[
https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-1060:
--
Description:
As pointed out by Hao
{quote}
The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
change to 0.5.0 instead.
{quote}
> remove SNAPSHOT from version
>
>
> Key: EAGLE-1060
> URL: https://issues.apache.org/jira/browse/EAGLE-1060
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> As pointed out by Hao
> {quote}
> The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
> change to 0.5.0 instead.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (EAGLE-1060) remove SNAPSHOT from version
Jayesh created EAGLE-1060: - Summary: remove SNAPSHOT from version Key: EAGLE-1060 URL: https://issues.apache.org/jira/browse/EAGLE-1060 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: Jayesh Assignee: Jayesh Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
