set your packing at "pom" and use build-helper-maven-plugin to
attached your exe build artifact to maven project.  Here you can
define any extension you like, in this case "exe"

-D

On Mon, Aug 18, 2008 at 7:32 PM, Andrew Hughes <[EMAIL PROTECTED]> wrote:
> I got the ant wrapped in a maven plugin working.. but there was little point
> when exec:exec was available. I've since used this to sucessfully invoke the
> csvs 2003 compiler (as below).
>
> However, now that I am building the exe I need to set the
> <packaging>exe</packaging> so that it can complete all build phases. I
> notice that the native plugin does this although Im not sure how, and there
> doesn't seem to be alot of documentation on this. Im hoping there is
> something under the hood that I can use.
>
> Cheers.
>
> -------------------------------------------------------
>
>    <build>
>    <plugins>
>      <plugin>
>        <groupId>org.codehaus.mojo</groupId>
>        <artifactId>exec-maven-plugin</artifactId>
>        <version>1.1</version>
>        <executions>
>          <execution>
>            <phase>compile</phase>
>            <goals>
>              <goal>exec</goal>
>            </goals>
>          </execution>
>        </executions>
>        <configuration>
>          <executable>Devenv.com</executable>
>          <workingDirectory>..</workingDirectory>
>          <arguments>
>            <argument>/build</argument>
>            <argument>release</argument>
>            <argument>${project.name}/${project.name}.sln</argument>
>          </arguments>
>        </configuration>
>      </plugin>
>    </plugins>
>  </build>
>
>
> On Fri, Aug 15, 2008 at 3:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
>
>> you can use maven-antrun-plugin  to build and +
>> build-helper-maven-plugin to install/deploy our artifacts, and still
>> keep your vsproj together
>>
>>
>>
>> On Thu, Aug 14, 2008 at 10:52 PM, Andrew Hughes <[EMAIL PROTECTED]>
>> wrote:
>> > Our (many) MSVS 2003 Projects are configured with XXXXX.vcproj files
>> > (Visual C Project). These files are what hold all the configuration and
>> > build instructions for the cpp project... yadda yadda yadda.
>> > Can I get the native provider to look at this file? Because really, this
>> is
>> > what we want... I don't want the maven and cpp visual studio
>> configuration
>> > to diverge and fall out of whack. The compilers should be the same.
>> >
>> > Cheers,
>> > Andrew
>> >
>> >
>> > On Thu, Aug 14, 2008 at 11:09 PM, Dan Tran <[EMAIL PROTECTED]> wrote:
>> >
>> >> native plugin does not use devcom, it uses MS compiler directly thru
>> >> envFactoryName
>> >>
>> >> there should be plenty to example in IT test cases if you pull the
>> source.
>> >>
>> >> -D
>> >>
>> >> On Thu, Aug 14, 2008 at 12:28 AM, Andrew Hughes <[EMAIL PROTECTED]>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > I'm trying to replace the following ant target to build some microsoft
>> >> > visual studio .net 2003 code. I am not a c++ person so I don't really
>> >> know
>> >> > what I am talking about! However there isn't any examples with the
>> >> > "Devenv.com" on the maven native site (
>> >> > http://mojo.codehaus.org/maven-native/native-maven-plugin/). I'm not
>> >> sure if
>> >> > the 2003 compiler is supported.
>> >> >
>> >> > Thanks fore reading.... on with the ant script.
>> >> >
>> >> >  <target name="build.exe" description="Compile to exe">
>> >> >   <exec executable="Devenv.com" dir="${module.path}"
>> failonerror="true">
>> >> >     <arg line="/build release &quot;${module.name}.sln&quot;" />
>> >> >   </exec>
>> >> >   <copy file="${module.path}\Release\${module.name}.exe"
>> >> > todir="${module.output.dir}" />
>> >> >  </target>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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]
>>
>>
>

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

Reply via email to