[#MULE-3844] Get rid of the example POMs in the "dist" directory

Mule

Get rid of the example POMs in the "dist" directory

Created: 16/Oct/08 06:30 AM Updated: 02/Dec/08 01:21 PM

Component/s:

Examples / Tutorials

Affects Version/s:

2.1.0

Fix Version/s:

Tech. Debt

Time Tracking:

Original Estimate:

2 days

Remaining Estimate:

2 days

Time Spent:

Not Specified

Issue Links:

Related

This issue relates to:

MULE-3636 Verify that the IDE config files can be generated by Maven from a full distribution

~~MULE-1655~~ Get rid of "dist" directory in examples

Labels:
User impact:	Medium
Effort points:	1
Affects Docs:	Yes

Description

« Hide

The examples ship have essentially two POMs: the one that's used in the regular reactor build and the ones in the "dist" directory that are bundled into the distribution. This duplication causes a lot fo maintainance work as we cannot check the distribution POMs in an automated fashion.

We created the distribution POMs because of some Maven deficiency, see my comment on ~~MULE-1592~~. I'm pretty sure that we can get rid of the distribution POMs with the current Maven versions.

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

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

See http://jira.codehaus.org/browse/MNG-2848, enabling profiles based on environment variables is supported as of Maven 2.0.9.

[ Permlink | « Hide ]

Daniel Feist added a comment - 28/Nov/08 06:55 AM

We should really only tackle this once example testing is automated.

[ Permlink | « Hide ]

Dirk Olmes added a comment - 01/Dec/08 04:52 AM

Talking to Travis and Dan I'm not convinced any more that removing the dist poms is actually a good idea. One of the purposes of separate POMs is to make the examples more "stand alone", i.e. separate them from the Maven reactor build, give them a stable version number of 1.0 and provide the necessary repository definitions. All this would be lost when we distribute the regular reactor POMs along with the examples.

The QA burden that these POMs (and the duplicate dependency definitions) impose should be relieved by some automated tests that operate on a full distribution to build and run the examples.