You can use the verbose syntax to ignore a specific goal from being executed during an Eclipse build:
https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html#ignore-plugin-goal I suggest you look at the effective pom of your project to find where the deploy goal is being executed (it's probably wrongly attached to a phase m2e executes) On Tue, May 19, 2020 at 3:15 PM Phil Adams <padam...@gmail.com> wrote: > Upon further review... It turns out that adding "<?m2e ignore?>" to my > pom.xml file prevents me from deploying it to Maven Central. Apparently > the pom validation performed by Sonatype during the artifact upload process > is balking at that directive. > Is there any other way to get eclipse/m2e to NOT build the deploy goal? > Ideally, I would be able to configure the goal to be used by "update > project". > > ---------- Forwarded message --------- > From: Phil Adams <padam...@gmail.com> > Date: Mon, May 11, 2020 at 8:27 AM > Subject: Re: [m2e-users] Maven -> Update Project triggers deploy goal > To: Maven Integration for Eclipse users mailing list < > m2e-users@eclipse.org> > > > Thanks for this tip! Worked like a charm :) > > On Sun, May 10, 2020 at 3:48 PM Francois Marot <francois.ma...@gmail.com> > wrote: > >> Hello Phil, >> I haven't look at the details of your project, but usually you can >> configure plugin's executions using the <?m2e XXXXXX?> syntax. >> In your case: <?m2e ignore?> is what you want. >> More info here: >> https://www.eclipse.org/m2e/documentation/release-notes-17.html >> Hope it helps >> >> François >> >> On Sun, 10 May 2020 at 17:43, Phil Adams <padam...@gmail.com> wrote: >> >>> I recently changed my build (project located here: >>> https://github.com/IBM/platform-services-java-sdk) to start using an >>> alternate deploy plugin (bintray-maven-plugin) so that >>> I can more easily deploy my artifacts to a Bintray repository. I have >>> my automated Travis builds set up to build the "deploy" goal only for a >>> tagged-release build. This is working fine. >>> >>> The issue is that within my local Eclipse environment whenever I trigger >>> the "Maven -> Update Project" action to refresh dependencies, I'm seeing >>> deploy-related errors in the "Problems" window and red X's appear on my >>> project names in the "Package Explorer" window. >>> I don't really want to trigger the "deploy" goal in my local environment >>> because I'm not interested in deploying snapshot artifacts and I also don't >>> have the necessary creds setup in my local environment. >>> >>> Why is the m2e plugin seemingly triggering the "deploy" goal? I've >>> tried to look for a way to configure the goal that is invoked by "Update >>> Project" but there doesn't appear to be one. >>> This error didn't occur when I was using the "maven-deploy-plugin", so >>> I'm wondering if there's some weird interaction between the m2e plugin and >>> the bintray-maven-plugin. >>> >>> Anyone have an idea as to how to avoid these errors in my local Eclipse >>> environment? >>> >>> Thanks in advance for any help! >>> >>> -- >>> Phil Adams >>> Georgetown, TX >>> _______________________________________________ >>> m2e-users mailing list >>> m2e-users@eclipse.org >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/m2e-users >>> >> _______________________________________________ >> m2e-users mailing list >> m2e-users@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/m2e-users >> > > > -- > Phil Adams > Georgetown, TX > > > -- > Phil Adams > Georgetown, TX > _______________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/m2e-users > -- "Have you tried turning it off and on again" - The IT Crowd And if that fails, then http://goo.gl/tnBgH5
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-users
