Subversion Repositories DevTools

Rev

Rev 391 | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 391 Rev 3525
Line 375... Line 375...
375 
 
 375 
 
376 
Closed and Archived Releases are not shown. The tool can still be used to update
 376 
Closed and Archived Releases are not shown. The tool can still be used to update
377 
the build files against such releases, but the Release Tag must be determined
 377 
the build files against such releases, but the Release Tag must be determined
378 
from Release Manager.
 378 
from Release Manager.
379 
 
 379 
 
380 
=item B<-rtag=nnn>
 380 
=item B<-rtag=nnn> also -rtag_id=nn or -rtagid=nn
381 
 
 381 
 
382 
This option specifies the Release, within the Release Manager Database, that will
 382 
This option specifies the Release, within the Release Manager Database, that will
383 
be used to update the build dependency file.
 383 
be used to update the build dependency file.
384 
 
 384 
 
385 
The Release Tag is provided by the Release Manager Web Page, or by the -Show option
 385 
The Release Tag is provided by the Release Manager Web Page, or by the -Show option
Line 401... Line 401...
401 
 
 401 
 
402 
This utilty will update the dependency information within a build file to
 402 
This utilty will update the dependency information within a build file to
403 
reflect the desired package-versions within a specified release.
 403 
reflect the desired package-versions within a specified release.
404 
 
 404 
 
405 
The intent of this utility is to simplify the process of package development by
 405 
The intent of this utility is to simplify the process of package development by
406 
automating the creating of a packages dependencies.
 406 
automating the maintenance of a packages dependencies.
407 
 
 407 
 
408 
The utility will:
 408 
The utility will:
409 
 
 409 
 
410 
=over 8
 410 
=over 8
411 
 
 411 
 
412 
=item *
 412 
=item *
413 
 
 413 
 
414 
Contact the Release Manager Database.
 414 
Contact the Release Manager Database.
415 
 
 415 
 
416 
The credentials are provided via JATS environment variables. JATS msut be
 416 
The credentials are provided via JATS environment variables. JATS must be
417 
correctly configured in order for this to work.
 417 
correctly configured in order for this to work.
418 
 
 418 
 
419 
=item *
 419 
=item *
420 
 
 420 
 
421 
Locate the release as specified by the Release Tag
 421 
Locate the Release as specified by the Release Tag
422 
 
 422 
 
423 
The name of the Release and the containing Project will be displayed.
 423 
The name of the Release and the containing Project will be displayed.
424 
 
 424 
 
425 
=item *
 425 
=item *
426 
 
 426 
 
427 
Extact all package-versions within the release
 427 
Extract all package-versions within the Release
428 
 
 428 
 
429 
The information is then written to a file called jats_rewrite.cfg. The file is
 429 
The information is then written to a file called jats_rewrite.cfg. If the file is
430 
left in place by the utility. It may be deleted.
 430 
left in place by the utility, with the '-keep' option, then it may be deleted
- 
 
 431 
and must not be committed to version control.
431 
 
 432 
 
432 
=item *
 433 
=item *
433 
 
 434 
 
434 
Invoke the jats rewrite utility to create or modify the build files.
 435 
Invoke the 'jats rewrite' utility to create or modify the build files.
435 
 
 436 
 
436 
Only the package dependencies are modified. The package version itself is not modified.
 437 
Only the package dependencies are modified. The package version itself is not modified.
437 
 
 438 
 
438 
=back
 439 
=back
439 
 
 440 
 
440 
The resultant file will be called 'auto.pl', by default. Jats will use this file
 - 
 
441 
in preference to the build.pl file.
 - 
 
442 
 
 - 
 
443 
This utility will use either the build.pl or auto.pl file as a template for
 441 
This utility will use either the build.pl or auto.pl file as a template for
444 
updating version numbers. The tool will not add or remove packages from the
 442 
updating version numbers. The tool will not add or remove packages from the
445 
build file.
 443 
build file nor will it modify the project suffix on a package.
446 
 
 444 
 
447 
The 'auto.pl' file will be used if it exists and it has a more recent timestamp
 445 
The 'auto.pl' file will be used if it exists and it has a more recent timestamp
448 
than the build.pl file. This allows a developer to modify either file without
 446 
than the build.pl file. This allows a developer to modify either file without
449 
fear of losing the changes.
 447 
fear of losing the changes.
450 
 
 448 
 
- 
 
 449 
=head1 EXAMPLE
- 
 
 450 
 
- 
 
 451 
The following command will update the build.pl file in the current directory so
- 
 
 452 
that the dependecies match those from the Release with an rtag_id of 25423.
- 
 
 453 
 
- 
 
 454 
    jats upddep -rtag_id=25423
- 
 
 455 
 
451 
=cut
 456 
=cut
452 
 
 457