CODEWITHSUNDEEP
javamaventomcatmaven-assembly-pluginmyeclipse
hublo
hublo

Reputation: 1180

MyEclipse Web project : deployment assembly

Using MyEclipse 2015 with the Maven plugin, I was once able to conditionally select which Maven dependencies to deploy to my Tomcat server from the "deployment assembly" configuration screen :

enter image description here

I created a new project, which probably missed one configuration, as I can't choose anymore which dependency to deply, and I have to deploy everything :

enter image description here

(I don't have the blue circles anymore .....)

The reason why I'm trying to do this is because MyEclipse seems to ignore the dependency type when deploying a Web application locally.

Does anyone have an idea what could be different between my 2 projects settings ?

Upvotes: 0

Views: 505

Answers (1)

Tony Weddle
Tony Weddle

Reputation: 2091

Your dependency definition in your POM should specify a scope of "provided" if you don't want it deployed. MyEclipse uses that information, so you shouldn't have to worry about matching maven settings to eclipse project settings.

Upvotes: 1

Related Questions