| So, after this is settled up, the question - what are the connectors good for and any advices / suggestions when to use them. I'm in particular puzzled by the buildhelper and m2e-jdt-plugins - what exactly they are doing and should they be always used. I mean, we don't have any problems with our current maven builds neither in eclipse nor outside it, but as far as I got it correct these connectors should interact b/n m2e and eclipse in order to avoid potential problems arising from the incremental builds in eclipse such as endless loops or memory leaks, etc. Any help will be much appreciated! 
 TIA, Ilko 
Hi and thanks for all the answers! 
 Sorry for the late reply, but I wanted to double check again everything with fresh workspace / svn co, etc., because the issue was specific to particular client. At last I found out that we are hitting this maven issue:
https://jira.codehaus.org/browse/MJAR-156The provided workaround seems to fix the problem for now and I hope that it won't cause another hidden problem :-(.
 
 Special thanks to Marcel, who provided great info about the internals of the WAS TE deployment - these details brought me to the root of the problem!
 The versions we are using, if of interest:
 
 
 RAD Version: 8.5.0 Build ID: RADO85-I20120529_2348m2e - Maven Integration for Eclipse    1.2.0.20120903-1050    org.eclipse.m2e.feature.feature.group m2e-wtp - Maven Integration for WTP (Incubation)    0.16.0.20120914-0945    org.eclipse.m2e.wtp.feature.feature.group 
m2e - slf4j over logback logging (Optional)    1.2.0.20120903-1050    org.eclipse.m2e.logback.feature.feature.groupm2e connector for mavenarchiver pom properties    0.15.0.201207090125-signed-201209140800    org.sonatype.m2e.mavenarchiver.feature.feature.group
WAS: 8.5.0.0OS: Windows 7 professional 64-bitThanks again to all of you! Ilko 
 
 |