RE: Suggestion to Update Java Version
Following up on the 1.7 upgrade, I did some checking with my customer installations and I did run across one customer who is using JRE 1.6. It is quite possible we will run into other installations. To give these users time to upgrade, we should plan the upgrade for a future release. We could pick 2.1, or if folks think we need to give the user more time, we could pick something further out. Let me know if you run into other users using 1.6 and any thoughts on upgrade timeing. Gary From: Gary O'Neall [mailto:g...@sourceauditor.com] Sent: Thursday, June 18, 2015 7:11 PM To: 'Yev Bronshteyn'; 'Ryan O'Meara' Cc: 'spdx-tech@lists.spdx.org' Subject: RE: Suggestion to Update Java Version I like the idea of moving to 1.7 - only concern is compatibility for existing users. I would propose that if no one objects due to compatibility or other concerns within the next 2 weeks, we go ahead and upgrade to 1.7. Gary From: spdx-tech-boun...@lists.spdx.org [mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of Yev Bronshteyn Sent: Thursday, June 18, 2015 8:11 AM To: Ryan O'Meara Cc: spdx-tech@lists.spdx.org Subject: Re: Suggestion to Update Java Version Given that the 2.0 tooling already requires significant code changes from the user, moving to one-before-current platform seems reasonable. I would argue it makes more sense to do it sooner rather than later, when the update has increased. On Jun 18, 2015, at 10:53 AM, Ryan O'Meara rome...@blackducksoftware.com wrote: Hi all, I have been making pull requests to the SPDX tools library via GitHub, and I noticed that the tools still use Java 1.6. I was wondering if we could consider updating to Java 1.7 - Oracle officially dropped support for Java 1.6 a long time ago, and is actually in the process of dropping support for Java 1.7. I figure asking users to upgrade their applications which use the library to Java 1.7 at this point isn't unreasonable. Does anyone have any thoughts or objections? If not I can put together a pull request to make this adjustment. Thanks, Ryan O'Meara ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech Yev Bronshteyn Senior Software Engineer Black Duck Software Black Duck Software http://www.blackducksoftware.com/ | OpenHUB https://www.openhub.net/ | OSDelivers http://osdelivers.blackducksoftware.com/ | OSS Logistics https://www.blackducksoftware.com/oss-logistics http://twitter.com/black_duck_sw https://www.linkedin.com/company/black-duck-software https://www.facebook.com/BlackDuckSoftware https://plus.google.com/+Blackducksoftware/ http://www.slideshare.net/blackducksoftware https://www.youtube.com/user/BlackDuckSoftware JP Morgan Chase Co. Hall of Innovation Inductee ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech
Re: Suggestion to Update Java Version
Given that the 2.0 tooling already requires significant code changes from the user, moving to one-before-current platform seems reasonable. I would argue it makes more sense to do it sooner rather than later, when the update has increased. On Jun 18, 2015, at 10:53 AM, Ryan O'Meara rome...@blackducksoftware.commailto:rome...@blackducksoftware.com wrote: Hi all, I have been making pull requests to the SPDX tools library via GitHub, and I noticed that the tools still use Java 1.6. I was wondering if we could consider updating to Java 1.7 - Oracle officially dropped support for Java 1.6 a long time ago, and is actually in the process of dropping support for Java 1.7. I figure asking users to upgrade their applications which use the library to Java 1.7 at this point isn’t unreasonable. Does anyone have any thoughts or objections? If not I can put together a pull request to make this adjustment. Thanks, Ryan O'Meara ___ Spdx-tech mailing list Spdx-tech@lists.spdx.orgmailto:Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech [cid:7EA68D51-363B-4FAD-A939-D9CD926D70AB] Yev Bronshteyn Senior Software Engineer Black Duck Software Black Duck Softwarehttp://www.blackducksoftware.com/ | OpenHUBhttps://www.openhub.net/ | OSDelivershttp://osdelivers.blackducksoftware.com/ | OSS Logisticshttps://www.blackducksoftware.com/oss-logistics [cid:E33E6B21-2C3E-4C55-8796-46161EE14AC6] http://twitter.com/black_duck_sw [cid:EDB9C095-85D8-437C-A4CF-A515712839CA] https://www.linkedin.com/company/black-duck-software [cid:8D343C4D-B65C-473A-96DE-792AF2B5D16E] https://www.facebook.com/BlackDuckSoftware [cid:3FCDCA9B-C8EA-4EB2-9184-457FF1A9AB5D] https://plus.google.com/+Blackducksoftware/ [cid:D1E6BBB6-3622-496C-B3BF-7DC86A214CB8] http://www.slideshare.net/blackducksoftware [cid:B8FD9DF1-3230-44BF-80DA-AEA16CB00E29] JP Morgan Chase Co. Hall of Innovation Inductee https://www.youtube.com/user/BlackDuckSoftware https://www.youtube.com/user/BlackDuckSoftware ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech
RE: Suggestion to Update Java Version
I like the idea of moving to 1.7 - only concern is compatibility for existing users. I would propose that if no one objects due to compatibility or other concerns within the next 2 weeks, we go ahead and upgrade to 1.7. Gary From: spdx-tech-boun...@lists.spdx.org [mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of Yev Bronshteyn Sent: Thursday, June 18, 2015 8:11 AM To: Ryan O'Meara Cc: spdx-tech@lists.spdx.org Subject: Re: Suggestion to Update Java Version Given that the 2.0 tooling already requires significant code changes from the user, moving to one-before-current platform seems reasonable. I would argue it makes more sense to do it sooner rather than later, when the update has increased. On Jun 18, 2015, at 10:53 AM, Ryan O'Meara rome...@blackducksoftware.com wrote: Hi all, I have been making pull requests to the SPDX tools library via GitHub, and I noticed that the tools still use Java 1.6. I was wondering if we could consider updating to Java 1.7 - Oracle officially dropped support for Java 1.6 a long time ago, and is actually in the process of dropping support for Java 1.7. I figure asking users to upgrade their applications which use the library to Java 1.7 at this point isn't unreasonable. Does anyone have any thoughts or objections? If not I can put together a pull request to make this adjustment. Thanks, Ryan O'Meara ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech Yev Bronshteyn Senior Software Engineer Black Duck Software Black Duck Software http://www.blackducksoftware.com/ | OpenHUB https://www.openhub.net/ | OSDelivers http://osdelivers.blackducksoftware.com/ | OSS Logistics https://www.blackducksoftware.com/oss-logistics http://twitter.com/black_duck_sw https://www.linkedin.com/company/black-duck-software https://www.facebook.com/BlackDuckSoftware https://plus.google.com/+Blackducksoftware/ http://www.slideshare.net/blackducksoftware https://www.youtube.com/user/BlackDuckSoftware JP Morgan Chase Co. Hall of Innovation Inductee ___ Spdx-tech mailing list Spdx-tech@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-tech
