On 24/11/2008, at 1:08 PM, Ray Kiddy wrote:
>
> On Oct 23, 2008, at 3:42 PM, Q wrote:
>
>> Our internal build server it configured to build WOLips nightlies
>> and getting it to work (and keep working over time) is something of
>> an art. You need to have a couple of dependencies available that
>> you might not otherwise have installed in your day to day copy of
>> eclipse, or may not be the version currently available from the
>> update sites.
>>
>> In your case you need jprofiler, but you will also need M2E 0.9.4
>> to build successfully.
>>
>> Unless you are building a custom version of WOLips for some reason
>> I would suggest just using the nighties from the mdimension site.
>>
>
> I tried adding something and this, of course, requires that I build
> WOLips. I was able to do this by adding two lines to my
> wobuild.properties file:
>
> wolips.no.jbuilder=true
> wolips.no.maven=true
>
> And then the diff below. After all, are JProfiler and Maven required
> to use WOLips? I would suggest not. And if somebody wants to build
> WOLips in the usual way, they can do nothing and the default is to
> require JProfiler and Maven. Not everyone needs to use these.
They aren't required to use WOLips, but they are required to build a
valid site deployment when using the ant builds. Eclipse can for some
reason get very confused if there are plugins listed in the site.xml
but are missing from the output, even if you don't explicitly try and
install them.
I almost never build wolips locally using ant. Exporting the modified
plugin or feature from eclipse is pretty simple (although doing so
does mess with the ant build files).
> I would file a bug in the WOLips JIRA but I am not finding my login
> info. It has been too long. Would someone be willing to commit this
> very low risk code, or something like it?
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10) Ph: +61 419 729 806
This archive was generated by hypermail 2.0.0 : Sun Nov 23 2008 - 23:09:55 EST