|
Re: Setting pack200=true on site.p2 causes missing content.jar and artifacts.jar and binary [message #544438 is a reply to message #544399] |
Fri, 02 July 2010 16:13 |
|
Hi Scott,
The site.packed is just an intermediate target directory containing the files that has been packed. The end product is
still in site.p2.
Regards,
Thomas Hallgren
On 07/02/2010 04:10 PM, Scott Anderson wrote:
> Using the following site generation command (which works when
> pack200=false), setting pack200=true causes the site to be generated
> packed, but missing content.jar and artifacts.jar and binary folder.
> Also I suppose as expected, the generated directory is named site.packed
> rather than site.p2. I have a feeling I'm being a dolt but its not
> becoming obvious to me yet. Anyone have a suggestion?
>
> Thanks!
>
>
> <buckminster command="perform">
> <args>
> <arg value="-Dbuckminster.output.root=${REMOVED}/${package.dir}/p2 "/>
> <arg value="-Dbuckminster.temp.root=${REMOVED}/${package.dir}/buildtmp "/>
> <arg value="-Dsite.pack200=true"/>
> <arg value="-Dcbi.include.source=false"/>
> <arg value="-Dtarget.os=*"/>
> <arg value="-Dtarget.ws=*"/>
> <arg value="-Dtarget.arch=*"/>
> <arg value="-Dqualifier.replacement.*=generator:buildTimestamp"/ >
> <arg
> value=" -Dgenerator.buildTimestamp.format='${build.qualifier.correct ed}' "/>
>
>
>
> <arg value="REMOVED.site#site.p2"/>
> </args>
> </buckminster>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03601 seconds