I see two options: 1. Upload the Websphere artifacts to your internal repo. This is IMO the preferred way to go as it will make it possible to use the same artifacts during compiling and testing as in runtime.
2. As long as you code against Java EE APIs, you could use any available artifacts implementing them as you declare provided scope. They will then be used during compiling and testing, but in runtime you will be using the ones in the Websphere platform. /Anders On Tue, Nov 6, 2012 at 9:57 PM, goyal.sharad <[email protected]> wrote: > Is there any sample project like Hello World exist which has Websphere 8 > dependencies? I do not want to upload our runtime dependencies in the maven > repository because they contains so many jars. > > In bbrief > > Is there any way to define our own runtime environment? > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Websphere-8-tp5729710.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
