On Nov 25, 2008, at 11:07 AM, Mike Schrag wrote:
>> I have two simple changes I wanted to suggest. The first was that
>> I wanted to suggest we allow <wo:field /> an addition to
>> <wo:textfield /> and such as that and I made an edit to wolips/
>> core/plugins/org.objectstyle.wolips.bindings/java/org/objectstyle/
>> wolips/bindings/preferences/PreferenceInitializer.java to support
>> this. The second was the build.xml changes that would allow me to
>> build.
> If this is already in WOTagRegistry in WOOgnl, then yeah .. If not,
> it would need to be added there, too.
>
>> But, I cannot uninstall the WOLips that I have, so I cannot
>> install a copy of WOLips that I have built, so I would not suggest
>> taking any code from me, as it would be untested.
> Just make a second Eclipse install, or more accurately, you should
> run in=>Eclipse Workspace to test with -- trying to test by doing
> an actual install is the way of madness. PDE development works
> really well, and you get hot code replace, etc.
>
Ok, I will do this. Is the following information correct?
from http://wiki.objectstyle.org/confluence/display/WOL/Installing
+WOLips:
> 1) If you made changes locally, Eclipse will not automatically
> install your changed plugins if the version number is the same. You
> have two options – either uninstall WOLips or cheat and increment
> the WOLips build version prior to building your local copy. To
> uninstall WOLips, just delete all org.objectstyle features and plug
> ins from your eclipse folder. To increment the build server
> version, open buildserver.version in your projects folder and
> increment the last number. Note that you will now be "competing"
> with version numbers from the official build server, so the next
> official build will not install because you already used the next
> number, but sometimes it's a quick hack to force an update if
> you're lazy...
If this is wrong, I can delete it. Or should this information be
contextualized into other documents?
>> Are the WOLips version numbers only an integer? If I am
>> understanding the wiki documentation, there is no way to creagte
>> an intermediate or temporary version number that would conflice
>> with a subsequent version number. This seems lame. O well.
> Eclipse plugin versions can be anything. I don't know the exact
> precedence, but I believe you can add extra strings to that.
> Whether our build files let you do that, though, is another issue
> entirely. But you can see lots of eclipse plugins in your plugins
> folder that do non-numeric version numbers.
Well, I will try it. If we can use arbitrary numbers, then that
documentation can be updated.
cheers - ray
This archive was generated by hypermail 2.0.0 : Tue Nov 25 2008 - 14:31:57 EST