[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.technology.m2e] Re: Cannot get Embedded maven to recognize profile specified in launch configuration

Run As -> Maven build...

Then I specify the profile in the text field on the launch configuration dialog. I have debugged m2e up to the point where it processes the launch configuration and correctly sets the -P parameter from the text field. The problem is that somehow the embedded runtime doesn't pick this up in my particular case.

How do I debug the embedded runtime and figure out why the -P parameter is insufficient to activate the profile?

-Will

"Igor Fedorenko" <igor@xxxxxxxxxxxxxx> wrote in message news:guc4t3$lau$1@xxxxxxxxxxxxxxxxxxxx
Are you running something like Run As->Maven install? How do you activate the profile?

--
Regards,
Igor



Will Horn wrote:
This is a strange issue, but I'm throwing it out to this newsgroup since I'm not sure how to proceed. I have a custom ant task that I want to run after the packaging phase (copy the test-jar somewhere). Some configurations work and some don't:

1) m2e using embedded maven - doesn't work
2) maven 2.0.9 cli - works
3) m2e using external 2.0.9 - works
4) m2e using embedded maven AND making the profile "active by default" - works
5) also downloaded and tried 2.1.0 which works as well


What is most confusing is that I can't reproduce this on a simple project. So it must be something in my complex project structure. I tried debugging m2e but got stuck without the source code for the embedded maven jars.

Ring a bell for anyone? What could cause a profile not to be picked up? Any suggestions on how to debug further?

Thanks,
Will