Short answer is no. packaging=pom is already used for two (!) primary purposes -- aggregation and configuration inheritance -- we did not find a way to allowing any other use without breaking the primary purposes.
-- Regards, Igor On 11-11-26 5:09 PM, Benson Margulies wrote:
The cargo archetype sets up packaging=pom but then explicitly adds in the compiler plugin and surefire and failsafe. Is there any way to persuade M2E 1.0 to treat this as a Java-nature project? _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
