3 Replies Latest reply on Mar 26, 2010 9:05 PM by asookazian

    m2e 0.10.0 heads up

    asookazian

      If you're using m2eclipse plugin, beware of m2e 0.10.0: MNGECLIPSE-2155


      The ejb modules will have .ejb rather than .jar extensions in application.xml generated by m2e and the EAR will not deploy.  I wasted half a day on this PITA.  :)


      Enjoy life on the bleeding edge...

        • 1. Re: m2e 0.10.0 heads up
          asookazian

          You have to wonder sometimes with these open-source frmwks (or any frmwk in general) about QA procedures/processes/resources.  This bug means that the m2e (Sonatype?) team did not even attempt to build an EAR or did (and it failed) and they let the bug go into 0.10.0 release.  That's nice.  I've never seen/heard a wiki or interview on JBoss QA processes, etc.  I know there is Hudson but what else?  The users/community are the QA...

          • 2. Re: m2e 0.10.0 heads up
            dan.j.allen

            That's why we have a QA team ;) And we are very proud to have them.


            ...which reminds me, we need a page that introduces them to the community ;)

            • 3. Re: m2e 0.10.0 heads up
              asookazian

              I found this doc but it's very old apparently.


              It would be nice to know some names of the QA folks at JBoss and an overview of the QA processes and tools, etc.