[jbosstools-dev] BuildContext in M2E Builders

Rob Cernich rcernich at redhat.com
Wed Oct 2 20:52:03 EDT 2013


Hey all,

I've been deep in the SwitchYard M2E build participant recently trying to figure out why we're ending up with stale markers in the workspace.  One thing I've found is that items refreshed by the resources mojo don't show up until they are refreshed by the m2e builder, which happens after all the build participants have executed (i.e. refreshes the files passed to BuildContext.refresh()).  This is problematic for me because I'm using scanners created off the context to check for changed files and am missing changes to resource files that have been copied to target/classes.  My plugin is executing in the process-classes phase, so I would expect the updated resources to be available.

I'm not a Maven expert, but it seems to me that if I'm scanning for changed files, I should be able to see _all_ the files that have changed, including those changed as a result of previous executions in the same context.  I would consider the current behavior a bug in the Eclipse BuildContext, but I'm not sure how it's supposed to work to begin with.  If any of you m2e experts could chime in with your thoughts, that would be much appreciated.

Thanks in advance,
Rob


More information about the jbosstools-dev mailing list