To change Maestro's port from Maestro's user interface:
Note:You will be prompted to restart Maestro. Because of the migration to Jetty in Maestro 2.2.0, Maestro needs to be manually restarted in order for the change made in the port to be reflected. You need to stop Maestro from the command-line and start it again. Maestro should now be accessible using the new port.
To manually change the port number for Maestro:
<Call id="projectServerPort" class="java.lang.System" name="setProperty"> <Arg>jetty.port</Arg> <Arg>8080</Arg> </Call>
Change 8080 to an available port number. Valid port numbers go up to 65535. Be sure to select a port number that is not in use on your system.
To specify the SCM credentials using Maestro's user interface:
The way to tell Continuum to only use the userid and password for the original POM retrieval is to check Use SCM Credential Cache, if available checkbox on the Add Maven 2.0+ Project screen. After checking that, Continuum will use cached credentials for SVN commands.
This feature is available because the user who added the project may not be the same user that Maestro is running under. If SVN passwords change frequently and you don't use the cached credentials feature then each project must be edited to change the password. Meanwhile, if Continuum executes a scheduled build using the old password, the SVN update will fail, and the user's SVN account may be locked depending on organizational policies.
By default, Continuum uses the userID and password from the original POM retrieval, for SVN access. To specify a different SVN userID and password, edit the project and delete the userID. Continuum will then rely on the cached SVN credentials.
The Artifact Repository Manager (based on Archiva) and Build Management (based on Continuum) are separate projects at Apache and consequently have slightly different designs. Therefore, the effective roles granted to the admin account in Continuum are different than in Archiva. In Archiva, the admin account has to be explicitly granted the Global Repository Manager role.
Maven is different from Ant in the fact we keep all of our artifacts in a location similar to a library. This library is accessible to all users and is outside of the source control. When a user needs an artifact they can simply check it out from the library. When a user creates an artifact they can check it in. To help keep maintain the repositories Maestro has an Artifact Repository Manager.
The Artifact Repository Manager (also called Archiva) is a tool that helps organizations manage their Maven- or Maestro-based repositories. The Artifact Repository Manager enables Maestro users to setup, configure, administer, and manage multiple, shared/corporate artifact repositories through a single, unified, Web-based UI. It provides tools to search and browse for repository content, including, but not limited to artifacts (jars, wars, ears, etc.) and POMs.
There are multiple managed repositories that are stored as part of the repository manager. The repository manager gives you a single view over all of those resources. Repositories to which you proxy or sync are pulled down into a specific managed repository, so things are no longer split by their original source location.
There are three levels of repository for a user:
An example is the repository of the project server that is installed when you install the Maestro Project Server distribution that is located in: [maestro_home]/projectserver/data/repository.
Maestro's Artifact Repository Manager uses indexes to speed up searching in the managed repositories.
To configure the roll mode of Maestro log file (maestro.log), [maestro_home]/projectserver/conf/wrapper.conf should be modified with the configurations similar to the following.
Roll modes DATE and SIZE cannot be used together. The wrapper.logfile.maxsize configuration is ignored if the wrapper.logfile.rollmode does not have the SIZE value. SIZE_OR_WRAPPER, or SIZE_OR_JVM can also be used in place of SIZE.
wrapper.logfile=%PLEXUS_BASE%/logs/maestro.log wrapper.logfile.maxsize=1000mb wrapper.logfile.rollmode=SIZE
The suffix k (kb) or m (mb) are used for the maxsize value.
The filename should contain YYYYMMDD in it. This is the format for the timestamp of the log file which will be replaced with the appropriate date.