geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-3908) Spec parent pom should be in a specs-parent project so releasing it doesn't copy all the specs that happen to be in trunk.
Date Wed, 12 Mar 2008 21:28:46 GMT

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

David Jencks closed GERONIMO-3908.
----------------------------------

    Resolution: Fixed

rev 636516.

> Spec parent pom should be in a specs-parent project so releasing it doesn't copy all
the specs that happen to be in trunk.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-3908
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3908
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem, specs
>    Affects Versions: 2.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.2
>
>
> Releasing the specs 1.4 pom produced a copy of all the specs that happened to be in trunk
at that moment in tags/specs-1.4/.  This is dumb but hard to avoid with the current directory
layout.
> I'm going to move the parent pom to a specs-parent directory and change its artifact
id to specs-parent.  This will make releasing it more clearly independent of any specs that
may be using it.
> As an independent comment I think the idea of erasing released specs from trunk is too
error prone.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message