Skip to Content

maven-wobootstrap-plugin

Version 15.1 by Henrique Prange on 2008/04/23 14:58
Warning
For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Introduction

The wobootstrap plug-in is used to import the WebObjects libraries to the Maven's local repository or a remote repository for sharing with other developers and projects (for WebObjects version 5.3 and later, the license is now included as part of the Xcode software license. Please review the license in the Xcode installer to verify if you are not breaking the current terms).

This plug-in searches for the WebObjects jars and generates all the required information (groupId, artifactId and version) to import the libraries to the particular repository.

The wobootstrap goals usually need to be executed once per WebObjects version.

WebObjects 5.2 or later must be installed in order to use the wobootstrap plug-in. The supported platforms include MacOS X, Windows and Linux.

Goals Overview

The wobootstrap plug-in has 2 goals:

  • wobootstrap:install* goal is used to import the WebObjects libraries to the local repository. It works in a similar way to the install:install-file goal, but the wobootstrap provides all the required information to install the jars.
  • woboostrap:deploy* goal is used to import the WebObjects libraries to the specified remote repository. It works in a similar way to the deploy:deploy-file  goal.

Usage

The wobootstrap:install Mojo

In most cases, wobootstrap:install doesn't need any configuration. It also doesn't need a Maven project to run.

Unknown macro: noformat. Click on this message for details.

The wobootstrap:deploy Mojo

The wobootstrap:deploy Mojo is used to install the WebObjects libraries to a remote repository (i.e. managed by an Enterprise Repository Manager). The full usage statement of the wobootstrap:deploy mojo can be described as:

Unknown macro: noformat. Click on this message for details.

If the url to deploy is not specified, the goal will fail. The repositoryId points to a server section in the settings.xml file. If you don't specify a repositoryId, Maven will try to extract authentication information using the default id 'remote-repository'.

Tips

If the following error happens while using the wobootstrap:deploy goal: "Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp"

See the solution here.