[jira] [Created] (STORM-3722) Update committer list

2020-12-09 Thread Bipin Prasad (Jira) 
Bipin Prasad created STORM-3722:
---

 Summary: Update committer list
 Key: STORM-3722
 URL: https://issues.apache.org/jira/browse/STORM-3722
 Project: Apache Storm
  Issue Type: Documentation
Reporter: Bipin Prasad
Assignee: Bipin Prasad


Update committer list



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (STORM-3708) ConstraintSolverConfig LOG messages should include topology id

2020-12-09 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li updated STORM-3708:

Priority: Minor  (was: Major)

> ConstraintSolverConfig LOG messages should include topology id
> --
>
> Key: STORM-3708
> URL: https://issues.apache.org/jira/browse/STORM-3708
> Project: Apache Storm
>  Issue Type: Improvement
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Minor
> Fix For: 2.3.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> LOG messages in ConstraintSolverConfig class should include topology id.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (STORM-3708) ConstraintSolverConfig LOG messages should include topology id

2020-12-09 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li resolved STORM-3708.
-
Fix Version/s: 2.3.0
   Resolution: Fixed

Thanks [~bipinprasad]. I merged this to master 
(58c7ad671e97bc5f8de6f6d85eb8129489ca6939)

> ConstraintSolverConfig LOG messages should include topology id
> --
>
> Key: STORM-3708
> URL: https://issues.apache.org/jira/browse/STORM-3708
> Project: Apache Storm
>  Issue Type: Improvement
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Major
> Fix For: 2.3.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> LOG messages in ConstraintSolverConfig class should include topology id.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (STORM-3721) Change child pom.xml reference to parent pom.xml

2020-12-09 Thread Ethan Li (Jira) 


 [ 
https://issues.apache.org/jira/browse/STORM-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ethan Li resolved STORM-3721.
-
Fix Version/s: 2.3.0
   Resolution: Fixed

Thanks [~bipinprasad]. I merged this to master 
(10a1e1ec434742ccb1d28d22411a915c75ed74d2)

> Change child pom.xml reference to parent pom.xml
> 
>
> Key: STORM-3721
> URL: https://issues.apache.org/jira/browse/STORM-3721
> Project: Apache Storm
>  Issue Type: Improvement
>  Components: build
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Minor
> Fix For: 2.3.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Several (but not all) module pom.xml files refer to the parent specifying 
> only the directory name. The correct syntax (as per Example 2 on 
> [https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)] 
> is to include the relative path to parent pom.xml
> {code:java}
> 
> com.mycompany.app
> my-app
> 1
> ../parent/pom.xml
>   
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)