Looks like attachment get not through. Here is again with password - sculptor. And it's ZIP file (stupid Gmail).
Pavel On Fri, Jul 3, 2009 at 6:35 PM, Pavel Tavoda<pavel.tav...@gmail.com> wrote: > Karsten TNX for hint but I found it more complicated than what we > need. I developed Maven plugin which care about removing untouched > files. > > Plugin have 3 actions: clean, before-generate, after-generate > > I have no idea how to test it, than I developed script 'test.sh' which > is included in attached zip file. Here is also way how to start it and > watch what's going on. > > Many questions: > * Patrik, can we make it as one of subprojects (I can change name, > artifactId, ..., I did my best to guess right names)? > > * Can somebody help me integrate it right way to sculptor POM? I don't > know how to configure POM.XML that right action (clean, > before-generate, after-generate) is started at right time in build > process. > > * Who is willing to test it in more realistic environment? > > Have a nice weekend > > Pavel > > > On Fri, Jul 3, 2009 at 11:50 AM, Karsten Thoms<karsten.th...@itemis.de> wrote: >> A good starting point is to provide a specialized Outlet >> implementation. The implementation class to use must be configured for >> the Maven Mojo to do this. >> >> You should read this article from Heiko about the Generation Gap >> pattern. He suggests to introduce a conditional generated folder, >> where only files are generated if they were not moved to a manually >> maintained folder. >> http://www.1160pm.net/2009/04/23/generation-gap-pattern/ >> >> ~Karsten >> >> Am 02.07.2009 um 13:04 schrieb Pavel Tavoda: >> >>> If I should be honest, what annoy me most now on Sculptor is >>> regeneration of one-time generated files (main/java main/resources). >>> Before I had idea with timestamps but this is difficult to handle. Now >>> I found maybe better solution. After generation we should checksum all >>> generated files in main/java and main/resources. Than before >>> generation we should check all sums and if file have same checksum we >>> should remove it (file wasn't change and we should regenerate it). >>> >>> I don't know enough details about oAW if I can write some hook method >>> which can do this for every generated file or I have to write Maven >>> plugin, which should be part of clean task. Can somebody give me any >>> hint about oAW or Maven where should I look? >>> >>> I'm willing to write anything what can help to solve this problem. >>> >>> TNX >>> >>> Pavel >>> >>> PS: Patrik, do we have already some incident about this? >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Fornax-developer mailing list >>> Fornax-developer@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/fornax-developer >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Fornax-developer mailing list >> Fornax-developer@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fornax-developer >> >
fornax-cartridges-sculptor-maven-plugin-checksum-zip.arch
Description: Binary data
------------------------------------------------------------------------------
_______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
