Re: [m2e-users] Maven test classes are visible to WTP

[Fred Bricon <fbricon@xxxxxxxxx>]

Hi Andrew,

WTP deploys what's under the Deployment Assembly property page of your project (fancy UI over .settings/org.eclipse.wst.common.component)

In the case of m2e-wtp , we *manually* remove the test output from deployment during project configuration. See : 

https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp/src/org/maven/ide/eclipse/wtp/WebFragmentProjectConfigurator.java#L102

and :

https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp/src/org/maven/ide/eclipse/wtp/WTPProjectsUtil.java#L492 

HIH

Fred Bricon

On Thu, Mar 8, 2012 at 12:51 AM, Andrew Eisenberg <andrew@xxxxxxxxxxxx> wrote:

Hi all,

I'm working through this issue and have hit a bit of a wall.
https://jira.codehaus.org/browse/GRECLIPSE-1372

I'm hoping that someone familier with WTP's M2E integration can help me
further.

When scanning a classpath, WTP is including test classes in the
deployed application.  This only happens when using Groovy-Eclipse M2E
integration, so there must be some kind of conflict there.

How does WTP determine what should be deployed?  Can someone point me
to some code that does this?

thanks,
Andrew
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

--
"Have you tried turning it off and on again" - The IT Crowd