Frequently Asked Questions

MuleForge is the one stop shop for developers working with Mule, who are looking for transports, modules, tools and examples for working on the Mule platform. It's a fully managed hosting environment for Mule extensions and applications built by the Mule community and MuleSource partners.

MuleForge projects include Mule applications and Mule extensions.

An extension typically provides a single feature such as a new Mule transport or transformer.

An application is more complex and provides a set of features, such as a tool for working with Mule, or an example demonstrating a particular use of Mule, which would be useful for other Mule users.

MuleForge applications and extensions are created by in-house MuleSource experts, members of MuleSource partners, and individual Mule users who want to share applications and Mule extensions that they have created. A quality assurance team reviews each project before it is posted to the MuleForge directory.

No restrictions are enforced by MuleForge, but you should read the project documentation and its license before using a project.

Yes, though the project must be used abiding by its license and any other terms set by the project owner.

A key feature of MuleForge is its openness. Developers, partners, and customers are all welcome to share their extensions and applications via MuleForge. As is true of other open exchange sites, this open model means that the community acts as the judge of the quality of the hosted projects. This implies that users should carefully evaluate the feedback, ratings, and reputation of its publisher, in order to assess its trustworthiness. In general, you should only install applications into your production deployment from publishers you and the community trust.

All projects on MuleForge have undergone only basic review by MuleSource and may be subject to random reviews. Projects that feature the "Mule Certified Application" logo have been more thoroughly reviewed for both their quality and the trustworthiness of their publisher.

• Click 'SEARCH' from the top navigation bar.
• Leave the Name field blank and the remaining fields set to 'Any'.

• Click 'SEARCH' from the top navigation bar.
• Select 'Not Setup' from the Status field.

Once a new project is set up in MuleForge by the MuleForge administration team, the project is given a status, which is one of these listed below:
Active: This is the status given by default when a project is created and a despot is identified. It also indicates that work for the project is ongoing.
Inactive: The Inactive status is given to projects which were once owned by a despot who is now no longer following the project. They have no despot or project members. Generally, such projects have some code submitted and online documentation.
Not Set Up: These are newly proposed projects which have not yet been created in MuleForge. They are currently being reviewed before being accepted or rejected by the MuleForge team.
No Owner: The No Owner status indicates that the project has no despot. It may either be a project which was simply proposed but was never owned, or else it may have been previously owned but not followed up any longer.

A despot is the name given to the owner or lead of a MuleForge project.

You need to be subscribed to the list in order to post message.

1. Go the project's homepage
2. From the left navigation bar, click 'Mailing Lists' under the 'Project Resources' heading.
3. Click 'Subscribe' next the list you are interested in.
4. If you are not logged it, or do not have an account, enter your email address.

Check whether your Mule Forge Confluence username is set correctly, by following these steps:

1. Log into your MuleForge account, by clicking 'ADMIN' from the top navigation bar and clicking 'Login' at the top right of the page that loads.
2. Once logged in, click 'My Page' from the top navigation bar.
3. click 'Personal Details', within the 'Configuration' section.
4. Type in your correct MuleForge Confluence username.
5. Click 'Update'.