You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Paul Ramirez (JIRA)" <ji...@apache.org> on 2011/06/23 18:25:47 UTC

[jira] [Created] (OODT-292) Parent Pom Undefined for Webapps

Parent Pom Undefined for Webapps
--------------------------------

                 Key: OODT-292
                 URL: https://issues.apache.org/jira/browse/OODT-292
             Project: OODT
          Issue Type: Bug
    Affects Versions: 0.3
            Reporter: Paul Ramirez
            Priority: Blocker
             Fix For: 0.3


webapp/components/pom.xml
webapp/fmbrowser/pom.xml
webapp/wmonitor/pom.xml

Do not specify:

<parent>
    <groupId>org.apache.oodt</groupId>
    <artifactId>oodt-core</artifactId>
    <version>0.3-SNAPSHOT</version>
    <relativePath>../../core/pom.xml</relativePath>
</parent>

This in turn means the <distributionManagement> section never gets included in the effective pom which leads to a blocker in the release:perform goal. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (OODT-292) Parent Pom Undefined for Webapps

Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ramirez closed OODT-292.
-----------------------------


> Parent Pom Undefined for Webapps
> --------------------------------
>
>                 Key: OODT-292
>                 URL: https://issues.apache.org/jira/browse/OODT-292
>             Project: OODT
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Paul Ramirez
>            Assignee: Paul Ramirez
>            Priority: Blocker
>             Fix For: 0.3
>
>
> webapp/components/pom.xml
> webapp/fmbrowser/pom.xml
> webapp/wmonitor/pom.xml
> Do not specify:
> <parent>
>     <groupId>org.apache.oodt</groupId>
>     <artifactId>oodt-core</artifactId>
>     <version>0.3-SNAPSHOT</version>
>     <relativePath>../../core/pom.xml</relativePath>
> </parent>
> This in turn means the <distributionManagement> section never gets included in the effective pom which leads to a blocker in the release:perform goal. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (OODT-292) Parent Pom Undefined for Webapps

Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ramirez resolved OODT-292.
-------------------------------

    Resolution: Fixed
      Assignee: Paul Ramirez

Committed revision 1138974

Release 0.3 can proceed without using a fancy svn script to perform magic.

> Parent Pom Undefined for Webapps
> --------------------------------
>
>                 Key: OODT-292
>                 URL: https://issues.apache.org/jira/browse/OODT-292
>             Project: OODT
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Paul Ramirez
>            Assignee: Paul Ramirez
>            Priority: Blocker
>             Fix For: 0.3
>
>
> webapp/components/pom.xml
> webapp/fmbrowser/pom.xml
> webapp/wmonitor/pom.xml
> Do not specify:
> <parent>
>     <groupId>org.apache.oodt</groupId>
>     <artifactId>oodt-core</artifactId>
>     <version>0.3-SNAPSHOT</version>
>     <relativePath>../../core/pom.xml</relativePath>
> </parent>
> This in turn means the <distributionManagement> section never gets included in the effective pom which leads to a blocker in the release:perform goal. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira