Hello,
I haven't managed to get the example from Peter Pilgrim's blog working. In
the example they use the ant task. The problem I faced was, that you have to
initialize the runtime with lot of properties and I wasn't feeling like
finding all the required properties.
Therefore I'm unsing the bat-file or shellscript included in each websphere
installation. It's setting up all the requiered properties. And in the poms
of my ejb projects it's looking like this.
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>verify</phase>
<configuration>
<tasks>
<property name="mvn.classpath" refid="
maven.runtime.classpath" />
<exec
executable="${custom.was.home}/bin/ejbdeploy.bat"
failonerror="true" os="Windows XP">
<arg value="${project.build.directory
}/${project.artifactId}-${project.version}.jar" />
<arg
value="${project.build.directory}/ejbdeply-working"
/>
<arg value="${project.build.directory
}/${project.artifactId}-${project.version}-OUTPUT.jar" />
<arg value="-cp" />
<arg value="${mvn.classpath}" />
</exec>
<exec
executable="${custom.was.home}/bin/ejbdeploy.sh"
failonerror="true" os="Linux">
<arg value="${project.build.directory
}/${project.artifactId}-${project.version}.jar" />
<arg
value="${project.build.directory}/ejbdeply-working"
/>
<arg value="${project.build.directory
}/${project.artifactId}-${project.version}-OUTPUT.jar" />
<arg value="-cp" />
<arg value="${mvn.classpath}" />
</exec>
<move file="${project.build.directory}/${
project.artifactId}-${project.version}.jar" tofile="${
project.build.directory}/${project.artifactId}-${project.version}-INPUT.jar"
/>
<move file="${project.build.directory}/${
project.artifactId}-${project.version}-OUTPUT.jar" tofile="${
project.build.directory}/${project.artifactId}-${project.version}.jar" />
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
It's working fine. The only condition you have is that you have access to a
Websphere installation on the machine you are building the ejb.
The ${custom.was.home} property is the path to the root directory of your
Websphere installation.
Hope this helps!
Kind Regards,
Thomas
On Jan 17, 2008 4:53 PM, David J. M. Karlsen <[EMAIL PROTECTED]> wrote:
> On Wed, 16 Jan 2008, Wendy Smoak wrote:
>
> Hmm, I'm running just fine with the IBM jdk from WebSphere 6.1:
>
> C:\data\felles\spring-utils>java -version
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20060511
> (SR2))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32
> j9vmwi3223-20060504 (JIT enabled)
> J9VM - 20060501_06428_lHdSMR
> JIT - 20060428_1800_r8
> GC - 20060501_AA)
> JCL - 20060511a
>
>
> > On Jan 16, 2008 6:19 AM, Jörg Schaible
> > <[EMAIL PROTECTED]> wrote:
> >
> >> For whatever reason, Maven 2 does not run on an IBM JDK.
> >
> > I don't see anything in JIRA about this. What issues have you run into?
>
>
> David J. M. Karlsen - +47 90 68 22 43
> http://www.davidkarlsen.com
> http://mp3.davidkarlsen.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
