DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5787>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5787 Enhanced PVCS task. Summary: Enhanced PVCS task. Product: Ant Version: 1.4.1 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hello, I have enhanced PVCS task: - addied ability to get to any directory, not only to workspace, - user name/password, - Bill of Materials. If you are interested in including these features I can send modified Pvcs.java and PvcsProject.java to you. Modified help page with new features description is here: <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252"> <META NAME="Generator" CONTENT="Microsoft Word 97"> <TITLE>PVCS task</TITLE> <META NAME="Template" CONTENT="C:\Program Files\Microsoft Office\Office\html.dot"> <META HTTP-EQUIV="Content-Language" CONTENT="en-us"></HEAD> <BODY LINK="#0000ff" VLINK="#800080"> <P><!doctype html public "-//w3c//dtd html 4.0 transitional//en"></P> <H1>Ant Pvcs Task User Manual</H1> <P>Modified by Pavel Vlasov (<A HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>) on 2002/01/10 </P> <UL> <LI>User and password properties to access protected repositories</LI> <LI>toDir property to get to any location</LI> <LI>bom and style properties to create a bill of materials - xml file that contains relative file names and revision numbers.</LI></UL> <P>by <BR> <!-- Names are in alphabetical order, on last name --></P> <UL> <LI>Thomas Christensen (<A HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>) </LI> <LI>Don Jeffery (<A HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>) </LI></UL> <P>Version 1.1 - 2001/06/27</P> <P>Problems with UNC pathnames and the use of () in paths are fixed and an updateonly argument introduced.</P> <P>Version 1.0 - 2001/01/31</P> <P>Initial release.</P> <P><HR></P> <H2>Table of Contents</H2> <UL> <LI><A HREF="#introduction">Introduction</A> </LI> <LI><A HREF="#configuretask">Pvcs Task</A> </LI></UL> <P><HR></P><DIR> <DIR> <H2><A NAME="introduction"></A>Introduction</H2> <P>The <pvcs task allows the user of ant to extract the latest edition of the source code from a PVCS repository. PVCS is a version control system developed by <A HREF="http://www.merant.com/products/pvcs";>Merant</A>. <BR> Before using this tag, the user running ant must have access to the commands of PVCS (get and pcli) and must have access to the repository. Note that the way to specify the repository is platform dependent so use property to specify location of repository. <BR> This version has been tested agains PVCS version 6.5 and 6.6 under Windows and Solaris. </P></DIR> </DIR> <P><HR></P><DIR> <DIR> <H2><A NAME="pvcs"></A>Pvcs Task</H2> <H3>Description</H3> <P>The pvcs task is set to point at a PVCS repository and optionally a project within that repository, and can from that specification get the latest version of the files contained by the repository. </P> <H3>Parameters</H3></DIR> </DIR> <TABLE BORDER CELLSPACING=1 CELLPADDING=2 WIDTH=623> <TR><TD WIDTH="12%" VALIGN="TOP"> <P><B>Attribute</B></TD> <TD WIDTH="78%" VALIGN="TOP"> <B><P>Description</B></TD> <TD WIDTH="10%" VALIGN="TOP"> <B><P>Required</B></TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>repository</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>The location of the repository (see your PVCS manuals)</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>Yes</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>pvcsproject</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>The project within the PVCS repository to extract files from ("/" is root project and that is default if this attribute isn't specified)</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>label</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>Only files marked with this label are extracted.</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>promotiongroup</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>Only files within this promotion group are extracted. Using both the <I>label</I> and the <I>promotiongroup</I> tag will cause the files in the promotion group and with that label to be extracted. </TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>force</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>If set to <I>yes</I> all files that exists and are writable are overwritten. Default <I>no</I> causes the files that are writable to be ignored. This stops the PVCS command <I>get</I> to stop asking questions!</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>workspace</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>By specifying a workspace, the files are extracted to that location. A PVCS workspace is a name for a location of the workfiles and isn't as such the location itself. You define the location for a workspace using the PVCS GUI clients. If this isn't specified the default workspace for the current user is used.</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>pvcsbin</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>On some systems the PVCS executables <I>pcli</I> and <I>get</I> are not found in the PATH. In such cases this attribute should be set to the bin directory of the PVCS installation containing the executables mentioned before. If this attribute isn't specified the tag expects the executables to be found using the PATH environment variable.</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>ignorereturncode</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>If set to <I>true</I> the return value from executing the pvcs commands are ignored.</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>updateonly</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>If set to <I>true</I> files are gotten only if newer than existing local files.</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>toDir</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>If this attribute is specified get retrieves files to this directory instead of working directory specified in project's workspace</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>bom</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>Bill Of Materials - xml file that contains relative file names and revision numbers. If bom is specified then get output doesn't go to console.</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>style</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>If bom is set and style is set then the stylesheet specified gets applied to bom</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>user</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>User name</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>password</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>Password</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>No</TD> </TR> </TABLE> <DIR> <DIR> <H3><A NAME="nested">Nested Elements</A></H3> <H3>pvcsproject element</H3> <CODE><P>pvcs</CODE> supports a nested <CODE><pvcsproject></CODE> element, that represents a project within the PVCS repository to extract files from. By nesting multiple <CODE><pvcsproject></CODE> elements under the <CODE><pvcs></CODE> task, multiple projects can be specified.</P> <H3>Parameters</H3></DIR> </DIR> <TABLE BORDER CELLSPACING=1 CELLPADDING=2 WIDTH=623> <TR><TD WIDTH="12%" VALIGN="TOP"> <P><B>Attribute</B></TD> <TD WIDTH="78%" VALIGN="TOP"> <B><P>Description</B></TD> <TD WIDTH="10%" VALIGN="TOP"> <B><P>Required</B></TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>name</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>The name of the pvcs project</TD> <TD WIDTH="10%" VALIGN="TOP"> <P>Yes</TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>workspace</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>By specifying a workspace, the files are extracted to that location. A PVCS workspace is a name for a location of the workfiles and isn't as such the location itself. You define the location for a workspace using the PVCS GUI clients. If this isn't specified the default workspace for the current user is used.</TD> <TD WIDTH="10%" VALIGN="TOP"> </TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>toDir</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>If this attribute is specified get retrieves files to this directory instead of working directory specified in project's workspace</TD> <TD WIDTH="10%" VALIGN="TOP"> </TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>bom</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>Bill Of Materials - xml file that contains relative file names and revision numbers. If bom is specified then get output doesn't go to console.</TD> <TD WIDTH="10%" VALIGN="TOP"> </TD> </TR> <TR><TD WIDTH="12%" VALIGN="TOP"> <P>style</TD> <TD WIDTH="78%" VALIGN="TOP"> <P>If bom is set and style is set then the stylesheet specified gets applied to bom</TD> <TD WIDTH="10%" VALIGN="TOP"> </TD> </TR> </TABLE> <DIR> <DIR> <H3>Examples</H3> <P>The following set-up extracts the latest version of the files in the pvcs repository. </P><DIR> <P> <!-- =================================================================== -- <BR> <!-- Get the latest version & nbsp; &nb sp;   ; & nbsp; &nb sp;   ; & nbsp; &nb sp;   ; -- <BR> <!-- =================================================================== -- <BR> <target name="getlatest" <BR> < pvcs repository="/mnt/pvcs" pvcsproject="/myprj"/ <BR> </target</P></DIR> <P>Now run: </P> <P> ant getlatest </P> <P>This will cause the following output to appear: </P> <PRE> getlatest: [pvcs] PVCS Version Manager (VMGUI) v6.6.10 (Build 870) for Windows NT/80x86 [pvcs] Copyright 1985-2000 MERANT. All rights reserved. [pvcs] PVCS Version Manager (get) v6.6.10 (Build 870) for Windows NT/80x86 [pvcs] Copyright 1985-2000 MERANT. All rights reserved. [pvcs] c:\myws\myprj\main.java <- C:\mypvcs\archives\myprj\main.java-arc [pvcs] rev 1.1 [pvcs] c:\myws\myprj\apache\tool.java <- C:\mypvcs\archives\myprj\apache\tools.java-arc [pvcs] rev 1.5 BUILD SUCCESSFUL Total time: 19 seconds</PRE> <P>This next example extracts the latest version of the files in the pvcs repository from two projects using nested <pvcsproject> elements. </P><DIR> <P> <!-- =================================================================== -- <BR> <!-- Get latest from myprj and myprj2 &n bsp; &nbs p; &n bsp; &nbs p; &n bsp; -- <BR> <!-- =================================================================== -- <BR> <target name="getlatest2" <BR> <pvcs repository="/mnt/pvcs" <BR> <pvcsproject name="/myprj" / <BR> <pvcsproject name="/myprj2" / <BR> </pvcs <BR> </target</P></DIR> <P>Now run: </P> <P> ant getlatest2 </P> <P>This will cause the following output to appear: </P> <PRE> getlatest2: [pvcs] PVCS Version Manager (VMGUI) v6.6.10 (Build 870) for Windows NT/80x86 [pvcs] Copyright 1985-2000 MERANT. All rights reserved. [pvcs] PVCS Version Manager (get) v6.6.10 (Build 870) for Windows NT/80x86 [pvcs] Copyright 1985-2000 MERANT. All rights reserved. [pvcs] c:\myws\myprj\main.java <- C:\mypvcs\archives\myprj\main.java-arc [pvcs] rev 1.1 [pvcs] c:\myws\myprj\apache\tool.java <- C:\mypvcs\archives\myprj\apache\tool.java-arc [pvcs] rev 1.5 [pvcs] c:\myws\myprj2\apache\tool2.java <- C:\mypvcs\archives\myprj2\apache\tool2.java-arc [pvcs] rev 1.2 BUILD SUCCESSFUL Total time: 22 seconds </PRE></DIR> </DIR> <P><HR></P> <P>PVCS is a registered trademark of MERANT. </P></BODY> </HTML> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
