Our temporary work around in lieu of a Maven 2 eclipse plugin was to
create a simple ant file that just calls maven as a process. This makes
it easy to kick off builds from eclipse. The content of our build file
follows:

<project name="supplementaldata Maven2 Wrapper" default="maven-install"
basedir=".">


  <property name="failonerror" value="true" />

  <target name="maven-generate-sources">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="generate-sources"/>
    </exec>
  </target>

  <target name="maven-compile">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="compile"/>
    </exec>
  </target>

  <target name="maven-test">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="test"/>
    </exec>
  </target>

  <target name="maven-package">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="package"/>
    </exec>
  </target>

  <target name="maven-install">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="install"/>
    </exec>
  </target>

  <target name="maven-deploy">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="deploy"/>
    </exec>
  </target>

  <target name="maven-verify">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="verify"/>
    </exec>
  </target>

  <target name="maven-version">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="-version"/>
    </exec>
  </target>

  <target name="maven-eclipse">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="eclipse:eclipse"/>
    </exec>
  </target>

  <target name="maven-javadoc">
    <exec dir="${basedir}"
          failonerror="${failonerror}"
          executable="m2.bat">
      <arg value="javadoc:javadoc"/>
    </exec>
  </target>

</project>

-----Original Message-----
From: Siegfried Heintze [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 18, 2005 12:37 AM
To: 'Maven Users List'
Subject: maven ant and maven.xml

I was hoping someone in the mavenide mailing list could help me get a
minimal project working with eclipse, mavenide and maven. I'm getting a
"an internal error occurred during: 'launching'" when I right click on
the maven goal in the mavenide in eclipse.

Since I'm still waiting for a response on that mailing list I decided to
"maven ant" and have eclipse use ant targets instead of maven goals. 

But that did not work either! Where is my "run" goal that I defined in
the maven.xml file? It is not there. Is there some way to force maven to
insert it?


Thanks,
Siegfried 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to