[equinox-dev] Eclipse (4.5.1 RC3) and Equinox (Mars.1 RC3) are complete and available for testing
This is our last scheduled build for Mars.1. Meaning from here on, we will build "on Demand" only for approved bugs. Ideally this build either is, or is very similar to, our final Mars.1 deliverable, which is due in one week. So, test well, and please verify any bugs you originated, that were marked fixed for Mars.1. The integration tests for Windows have not yet finished running, so the pages will be updated once they are done (and given the nature of the changes in this final candidate, we would not expect any surprises). Eclipse downloads: http://download.eclipse.org/eclipse/downloads/drops4/M-4.5.1RC3-201509040015/ Update existing (non-production) installs: http://download.eclipse.org/eclipse/updates/4.5-M-builds/ Specific repository good for building against: http://download.eclipse.org/eclipse/updates/4.5-M-builds/M-4.5.1RC3-201509040015/ Equinox specific downloads: http://download.eclipse.org/equinox/drops/M-Mars.1RC3-201509040015/ As always, this announcement is for the Eclipse Platform project only -- the Simultaneous Release RC3 is due in one week. Thanks to everyone who contributed to this checkpoint. ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] org.eclipse.equinox.security
That is a great question. I don't see why the path is restricted like it is. Perhaps you can open a bug and provide a contribution as well as tests that use a wider range of characters. Tom - Original message -From: Nikolis Galerakis Sent by: equinox-dev-boun...@eclipse.orgTo: equinox-dev@eclipse.orgCc:Subject: [equinox-dev] org.eclipse.equinox.securityDate: Fri, Sep 4, 2015 6:57 AM Hello all I am currently using org.eclipse.equinox.security bundle by using Eclipse Secure Storage . What I want to do is give my users the possibility to save Nodes in the Secure Storage with Names that contain German and French Special characters such as öäÖÄ so what this means is that I would need to loosen up the control in the isValid method in the org.eclipse.equinox.internal.security.storage.SecurePreferences. I want to use the characters with ASCII codes 32-255 the question is : Is there any reason not to do so ? why is the isValid ASCII code ranges from 32-160 at the moment ? Thanks in advance, Nikolaos ___equinox-dev mailing listequinox-dev@eclipse.orgTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] org.eclipse.equinox.security
Hello all I am currently using org.eclipse.equinox.security bundle by using Eclipse Secure Storage . What I want to do is give my users the possibility to save Nodes in the Secure Storage with Names that contain German and French Special characters such as öäÖÄ so what this means is that I would need to loosen up the control in the *isValid* method in the org.eclipse.equinox.internal.security.storage.SecurePreferences. I want to use the characters with ASCII codes 32-255 the question is : Is there any reason not to do so ? why is the *isValid* ASCII code ranges from 32-160 at the moment ? Thanks in advance, Nikolaos ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
