Notes

This section discusses items to be aware of when using different aspects of Maestro.

File protocol

The file protocol should be off by default. Enabling the file protocol may be a security risk when enabled on a publicly available instance as it may allow reading of unintended files from the server via the Web interface, so is disabled by default.

Release update policy

The Maestro distribution includes several supported plugins. The installer sets your settings.xml file such that central becomes your project server, so those are the only plugins you get and typically you should not need to check for updates. central is set to http://repo.exist.com/maven2/ with <releases><updatePolicy>never</updatePolicy> - making sure that new versions of those already present are never retrieved unless the configuration is overridden.

Although this is not recommended for production environments, if you are interested in testing development versions of plugins please see: http://maven.apache.org/guides/development/guide-testing-development-plugins.html.

Environment Variables

Customizations that you make to the Maestro Project Server are stored in ${appserver.base}/conf. The ${appserver.base} variable is used within Maestro scripts and usually not modified by users.

SSL

When working with SSL in Maestro, you might encounter invalid or not found SSL certificate warnings.

This can occur in the following uses of SSL:

  • Mail sent to a SSL encrypted email server.
  • Continuum fetching the POM for a Maven 2.x project add.
  • Continuum deploying to an HTTPS secured repository.
  • Archiva using an HTTPS secured remote repository.

Example of log message (when sending an email):

  INFO | jvm 1 | 2006/12/14 19:41:29 | org.codehaus.plexus.mailsender.MailSenderException: Error while sending mail.
  INFO | jvm 1 | 2006/12/14 19:41:29 | at
  org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(AbstractJavamailMailSender.java:129)
  ...
  INFO | jvm 1 | 2006/12/14 19:41:29 | Caused by: javax.mail.MessagingException: Can't send command to SMTP host;
  INFO | jvm 1 | 2006/12/14 19:41:29 | nested exception is:
  INFO | jvm 1 | 2006/12/14 19:41:29 | javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
  PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException:
  unable to find valid certification path to requested target 
  INFO | jvm 1 | 2006/12/14 19:41:29 | at com.sun.mail.smtp.SMTPTransport.sendCommand(SMTPTransport.java:1420)
  ...
  INFO | jvm 1 | 2006/12/14 19:41:29 | Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException:
  PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException:
  unable to find valid certification path to requested target
  INFO | jvm 1 | 2006/12/14 19:41:29 | at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
  ...
  INFO | jvm 1 | 2006/12/14 19:41:29 | Caused by: sun.security.validator.ValidatorException: PKIX path building failed:
  sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  INFO | jvm 1 | 2006/12/14 19:41:29 | at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:221)
  ...
  INFO | jvm 1 | 2006/12/14 19:41:29 | Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
  unable to find valid certification path to requested target
  INFO | jvm 1 | 2006/12/14 19:41:29 | at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:236)
  ...