You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jo Support <jo...@gmail.com> on 2008/06/10 12:55:21 UTC

Maven & WebSphere 6.1

Hello folks,

I'm following the instructions from
http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating in
order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should have
the following jars under <was6home>/lib :

- wsanttasks.jar
- webservices.jar
- wsprofile.jar
- ffdc.jar
- wsdl4j.jar
- commons-logging-api.jar
- commons-discovery.jar
- ras.jar
- wsexception.jar
- emf.jar
- classloader.jar

But they're missing. I have

IBM WebSphere 6.1 AS Network Deployment

- Am I using a wrong version of WAS?
- Am I following an out-of-date how-to guide?

Thanks in advance,
Jo

Re: Maven & WebSphere 6.1

Posted by Marco Mistroni <mm...@gmail.com>.
Jo,
  my 2 cents here,
it *could* be, but i think except for ws specific jars, you shouuld be able
to fetch ther est
from maven repo.

hth
 marco

On Tue, Jun 10, 2008 at 11:55 AM, Jo Support <jo...@gmail.com> wrote:

> Hello folks,
>
> I'm following the instructions from
>
> http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integratingin
> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should have
> the following jars under <was6home>/lib :
>
> - wsanttasks.jar
> - webservices.jar
> - wsprofile.jar
> - ffdc.jar
> - wsdl4j.jar
> - commons-logging-api.jar
> - commons-discovery.jar
> - ras.jar
> - wsexception.jar
> - emf.jar
> - classloader.jar
>
> But they're missing. I have
>
> IBM WebSphere 6.1 AS Network Deployment
>
> - Am I using a wrong version of WAS?
> - Am I following an out-of-date how-to guide?
>
> Thanks in advance,
> Jo
>

Re: Maven & WebSphere 6.1

Posted by da...@davidkarlsen.com.
On Tue, 10 Jun 2008, Jo Support wrote:

> Hello folks,
>
> I'm following the instructions from
> http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating in
> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should have
> the following jars under <was6home>/lib :

This plugin might come in handy for you:
http://mojo.codehaus.org/was6-maven-plugin/


--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven & WebSphere 6.1

Posted by Lee Meador <le...@leemeador.com>.
Just a note to remind that the dependencies are different for WAS 6.0 and
6.1.

One particular difference is the "eclipse-like" paths to important jars in
6.1 that weren't there in 6.0. These paths look like paths to jars inside
eclipse plugins and have a "plugins" folder as one path component.

Thanks.

-- Lee

On Sun, Jun 29, 2008 at 8:06 PM, <Ch...@aami.com.au> wrote:

> Hi Jon,
>
>        Not to my knowledge. I used the list that RSA V7 uses as the
> WebSphere Application Server v6.1 Runtime classpath container, so that is
> what RSA uses itself to compile against. Which from Maven's point of view,
> it should be all that we need.
>
>        I've not run into issues with that list yet.
>



>
> -Chris
>
> news <ne...@ger.gmane.org> wrote on 27/06/2008 23:09:09:
>
> > Hi Chris
> >
> > This is exactly what i was looking for - you mentioned below that this
> > was part of the batch file you use.  Are there any WAS 6.1 libraries
> > missing from the list below.
> >
> > Cheers
> >
> > Jon
> >
> > Chris_Graham@aami.com.au wrote:
> > > Hi.
> > >
> > > I do not get maven to actually generate the EJB deployment code,
> WebSphere
> > > itself will do it at deployment time, so I do. If nothing else, this
> will
> > > give you a list of the jars that you need.
> > >
> > > Using RSA V7, it defines a classpath container that has all of the
> > > necessary jars in it needed to support complete websphere 6.1
> development.
> > > What I have done is to define a runtime library/aggregrate pom for the
>
> > > websphere runtime. I have not needed to define one for the JRE.
> > >
> > > This is part of a batch file that I used to copy the necessary runtime
>
> > > files (as defined in the classpath container) to a temp holding dir,
> and
> > > then install/deploy them into your repo.
> > >
> > > md C:\Temp\Maven\WAS61
> > >
> > > copy "C:\Program
> > > Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > > Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > >
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar"
>
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > > Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > >
>
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar"
>
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > >
>
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar"
>
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > >
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > >
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar"
>
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > >
>
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar"
>
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > > Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar"
> > > C:\Temp\Maven\WAS61
> > > copy "C:\Program
> > >
>
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar"
>
> > > C:\Temp\Maven\WAS61
> > >
> > > That should have these files in the C:\Temp\maven\WAS61 dir:
> > >
> > >             50,767 bootstrap.jar
> > >            430,143 com.ibm.mq.jar
> > >          1,238,366 com.ibm.mqjms.jar
> > >             77,523 com.ibm.ws.ejbportable_6.1.0.jar
> > >          3,355,425 com.ibm.ws.emf_2.1.0.jar
> > >            622,223 com.ibm.ws.portletcontainer_2.0.0.jar
> > >          1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
> > >         53,066,732 com.ibm.ws.runtime_6.1.0.jar
> > >         11,771,638 com.ibm.ws.sib.server_2.0.0.jar
> > >          1,179,014 com.ibm.ws.sip.container_6.1.0.jar
> > >          9,221,353 com.ibm.ws.wccm_6.1.0.jar
> > >          3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
> > >            546,698 j2ee.jar
> > >            202,255 mail-impl.jar
> > >             72,730 marshall.jar
> > >
> > > I deployed them to the repo (in this case proximity) using:
> > >
> > > call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar
> > > -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq
> > > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar
> > > -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms
> > > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=bootstrap.jar
> > > -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap
> > > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=j2ee.jar
> > > -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee  -Dversion=6.1
>
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=mail-impl.jar
> > > -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl
> > > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=marshall.jar
> > > -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall
> -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> > > -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.emf_2.1.0
> > >     -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file
> -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> > > -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> > > -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> > > -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> > > -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> > > -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.wccm_6.1.0
> > >        -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > > call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar
> > > -DgroupId=com.ibm.websphere.appserver
> > > -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1
> > > -Dpackaging=jar -DgeneratePom=true
> > >
> > > I created a pom that aggregrates them all together:
> > >
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <project xmlns="http://maven.apache.org/POM/4.0.0"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > > http://maven.apache.org/maven-v4_0_0.xsd">
> > >     <modelVersion>4.0.0</modelVersion>
> > >     <groupId>com.ibm.websphere.appserver</groupId>
> > >     <artifactId>runtime</artifactId>
> > >     <version>6.1</version>
> > >     <packaging>pom</packaging>
> > >     <description>Library POM for the WebSphere v6.1
> runtime.</description>
> > >     <dependencies>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.mq</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.mqjms</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>bootstrap</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>j2ee</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>mail-impl</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>marshall</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >         <dependency>
> > >           <groupId>com.ibm.websphere.appserver</groupId>
> > >           <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
> > >           <version>6.1</version>
> > >         </dependency>
> > >     </dependencies>
> > > </project>
> > >
> > > I deployed it:
> > >
> > > call mvn deploy:deploy-file -Dfile=websphere-61.pom
> > > -DpomFile=websphere-61.pom
> > >
> > > So, then all I need to do it to add this dependency to my code, and
> we're
> > > all done.
> > >
> > >         <dependency>
> > >             <groupId>com.ibm.websphere.appserver</groupId>
> > >             <artifactId>runtime</artifactId>
> > >             <version>6.1</version>
> > >             <type>pom</type>
> > >             <scope>provided</scope>
> > >         </dependency>
> > >
> > > Hope this helps.
> > >
> > > -Chris
> > >
> > > "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
> > >
> > >> Hello folks,
> > >>
> > >> I'm following the instructions from
> > >>
> > >
>
> http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating
>
> > > in
> > >> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I
> should
> > > have
> > >> the following jars under <was6home>/lib :
> > >>
> > >> - wsanttasks.jar
> > >> - webservices.jar
> > >> - wsprofile.jar
> > >> - ffdc.jar
> > >> - wsdl4j.jar
> > >> - commons-logging-api.jar
> > >> - commons-discovery.jar
> > >> - ras.jar
> > >> - wsexception.jar
> > >> - emf.jar
> > >> - classloader.jar
> > >>
> > >> But they're missing. I have
> > >>
> > >> IBM WebSphere 6.1 AS Network Deployment
> > >>
> > >> - Am I using a wrong version of WAS?
> > >> - Am I following an out-of-date how-to guide?
> > >>
> > >> Thanks in advance,
> > >> Jo
> > >>
> > >>
> > >> The following message has been automatically added by the Internet
> mail
> > >> gateway to comply with the Group's Information Security requirements.
> > >>
> > >> "This e-mail has arrived via the Internet, and therefore you should
> be
> > >> cautious about its origin and content. Replies which contain
> sensitive
> > >> information and / or legal/contractual obligations are particularly
> > > vulnerable.
> > >> In these cases you should not reply unless you are authorised to do
> so,
> > >> and adequate encryption is employed."
> > >>
> > >> If you have any questions, please contact the IS Service Desk.
> > >
> > > **********************************************************************
> > > CAUTION - This message is intended for the addressee named above. It
> > may contain privileged or confidential information.
> > >
> > > If you are not the intended recipient of this message you must:
> > > - Not use, copy, distribute or disclose it to anyone other than the
> addressee;
> > > - Notify the sender via return email; and
> > > - Delete the message (and any related attachments) from your computer
> > immediately.
> > >
> > > Internet emails are not necessarily secure. Australian Associated
> > Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related
> > entities, do not accept responsibility for changes made to this message
> > after it was sent.
> > >
> > > Unless otherwise stated, views expressed within this email are the
> > author's own and do not represent those of AAMI.
> > > **********************************************************************
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > The following message has been automatically added by the Internet mail
> > gateway to comply with the Group's Information Security requirements.
> >
> > "This e-mail has arrived via the Internet, and therefore you should be
> > cautious about its origin and content. Replies which contain sensitive
> > information and / or legal/contractual obligations are particularly
> vulnerable.
> >
> > In these cases you should not reply unless you are authorised to do so,
> > and adequate encryption is employed."
> >
> > If you have any questions, please contact the IS Service Desk.
>
>
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It may
> contain privileged or confidential information.
>
> If you are not the intended recipient of this message you must:
> - Not use, copy, distribute or disclose it to anyone other than the
> addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer
> immediately.
>
> Internet emails are not necessarily secure. Australian Associated Motors
> Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not
> accept responsibility for changes made to this message after it was sent.
>
> Unless otherwise stated, views expressed within this email are the author's
> own and do not represent those of AAMI.
> **********************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

Re: AW: Re: Maven & WebSphere 6.1

Posted by Ch...@aami.com.au.
Hi Marc,

        I've not used that plugin sorry.

-Chris


"Lustig, Marc (Allianz Deutschland, externer Mitarbeiter)" 
<EX...@ALLIANZ.DE> wrote on 28/06/2008 00:11:50:

> re was6-plugin:
> 
> it needs a local was6-installation.
> has anybody tried to track down the files which are actually necessary 
to
> keep the was6-plugin running (I guess some was-ant-tasks.jar, etc.) ?
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: news [mailto:news@ger.gmane.org] Im Auftrag von Jon SlinnHawkins
> Gesendet: Freitag, 27. Juni 2008 15:09
> An: users@maven.apache.org
> Betreff: Re: Maven & WebSphere 6.1
> 
> Hi Chris
> 
> This is exactly what i was looking for - you mentioned below that this 
> was part of the batch file you use.  Are there any WAS 6.1 libraries 
> missing from the list below.
> 
> Cheers
> 
> Jon
> 
> Chris_Graham@aami.com.au wrote:
> > Hi.
> > 
> > I do not get maven to actually generate the EJB deployment code, 
WebSphere 
> > itself will do it at deployment time, so I do. If nothing else, this 
will 
> > give you a list of the jars that you need.
> > 
> > Using RSA V7, it defines a classpath container that has all of the 
> > necessary jars in it needed to support complete websphere 6.1 
development. 
> > What I have done is to define a runtime library/aggregrate pom for the 

> > websphere runtime. I have not needed to define one for the JRE.
> > 
> > This is part of a batch file that I used to copy the necessary runtime 

> > files (as defined in the classpath container) to a temp holding dir, 
and 
> > then install/deploy them into your repo.
> > 
> > md C:\Temp\Maven\WAS61
> > 
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar" 

> > C:\Temp\Maven\WAS61
> > 
> > That should have these files in the C:\Temp\maven\WAS61 dir:
> > 
> >             50,767 bootstrap.jar
> >            430,143 com.ibm.mq.jar
> >          1,238,366 com.ibm.mqjms.jar
> >             77,523 com.ibm.ws.ejbportable_6.1.0.jar
> >          3,355,425 com.ibm.ws.emf_2.1.0.jar
> >            622,223 com.ibm.ws.portletcontainer_2.0.0.jar
> >          1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
> >         53,066,732 com.ibm.ws.runtime_6.1.0.jar
> >         11,771,638 com.ibm.ws.sib.server_2.0.0.jar
> >          1,179,014 com.ibm.ws.sip.container_6.1.0.jar
> >          9,221,353 com.ibm.ws.wccm_6.1.0.jar
> >          3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
> >            546,698 j2ee.jar
> >            202,255 mail-impl.jar
> >             72,730 marshall.jar
> > 
> > I deployed them to the repo (in this case proximity) using:
> > 
> > call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=bootstrap.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=j2ee.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee  -Dversion=6.1 

> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=mail-impl.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=marshall.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall 
-Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.emf_2.1.0 
> >     -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file 
-Dfile=com.ibm.ws.portletcontainer_2.0.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.wccm_6.1.0 
> >        -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > 
> > I created a pom that aggregrates them all together:
> > 
> > <?xml version="1.0" encoding="UTF-8"?>
> > <project xmlns="http://maven.apache.org/POM/4.0.0" 
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> > http://maven.apache.org/maven-v4_0_0.xsd">
> >     <modelVersion>4.0.0</modelVersion>
> >     <groupId>com.ibm.websphere.appserver</groupId>
> >     <artifactId>runtime</artifactId>
> >     <version>6.1</version>
> >     <packaging>pom</packaging>
> >     <description>Library POM for the WebSphere v6.1 
runtime.</description>
> >     <dependencies>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.mq</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.mqjms</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>bootstrap</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>j2ee</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>mail-impl</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>marshall</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >     </dependencies>
> > </project>
> > 
> > I deployed it:
> > 
> > call mvn deploy:deploy-file -Dfile=websphere-61.pom 
> > -DpomFile=websphere-61.pom
> > 
> > So, then all I need to do it to add this dependency to my code, and 
we're 
> > all done.
> > 
> >         <dependency>
> >             <groupId>com.ibm.websphere.appserver</groupId>
> >             <artifactId>runtime</artifactId>
> >             <version>6.1</version>
> >             <type>pom</type>
> >             <scope>provided</scope>
> >         </dependency>
> > 
> > Hope this helps.
> > 
> > -Chris
> > 
> > "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
> > 
> >> Hello folks,
> >>
> >> I'm following the instructions from
> >>
> > 
http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating 

> > in
> >> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I 
should 
> > have
> >> the following jars under <was6home>/lib :
> >>
> >> - wsanttasks.jar
> >> - webservices.jar
> >> - wsprofile.jar
> >> - ffdc.jar
> >> - wsdl4j.jar
> >> - commons-logging-api.jar
> >> - commons-discovery.jar
> >> - ras.jar
> >> - wsexception.jar
> >> - emf.jar
> >> - classloader.jar
> >>
> >> But they're missing. I have
> >>
> >> IBM WebSphere 6.1 AS Network Deployment
> >>
> >> - Am I using a wrong version of WAS?
> >> - Am I following an out-of-date how-to guide?
> >>
> >> Thanks in advance,
> >> Jo
> >>
> >>
> >> The following message has been automatically added by the Internet 
mail 
> >> gateway to comply with the Group's Information Security requirements.
> >>
> >> "This e-mail has arrived via the Internet, and therefore you should 
be 
> >> cautious about its origin and content. Replies which contain 
sensitive 
> >> information and / or legal/contractual obligations are particularly 
> > vulnerable.
> >> In these cases you should not reply unless you are authorised to do 
so, 
> >> and adequate encryption is employed."
> >>
> >> If you have any questions, please contact the IS Service Desk.
> > 
> > **********************************************************************
> > CAUTION - This message is intended for the addressee named above. It 
> may contain privileged or confidential information. 
> > 
> > If you are not the intended recipient of this message you must: 
> > - Not use, copy, distribute or disclose it to anyone other than the 
addressee;
> > - Notify the sender via return email; and
> > - Delete the message (and any related attachments) from your computer 
> immediately.
> > 
> > Internet emails are not necessarily secure. Australian Associated 
> Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related 
> entities, do not accept responsibility for changes made to this message 
> after it was sent.
> > 
> > Unless otherwise stated, views expressed within this email are the 
> author's own and do not represent those of AAMI.
> > **********************************************************************
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> The following message has been automatically added by the Internet mail 
> gateway to comply with the Group's Information Security requirements.
> 
> "This e-mail has arrived via the Internet, and therefore you should be 
> cautious about its origin and content. Replies which contain sensitive 
> information and / or legal/contractual obligations are particularly 
vulnerable.
> 
> In these cases you should not reply unless you are authorised to do so, 
> and adequate encryption is employed."
> 
> If you have any questions, please contact the IS Service Desk.


**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. 

If you are not the intended recipient of this message you must: 
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.

Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.

Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


AW: Re: Maven & WebSphere 6.1

Posted by "Lustig, Marc (Allianz Deutschland, externer Mitarbeiter)" <EX...@ALLIANZ.DE>.
re was6-plugin:

it needs a local was6-installation.
has anybody tried to track down the files which are actually necessary to keep the was6-plugin running (I guess some was-ant-tasks.jar, etc.) ?
 

-----Ursprüngliche Nachricht-----
Von: news [mailto:news@ger.gmane.org] Im Auftrag von Jon SlinnHawkins
Gesendet: Freitag, 27. Juni 2008 15:09
An: users@maven.apache.org
Betreff: Re: Maven & WebSphere 6.1

Hi Chris

This is exactly what i was looking for - you mentioned below that this 
was part of the batch file you use.  Are there any WAS 6.1 libraries 
missing from the list below.

Cheers

Jon

Chris_Graham@aami.com.au wrote:
> Hi.
> 
> I do not get maven to actually generate the EJB deployment code, WebSphere 
> itself will do it at deployment time, so I do. If nothing else, this will 
> give you a list of the jars that you need.
> 
> Using RSA V7, it defines a classpath container that has all of the 
> necessary jars in it needed to support complete websphere 6.1 development. 
> What I have done is to define a runtime library/aggregrate pom for the 
> websphere runtime. I have not needed to define one for the JRE.
> 
> This is part of a batch file that I used to copy the necessary runtime 
> files (as defined in the classpath container) to a temp holding dir, and 
> then install/deploy them into your repo.
> 
> md C:\Temp\Maven\WAS61
> 
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar" 
> C:\Temp\Maven\WAS61
> 
> That should have these files in the C:\Temp\maven\WAS61 dir:
> 
>             50,767 bootstrap.jar
>            430,143 com.ibm.mq.jar
>          1,238,366 com.ibm.mqjms.jar
>             77,523 com.ibm.ws.ejbportable_6.1.0.jar
>          3,355,425 com.ibm.ws.emf_2.1.0.jar
>            622,223 com.ibm.ws.portletcontainer_2.0.0.jar
>          1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
>         53,066,732 com.ibm.ws.runtime_6.1.0.jar
>         11,771,638 com.ibm.ws.sib.server_2.0.0.jar
>          1,179,014 com.ibm.ws.sip.container_6.1.0.jar
>          9,221,353 com.ibm.ws.wccm_6.1.0.jar
>          3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
>            546,698 j2ee.jar
>            202,255 mail-impl.jar
>             72,730 marshall.jar
> 
> I deployed them to the repo (in this case proximity) using:
> 
> call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=bootstrap.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=j2ee.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee  -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=mail-impl.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=marshall.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall  -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0    
>     -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.wccm_6.1.0   
>        -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> 
> I created a pom that aggregrates them all together:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0" 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/maven-v4_0_0.xsd">
>     <modelVersion>4.0.0</modelVersion>
>     <groupId>com.ibm.websphere.appserver</groupId>
>     <artifactId>runtime</artifactId>
>     <version>6.1</version>
>     <packaging>pom</packaging>
>     <description>Library POM for the WebSphere v6.1 runtime.</description>
>     <dependencies>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mq</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mqjms</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>bootstrap</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>j2ee</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>mail-impl</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>marshall</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>     </dependencies>
> </project>
> 
> I deployed it:
> 
> call mvn deploy:deploy-file -Dfile=websphere-61.pom 
> -DpomFile=websphere-61.pom
> 
> So, then all I need to do it to add this dependency to my code, and we're 
> all done.
> 
>         <dependency>
>             <groupId>com.ibm.websphere.appserver</groupId>
>             <artifactId>runtime</artifactId>
>             <version>6.1</version>
>             <type>pom</type>
>             <scope>provided</scope>
>         </dependency>
> 
> Hope this helps.
> 
> -Chris
> 
> "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
> 
>> Hello folks,
>>
>> I'm following the instructions from
>>
> http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating 
> in
>> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should 
> have
>> the following jars under <was6home>/lib :
>>
>> - wsanttasks.jar
>> - webservices.jar
>> - wsprofile.jar
>> - ffdc.jar
>> - wsdl4j.jar
>> - commons-logging-api.jar
>> - commons-discovery.jar
>> - ras.jar
>> - wsexception.jar
>> - emf.jar
>> - classloader.jar
>>
>> But they're missing. I have
>>
>> IBM WebSphere 6.1 AS Network Deployment
>>
>> - Am I using a wrong version of WAS?
>> - Am I following an out-of-date how-to guide?
>>
>> Thanks in advance,
>> Jo
>>
>>
>> The following message has been automatically added by the Internet mail 
>> gateway to comply with the Group's Information Security requirements.
>>
>> "This e-mail has arrived via the Internet, and therefore you should be 
>> cautious about its origin and content. Replies which contain sensitive 
>> information and / or legal/contractual obligations are particularly 
> vulnerable.
>> In these cases you should not reply unless you are authorised to do so, 
>> and adequate encryption is employed."
>>
>> If you have any questions, please contact the IS Service Desk.
> 
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. 
> 
> If you are not the intended recipient of this message you must: 
> - Not use, copy, distribute or disclose it to anyone other than the addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer immediately.
> 
> Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.
> 
> Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
> **********************************************************************


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven & WebSphere 6.1

Posted by Ch...@aami.com.au.
Hi Jon,

        Not to my knowledge. I used the list that RSA V7 uses as the 
WebSphere Application Server v6.1 Runtime classpath container, so that is 
what RSA uses itself to compile against. Which from Maven's point of view, 
it should be all that we need.

        I've not run into issues with that list yet.

-Chris

news <ne...@ger.gmane.org> wrote on 27/06/2008 23:09:09:

> Hi Chris
> 
> This is exactly what i was looking for - you mentioned below that this 
> was part of the batch file you use.  Are there any WAS 6.1 libraries 
> missing from the list below.
> 
> Cheers
> 
> Jon
> 
> Chris_Graham@aami.com.au wrote:
> > Hi.
> > 
> > I do not get maven to actually generate the EJB deployment code, 
WebSphere 
> > itself will do it at deployment time, so I do. If nothing else, this 
will 
> > give you a list of the jars that you need.
> > 
> > Using RSA V7, it defines a classpath container that has all of the 
> > necessary jars in it needed to support complete websphere 6.1 
development. 
> > What I have done is to define a runtime library/aggregrate pom for the 

> > websphere runtime. I have not needed to define one for the JRE.
> > 
> > This is part of a batch file that I used to copy the necessary runtime 

> > files (as defined in the classpath container) to a temp holding dir, 
and 
> > then install/deploy them into your repo.
> > 
> > md C:\Temp\Maven\WAS61
> > 
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar" 

> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar" 
> > C:\Temp\Maven\WAS61
> > copy "C:\Program 
> > 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar" 

> > C:\Temp\Maven\WAS61
> > 
> > That should have these files in the C:\Temp\maven\WAS61 dir:
> > 
> >             50,767 bootstrap.jar
> >            430,143 com.ibm.mq.jar
> >          1,238,366 com.ibm.mqjms.jar
> >             77,523 com.ibm.ws.ejbportable_6.1.0.jar
> >          3,355,425 com.ibm.ws.emf_2.1.0.jar
> >            622,223 com.ibm.ws.portletcontainer_2.0.0.jar
> >          1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
> >         53,066,732 com.ibm.ws.runtime_6.1.0.jar
> >         11,771,638 com.ibm.ws.sib.server_2.0.0.jar
> >          1,179,014 com.ibm.ws.sip.container_6.1.0.jar
> >          9,221,353 com.ibm.ws.wccm_6.1.0.jar
> >          3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
> >            546,698 j2ee.jar
> >            202,255 mail-impl.jar
> >             72,730 marshall.jar
> > 
> > I deployed them to the repo (in this case proximity) using:
> > 
> > call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=bootstrap.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=j2ee.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee  -Dversion=6.1 

> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=mail-impl.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl 
> > -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=marshall.jar 
> > -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall 
-Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.emf_2.1.0 
> >     -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file 
-Dfile=com.ibm.ws.portletcontainer_2.0.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.wccm_6.1.0 
> >        -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> > call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar 
> > -DgroupId=com.ibm.websphere.appserver 
> > -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1 
> > -Dpackaging=jar -DgeneratePom=true
> > 
> > I created a pom that aggregrates them all together:
> > 
> > <?xml version="1.0" encoding="UTF-8"?>
> > <project xmlns="http://maven.apache.org/POM/4.0.0" 
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> > http://maven.apache.org/maven-v4_0_0.xsd">
> >     <modelVersion>4.0.0</modelVersion>
> >     <groupId>com.ibm.websphere.appserver</groupId>
> >     <artifactId>runtime</artifactId>
> >     <version>6.1</version>
> >     <packaging>pom</packaging>
> >     <description>Library POM for the WebSphere v6.1 
runtime.</description>
> >     <dependencies>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.mq</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.mqjms</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>bootstrap</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>j2ee</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>mail-impl</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>marshall</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >         <dependency>
> >           <groupId>com.ibm.websphere.appserver</groupId>
> >           <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
> >           <version>6.1</version>
> >         </dependency>
> >     </dependencies>
> > </project>
> > 
> > I deployed it:
> > 
> > call mvn deploy:deploy-file -Dfile=websphere-61.pom 
> > -DpomFile=websphere-61.pom
> > 
> > So, then all I need to do it to add this dependency to my code, and 
we're 
> > all done.
> > 
> >         <dependency>
> >             <groupId>com.ibm.websphere.appserver</groupId>
> >             <artifactId>runtime</artifactId>
> >             <version>6.1</version>
> >             <type>pom</type>
> >             <scope>provided</scope>
> >         </dependency>
> > 
> > Hope this helps.
> > 
> > -Chris
> > 
> > "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
> > 
> >> Hello folks,
> >>
> >> I'm following the instructions from
> >>
> > 
http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating 

> > in
> >> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I 
should 
> > have
> >> the following jars under <was6home>/lib :
> >>
> >> - wsanttasks.jar
> >> - webservices.jar
> >> - wsprofile.jar
> >> - ffdc.jar
> >> - wsdl4j.jar
> >> - commons-logging-api.jar
> >> - commons-discovery.jar
> >> - ras.jar
> >> - wsexception.jar
> >> - emf.jar
> >> - classloader.jar
> >>
> >> But they're missing. I have
> >>
> >> IBM WebSphere 6.1 AS Network Deployment
> >>
> >> - Am I using a wrong version of WAS?
> >> - Am I following an out-of-date how-to guide?
> >>
> >> Thanks in advance,
> >> Jo
> >>
> >>
> >> The following message has been automatically added by the Internet 
mail 
> >> gateway to comply with the Group's Information Security requirements.
> >>
> >> "This e-mail has arrived via the Internet, and therefore you should 
be 
> >> cautious about its origin and content. Replies which contain 
sensitive 
> >> information and / or legal/contractual obligations are particularly 
> > vulnerable.
> >> In these cases you should not reply unless you are authorised to do 
so, 
> >> and adequate encryption is employed."
> >>
> >> If you have any questions, please contact the IS Service Desk.
> > 
> > **********************************************************************
> > CAUTION - This message is intended for the addressee named above. It 
> may contain privileged or confidential information. 
> > 
> > If you are not the intended recipient of this message you must: 
> > - Not use, copy, distribute or disclose it to anyone other than the 
addressee;
> > - Notify the sender via return email; and
> > - Delete the message (and any related attachments) from your computer 
> immediately.
> > 
> > Internet emails are not necessarily secure. Australian Associated 
> Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related 
> entities, do not accept responsibility for changes made to this message 
> after it was sent.
> > 
> > Unless otherwise stated, views expressed within this email are the 
> author's own and do not represent those of AAMI.
> > **********************************************************************
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> The following message has been automatically added by the Internet mail 
> gateway to comply with the Group's Information Security requirements.
> 
> "This e-mail has arrived via the Internet, and therefore you should be 
> cautious about its origin and content. Replies which contain sensitive 
> information and / or legal/contractual obligations are particularly 
vulnerable.
> 
> In these cases you should not reply unless you are authorised to do so, 
> and adequate encryption is employed."
> 
> If you have any questions, please contact the IS Service Desk.


**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. 

If you are not the intended recipient of this message you must: 
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.

Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.

Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven & WebSphere 6.1

Posted by Jon SlinnHawkins <j....@elsevier.com>.
Hi Chris

This is exactly what i was looking for - you mentioned below that this 
was part of the batch file you use.  Are there any WAS 6.1 libraries 
missing from the list below.

Cheers

Jon

Chris_Graham@aami.com.au wrote:
> Hi.
> 
> I do not get maven to actually generate the EJB deployment code, WebSphere 
> itself will do it at deployment time, so I do. If nothing else, this will 
> give you a list of the jars that you need.
> 
> Using RSA V7, it defines a classpath container that has all of the 
> necessary jars in it needed to support complete websphere 6.1 development. 
> What I have done is to define a runtime library/aggregrate pom for the 
> websphere runtime. I have not needed to define one for the JRE.
> 
> This is part of a batch file that I used to copy the necessary runtime 
> files (as defined in the classpath container) to a temp holding dir, and 
> then install/deploy them into your repo.
> 
> md C:\Temp\Maven\WAS61
> 
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar" 
> C:\Temp\Maven\WAS61
> copy "C:\Program 
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar" 
> C:\Temp\Maven\WAS61
> 
> That should have these files in the C:\Temp\maven\WAS61 dir:
> 
>             50,767 bootstrap.jar
>            430,143 com.ibm.mq.jar
>          1,238,366 com.ibm.mqjms.jar
>             77,523 com.ibm.ws.ejbportable_6.1.0.jar
>          3,355,425 com.ibm.ws.emf_2.1.0.jar
>            622,223 com.ibm.ws.portletcontainer_2.0.0.jar
>          1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
>         53,066,732 com.ibm.ws.runtime_6.1.0.jar
>         11,771,638 com.ibm.ws.sib.server_2.0.0.jar
>          1,179,014 com.ibm.ws.sip.container_6.1.0.jar
>          9,221,353 com.ibm.ws.wccm_6.1.0.jar
>          3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
>            546,698 j2ee.jar
>            202,255 mail-impl.jar
>             72,730 marshall.jar
> 
> I deployed them to the repo (in this case proximity) using:
> 
> call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=bootstrap.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=j2ee.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee  -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=mail-impl.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl  
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=marshall.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall  -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0    
>     -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar 
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.wccm_6.1.0   
>        -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar 
> -DgroupId=com.ibm.websphere.appserver 
> -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1 
> -Dpackaging=jar -DgeneratePom=true
> 
> I created a pom that aggregrates them all together:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0" 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/maven-v4_0_0.xsd">
>     <modelVersion>4.0.0</modelVersion>
>     <groupId>com.ibm.websphere.appserver</groupId>
>     <artifactId>runtime</artifactId>
>     <version>6.1</version>
>     <packaging>pom</packaging>
>     <description>Library POM for the WebSphere v6.1 runtime.</description>
>     <dependencies>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mq</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mqjms</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>bootstrap</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>j2ee</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>mail-impl</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>marshall</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>     </dependencies>
> </project>
> 
> I deployed it:
> 
> call mvn deploy:deploy-file -Dfile=websphere-61.pom 
> -DpomFile=websphere-61.pom
> 
> So, then all I need to do it to add this dependency to my code, and we're 
> all done.
> 
>         <dependency>
>             <groupId>com.ibm.websphere.appserver</groupId>
>             <artifactId>runtime</artifactId>
>             <version>6.1</version>
>             <type>pom</type>
>             <scope>provided</scope>
>         </dependency>
> 
> Hope this helps.
> 
> -Chris
> 
> "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
> 
>> Hello folks,
>>
>> I'm following the instructions from
>>
> http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating 
> in
>> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should 
> have
>> the following jars under <was6home>/lib :
>>
>> - wsanttasks.jar
>> - webservices.jar
>> - wsprofile.jar
>> - ffdc.jar
>> - wsdl4j.jar
>> - commons-logging-api.jar
>> - commons-discovery.jar
>> - ras.jar
>> - wsexception.jar
>> - emf.jar
>> - classloader.jar
>>
>> But they're missing. I have
>>
>> IBM WebSphere 6.1 AS Network Deployment
>>
>> - Am I using a wrong version of WAS?
>> - Am I following an out-of-date how-to guide?
>>
>> Thanks in advance,
>> Jo
>>
>>
>> The following message has been automatically added by the Internet mail 
>> gateway to comply with the Group's Information Security requirements.
>>
>> "This e-mail has arrived via the Internet, and therefore you should be 
>> cautious about its origin and content. Replies which contain sensitive 
>> information and / or legal/contractual obligations are particularly 
> vulnerable.
>> In these cases you should not reply unless you are authorised to do so, 
>> and adequate encryption is employed."
>>
>> If you have any questions, please contact the IS Service Desk.
> 
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. 
> 
> If you are not the intended recipient of this message you must: 
> - Not use, copy, distribute or disclose it to anyone other than the addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer immediately.
> 
> Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.
> 
> Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
> **********************************************************************


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven & WebSphere 6.1

Posted by Jon Seymour <jo...@gmail.com>.
We are doing something similar in order to take advantage of
WebSphere's Wsdl2Java ant task implementation as part of our Maven
build. We store the WSDL in source control and generate the derived
Java types with the Maven build. As with Chris' case, we don't need an
actual WebSphere instance in the build environment, just the jars
extracted from the runtime [ pom for WebSphere 6.0 included below ]

We see the chief advantage of doing is that we can are guaranteed to
detect gross inconsistencies between the WSDL and Java at build time,
rather than runtime which is possible if one relies on a manually
initiated IDE-centric process to generate the Java from the WSDL.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>org.example</groupId>
	<artifactId>wsdl2java-support</artifactId>
	<packaging>pom</packaging>
	<name>WSDL Generation Support</name>
	<version>1.0-SNAPSHOT</version>
	<description>
		Contains the dependencies required to support WSDL generation during
the Maven build.
	</description>
	<dependencies>
		<dependency>
			<groupId>ant-contrib</groupId>
			<artifactId>ant-contrib</artifactId>
			<version>1.0b2</version>
		</dependency>
		<dependency>
			<groupId>ant</groupId>
			<artifactId>ant-trax</artifactId>
			<version>1.6.5</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>wsanttasks</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>ffdc</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>webservices</artifactId>
			<version>6.0.2.19</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>bootstrap</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>commons-logging</groupId>
			<artifactId>commons-logging</artifactId>
			<version>1.0.4</version>
		</dependency>
		<dependency>
			<groupId>commons-discovery</groupId>
			<artifactId>commons-discovery</artifactId>
			<version>0.4</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>emf</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>wccm_base</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>deployutils</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>classloader</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>wsdl4j</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>ras</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>org.example.dependencies</groupId>
			<artifactId>wsexception</artifactId>
			<version>6.0.2.25</version>
		</dependency>
		<dependency>
			<groupId>javax.j2ee</groupId>
			<artifactId>j2ee</artifactId>
			<version>1.4</version>
		</dependency>
	</dependencies>
</project>

jon seymour
IBM GBS (Sydney)

On Fri, Jun 13, 2008 at 10:32 AM,  <Ch...@aami.com.au> wrote:
> Hello Siarhei.
>
> No, we don't need to generate the stubs and ties in the IDE for a remote
> deployment. However, obviously you would have to do that when using the
> local test environment, and I use the IDE to do that. It is much easier
> (and more natural for me at least) to have the IDE to generate such things
> than to use maven for that task. So I simply skip it.
>
> We do not deploy from a CI environment, and probably never will do so. All
> (most?) of our application communicate with one or more mainframes, and
> they sometimes need to deploy their code as well... :-)  That would not
> work from a CI environment, as it requires more manual integration with
> other code (on the M/F). However, if the app was _entirely_ self
> contained, ie did everything itself and have no other external links etc,
> then I may consider gettting the build to do it, but at this point, I
> don't see the point.
>
> Basically, the model that I have in my head at the moment, is that we'll
> use CI to automate the builds, run the tests, produce the reports, and
> (when I work out how to) upload the ear to the remote server but not
> deploy it.
>
> We have a web app (deploy site) that allows us deploy our ear artifacts to
> the necessary instances, retrieve logs from production etc. That is what
> we have to use to deploy apps, that we can only do in our system test
> (real websphere on AIX) env. We have a separate team that manages the
> websphere environment for us.
>
> When we deploy, and the stubs and ties are done for us, here is the
> output:
>
> ADMA5018I: The EJBDeploy command is running on enterprise archive (EAR)
> file /tmp/app38179.ear.
>
> Starting workbench.
>
> framework search path: /ibmapp2/websphere61/base/deploytool/itp/plugins
>
> Creating the project.
>
> Deploying jar DiallerEJB-1.0-SNAPSHOT
>
> Generating deployment code
>
> Invoking RMIC.
>
> Writing output file
>
> Shutting down workbench.
>
> EJBDeploy complete.
> 0 Errors, 0 Warnings, 0 Informational Messages
>
> ADMA5007I: The EJBDeploy command completed on
> /ibmapp2/websphere61/deploymgr/wstemp/wstemp/app_11a7f4e92be/dpl/dpl_dial.ear
>
> I would recommend that you (well, everyone really) do a manual deployment
> of an ear file using the admin console, just so that they understand what
> is done and the issues involved.
>
> -Chris
>
> "Siarhei Dudzin" <si...@gmail.com> wrote on 13/06/2008 08:09:36:
>
>> Hi Chris,
>>
>> This is very interesting approach. Does that mean you have to actually
>> generate stubs&sceletons in IDE before you can build with maven?
>> How do you deploy your apps to a server in CI environment? Do you use
> hot
>> deployment (then you might have timing issues) or do you not deploy at
> all
>> and only do unit testing?
>>
>>
>> Regards,
>> Siarhei
>>
>> On Wed, Jun 11, 2008 at 3:35 AM, <Ch...@aami.com.au> wrote:
>>
>> > Hi.
>> >
>> > I do not get maven to actually generate the EJB deployment code,
> WebSphere
>> > itself will do it at deployment time, so I do. If nothing else, this
> will
>> > give you a list of the jars that you need.
>> >
>>
>>
>> The following message has been automatically added by the Internet mail
>> gateway to comply with the Group's Information Security requirements.
>>
>> "This e-mail has arrived via the Internet, and therefore you should be
>> cautious about its origin and content. Replies which contain sensitive
>> information and / or legal/contractual obligations are particularly
> vulnerable.
>>
>> In these cases you should not reply unless you are authorised to do so,
>> and adequate encryption is employed."
>>
>> If you have any questions, please contact the IS Service Desk.
>
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information.
>
> If you are not the intended recipient of this message you must:
> - Not use, copy, distribute or disclose it to anyone other than the addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer immediately.
>
> Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.
>
> Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
> **********************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven & WebSphere 6.1

Posted by Ch...@aami.com.au.
Hello Siarhei.

No, we don't need to generate the stubs and ties in the IDE for a remote 
deployment. However, obviously you would have to do that when using the 
local test environment, and I use the IDE to do that. It is much easier 
(and more natural for me at least) to have the IDE to generate such things 
than to use maven for that task. So I simply skip it.

We do not deploy from a CI environment, and probably never will do so. All 
(most?) of our application communicate with one or more mainframes, and 
they sometimes need to deploy their code as well... :-)  That would not 
work from a CI environment, as it requires more manual integration with 
other code (on the M/F). However, if the app was _entirely_ self 
contained, ie did everything itself and have no other external links etc, 
then I may consider gettting the build to do it, but at this point, I 
don't see the point.

Basically, the model that I have in my head at the moment, is that we'll 
use CI to automate the builds, run the tests, produce the reports, and 
(when I work out how to) upload the ear to the remote server but not 
deploy it.

We have a web app (deploy site) that allows us deploy our ear artifacts to 
the necessary instances, retrieve logs from production etc. That is what 
we have to use to deploy apps, that we can only do in our system test 
(real websphere on AIX) env. We have a separate team that manages the 
websphere environment for us.

When we deploy, and the stubs and ties are done for us, here is the 
output:

ADMA5018I: The EJBDeploy command is running on enterprise archive (EAR) 
file /tmp/app38179.ear.

Starting workbench.

framework search path: /ibmapp2/websphere61/base/deploytool/itp/plugins

Creating the project.

Deploying jar DiallerEJB-1.0-SNAPSHOT

Generating deployment code

Invoking RMIC.

Writing output file

Shutting down workbench.

EJBDeploy complete.
0 Errors, 0 Warnings, 0 Informational Messages

ADMA5007I: The EJBDeploy command completed on 
/ibmapp2/websphere61/deploymgr/wstemp/wstemp/app_11a7f4e92be/dpl/dpl_dial.ear

I would recommend that you (well, everyone really) do a manual deployment 
of an ear file using the admin console, just so that they understand what 
is done and the issues involved.

-Chris

"Siarhei Dudzin" <si...@gmail.com> wrote on 13/06/2008 08:09:36:

> Hi Chris,
> 
> This is very interesting approach. Does that mean you have to actually
> generate stubs&sceletons in IDE before you can build with maven?
> How do you deploy your apps to a server in CI environment? Do you use 
hot
> deployment (then you might have timing issues) or do you not deploy at 
all
> and only do unit testing?
> 
> 
> Regards,
> Siarhei
> 
> On Wed, Jun 11, 2008 at 3:35 AM, <Ch...@aami.com.au> wrote:
> 
> > Hi.
> >
> > I do not get maven to actually generate the EJB deployment code, 
WebSphere
> > itself will do it at deployment time, so I do. If nothing else, this 
will
> > give you a list of the jars that you need.
> >
> 
> 
> The following message has been automatically added by the Internet mail 
> gateway to comply with the Group's Information Security requirements.
> 
> "This e-mail has arrived via the Internet, and therefore you should be 
> cautious about its origin and content. Replies which contain sensitive 
> information and / or legal/contractual obligations are particularly 
vulnerable.
> 
> In these cases you should not reply unless you are authorised to do so, 
> and adequate encryption is employed."
> 
> If you have any questions, please contact the IS Service Desk.

**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. 

If you are not the intended recipient of this message you must: 
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.

Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.

Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven & WebSphere 6.1

Posted by Siarhei Dudzin <si...@gmail.com>.
Hi Chris,

This is very interesting approach. Does that mean you have to actually
generate stubs&sceletons in IDE before you can build with maven?
How do you deploy your apps to a server in CI environment? Do you use hot
deployment (then you might have timing issues) or do you not deploy at all
and only do unit testing?


Regards,
Siarhei

On Wed, Jun 11, 2008 at 3:35 AM, <Ch...@aami.com.au> wrote:

> Hi.
>
> I do not get maven to actually generate the EJB deployment code, WebSphere
> itself will do it at deployment time, so I do. If nothing else, this will
> give you a list of the jars that you need.
>

Re: Maven & WebSphere 6.1

Posted by Jo Support <jo...@gmail.com>.
Thanks to all for the suggestions!

However I didn't be so specific in my first message: I need to force
generation of stubs and skeletons for two EJBs because they are clients for
a profiler app and a transport bus app and they have to be distributed in
each product that uses these apps: I can't declare those clients as EJBs in
application.xml of my products EAR becasue if I do so, I'd need to deploy
the whole profiler and transport apps each time. So, WebSphere will not
generate deployment code in deployment time if they're not declared as EJBs.

Hoping my english is good enough to make me understood... :)

Jo

On Wed, Jun 11, 2008 at 7:26 AM, Baeriswyl Kuno - Extern (IT-BA-MV)
<ku...@sbb.ch> wrote:

> Hello!
>
> I've got another approach. First, I've defined a WAS_HOME constant in my
> parent pom. Second, I've defined the websphere dependencies with system
> scope. Or in other words, I've defined the dependencies with a link to the
> local filesystem using the WAS_HOME constant. With this approach you don't
> need to copy the libraties into the repository. Furthermore, you can handle
> different Websphere versions. Though, it requires a local copy of WAS. And
> preferably with identical install path. In case the install path isn't
> identical, the constant WAS_HOME an be changed at runtime.
> At the beginning, I've copied the libraries to the repository too, however,
> I've stated that I need the WAS_HOME constant anyway when I started using
> was6 Plugin.
>
> Regards
>
> Kuno
>
> -----Ursprüngliche Nachricht-----
> Von: Chris_Graham@aami.com.au [mailto:Chris_Graham@aami.com.au]
> Gesendet: Mittwoch, 11. Juni 2008 03:35
> An: Maven Users List
> Betreff: Re: Maven & WebSphere 6.1
>
>
> Hi.
>
> I do not get maven to actually generate the EJB deployment code, WebSphere
> itself will do it at deployment time, so I do. If nothing else, this will
> give you a list of the jars that you need.
>
> Using RSA V7, it defines a classpath container that has all of the
> necessary jars in it needed to support complete websphere 6.1 development.
> What I have done is to define a runtime library/aggregrate pom for the
> websphere runtime. I have not needed to define one for the JRE.
>
> This is part of a batch file that I used to copy the necessary runtime
> files (as defined in the classpath container) to a temp holding dir, and
> then install/deploy them into your repo.
>
> md C:\Temp\Maven\WAS61
>
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar"
> C:\Temp\Maven\WAS61
>
> That should have these files in the C:\Temp\maven\WAS61 dir:
>
>            50,767 bootstrap.jar
>           430,143 com.ibm.mq.jar
>         1,238,366 com.ibm.mqjms.jar
>            77,523 com.ibm.ws.ejbportable_6.1.0.jar
>         3,355,425 com.ibm.ws.emf_2.1.0.jar
>           622,223 com.ibm.ws.portletcontainer_2.0.0.jar
>         1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
>        53,066,732 com.ibm.ws.runtime_6.1.0.jar
>        11,771,638 com.ibm.ws.sib.server_2.0.0.jar
>         1,179,014 com.ibm.ws.sip.container_6.1.0.jar
>         9,221,353 com.ibm.ws.wccm_6.1.0.jar
>         3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
>           546,698 j2ee.jar
>           202,255 mail-impl.jar
>            72,730 marshall.jar
>
> I deployed them to the repo (in this case proximity) using:
>
> call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq-Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file
> -Dfile=com.ibm.mqjms.jar -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.mqjms -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=bootstrap.jar
> -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file
> -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee
>  -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn
> deploy:deploy-file -Dfile=mail-impl.jar
> -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file
> -Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver
> -DartifactId=marshall  -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call
> mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0
>    -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file
> -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.wccm_6.1.0
>       -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
>
> I created a pom that aggregrates them all together:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
>    <modelVersion>4.0.0</modelVersion>
>    <groupId>com.ibm.websphere.appserver</groupId>
>    <artifactId>runtime</artifactId>
>    <version>6.1</version>
>    <packaging>pom</packaging>
>    <description>Library POM for the WebSphere v6.1 runtime.</description>
>    <dependencies>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.mq</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.mqjms</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>bootstrap</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>j2ee</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>mail-impl</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>marshall</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>        <dependency>
>          <groupId>com.ibm.websphere.appserver</groupId>
>          <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
>          <version>6.1</version>
>        </dependency>
>    </dependencies>
> </project>
>
> I deployed it:
>
> call mvn deploy:deploy-file -Dfile=websphere-61.pom
> -DpomFile=websphere-61.pom
>
> So, then all I need to do it to add this dependency to my code, and we're
> all done.
>
>        <dependency>
>            <groupId>com.ibm.websphere.appserver</groupId>
>            <artifactId>runtime</artifactId>
>            <version>6.1</version>
>            <type>pom</type>
>            <scope>provided</scope>
>        </dependency>
>
> Hope this helps.
>
> -Chris
>
> "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
>
> > Hello folks,
> >
> > I'm following the instructions from
> >
>
> http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating
> in
> > order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should
> have
> > the following jars under <was6home>/lib :
> >
> > - wsanttasks.jar
> > - webservices.jar
> > - wsprofile.jar
> > - ffdc.jar
> > - wsdl4j.jar
> > - commons-logging-api.jar
> > - commons-discovery.jar
> > - ras.jar
> > - wsexception.jar
> > - emf.jar
> > - classloader.jar
> >
> > But they're missing. I have
> >
> > IBM WebSphere 6.1 AS Network Deployment
> >
> > - Am I using a wrong version of WAS?
> > - Am I following an out-of-date how-to guide?
> >
> > Thanks in advance,
> > Jo
> >
> >
> > The following message has been automatically added by the Internet
> > mail gateway to comply with the Group's Information Security
> > requirements.
> >
> > "This e-mail has arrived via the Internet, and therefore you should be
> > cautious about its origin and content. Replies which contain sensitive
> > information and / or legal/contractual obligations are particularly
> vulnerable.
> >
> > In these cases you should not reply unless you are authorised to do
> > so, and adequate encryption is employed."
> >
> > If you have any questions, please contact the IS Service Desk.
>
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It may
> contain privileged or confidential information.
>
> If you are not the intended recipient of this message you must:
> - Not use, copy, distribute or disclose it to anyone other than the
> addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer
> immediately.
>
> Internet emails are not necessarily secure. Australian Associated Motors
> Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not
> accept responsibility for changes made to this message after it was sent.
>
> Unless otherwise stated, views expressed within this email are the author's
> own and do not represent those of AAMI.
> **********************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

AW: AW: Maven & WebSphere 6.1

Posted by "Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch>.
Hello Chris,

thanks for your feedback. I agree with you, local installation isn't a very good approach. As already mentioned, was6 maven plugin requires a local installation for the generation of the stubs and skeletons anyway. Therfore, I've decited to go this way, after I had tried your way.

However, I'd like to share different opinions and maybe we'll find even a better approach.

Thanks a lot.

Kuno

-----Urspr�ngliche Nachricht-----
Von: Chris_Graham@aami.com.au [mailto:Chris_Graham@aami.com.au]
Gesendet: Donnerstag, 12. Juni 2008 01:56
An: Maven Users List
Betreff: Re: AW: Maven & WebSphere 6.1


Hi Kuno.

        I understand why you've done what you've done, but it is not a very CI friendly approach (as it does require a local install).

        Multiple versions, and even fix pack variations, and especially when you may wish to consider feature packs (ejb 3, web services etc), putting it into the repository makes far better sense.

        Which is why I provided the steps that I used to create it and supplied the pom. I should save someone a few hours.

        I would be interested to see an example of your system scope pointing to the local file system, could you please share an example?

        Ta.

        As always, use whatever works best for you!

-Chris


"Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch> wrote on 11/06/2008 15:26:43:

> Hello!
>
> I've got another approach. First, I've defined a WAS_HOME constant in
> my

> parent pom. Second, I've defined the websphere dependencies with
> system scope. Or in other words, I've defined the dependencies with a
> link to the local filesystem using the WAS_HOME constant. With this
> approach you

> don't need to copy the libraties into the repository. Furthermore, you
> can handle different Websphere versions. Though, it requires a local
copy
> of WAS. And preferably with identical install path. In case the
> install path isn't identical, the constant WAS_HOME an be changed at
> runtime. At the beginning, I've copied the libraries to the repository
> too, however, I've stated that I need the WAS_HOME constant anyway
> when I started using was6 Plugin.
>
> Regards
>
> Kuno
>
> -----Urspr�ngliche Nachricht-----
> Von: Chris_Graham@aami.com.au [mailto:Chris_Graham@aami.com.au]
> Gesendet: Mittwoch, 11. Juni 2008 03:35
> An: Maven Users List
> Betreff: Re: Maven & WebSphere 6.1
>
>
> Hi.
>
> I do not get maven to actually generate the EJB deployment code,
> WebSphere itself will do it at deployment time, so I do. If nothing
else,
> this will give you a list of the jars that you need.
>
> Using RSA V7, it defines a classpath container that has all of the
> necessary jars in it needed to support complete websphere 6.1
> development. What I have done is to define a runtime
> library/aggregrate pom for the websphere runtime. I have not needed to
> define one for the
JRE.
>
> This is part of a batch file that I used to copy the necessary runtime
> files (as defined in the classpath container) to a temp holding dir,
> and

> then install/deploy them into your repo.
>
> md C:\Temp\Maven\WAS61
>
> copy "C:\Program
Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program
> Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.
> ibm.mqjms.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> ejbportable_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> emf_2.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> portletcontainer_2.0.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> runtime.dist_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> runtime_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> sib.server_2.0.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> sip.container_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> wccm_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> webcontainer_2.0.0.jar"
> C:\Temp\Maven\WAS61
>
> That should have these files in the C:\Temp\maven\WAS61 dir:
>
>             50,767 bootstrap.jar
>            430,143 com.ibm.mq.jar
>          1,238,366 com.ibm.mqjms.jar
>             77,523 com.ibm.ws.ejbportable_6.1.0.jar
>          3,355,425 com.ibm.ws.emf_2.1.0.jar
>            622,223 com.ibm.ws.portletcontainer_2.0.0.jar
>          1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
>         53,066,732 com.ibm.ws.runtime_6.1.0.jar
>         11,771,638 com.ibm.ws.sib.server_2.0.0.jar
>          1,179,014 com.ibm.ws.sip.container_6.1.0.jar
>          9,221,353 com.ibm.ws.wccm_6.1.0.jar
>          3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
>            546,698 j2ee.jar
>            202,255 mail-impl.jar
>             72,730 marshall.jar
>
> I deployed them to the repo (in this case proximity) using:
>
> call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm.
> websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1
-Dpackaging=jar
> -DgeneratePom=true call mvn deploy:deploy-file
> -Dfile=com.ibm.mqjms.jar
-
> DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms -
> Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn
> deploy:deploy- file -Dfile=bootstrap.jar
> -DgroupId=com.ibm.websphere.appserver - DartifactId=bootstrap
> -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn
> deploy:deploy-file -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.
> appserver -DartifactId=j2ee  -Dversion=6.1 -Dpackaging=jar -
> DgeneratePom=true call mvn deploy:deploy-file -Dfile=mail-impl.jar -
> DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl
-Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -
> Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver -
> DartifactId=marshall  -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar -
> DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0
>     -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file
> -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 -
> Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file
-Dfile=com.
> ibm.ws.runtime.dist_6.1.0.jar -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar -
> DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.wccm_6.1.0
>        -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
>
> I created a pom that aggregrates them all together:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
>     <modelVersion>4.0.0</modelVersion>
>     <groupId>com.ibm.websphere.appserver</groupId>
>     <artifactId>runtime</artifactId>
>     <version>6.1</version>
>     <packaging>pom</packaging>
>     <description>Library POM for the WebSphere v6.1
runtime.</description>
>     <dependencies>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mq</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mqjms</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>bootstrap</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>j2ee</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>mail-impl</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>marshall</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>     </dependencies>
> </project>
>
> I deployed it:
>
> call mvn deploy:deploy-file -Dfile=websphere-61.pom
-DpomFile=websphere-61.pom
>
> So, then all I need to do it to add this dependency to my code, and
we'reall done.
>
>         <dependency>
>             <groupId>com.ibm.websphere.appserver</groupId>
>             <artifactId>runtime</artifactId>
>             <version>6.1</version>
>             <type>pom</type>
>             <scope>provided</scope>
>         </dependency>
>
> Hope this helps.
>
> -Chris
>
> "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
>
> > Hello folks,
> >
> > I'm following the instructions from
> >
>
http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating
> in
> > order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I
> > should
> have
> > the following jars under <was6home>/lib :
> >
> > - wsanttasks.jar
> > - webservices.jar
> > - wsprofile.jar
> > - ffdc.jar
> > - wsdl4j.jar
> > - commons-logging-api.jar
> > - commons-discovery.jar
> > - ras.jar
> > - wsexception.jar
> > - emf.jar
> > - classloader.jar
> >
> > But they're missing. I have
> >
> > IBM WebSphere 6.1 AS Network Deployment
> >
> > - Am I using a wrong version of WAS?
> > - Am I following an out-of-date how-to guide?
> >
> > Thanks in advance,
> > Jo
> >
> >
> > The following message has been automatically added by the Internet
> > mail gateway to comply with the Group's Information Security
> > requirements.
> >
> > "This e-mail has arrived via the Internet, and therefore you should
> > be cautious about its origin and content. Replies which contain
> > sensitive information and / or legal/contractual obligations are
> > particularly
> vulnerable.
> >
> > In these cases you should not reply unless you are authorised to do
> > so, and adequate encryption is employed."
> >
> > If you have any questions, please contact the IS Service Desk.
>
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It
> may

> contain privileged or confidential information.
>
> If you are not the intended recipient of this message you must:
> - Not use, copy, distribute or disclose it to anyone other than the
addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer
immediately.
>
> Internet emails are not necessarily secure. Australian Associated
> Motors

> Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities,
> do

> not accept responsibility for changes made to this message after it
> was
sent.
>
> Unless otherwise stated, views expressed within this email are the
> author's own and do not represent those of AAMI.
> **********************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> The following message has been automatically added by the Internet
> mail gateway to comply with the Group's Information Security
> requirements.
>
> "This e-mail has arrived via the Internet, and therefore you should be
> cautious about its origin and content. Replies which contain sensitive
> information and / or legal/contractual obligations are particularly
vulnerable.
>
> In these cases you should not reply unless you are authorised to do
> so, and adequate encryption is employed."
>
> If you have any questions, please contact the IS Service Desk.


**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information.

If you are not the intended recipient of this message you must:
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.

Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.

Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: AW: Maven & WebSphere 6.1

Posted by Ch...@aami.com.au.
Hi Kuno.

        I understand why you've done what you've done, but it is not a 
very CI friendly approach (as it does require a local install). 

        Multiple versions, and even fix pack variations, and especially 
when you may wish to consider feature packs (ejb 3, web services etc), 
putting it into the repository makes far better sense.

        Which is why I provided the steps that I used to create it and 
supplied the pom. I should save someone a few hours.

        I would be interested to see an example of your system scope 
pointing to the local file system, could you please share an example?

        Ta.

        As always, use whatever works best for you!

-Chris


"Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch> wrote on 
11/06/2008 15:26:43:

> Hello!
> 
> I've got another approach. First, I've defined a WAS_HOME constant in my 

> parent pom. Second, I've defined the websphere dependencies with system 
> scope. Or in other words, I've defined the dependencies with a link to 
> the local filesystem using the WAS_HOME constant. With this approach you 

> don't need to copy the libraties into the repository. Furthermore, you 
> can handle different Websphere versions. Though, it requires a local 
copy
> of WAS. And preferably with identical install path. In case the install 
> path isn't identical, the constant WAS_HOME an be changed at runtime.
> At the beginning, I've copied the libraries to the repository too, 
> however, I've stated that I need the WAS_HOME constant anyway when I 
> started using was6 Plugin.
> 
> Regards
> 
> Kuno
> 
> -----Ursprüngliche Nachricht-----
> Von: Chris_Graham@aami.com.au [mailto:Chris_Graham@aami.com.au]
> Gesendet: Mittwoch, 11. Juni 2008 03:35
> An: Maven Users List
> Betreff: Re: Maven & WebSphere 6.1
> 
> 
> Hi.
> 
> I do not get maven to actually generate the EJB deployment code, 
> WebSphere itself will do it at deployment time, so I do. If nothing 
else,
> this will give you a list of the jars that you need.
> 
> Using RSA V7, it defines a classpath container that has all of the 
> necessary jars in it needed to support complete websphere 6.1 
> development. What I have done is to define a runtime library/aggregrate 
> pom for the websphere runtime. I have not needed to define one for the 
JRE.
> 
> This is part of a batch file that I used to copy the necessary runtime 
> files (as defined in the classpath container) to a temp holding dir, and 

> then install/deploy them into your repo.
> 
> md C:\Temp\Maven\WAS61
> 
> copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.
> ibm.mqjms.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> ejbportable_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> emf_2.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> portletcontainer_2.0.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> runtime.dist_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> runtime_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> sib.server_2.0.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> sip.container_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> wccm_6.1.0.jar"
> C:\Temp\Maven\WAS61
> copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.
> webcontainer_2.0.0.jar"
> C:\Temp\Maven\WAS61
> 
> That should have these files in the C:\Temp\maven\WAS61 dir:
> 
>             50,767 bootstrap.jar
>            430,143 com.ibm.mq.jar
>          1,238,366 com.ibm.mqjms.jar
>             77,523 com.ibm.ws.ejbportable_6.1.0.jar
>          3,355,425 com.ibm.ws.emf_2.1.0.jar
>            622,223 com.ibm.ws.portletcontainer_2.0.0.jar
>          1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
>         53,066,732 com.ibm.ws.runtime_6.1.0.jar
>         11,771,638 com.ibm.ws.sib.server_2.0.0.jar
>          1,179,014 com.ibm.ws.sip.container_6.1.0.jar
>          9,221,353 com.ibm.ws.wccm_6.1.0.jar
>          3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
>            546,698 j2ee.jar
>            202,255 mail-impl.jar
>             72,730 marshall.jar
> 
> I deployed them to the repo (in this case proximity) using:
> 
> call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm.
> websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1 
-Dpackaging=jar
> -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar 
-
> DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms -
> Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-
> file -Dfile=bootstrap.jar -DgroupId=com.ibm.websphere.appserver -
> DartifactId=bootstrap -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true 
> call mvn deploy:deploy-file -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.
> appserver -DartifactId=j2ee  -Dversion=6.1 -Dpackaging=jar -
> DgeneratePom=true call mvn deploy:deploy-file -Dfile=mail-impl.jar -
> DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl 
-Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -
> Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver -
> DartifactId=marshall  -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true 
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar -
> DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0
>     -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 -
> Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file 
-Dfile=com.
> ibm.ws.runtime.dist_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar -
> DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.wccm_6.1.0
>        -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
> call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar
> -DgroupId=com.ibm.websphere.appserver
> -DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1
> -Dpackaging=jar -DgeneratePom=true
> 
> I created a pom that aggregrates them all together:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
>     <modelVersion>4.0.0</modelVersion>
>     <groupId>com.ibm.websphere.appserver</groupId>
>     <artifactId>runtime</artifactId>
>     <version>6.1</version>
>     <packaging>pom</packaging>
>     <description>Library POM for the WebSphere v6.1 
runtime.</description>
>     <dependencies>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mq</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.mqjms</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>bootstrap</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>j2ee</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>mail-impl</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>marshall</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>         <dependency>
>           <groupId>com.ibm.websphere.appserver</groupId>
>           <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
>           <version>6.1</version>
>         </dependency>
>     </dependencies>
> </project>
> 
> I deployed it:
> 
> call mvn deploy:deploy-file -Dfile=websphere-61.pom 
-DpomFile=websphere-61.pom
> 
> So, then all I need to do it to add this dependency to my code, and 
we'reall done.
> 
>         <dependency>
>             <groupId>com.ibm.websphere.appserver</groupId>
>             <artifactId>runtime</artifactId>
>             <version>6.1</version>
>             <type>pom</type>
>             <scope>provided</scope>
>         </dependency>
> 
> Hope this helps.
> 
> -Chris
> 
> "Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:
> 
> > Hello folks,
> >
> > I'm following the instructions from
> >
> 
http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating
> in
> > order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should
> have
> > the following jars under <was6home>/lib :
> >
> > - wsanttasks.jar
> > - webservices.jar
> > - wsprofile.jar
> > - ffdc.jar
> > - wsdl4j.jar
> > - commons-logging-api.jar
> > - commons-discovery.jar
> > - ras.jar
> > - wsexception.jar
> > - emf.jar
> > - classloader.jar
> >
> > But they're missing. I have
> >
> > IBM WebSphere 6.1 AS Network Deployment
> >
> > - Am I using a wrong version of WAS?
> > - Am I following an out-of-date how-to guide?
> >
> > Thanks in advance,
> > Jo
> >
> >
> > The following message has been automatically added by the Internet
> > mail gateway to comply with the Group's Information Security
> > requirements.
> >
> > "This e-mail has arrived via the Internet, and therefore you should be
> > cautious about its origin and content. Replies which contain sensitive
> > information and / or legal/contractual obligations are particularly
> vulnerable.
> >
> > In these cases you should not reply unless you are authorised to do
> > so, and adequate encryption is employed."
> >
> > If you have any questions, please contact the IS Service Desk.
> 
> **********************************************************************
> CAUTION - This message is intended for the addressee named above. It may 

> contain privileged or confidential information.
> 
> If you are not the intended recipient of this message you must:
> - Not use, copy, distribute or disclose it to anyone other than the 
addressee;
> - Notify the sender via return email; and
> - Delete the message (and any related attachments) from your computer 
immediately.
> 
> Internet emails are not necessarily secure. Australian Associated Motors 

> Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do 

> not accept responsibility for changes made to this message after it was 
sent.
> 
> Unless otherwise stated, views expressed within this email are the 
> author's own and do not represent those of AAMI.
> **********************************************************************
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> The following message has been automatically added by the Internet mail 
> gateway to comply with the Group's Information Security requirements.
> 
> "This e-mail has arrived via the Internet, and therefore you should be 
> cautious about its origin and content. Replies which contain sensitive 
> information and / or legal/contractual obligations are particularly 
vulnerable.
> 
> In these cases you should not reply unless you are authorised to do so, 
> and adequate encryption is employed."
> 
> If you have any questions, please contact the IS Service Desk.


**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. 

If you are not the intended recipient of this message you must: 
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.

Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.

Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


AW: Maven & WebSphere 6.1

Posted by "Baeriswyl Kuno - Extern (IT-BA-MV)" <ku...@sbb.ch>.
Hello!

I've got another approach. First, I've defined a WAS_HOME constant in my parent pom. Second, I've defined the websphere dependencies with system scope. Or in other words, I've defined the dependencies with a link to the local filesystem using the WAS_HOME constant. With this approach you don't need to copy the libraties into the repository. Furthermore, you can handle different Websphere versions. Though, it requires a local copy of WAS. And preferably with identical install path. In case the install path isn't identical, the constant WAS_HOME an be changed at runtime.
At the beginning, I've copied the libraries to the repository too, however, I've stated that I need the WAS_HOME constant anyway when I started using was6 Plugin.

Regards

Kuno

-----Ursprüngliche Nachricht-----
Von: Chris_Graham@aami.com.au [mailto:Chris_Graham@aami.com.au]
Gesendet: Mittwoch, 11. Juni 2008 03:35
An: Maven Users List
Betreff: Re: Maven & WebSphere 6.1


Hi.

I do not get maven to actually generate the EJB deployment code, WebSphere itself will do it at deployment time, so I do. If nothing else, this will give you a list of the jars that you need.

Using RSA V7, it defines a classpath container that has all of the necessary jars in it needed to support complete websphere 6.1 development. What I have done is to define a runtime library/aggregrate pom for the websphere runtime. I have not needed to define one for the JRE.

This is part of a batch file that I used to copy the necessary runtime files (as defined in the classpath container) to a temp holding dir, and then install/deploy them into your repo.

md C:\Temp\Maven\WAS61

copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar"
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar"
C:\Temp\Maven\WAS61

That should have these files in the C:\Temp\maven\WAS61 dir:

            50,767 bootstrap.jar
           430,143 com.ibm.mq.jar
         1,238,366 com.ibm.mqjms.jar
            77,523 com.ibm.ws.ejbportable_6.1.0.jar
         3,355,425 com.ibm.ws.emf_2.1.0.jar
           622,223 com.ibm.ws.portletcontainer_2.0.0.jar
         1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
        53,066,732 com.ibm.ws.runtime_6.1.0.jar
        11,771,638 com.ibm.ws.sib.server_2.0.0.jar
         1,179,014 com.ibm.ws.sip.container_6.1.0.jar
         9,221,353 com.ibm.ws.wccm_6.1.0.jar
         3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
           546,698 j2ee.jar
           202,255 mail-impl.jar
            72,730 marshall.jar

I deployed them to the repo (in this case proximity) using:

call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=bootstrap.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee  -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=mail-impl.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall  -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar
-DgroupId=com.ibm.websphere.appserver
-DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0
    -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar
-DgroupId=com.ibm.websphere.appserver
-DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar
-DgroupId=com.ibm.websphere.appserver
-DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar
-DgroupId=com.ibm.websphere.appserver
-DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar
-DgroupId=com.ibm.websphere.appserver
-DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar
-DgroupId=com.ibm.websphere.appserver
-DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.wccm_6.1.0
       -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar
-DgroupId=com.ibm.websphere.appserver
-DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1
-Dpackaging=jar -DgeneratePom=true

I created a pom that aggregrates them all together:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.ibm.websphere.appserver</groupId>
    <artifactId>runtime</artifactId>
    <version>6.1</version>
    <packaging>pom</packaging>
    <description>Library POM for the WebSphere v6.1 runtime.</description>
    <dependencies>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.mq</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.mqjms</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>bootstrap</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>j2ee</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>mail-impl</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>marshall</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
          <version>6.1</version>
        </dependency>
    </dependencies>
</project>

I deployed it:

call mvn deploy:deploy-file -Dfile=websphere-61.pom -DpomFile=websphere-61.pom

So, then all I need to do it to add this dependency to my code, and we're all done.

        <dependency>
            <groupId>com.ibm.websphere.appserver</groupId>
            <artifactId>runtime</artifactId>
            <version>6.1</version>
            <type>pom</type>
            <scope>provided</scope>
        </dependency>

Hope this helps.

-Chris

"Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:

> Hello folks,
>
> I'm following the instructions from
>
http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating
in
> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should
have
> the following jars under <was6home>/lib :
>
> - wsanttasks.jar
> - webservices.jar
> - wsprofile.jar
> - ffdc.jar
> - wsdl4j.jar
> - commons-logging-api.jar
> - commons-discovery.jar
> - ras.jar
> - wsexception.jar
> - emf.jar
> - classloader.jar
>
> But they're missing. I have
>
> IBM WebSphere 6.1 AS Network Deployment
>
> - Am I using a wrong version of WAS?
> - Am I following an out-of-date how-to guide?
>
> Thanks in advance,
> Jo
>
>
> The following message has been automatically added by the Internet
> mail gateway to comply with the Group's Information Security
> requirements.
>
> "This e-mail has arrived via the Internet, and therefore you should be
> cautious about its origin and content. Replies which contain sensitive
> information and / or legal/contractual obligations are particularly
vulnerable.
>
> In these cases you should not reply unless you are authorised to do
> so, and adequate encryption is employed."
>
> If you have any questions, please contact the IS Service Desk.

**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information.

If you are not the intended recipient of this message you must:
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.

Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.

Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven & WebSphere 6.1

Posted by Ch...@aami.com.au.
Hi.

I do not get maven to actually generate the EJB deployment code, WebSphere 
itself will do it at deployment time, so I do. If nothing else, this will 
give you a list of the jars that you need.

Using RSA V7, it defines a classpath container that has all of the 
necessary jars in it needed to support complete websphere 6.1 development. 
What I have done is to define a runtime library/aggregrate pom for the 
websphere runtime. I have not needed to define one for the JRE.

This is part of a batch file that I used to copy the necessary runtime 
files (as defined in the classpath container) to a temp holding dir, and 
then install/deploy them into your repo.

md C:\Temp\Maven\WAS61

copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar" 
C:\Temp\Maven\WAS61
copy "C:\Program 
Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar" 
C:\Temp\Maven\WAS61

That should have these files in the C:\Temp\maven\WAS61 dir:

            50,767 bootstrap.jar
           430,143 com.ibm.mq.jar
         1,238,366 com.ibm.mqjms.jar
            77,523 com.ibm.ws.ejbportable_6.1.0.jar
         3,355,425 com.ibm.ws.emf_2.1.0.jar
           622,223 com.ibm.ws.portletcontainer_2.0.0.jar
         1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar
        53,066,732 com.ibm.ws.runtime_6.1.0.jar
        11,771,638 com.ibm.ws.sib.server_2.0.0.jar
         1,179,014 com.ibm.ws.sip.container_6.1.0.jar
         9,221,353 com.ibm.ws.wccm_6.1.0.jar
         3,267,808 com.ibm.ws.webcontainer_2.0.0.jar
           546,698 j2ee.jar
           202,255 mail-impl.jar
            72,730 marshall.jar

I deployed them to the repo (in this case proximity) using:

call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq  
-Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms  
-Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=bootstrap.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap  
-Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=j2ee.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee  -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=mail-impl.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl  
-Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=marshall.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=marshall  -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar 
-DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.ejbportable_6.1.0      -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0    
    -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar 
-DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar 
-DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.runtime.dist_6.1.0     -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar 
-DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.runtime_6.1.0          -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.sib.server_2.0.0.jar 
-DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.sib.server_2.0.0       -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.sip.container_6.1.0.jar 
-DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.sip.container_6.1.0    -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.wccm_6.1.0.jar 
-DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.wccm_6.1.0   
       -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true
call mvn deploy:deploy-file -Dfile=com.ibm.ws.webcontainer_2.0.0.jar 
-DgroupId=com.ibm.websphere.appserver 
-DartifactId=com.ibm.ws.webcontainer_2.0.0     -Dversion=6.1 
-Dpackaging=jar -DgeneratePom=true

I created a pom that aggregrates them all together:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.ibm.websphere.appserver</groupId>
    <artifactId>runtime</artifactId>
    <version>6.1</version>
    <packaging>pom</packaging>
    <description>Library POM for the WebSphere v6.1 runtime.</description>
    <dependencies>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.mq</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.mqjms</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>bootstrap</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>j2ee</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>mail-impl</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>marshall</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.ejbportable_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.emf_2.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.portletcontainer_2.0.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.runtime.dist_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.runtime_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.sib.server_2.0.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.sip.container_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.wccm_6.1.0</artifactId>
          <version>6.1</version>
        </dependency>
        <dependency>
          <groupId>com.ibm.websphere.appserver</groupId>
          <artifactId>com.ibm.ws.webcontainer_2.0.0</artifactId>
          <version>6.1</version>
        </dependency>
    </dependencies>
</project>

I deployed it:

call mvn deploy:deploy-file -Dfile=websphere-61.pom 
-DpomFile=websphere-61.pom

So, then all I need to do it to add this dependency to my code, and we're 
all done.

        <dependency>
            <groupId>com.ibm.websphere.appserver</groupId>
            <artifactId>runtime</artifactId>
            <version>6.1</version>
            <type>pom</type>
            <scope>provided</scope>
        </dependency>

Hope this helps.

-Chris

"Jo Support" <jo...@gmail.com> wrote on 10/06/2008 20:55:21:

> Hello folks,
> 
> I'm following the instructions from
> 
http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating 
in
> order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should 
have
> the following jars under <was6home>/lib :
> 
> - wsanttasks.jar
> - webservices.jar
> - wsprofile.jar
> - ffdc.jar
> - wsdl4j.jar
> - commons-logging-api.jar
> - commons-discovery.jar
> - ras.jar
> - wsexception.jar
> - emf.jar
> - classloader.jar
> 
> But they're missing. I have
> 
> IBM WebSphere 6.1 AS Network Deployment
> 
> - Am I using a wrong version of WAS?
> - Am I following an out-of-date how-to guide?
> 
> Thanks in advance,
> Jo
> 
> 
> The following message has been automatically added by the Internet mail 
> gateway to comply with the Group's Information Security requirements.
> 
> "This e-mail has arrived via the Internet, and therefore you should be 
> cautious about its origin and content. Replies which contain sensitive 
> information and / or legal/contractual obligations are particularly 
vulnerable.
> 
> In these cases you should not reply unless you are authorised to do so, 
> and adequate encryption is employed."
> 
> If you have any questions, please contact the IS Service Desk.

**********************************************************************
CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. 

If you are not the intended recipient of this message you must: 
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer immediately.

Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent.

Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org