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.
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
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
[EMAIL PROTECTED] wrote:
Hi.
I do not get maven to actually generate the EJB deployment code,
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
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
Hi Chris,
This is very interesting approach. Does that mean you have to actually
generate stubssceletons 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
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
-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
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
.
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 12. Juni 2008 01:56
An: Maven Users List
Betreff: Re: AW: 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
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 [EMAIL PROTECTED] wrote:
Hello folks,
I'm following the instructions from
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
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
14 matches
Mail list logo
