<br><div><span class="gmail_quote">On 8/4/06, <b class="gmail_sendername">Max Rydahl Andersen</b> <<a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>eh, no - we already have one jdk 1.5 plugin ;)<br><br>it is called org.hibernate.eclipse.jdt.apt.ui and is distributed with<br>everything,<br>but simply has a matching execution environment in manifest.</blockquote><div>
<br>Spiffy -- this is the same way the eviware plugins are working, so this should be fine I guess.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
May I ask why this plugin is depedent on jdk 1.5 ? Does JBossWS require<br>1.5 ?</blockquote><div><br>JBossWS does require 1.5 I believe, but more than that the entire SoapUI core (which they are reusing in their plugins) is
1.5...<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On a side note: Depending on WTP 2.0 for now will be deadly ;(<br>They don't have any release planned for a year now.
<br>Users will go crazy about yet another dependency hell.</blockquote><div><br>I wasn't suggesting we move WTP 2.0 right away, just suggesting that "when we do" (sounds like a year from now?) 1.5 compatibility would be something we were forced into.
<br></div><br></div><br>-- <br>Marshall Culpepper<br><a href="mailto:marshall.culpepper@jboss.com">marshall.culpepper@jboss.com</a><br>JBoss Eclipse IDE Lead, JBoss Inc.