Re: The Genapp plugin

[Erik Husby]

Charles Daniels wrote:
The only thing I have to do now is check the files in that directory against
the files in my plugin so that I only update the template directory if the
plugin contains newer files.  Here's the preGoal in my plugin:
 <preGoal name="genapp">
   <!-- TODO: Delete/copy only when necessary -->
   <ant:delete dir="${user.home}/.maven/template/mytemplate"/>
   <ant:copy todir="${user.home}/.maven/template/mytemplate"
preservelastmodified="true">
     <ant:fileset dir="${plugin.resources}/genapp/mytemplate"/>
   </ant:copy>
 </preGoal>
I first delete my template directory in case a new release of my plugin has
eliminated or moved any template files.
I hope that helps.
-- Chuck
 

Great Idea -- one thing I would suggest changing. Use 
${.maven.home.local}/template instead of ${user.home}/.maven/template  
The reason being that on our XP workstations we use roaming profiles. 
That means that ${user.home}/.maven gets copied from/to the network when 
we log in/out. And several hundred megabytes of jar files takes a while 
to copy. So we have our build.properties point maven.home.local to a 
local disk.

And I provide a .BAT file on our local site that developers download to 
install the plugins that I'm providing. You could do something similar 
and invoke the setup from the .BAT file.

--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard 
Rm. 2192  320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]