Re: [jbosside-dev] SoapUI/JBossWS finally working.. and 1.5 source discussion
by Marshall Culpepper
On 8/4/06, Max Rydahl Andersen <max.andersen(a)jboss.com> wrote:
>
>
> eh, no - we already have one jdk 1.5 plugin ;)
>
> it is called org.hibernate.eclipse.jdt.apt.ui and is distributed with
> everything,
> but simply has a matching execution environment in manifest.
Spiffy -- this is the same way the eviware plugins are working, so this
should be fine I guess.
May I ask why this plugin is depedent on jdk 1.5 ? Does JBossWS require
> 1.5 ?
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...
On a side note: Depending on WTP 2.0 for now will be deadly ;(
> They don't have any release planned for a year now.
> Users will go crazy about yet another dependency hell.
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.
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBoss Eclipse IDE Lead, JBoss Inc.
18 years, 4 months
[jbosside-dev] Re: JBossIDE WSTools source directory problem
by lars@eviware.com
Hi,This will not a problem. The src/conf directory was empty. I deleted it and thought I had removed it from build.properties too./Lars >-----Original Message----- >Datum: 2006-08-03 05:51:57 >Från: Marshall Culpepper <marshall.culpepper(a)jboss.com> >Till: jbosside-dev(a)lists.jboss.org <jbosside-dev(a)lists.jboss.org>, Ole Matzura <ole(a)eviware.com>, lars(a)eviware.com >Ämne: JBossIDE WSTools source directory problem > >Hey guys I ran into a slight problem when integrating JBossWS SoapUI plugins >into releng tonight. Basically it looks like the " >com.eviware.soapui.jbosside.wstools" plugin has a source directory >"src/conf" in it's build.properties, but it doesn't exist anywhere in the >subversion repository. Looking over the groovy script that Lars pointed me >to I couldn't find any preparation etc. going on to make this directory, so >I've committed a build.properties with src/conf removed to see if I can move >forward and make the build work. > >Will this cause any undue headaches for you guys? Luckily it's a pretty >small change.. and if there's any fallout I blame Ole for giving me commit >access =). > >-- >Marshall Culpepper >marshall.culpepper(a)jboss.com >JBoss Eclipse IDE Lead, JBoss Inc. >
18 years, 4 months
[jbosside-dev] JBossIDE WSTools source directory problem
by Marshall Culpepper
Hey guys I ran into a slight problem when integrating JBossWS SoapUI plugins
into releng tonight. Basically it looks like the "
com.eviware.soapui.jbosside.wstools" plugin has a source directory
"src/conf" in it's build.properties, but it doesn't exist anywhere in the
subversion repository. Looking over the groovy script that Lars pointed me
to I couldn't find any preparation etc. going on to make this directory, so
I've committed a build.properties with src/conf removed to see if I can move
forward and make the build work.
Will this cause any undue headaches for you guys? Luckily it's a pretty
small change.. and if there's any fallout I blame Ole for giving me commit
access =).
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBoss Eclipse IDE Lead, JBoss Inc.
18 years, 4 months
[jbosside-dev] JBoss Cache IDE Integration
by Gurkan Erdogdu
Hey Marshall;
Some problems with integration. I downloaded the
standalone cache plugin but it did not work because of
the some dependency plugins are not contained in the
plugins directory.
I looked at the feature file but it seems correct and
it points out all the dependency plugins.
What can be the problem?
Gurkan
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
18 years, 4 months