[forge-dev] Testing WebLogic code
ggastald at redhat.com
ggastald at redhat.com
Fri Dec 7 12:14:23 EST 2012
Hi Luca,
My opinion is barely the same. I think that tests with WebLogic should
be run manually. We could provide a profile, but we are only enabling it
manually or if the CI holds a licensed Weblogic instance for testing.
What are the other thoughts on this ?
On 12/07/2012 09:36 AM, Luca Masini wrote:
> As suggested I wrote on Arquillian community and this is the response:
>
> "The Arquillian WebLogic Container only depend on JavaEE libs compile
> time, so we avoid the license issue there. But when it comes to
> running/testing, you'll need a license.
>
> So currently, the WebLogic container is only built(compiled/packaged)
> on our CI. Community members that hold a license run the test suite
> manually.
>
> I don't remember how the WebLogic developer license is, but the
> WebSphere Developer license states things like: can not be used for
> testing, only valid to the local developer computer, can not be placed
> as part of a build server, etc etc.
>
> Seemingly, you're not allowed to release code that requires container
> libraries compile time based on those licenses. Even if compiled from
> the local computer that has the license."
>
> Is exactly our case. I would like to remember that, on contrary of
> WebSphere, when I asked about license problem Oracle answered me that
> for them is enough that we don't use WebLogic for a production site.
>
> What to do now ?
>
> --
> ****************************************
> http://www.lucamasini.net
> http://twitter.com/lmasini
> http://www.linkedin.com/pub/luca-masini/7/10/2b9
> ****************************************
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
--
*George Gastaldi* | /Senior Software Engineer/
JBoss Forge Team
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20121207/121bede8/attachment.html
More information about the forge-dev
mailing list