Ok, here I resubmit the patches again if you want to take a look at
them. I supply two files: one for the tomahawk build.properties file,
which includes a property that tells if the subproject has to update
the lastModified or not (of course, only tomahawk needs this). I also
provide the patch for the build.xml (all the build.xml files, of
course), but I supply the patch for the tomahawk subproject. Do you
prefer that I apply a patch for all the build.xml's? I'm am not sure
how to create a diff file for the build.xml of all the subprojects at
the same time? Is this possible? Copying the one resulting after the
patch to the other subprojects and to the current/build folder should
suffice.
For the needed new target in the build.xml I adapted Sylvain's
build.xml code from the version before the reorg...

Regards,

Bruno

2005/7/10, Sylvain Vieujot <[EMAIL PROTECTED]>:
>  Thanks Bruno.
>  
>  Sylvain.
> 
>  
>  On Sun, 2005-07-10 at 15:36 +0200, Bruno Aranda wrote: 
>  I gave a patch to Sean for this. In the old build, when the component
> jars was generated a variable (lastModified) in a *.properties file
> was set to the current date. This date is used to do some caching with
> the resource files which are included using the AddResources class. I
> could resubmit again this patch, although I was not very happy with
> it...
> 
> Bruno
> 
> 2005/7/9, Martin Marinschek <[EMAIL PROTECTED]>:
> > Hi Sylvain,
> > 
> > for some time now, I get the following log entry when playing around
> > with MyFaces:
> > 
> > (util.AddResource 157 ) Unparsable lastModified :
> > @lastModified@
> > 
> > I really don't know what this is about, would you mind having a look on
> that?
> > 
> > regards,
> > 
> > Martin
> >
> 
>

Attachment: tomahawk-build.diff
Description: Binary data

Attachment: tomahawk-build-properties.diff
Description: Binary data

Reply via email to