[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557283#action_12557283
]
Rick Hillegas commented on DERBY-3117:
--------------------------------------
Hi Kristian,
Thanks for committing your improvement to BUILDING.txt. I'm not sure what you
mean by duplicate code. I think this is the trajectory we are on:
1) Check in the PropertySetter but leave the old scheme as the default. This
phase lasted a month. In this phase other people were able to make
PropertySetter work correctly in more environments.
2) Make PropertySetter the default. This is the phase we're in now. It appears
from your experience with DERBY-3149 that some people are not happy with the
new default behavior and have not switched over to using it.
3) Remove the old scheme and just rely on PropertySetter. I think that before
we can move to this phase, we have to address the problems that are keeping
people stuck on the old scheme. Hopefully this is just a matter of making
PropertySetter smarter.
I was only aware of one issue which prevented us from moving from (2) to (3).
That is an issue raised by Andrew just before the holidays:
http://www.nabble.com/Re%3A-Change-to-Derby-build-soon-p14463570.html Thanks
for bringing my attention to the issue which Kathey encountered in DERBY-3149.
I think we still need to do the following before we can move from (2) to (3):
A) Fix the known issues raised by Andrew and Kathey.
B) Warn the community that we want to remove the old scheme. We could poll the
community to discover who is still stuck on the old scheme and why.
C) Fix the issues raised by that poll.
D) Remove the old scheme.
That, at least, is what makes sense to me.
> Adjust master build script to require the Java 5 compiler to build Derby
> ------------------------------------------------------------------------
>
> Key: DERBY-3117
> URL: https://issues.apache.org/jira/browse/DERBY-3117
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.4.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: BuildDefaults.txt, d3117-solaris.diff,
> derby-3117-01-enforceJava5-aa.diff, derby-3117-01-enforceJava5-ab.diff,
> derby-3117-01-enforceJava5-ac.diff, derby-3117-02-website-aa.diff,
> derby-3117-03-junit-aa.diff, derby-3117-04-propertySetter-aa.diff,
> derby-3117-04-propertySetter-ab.diff, derby-3117-04-propertySetter-ac.diff,
> derby-3117-04-propertySetter-ad.diff, derby-3117-04-propertySetter-ae.diff,
> derby-3117-04-propertySetter-af.diff, derby-3117-04-propertySetter-ag.diff,
> derby-3117-04-propertySetter-ah.diff, derby-3117-05-setterCleanup-aa.diff,
> derby-3117-06-setterDefault-aa.diff, derby-3117-07-buildInstructions-aa.diff,
> derby-3117-08a-j15libBuildingInstr.diff, derby_source.html
>
>
> Require the Java 5 compiler in order to build Derby as approved by the
> community recently:
> http://www.nabble.com/-VOTE--Require-Java-5-%28or-later%29-compiler-to-build-Derby-tf4522491.html#a13030783
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
