Re: [m2e-users] Compiler madness!

[Fred Bricon <fbricon@xxxxxxxxx>]

If you use m2e 1.1, you can test a staged catalog by launching eclipse with the following argument in your eclipse.ini :

-Dm2e.discovery.url="" href="http://download.eclipse.org/technology/m2e/discovery/directory-test-1.1.xml">http://download.eclipse.org/technology/m2e/discovery/directory-test-1.1.xml 

See  http://wiki.eclipse.org/Eclipse.ini for more details on eclipse.ini customization.

Fred Bricon

On Tue, Jun 5, 2012 at 4:40 PM, Peter Murray <pete@xxxxxxxxxxx> wrote:

Thanks, Igor.  That worked a champ!

-pete

On Tue, Jun 5, 2012 at 10:36 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:

I thought somebody provided this already, not sure. Not very high on my
priority list.

--
Regards,
Igor

On 12-06-05 10:33 AM, Peter Murray wrote:

Thanks, Igor - and sorry for the inappropriate posting.

On topic, however - is there a chance that m2e will have a lifecycle
mapping for this compiler?

-pete

On Tue, Jun 5, 2012 at 10:26 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx

<mailto:igor@xxxxxxxxxxxxxx>> wrote:

   You can try tycho-compiler-jdt 0.15.0 (compiler id=jdt), which uses 3.8
   jdt core bits. If this does not work, I suggest you ask on maven users
   mailing list, this list is dedicated to m2e-specific questions and
   discussions.

   --
   Regards,
   Igor


   On 12-06-05 10:21 AM, Peter Murray wrote:


       Greetings all,

       We're trying to create a maven build for projects which build
       fine in
       eclipse and we're running into trouble.  Here's what we're seeing:

       1) The standard JDK 7u3 compiler (and 6u31) do not handle some
       number of
       cases (which we apparently use a lot) of parameterized type
       inference.
       Inside eclipse indigo, these compile fine, but the default
       compilation
       settings from maven do not handle them.

       2) The latest plexus-compiler-eclipse gacks with an NPE in
       getTypeOrPackage - no information on how to resolve in our code.  It
       appears to be a bit stale vis a vis the latest indigo jdt
       version - so
       that may be the issue.

       Is there any hope of creating a maven build that mimics the eclipse
       compiler behavior?

       Cheers,

       --
       -pete
       peter m. murray

       _________________________________________________
       m2e-users mailing list
       m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
       https://dev.eclipse.org/__mailman/listinfo/m2e-users
       <https://dev.eclipse.org/mailman/listinfo/m2e-users>

   _________________________________________________
   m2e-users mailing list
   m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
   https://dev.eclipse.org/__mailman/listinfo/m2e-users

   <https://dev.eclipse.org/mailman/listinfo/m2e-users>




--
-pete
peter m. murray

pete@xxxxxxxxxxx <mailto:pete@xxxxxxxxxxx>

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

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

--
-pete
peter m. murray
pete@xxxxxxxxxxx

_______________________________________________
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