You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Ethan Li (Jira)" <ji...@apache.org> on 2020/12/09 17:34:00 UTC

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

     [ 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}
> <parent>
>     <groupId>com.mycompany.app</groupId>
>     <artifactId>my-app</artifactId>
>     <version>1</version>
>     <relativePath>../parent/pom.xml</relativePath>
>   </parent>
> {code}



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