maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MNG-223) consider replacement for <versions/>
Date Wed, 23 Mar 2005 01:45:45 GMT
     [ http://jira.codehaus.org/browse/MNG-223?page=history ]

Brett Porter updated MNG-223:
-----------------------------

    Description: 
We removed <versions/> from the POM in m2, which made sense as the POM should be a snapshot
of the current state of the project, not the history.

We can easily get old versions from the repository, however SCM tag names are missing (so
these may need to be stored in the POM at release time).

Another concern is that all project data should be available from the SCM - so if the repository
goes away it can be easily recreated. Would we need to manually redeploy from every historical
tag? Just the versions desired? Would having another archive versions.xml in SCM help with
any of the tasks?

I'm in favour of just using the repository + adding the tag at release time, but we need to
give all use cases due consideration.

  was:
We removed <versions/> from the POM in m2, which made sense as the POM should be a snapshot
of the current state of the project, not the history.

We can easily get old versions from the repository, however SCM tag names are missing (so
these may need to be stored in the POM at release time).

Another concern is that all project data should be available from the SCM - so if the repository
goes away it can be easily recreated. Would we need to manually redeploy from every historical
tag? Just the versions desired? Would having another archive versions.xml in SCM help with
any of the tasks?


> consider replacement for <versions/>
> ------------------------------------
>
>          Key: MNG-223
>          URL: http://jira.codehaus.org/browse/MNG-223
>      Project: m2
>         Type: Task
>   Components: design
>     Reporter: Brett Porter

>
>
> We removed <versions/> from the POM in m2, which made sense as the POM should be
a snapshot of the current state of the project, not the history.
> We can easily get old versions from the repository, however SCM tag names are missing
(so these may need to be stored in the POM at release time).
> Another concern is that all project data should be available from the SCM - so if the
repository goes away it can be easily recreated. Would we need to manually redeploy from every
historical tag? Just the versions desired? Would having another archive versions.xml in SCM
help with any of the tasks?
> I'm in favour of just using the repository + adding the tag at release time, but we need
to give all use cases due consideration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message