On Tue, Apr 20, 2010 at 5:56 PM, Brett Porter <[email protected]> wrote:
> > On 20/04/2010, at 7:26 PM, Deng Ching wrote: > > > Hi Brett, > > > > I'm currently looking at MRM-1362 (Add simple 'CRUD' pages for > project-level > > metadata along with a "generic metadata" plugin), and I have a question > > regarding this feature. As I understand it, the contents of the project > > version metadata (version-metadata.properties) comes mostly from the POM. > If > > we're going to provide a CRUD functionality for it through the webapp, > won't > > it have an effect that the info in the POM may not be the same as the > info > > stored in the project version metadata? > > Yep, good point. I was really looking for a simple starting point, so I'm > happy if this just gets defined and documented in one way of your choice, > eg. > - you can change it and it's not reflected back (so will be inconsistent). > You may or may not add another metadata property to indicate this so the UI > can indicate it, or record all the maven stuff in duplicate fields so that > originals can be shown > Would it pose a problem if we reflect the changes in the metadata to the POM itself? Then put a warning that any changes (to specific fields) will get reflected to the POM and at the same time, limit which properties associated to certain POM info can be modified. > - don't allow editing a fixed set of fields that we don't think makes sense > > Versioning the metadata would be an interesting future change also that > might help here. > > - Brett > > -- > Brett Porter > [email protected] > http://brettporter.wordpress.com/ > > > > >
