Re: [m2e-dev] m2e Connectors and dependence on plugin

[Pino Silvaggio <pino.silvaggio@xxxxxxxxx>]

Well, lets forget the workspace integration solution for a moment...

The current available methods to retrieve configuration parameters is 
limited.
I do not really need the plugin or its structures... Reflection implies 
I have the
plugin classes. I only need the parameters in some form.

I could read the configuration xml but it's not very elegant. Maybe 
that's the only solution?

On 11/29/2011 07:58 AM, Igor Fedorenko wrote:
> The best solution here is to push workspace integration to the Maven
> plugin itself (via plexus-build-api). This is the only way to guarantee
> workspace and command line builds behave consistently.
>
> You could embed particular version of the maven plugin jar into your m2e
> extension (as mentioned by Rafal), but this means your m2e extension
> will only work for one version of the configuration data structures.
>
> Another option is to use reflection to access just the configuration
> information you need.
>
> --
> Regards,
> Igor
>
> On 11-11-29 2:10 AM, Pino Silvaggio wrote:
> > I am writing a truezip connector.
> >
> > Suppose I need to access the values under files, fileSet, fileSets.
> >
> > These are structures that I need to figure out if I need to run
> > the build. For example, if the sources are external to the workspace
> > I won't run the build on incremental. Else, i'll do the same scan 
> > pattern
> > to recognize changes... At least this is what I am thinking at this
> > point...
> >
> > My question is how do I get access to these classes (files, fileSet and
> > fileSets) ???
> >
> > Even though this is a question of my specific case, how would you
> > access the plugin classes from a connector when needed?
> >
> > Using pom deps don't work (ignored, of course, osgi...)
> > _______________________________________________
> > m2e-dev mailing list
> > m2e-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev