HI All,
Thanks for your help.
I am able to build my JAR file by using following command.
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.2</version>
<executions>
<execution>
<id>install</id>
<phase>install</phase>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
<configuration>
<executable>C:\Documents and
Settings\DS100193\workspace\WorkCenterPlatformMavenProject\WPSEjb\WPSEjb.bat</executable>
</configuration>
</plugin>
Thanks all for your help. And special thanks to Stephen.
-Daivish.
On Thu, Aug 11, 2011 at 10:46 AM, Daivish Shah <[email protected]>wrote:
> What is the purpose for moving from Ant to Maven in such environments?
>
> The purpose is to maintain different versions and to identify which version
> of JAR or EAR has issue so we can identify it quickly.
>
> Thanks,
> daivish.
>
>
> On Thu, Aug 11, 2011 at 10:30 AM, Wayne Fay <[email protected]> wrote:
>
>> > We can't move all projects to MAVEN at this moment so idea is to convert
>> > some projects from ANT to MAVEN and slowly slowly we can implement or
>> > convert all project from ANT to MAVEN.
>>
>> You don't understand my point. I am not asking why you can't move ALL
>> your projects from Ant to Maven. I am asking why you are moving ANY
>> projects from Ant to Maven.
>>
>> I don't see how any of this work is giving you a better build
>> environment. You are simply trading complex Ant builds that work for
>> complex Maven builds that just call Ant that don't (right now at
>> least) work.
>>
>> What is the purpose for moving from Ant to Maven in such environments?
>>
>> Wayne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
