[ http://issues.apache.org/jira/browse/GERONIMO-1710?page=comments#action_12422538 ] Jason Dillon commented on GERONIMO-1710: ----------------------------------------
I think I see why this might be needed now... Looks like the best way to handle this is to allow m2 to filter these files to pick up the configuration, and thus we need a plugin to set these specialized dynamic properties. Note, I had originally thought that antrun would be best for this... BUT, I just ran into a problem running Clover which invalidates that theory, since it does a full recompile and sets up a separate clover/classes... we need to have the resources put there for clover to function correctly. So, based on that it sounds like it would be better to use the m2 filtering mechanism to handle expansion rather than writing out the properties file by a custom plugin. The custom plugin however needs to set the properties. > Geronimo timestamp plugin for Maven2 > ------------------------------------ > > Key: GERONIMO-1710 > URL: http://issues.apache.org/jira/browse/GERONIMO-1710 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: buildsystem > Reporter: Jacek Laskowski > Assigned To: Anders Hessellund Jensen > Priority: Minor > > This is a contribution of Anders to create the geronimo-version.properties > file with timestamp information during Geronimo's build. It should eventually > end up as an Maven2 official plugin since there're not much reason to keep it > here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
