[jbosstools-dev] Fwd: Fwd: [m2e-dev] Questions about the Maven Builder

[Alexey Kazakov]

So we don't have to care about maven builder order.
Thanks Fred.

On 07/25/2011 01:01 AM, Fred Bricon wrote:
> Hi Alexey,
>
> see Igor's reply :
>
>     ---------- Forwarded message ----------
>     From: *Igor Fedorenko* <igor at ifedorenko.com
>     <mailto:igor at ifedorenko.com>>
>     Date: 2011/7/25
>     Subject: Re: [m2e-dev] Questions about the Maven Builder
>     To: m2e-dev at eclipse.org <mailto:m2e-dev at eclipse.org>
>
>
>     In theory, builders order should not matter. Builders produce
>     workspace
>     changes, so if m2e builder changed any workspace resources, this will
>     trigger new build cycle (assuming workspace build is ON, of
>     course), and
>     these changes will be picked up by other builders.
>
>     Project metadata changes is another story. Although I have not
>     seen this
>     is documented anywhere, I believe general assumption is that project
>     configuration is (relatively) static and does not change as a
>     result of
>     project build. So if maven builder changes or updates project
>     configuration (things like application.xml and OSGi bundle
>     manifest), it
>     sort of falls into a gray territory, in theory everything is
>     supposed to
>     work, but in practice some tools may get confused and may need extra
>     help to "notice" new project metadata.
>
>     --
>     Regards,
>     Igor
>
>
> m2e configurators (JDT, WTP, JSF, CDI ...) are all called by the maven 
> builder, hence the phrase "if m2e builder changed any workspace 
> resources ...". As a matter of fact, resources are being 
> created/changed by these configurators, generating new build cycles. HIH.
>
> Regards,
>
> Fred Bricon
>
>
>
> On 11-07-25 12:00 AM, Fred Bricon wrote:
>
>     Hello World,
>
>     I'm not sure about the answer so I think it's best if I forward the
>     question here :
>
>        -------- Original Message --------
>        Subject:    Maven builder
>        Date:       Fri, 22 Jul 2011 16:30:55 -0700
>        From:       Alexey Kazakov <akazakov at exadel.com
>     <mailto:akazakov at exadel.com> <mailto:akazakov at exadel.com
>     <mailto:akazakov at exadel.com>>>
>        Reply-To: akazakov at exadel.com <mailto:akazakov at exadel.com>
>     <mailto:akazakov at exadel.com <mailto:akazakov at exadel.com>>
>        To: fbricon at redhat.com <mailto:fbricon at redhat.com>
>     <mailto:fbricon at redhat.com <mailto:fbricon at redhat.com>>,
>     jbosstools-dev
>
>     <jbosstools-dev at lists.jboss.org
>     <mailto:jbosstools-dev at lists.jboss.org>
>     <mailto:jbosstools-dev at lists.jboss.org
>     <mailto:jbosstools-dev at lists.jboss.org>>>
>
>
>
>
>        Hi Fred,
>
>        Fighting with Jose Freitas' problem with not-working code
>     completion
>        for JSF tags I looked at his .project file:
>     http://pastebin.com/bDLDDq2C
>        There is a builder org.eclipse.m2e.core.maven2Builder which
>        isdeclared as the last one in the list of the builders. Eventually
>
>        we found the reason of not-working code completion. It's not
>     related
>        to maven stuff at all (he didn't install JSF tools:
>     https://issues.jboss.org/browse/JBIDE-9397 ). But anyway, could it
>        be a problem if the maven builder declared last? For instance:
>
>        1. Java builder build the project.
>        2. CDI builder builds the project using Java model (cdi builder
>        should be declared after Java builder and we create a problem
>     marker
>        if it's not so).
>        3. KB builder builds the project using Java model (so we check the
>        build order again).
>        4. WST validation builder validate the project. We extend this
>        validation and check if CDI, KB, Seam builders declared before the
>        WST builder.
>
>        So, what about Maven? Does it do anything that could influence CDI,
>        JSF, Seam and don't trigger a new cycle of building? Should we care
>        if maven declared after CDI/KB/WST?
>        I tested Jose's project and everything seems to work, but I could
>        miss something.
>
>
>
>     Thanks for you insights.
>
>     Regards,
>
>     Fred Bricon
>     --
>     "Have you tried turning it off and on again" - The IT Crowd
>
>
>     _______________________________________________
>     m2e-dev mailing list
>     m2e-dev at eclipse.org <mailto:m2e-dev at eclipse.org>
>     https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev at eclipse.org <mailto:m2e-dev at eclipse.org>
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
>
>
> -- 
> "Have you tried turning it off and on again" - The IT Crowd
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20110725/a351bcc6/attachment-0001.html