[
https://issues.apache.org/jira/browse/DERBY-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135388#comment-13135388
]
Kristian Waagan commented on DERBY-5469:
----------------------------------------
Kathey wrote:
-----
I wonder, is their a reason we use the manifest entries instead of the system
properties [1] to determine this information?
-----
Yes, spawning a process for each of the candidate VMs to extract the system
properties is taking much longer. This will surely annoy some developers.
Both the mechanisms we are using to determine the version ("encoded" in the
directory name, and inspecting JAR files manifest) have weaknesses. As Rick
suggests, we should consider a simplified build process and leave the more
complex configurations to be manually configured by those who want/have to run
with them.
I believe the reason why the PropertySetter was created was to allow casual
developers and newcomers to Derby to get started quickly. Today the minimal
requirement for a build is probably one JDK, and that should be the VM used to
invoke ant.
> Make it possible to build Derby if you are on Mac OS X and your JDK is JDK 7
> ----------------------------------------------------------------------------
>
> Key: DERBY-5469
> URL: https://issues.apache.org/jira/browse/DERBY-5469
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-5469-01-ae-add17andJavadoc.diff,
> derby-5469-01-af-dontSetUprevVariables.diff, derby-5469-01-ag-cleanedUp.diff
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
