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)" <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> 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" <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
