[#MULE-3784] Examples should not build w/ Maven if $MULE_HOME is not set

Mule

Examples should not build w/ Maven if $MULE_HOME is not set

Created: 06/Oct/08 11:29 AM Updated: 15/Nov/08 11:40 AM

Component/s:

Examples / Tutorials

Affects Version/s:

None

Fix Version/s:

2.x Product Backlog

Time Tracking:

Not Specified

Labels:
User impact:	Medium

Description

« Hide

Some of the examples (loanbroker, scripting) require the user to build them before they will run. If the user builds them w/ Ant and has not set $MULE_HOME, the build quits w/ a message telling the user to set $MULE_HOME. However, if they build w/ Maven, they get no warning message but then the example still won't run and the user is left wondering why.

(Why = the 3rd-party libs were not copied into $MULE_HOME/lib/user)

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Daniel Feist added a comment - 08/Oct/08 03:35 PM

Travis is this a blocker for 2.1.1, or something we should do in some other minor release?

[ Permlink | « Hide ]

Travis Carlson added a comment - 08/Oct/08 03:54 PM

No, not a blocker, it's been this way for quite a while.

[ Permlink | « Hide ]

Dirk Olmes added a comment - 16/Oct/08 08:32 AM

This is somewhat a blocker for unifying the distribution POMs and the regular example POMs. In the reactor build, MULE_HOME is not set and should not be checked either. When building the examples we want to enforce it.

[ Permlink | « Hide ]

Ross Mason added a comment - 15/Nov/08 11:40 AM

It seems like this is a straight forward fix to enforce the check in the parent examples distribution pom file.