Question

I'm trying to deploy a Mule application to Standalone using Maven, but Maven is unable to move my app to the relevant apps folder and I'm given the following warning:

[WARNING] MULE_HOME is not set, not copying <app-name>

However, MULE_HOME is set, and a simple echo $MULE_HOME in Terminal gives the following, which is correct:

/opt/mule

Is there a known fix to this? Currently having to manually copy to the apps directory.

Was it helpful?

Solution

Ok, I've figured out where the issue was here. My standalone instance of Mule is in a directory /opt/mule-standalone-3.4.0 with an alias /opt/mule pointing to the same location. For some reason, Maven didn't like MULE_HOME being set to the alias. When amended to point to the actual directory, all worked fine.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top