From sergio.lopes at embrapa.br Fri Feb 3 13:50:41 2017 From: sergio.lopes at embrapa.br (Sergio Lopes Junior - Embrapa Arroz e Feijao - CNPAF) Date: Fri, 3 Feb 2017 11:50:41 -0200 (BRST) Subject: Error Writing on I2C Bus with Device I/O Library In-Reply-To: <211739910.11974572.1486129516558.JavaMail.root@embrapa.br> Message-ID: <1076890326.11976830.1486129841518.JavaMail.root@embrapa.br> Hi guys, We have encountered an error using the Device I/O library to access an Analog Digital Converter - ADC (MCP3424 chip) by I2C bus with recent versions of java (above version 1.8.0_71). We are using the Toradex iMX6 DualLite 512MB IT card (https://www.toradex.com/en/computer-on-modules/colibri-arm-family/nxp-freescale-imx6). This board uses a linux based on OpenEmbedded (http://www.openembedded.org/wiki/Main_Page) and has an ARMv7 architecture: uname -a Linux colibri-imx6 3.10.17-dirty #16 SMP Thu Jan 7 09:48:46 BRST 2016 armv7l GNU/Linux Whenever an attempt is made to write to the I2C bus, the jdk.dio.UnavailableDeviceException exception is thrown with the message "Locked by other application". To analyze the error we wrote an example application with the class DeviceIOSamples and copied all its files to the / opt / deviceIOSamples directory on the Toradex card: ls -l /opt/deviceIOSamples -rw-r--r-- 1 root root 3569 Feb 2 16:43 DeviceIOSamples-0.0.1.jar -rwxr-xr-x 1 root root 427 Feb 2 16:19 deviceIOSamples.sh -rw-r--r-- 1 root root 197907 Feb 1 13:54 dio.jar -rw-r--r-- 1 root root 1326 Feb 2 13:29 dio.properties -rw-r--r-- 1 root root 2406 Dec 16 11:51 java.policy -rw-r--r-- 1 root root 138324 Feb 1 13:54 libdio.so When running the application with jdk version 1.8.0_71 (jdk1.8.0_71-b15), everything works correctly: java -version java version "1.8.0_71" Java(TM) SE Runtime Environment (build 1.8.0_71-b15) Java HotSpot(TM) Client VM (build 25.71-b15, mixed mode) cd /opt/deviceIOSamples ./deviceIOSamples.sh ---------------------------------------------------- I2C Device Test (MCP3424 ADC Chip) Channel = 3, resolution = 18 bits and pga = x1 ---------------------------------------------------- 1 - opening adc device 2 - send configuration to adc device 3 - reading bytes referring to the conversion performed by the adc device 4 - successful conversion of analogue value ---------------------------------------------------- Analog Value = 0.6563593750000001 mV ---------------------------------------------------- When changing the java to any version after 1.8.0_71 the error appears: java -version java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) Client VM (build 25.121-b13, mixed mode) cd /opt/deviceIOSamples ./deviceIOSamples.sh ---------------------------------------------------- I2C Device Test (MCP3424 ADC Chip) Channel = 3, resolution = 18 bits and pga = x1 ---------------------------------------------------- 1 - opening adc device 2 - send configuration to adc device ---------------------------------------------------- jdk.dio.UnavailableDeviceException: Locked by other application at com.oracle.dio.impl.AbstractPeripheral.conditionalLock(AbstractPeripheral.java:99) at com.oracle.dio.i2cbus.impl.I2CSlaveImpl.transfer(I2CSlaveImpl.java:224) at com.oracle.dio.i2cbus.impl.I2CSlaveImpl.write(I2CSlaveImpl.java:168) at com.oracle.dio.i2cbus.impl.I2CSlaveImpl.write(I2CSlaveImpl.java:178) at DeviceIOSamples.main(DeviceIOSamples.java:28) ---------------------------------------------------- We already tested several versions of java after version 1.8.0_71 and in all them, the same error appears when writing on the I2C bus. We have reached a deadlock in the project regarding the use of the Device I/O library, because we need to use I2C devices. If we can not solve this problem, we will have to abandon it and move on to another hardware access strategy. Has anyone had this or could you help us? Any help will be very welcome. Thank you, Sergio Lopes Jr. Software developer at Embrapa Rice and Bean, Goi?nia / GO - Brazil. >>>>>>>>>>>>>>> Compilation of the Device I / O library: <<<<<<<<<<<<<<< The compilation of the Device I / O library was performed with linaro on linux Ubuntu 32 bit: sudo apt-get update sudo apt-get upgrade wget -c https://releases.linaro.org/components/toolchain/binaries/latest-6/arm-linux-gnueabihf/gcc-linaro-6.2.1-2016.11-i686_arm-linux-gnueabihf.tar.xz sudo tar -xvf gcc-linaro-6.2.1-2016.11-i686_arm-linux-gnueabihf.tar.xz -C /opt sudo mv /opt/gcc-linaro-6.2.1-2016.11-i686_arm-linux-gnueabihf /opt/gcc-linaro export PATH=/opt/gcc-linaro/bin:$PATH export PI_TOOLS=/opt/gcc-linaro export CROSS_COMPILE=arm-linux-gnueabihf- Download file jdk-8u121-linux-x64.tar.gz no endere?o http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html?ssSourceSiteId=otnpt sudo tar -zxvf jdk-8u121-linux-x64.tar.gz -C /opt sudo mv /opt/jdk1.8.0_121 /opt/java export JAVA_HOME=/opt/java export PATH=$JAVA_HOME/bin:$PATH hg clone http://hg.openjdk.java.net/dio/dev dio cd dio Replace the lines in the Makefile: TARGET_CC := $(TARGET_TOOLCHAIN)/bin/gcc TARGET_CXX := $(TARGET_TOOLCHAIN)/bin/g++ TARGET_LD := $(TARGET_TOOLCHAIN)/bin/gcc For: TARGET_CC := $(TARGET_TOOLCHAIN)/bin/arm-linux-gnueabihf-gcc TARGET_CXX := $(TARGET_TOOLCHAIN)/bin/arm-linux-gnueabihf-g++ TARGET_LD := $(TARGET_TOOLCHAIN)/bin/arm-linux-gnueabihf-gcc make ARCH=arm Copy the dio/build/jar/dio.jar and dio/build/so/libdio.so files to the application directory >>>>>>>>>>>>>>> Sample application class (DeviceIOSamples.java): <<<<<<<<<<<<<<< import java.nio.ByteBuffer; import java.time.ZonedDateTime; import jdk.dio.DeviceManager; import jdk.dio.i2cbus.I2CDevice; public class DeviceIOSamples { public static void main(String[] args) { System.out.println("----------------------------------------------------"); System.out.println("I2C Device Test (MCP3424 ADC Chip)"); System.out.println("Channel = 3, resolution = 18 bits and pga = x1"); System.out.println("----------------------------------------------------"); try { // MCP3424 chip configuration // bit 7 : Operation set bit. 0 = set configuration and 1 = start a new conversion. // bit 6-5: Channel Selection Bits. 00 = channel 1, 01 = channel 2, 10 = channel 3 and 11 = channel 4. // bit 4 : Conversion Mode Bit. 1 = Continuous Conversion Mode (Default) and 0 = One-Shot Conversion Mode. // bit 3-2: Sample Rate Selection Bit. 00 = 240 SPS (12 bits), 01 = 60 SPS (14 bits), 10 = 15 SPS (16 bits) and 11 = 3.75 SPS (18 bits). // bit 1-0: PGA Gain Selection Bits. 00 = x1, 01 = x2, 10 = x4 and 11 = x8. // opening adc device (MCP3424 chip) // 100 = deviceType:i2cbus.I2CDevice, name:ADC_1, controllerNumber:1, address:0x68 (dio.properties) System.out.println("1 - opening adc device"); I2CDevice i2cDevice = (I2CDevice) DeviceManager.open(100); // send configuration to adc device (operation = start-new-conversion, channel = 3, conversion-mode = one-shot , resolution = 18 bits and pga = x1) System.out.println("2 - send configuration to adc device"); i2cDevice.write(0b11001100); // reading bytes referring to the conversion performed by the adc device System.out.println("3 - reading bytes referring to the conversion performed by the adc device"); int timeout = 1000; // timeout for analog value conversion in ms ByteBuffer buffer = ByteBuffer.allocate(4); int adcValue = 0; double voltage = 0; long startTime = ZonedDateTime.now().toInstant().toEpochMilli(); long currentTime = startTime; while (true) { // checking that exceeded the timeout for the operation currentTime = ZonedDateTime.now().toInstant().toEpochMilli(); if ((currentTime - startTime) > timeout) { throw new Exception("Exceeded the timeout for analog value conversion"); } // clear buffer buffer.clear(); // reading bytes from ADC i2cDevice.read(buffer); // checking that successfully performed reading if ((buffer.get(3) >>> 7) == 1){ continue; }; // calculating voltage value adcValue = ((buffer.get(0) & 0b00000011) << 16) | ((buffer.get(1) & 0xFF) << 8) | (buffer.get(2) & 0xFF); voltage = (((adcValue * (0.0000078125 / 0.5))) * 2.471) * 1000; // checking that it is valid voltage if (voltage >= 0) { break; } } // successful conversion of analogue value System.out.println("4 - successful conversion of analogue value"); System.out.println("----------------------------------------------------"); System.out.println("Analog Value = " + voltage + " mV"); System.out.println("----------------------------------------------------"); } catch (Exception e) { // error in conversion of analogue value System.out.println("----------------------------------------------------"); e.printStackTrace(); System.out.println("----------------------------------------------------"); } } } >>>>>>>>>>>>>>>>>> Device I/O Properties File (dio.properties): <<<<<<<<<<<<<<<<<<<< # DEFAULT CONFIG gpio.GPIOPin = direction:0, mode:1, trigger:0, initValue:0, predefined:true uart.UART = baudRate:9600, parity:0, dataBits:8, stopBits:1, flowControl:0, predefined:true i2cbus.I2CDevice = addressSize:7, clockFrequency:-1, predefined:true # ADC device (chip MCP3424): # - i2c address : 0x68 # - resolution : 18 bits # - conversion mode : one-shot # - programmable gain amplifier (PGA) : 1 # - channels address : 1 = 0x50, 2 = 0x70, 3 = 0x10 and 4 = 0x30. 100 = deviceType:i2cbus.I2CDevice, name:ADC_1, controllerNumber:1, address:0x68 >>>>>>>>>>>>>>>>>>>>>> Java Police File (java.policy): <<<<<<<<<<<<<<<<<<<<<<<<<<<<< grant { permission "java.util.PropertyPermission" "jdk.dio.registry", "read"; permission "java.io.FilePermission" "./dio.properties-raspberrypi", "read,write"; permission "java.lang.RuntimePermission" "loadLibrary.dio"; permission "java.util.PropertyPermission" "user.dir", "read"; permission jdk.dio.DeviceMgmtPermission "*:*", "open"; permission jdk.dio.adc.ADCPermission "*:*"; permission jdk.dio.atcmd.ATPermission "*:*"; permission jdk.dio.counter.CounterPermission "*:*"; permission jdk.dio.dac.DACPermission "*:*"; permission jdk.dio.generic.GenericPermission "*:*"; permission jdk.dio.gpio.GPIOPinPermission "*:*", "open,setdirection"; permission jdk.dio.gpio.GPIOPortPermission "*:*"; permission jdk.dio.i2cbus.I2CPermission "*:*", "open,powermanage"; permission jdk.dio.pwm.PWMPermission "*:*"; permission jdk.dio.spibus.SPIPermission "*:*"; permission jdk.dio.uart.UARTPermission "*:*"; permission jdk.dio.watchdog.WatchdogTimerPermission "*:*"; }; >>>>>>>>>>> Script to run the sample application (deviceIOSamples.sh): <<<<<<<<<<< java -Xmx64m \ -classpath /opt/deviceIOSamples:/opt/deviceIOSamples/dio.jar:/opt/deviceIOSamples/DeviceIOSamples-0.0.1.jar:$CLASSPATH \ -Djava.library.path=/opt/deviceIOSamples \ -Djdk.dio.registry=/opt/deviceIOSamples/dio.properties \ -Djava.security.policy=/opt/deviceIOSamples/java.policy \ -Duser.country=BR \ -Duser.language=pt \ -Duser.timezone=America/Sao_Paulo \ DeviceIOSamples ____________________________________________________________________________ Aviso de confidencialidade Esta mensagem da Empresa Brasileira de Pesquisa Agropecuaria (Embrapa), empresa publica federal regida pelo disposto na Lei Federal no. 5.851, de 7 de dezembro de 1972, e enviada exclusivamente a seu destinatario e pode conter informacoes confidenciais, protegidas por sigilo profissional. Sua utilizacao desautorizada e ilegal e sujeita o infrator as penas da lei. Se voce a recebeu indevidamente, queira, por gentileza, reenvia-la ao emitente, esclarecendo o equivoco. Confidentiality note This message from Empresa Brasileira de Pesquisa Agropecuaria (Embrapa), a government company established under Brazilian law (5.851/72), is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you are not the addressee, please send it back, elucidating the failure. From Alan.Bateman at oracle.com Fri Feb 3 14:01:17 2017 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 3 Feb 2017 14:01:17 +0000 Subject: Error Writing on I2C Bus with Device I/O Library In-Reply-To: <1076890326.11976830.1486129841518.JavaMail.root@embrapa.br> References: <1076890326.11976830.1486129841518.JavaMail.root@embrapa.br> Message-ID: <916e3a5f-c220-b41a-d929-ae290e5b6ca5@oracle.com> On 03/02/2017 13:50, Sergio Lopes Junior - Embrapa Arroz e Feijao - CNPAF wrote: > > Hi guys, > > > We have encountered an error using the Device I/O library to access an Analog Digital Converter - ADC (MCP3424 chip) > by I2C bus with recent versions of java (above version 1.8.0_71). > > This seems something more appropriate for the dio-dev mailing list. -Alan. From brian.goetz at oracle.com Thu Feb 9 00:05:34 2017 From: brian.goetz at oracle.com (Brian Goetz) Date: Wed, 8 Feb 2017 16:05:34 -0800 Subject: Result: New Project: Amber Message-ID: <0930C5E0-1C23-4C64-9B72-15A2C8D68BB1@oracle.com> Voting on Project Amber [1], with initial Lead of Brian Goetz, is now closed. Yes: 23 Veto: 0 Abstain: 0 Invalid (vote by non-committer): 1 According to the Bylaws definition of Lazy Consensus, this is sufficient to approve the new Project and its initial Lead. -Brian Goetz [1] http://mail.openjdk.java.net/pipermail/discuss/2017-January/004099.html From john.r.rose at oracle.com Wed Feb 22 20:01:49 2017 From: john.r.rose at oracle.com (John Rose) Date: Wed, 22 Feb 2017 12:01:49 -0800 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Vote: yes (Noting, for the curious, that Alpine Road runs through Portola Valley, California.) ? John > On Feb 22, 2017, at 10:17 AM, Mikael Vidstedt wrote: > > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. From maurizio.cimadamore at oracle.com Wed Feb 22 21:52:28 2017 From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore) Date: Wed, 22 Feb 2017 21:52:28 +0000 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Vote: yes Maurizio On 22/02/17 18:17, Mikael Vidstedt wrote: > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote From dalibor.topic at oracle.com Wed Feb 22 22:33:21 2017 From: dalibor.topic at oracle.com (dalibor topic) Date: Wed, 22 Feb 2017 23:33:21 +0100 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Vote: Yes! The OpenJDK Porters Group is a sponsor of this Project. cheers, dalibor topic, OpenJDK Porters Group Lead -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From david.holmes at oracle.com Thu Feb 23 03:19:22 2017 From: david.holmes at oracle.com (David Holmes) Date: Thu, 23 Feb 2017 13:19:22 +1000 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <5998059b-d072-6730-861e-d6c1de1e5963@oracle.com> Vote: yes David On 23/02/2017 4:17 AM, Mikael Vidstedt wrote: > > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote > From mark.reinhold at oracle.com Thu Feb 23 03:54:13 2017 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Wed, 22 Feb 2017 19:54:13 -0800 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <20170222195413.767217993@eggemoggin.niobe.net> Vote: yes - Mark From peter.lawrey at gmail.com Thu Feb 23 06:46:09 2017 From: peter.lawrey at gmail.com (Peter Lawrey) Date: Thu, 23 Feb 2017 06:46:09 +0000 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Vote: Yes On 22 Feb 2017 21:53, "Maurizio Cimadamore" wrote: > Vote: yes > > Maurizio > > > On 22/02/17 18:17, Mikael Vidstedt wrote: > >> I hereby propose the creation of Project Portola with myself as the >> Lead and the Porters group as the sponsoring group. >> >> This Project will provide a port of the JDK to the Alpine Linux [1] >> distribution, and in particular the "musl" C library [2]. >> >> About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 >> Committer, and also a Committer in the Panama project where he has >> been working on providing significantly improved support for >> foreign/native data and function access. He is working in the Hotspot >> team at Oracle, and has been working with JVMs for more than 15 years. >> >> The initial Reviewers and Committers will be: >> >> Mikael Vidstedt >> David Holmes >> Erik Joelsson >> Kumar Srinivasan >> Alan Bateman >> Vladimir Kozlov >> Sangheon Kim >> Poonam Bajaj >> Jini George >> >> The project will host at least the following mailing list: >> >> * portola-dev for development discussions and user feedback >> >> The initial source of this project will be based on a clone of a JDK >> 10 repository. Changes from the JDK 10 parent will be synced into >> Portola periodically. Similar to Projects Lambda and Valhalla, we will >> follow a "commit first, review later" policy, as code will not flow >> directly from the Portola repositories into the JDK repositories, but >> instead will be done by a "curated merge" where select changes are >> extracted into new changesets for incorporation into JDK repositories >> when they are ready for inclusion. >> >> Votes are due by March 8, 2017. >> >> Only current OpenJDK Members [3] are eligible to vote on this motion. >> Votes must be cast in the open on the discuss list. Replying to this >> message is sufficient if your mail program honors the Reply-To header. >> >> For Lazy Consensus voting instructions, see [4]. >> >> >> [1] https://www.alpinelinux.org >> [2] http://www.musl-libc.org >> [3] http://openjdk.java.net/census#members >> [4] http://openjdk.java.net/projects/#new-project-vote >> > > From laurent.daynes at oracle.com Thu Feb 23 08:35:35 2017 From: laurent.daynes at oracle.com (Laurent Daynes) Date: Thu, 23 Feb 2017 09:35:35 +0100 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <58AE9ED7.3090300@oracle.com> Vote:yes On 2/22/17 7:17 PM, Mikael Vidstedt wrote: > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote From volker.simonis at gmail.com Thu Feb 23 10:05:51 2017 From: volker.simonis at gmail.com (Volker Simonis) Date: Thu, 23 Feb 2017 11:05:51 +0100 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Vote: yes As you can see from my vote, I'm all for this project, but I have several comments and questions: 1. According to the OpenJDK guide lines "It is recommended (and I'd consider it "good style") that any proposal for a new Project be discussed publicly before being proposed for a vote. I haven't seen such a discussion :) 2. What is the scope of this "port" - will it be considered as a new OS or will it be handled as a "linux" flavor? 3. Which architectures will be supported? From a quick look at the "musl" page I saw that s390 is not supported and aarch64 support is only experimental. Thank you and best regards, Volker [1] http://openjdk.java.net/projects/#new-project On Wed, Feb 22, 2017 at 7:17 PM, Mikael Vidstedt wrote: > > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote From vladimir.kozlov at oracle.com Thu Feb 23 18:20:13 2017 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Thu, 23 Feb 2017 10:20:13 -0800 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <8ff5036c-21ab-8148-1fb6-ae3fa9153ab0@oracle.com> Vote: yes On 2/22/17 10:17 AM, Mikael Vidstedt wrote: > > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote > From Peter.B.Kessler at Oracle.COM Thu Feb 23 18:25:40 2017 From: Peter.B.Kessler at Oracle.COM (Peter B. Kessler) Date: Thu, 23 Feb 2017 10:25:40 -0800 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Vote: yes. ... peter On 02/22/17 10:17 AM, Mikael Vidstedt wrote: > > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > .... From mikael.vidstedt at oracle.com Thu Feb 23 18:58:37 2017 From: mikael.vidstedt at oracle.com (Mikael Vidstedt) Date: Thu, 23 Feb 2017 10:58:37 -0800 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Volker, Thank you for the excellent comments/questions. My bad on not bringing this up for discussion before sending out the CFV - I must have listened too closely to the violent agreement amongst all the voices in my head. I think we'd have to discover and discuss as part of the project how exactly to model the Alpine/musl port, but if it helps the preliminary investigation I did on linux/x64 before sending this CFV out tells me that the changes seem to mostly revolve around cleaning up various parts of the ?linux" (and ?posix") JDK sources, effectively just making the code base as a whole more portable. That preliminary work did not uncover anything inherently CPU architecture specific, so until proven otherwise I would assume that the musl supported platforms is the limiting factor. Hope this helps, Mikael > On Feb 23, 2017, at 2:05 AM, Volker Simonis wrote: > > Vote: yes > > As you can see from my vote, I'm all for this project, but I have > several comments and questions: > > 1. According to the OpenJDK guide lines "It is recommended (and I'd > consider it "good style") that any proposal for a new Project be > discussed publicly before being proposed for a vote. I haven't seen > such a discussion :) > 2. What is the scope of this "port" - will it be considered as a new > OS or will it be handled as a "linux" flavor? > 3. Which architectures will be supported? From a quick look at the > "musl" page I saw that s390 is not supported and aarch64 support is > only experimental. > > Thank you and best regards, > Volker > > [1] http://openjdk.java.net/projects/#new-project > > On Wed, Feb 22, 2017 at 7:17 PM, Mikael Vidstedt > wrote: >> >> I hereby propose the creation of Project Portola with myself as the >> Lead and the Porters group as the sponsoring group. >> >> This Project will provide a port of the JDK to the Alpine Linux [1] >> distribution, and in particular the "musl" C library [2]. >> >> About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 >> Committer, and also a Committer in the Panama project where he has >> been working on providing significantly improved support for >> foreign/native data and function access. He is working in the Hotspot >> team at Oracle, and has been working with JVMs for more than 15 years. >> >> The initial Reviewers and Committers will be: >> >> Mikael Vidstedt >> David Holmes >> Erik Joelsson >> Kumar Srinivasan >> Alan Bateman >> Vladimir Kozlov >> Sangheon Kim >> Poonam Bajaj >> Jini George >> >> The project will host at least the following mailing list: >> >> * portola-dev for development discussions and user feedback >> >> The initial source of this project will be based on a clone of a JDK >> 10 repository. Changes from the JDK 10 parent will be synced into >> Portola periodically. Similar to Projects Lambda and Valhalla, we will >> follow a "commit first, review later" policy, as code will not flow >> directly from the Portola repositories into the JDK repositories, but >> instead will be done by a "curated merge" where select changes are >> extracted into new changesets for incorporation into JDK repositories >> when they are ready for inclusion. >> >> Votes are due by March 8, 2017. >> >> Only current OpenJDK Members [3] are eligible to vote on this motion. >> Votes must be cast in the open on the discuss list. Replying to this >> message is sufficient if your mail program honors the Reply-To header. >> >> For Lazy Consensus voting instructions, see [4]. >> >> >> [1] https://www.alpinelinux.org >> [2] http://www.musl-libc.org >> [3] http://openjdk.java.net/census#members >> [4] http://openjdk.java.net/projects/#new-project-vote From magnus.ihse.bursie at oracle.com Thu Feb 23 20:48:46 2017 From: magnus.ihse.bursie at oracle.com (Magnus Ihse Bursie) Date: Thu, 23 Feb 2017 21:48:46 +0100 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <7d368a98-6513-f16d-376b-22da758d64a0@oracle.com> Vote: yes /Magnus On 2017-02-22 19:17, Mikael Vidstedt wrote: > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote From volker.simonis at gmail.com Fri Feb 24 08:14:12 2017 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 24 Feb 2017 09:14:12 +0100 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: Hi Mikael, thanks for sharing more details. I agree that cleaning the linux/posix parts up is desirable and a nice side effect of this project. Will Alpine/musl be an Oracle-supported platform, i.e. will it be tested by JPRT? Regards, Volker On Thu, Feb 23, 2017 at 7:58 PM, Mikael Vidstedt wrote: > > Volker, > > Thank you for the excellent comments/questions. My bad on not bringing this up for discussion before sending out the CFV - I must have listened too closely to the violent agreement amongst all the voices in my head. > > I think we'd have to discover and discuss as part of the project how exactly to model the Alpine/musl port, but if it helps the preliminary investigation I did on linux/x64 before sending this CFV out tells me that the changes seem to mostly revolve around cleaning up various parts of the ?linux" (and ?posix") JDK sources, effectively just making the code base as a whole more portable. That preliminary work did not uncover anything inherently CPU architecture specific, so until proven otherwise I would assume that the musl supported platforms is the limiting factor. > > Hope this helps, > Mikael > > >> On Feb 23, 2017, at 2:05 AM, Volker Simonis wrote: >> >> Vote: yes >> >> As you can see from my vote, I'm all for this project, but I have >> several comments and questions: >> >> 1. According to the OpenJDK guide lines "It is recommended (and I'd >> consider it "good style") that any proposal for a new Project be >> discussed publicly before being proposed for a vote. I haven't seen >> such a discussion :) >> 2. What is the scope of this "port" - will it be considered as a new >> OS or will it be handled as a "linux" flavor? >> 3. Which architectures will be supported? From a quick look at the >> "musl" page I saw that s390 is not supported and aarch64 support is >> only experimental. >> >> Thank you and best regards, >> Volker >> >> [1] http://openjdk.java.net/projects/#new-project >> >> On Wed, Feb 22, 2017 at 7:17 PM, Mikael Vidstedt >> wrote: >>> >>> I hereby propose the creation of Project Portola with myself as the >>> Lead and the Porters group as the sponsoring group. >>> >>> This Project will provide a port of the JDK to the Alpine Linux [1] >>> distribution, and in particular the "musl" C library [2]. >>> >>> About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 >>> Committer, and also a Committer in the Panama project where he has >>> been working on providing significantly improved support for >>> foreign/native data and function access. He is working in the Hotspot >>> team at Oracle, and has been working with JVMs for more than 15 years. >>> >>> The initial Reviewers and Committers will be: >>> >>> Mikael Vidstedt >>> David Holmes >>> Erik Joelsson >>> Kumar Srinivasan >>> Alan Bateman >>> Vladimir Kozlov >>> Sangheon Kim >>> Poonam Bajaj >>> Jini George >>> >>> The project will host at least the following mailing list: >>> >>> * portola-dev for development discussions and user feedback >>> >>> The initial source of this project will be based on a clone of a JDK >>> 10 repository. Changes from the JDK 10 parent will be synced into >>> Portola periodically. Similar to Projects Lambda and Valhalla, we will >>> follow a "commit first, review later" policy, as code will not flow >>> directly from the Portola repositories into the JDK repositories, but >>> instead will be done by a "curated merge" where select changes are >>> extracted into new changesets for incorporation into JDK repositories >>> when they are ready for inclusion. >>> >>> Votes are due by March 8, 2017. >>> >>> Only current OpenJDK Members [3] are eligible to vote on this motion. >>> Votes must be cast in the open on the discuss list. Replying to this >>> message is sufficient if your mail program honors the Reply-To header. >>> >>> For Lazy Consensus voting instructions, see [4]. >>> >>> >>> [1] https://www.alpinelinux.org >>> [2] http://www.musl-libc.org >>> [3] http://openjdk.java.net/census#members >>> [4] http://openjdk.java.net/projects/#new-project-vote > From dalibor.topic at oracle.com Fri Feb 24 13:34:54 2017 From: dalibor.topic at oracle.com (dalibor topic) Date: Fri, 24 Feb 2017 14:34:54 +0100 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <9f65c6bb-154a-213b-8e48-71346750922d@oracle.com> On 23.02.2017 19:58, Mikael Vidstedt wrote: > I would assume that the musl supported platforms is the limiting factor. For reference, a list can be found at https://www.musl-libc.org/doc/1.0.0/manual.html cheers, dalibor topic -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From iris.clark at oracle.com Fri Feb 24 17:11:47 2017 From: iris.clark at oracle.com (Iris Clark) Date: Fri, 24 Feb 2017 09:11:47 -0800 (PST) Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <684b86fe-ac76-43d0-b781-e0dc210629bf@default> Vote: yes iris From mikael.vidstedt at oracle.com Mon Feb 27 16:52:38 2017 From: mikael.vidstedt at oracle.com (Mikael Vidstedt) Date: Mon, 27 Feb 2017 08:52:38 -0800 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: We?re still working out the details around how this can be built and tested, so about the only thing I know right now is that It?s highly likely that we?ll choose to cross-compile from our usual linux glibc based (x64) machines. Cheers, Mikael > On Feb 24, 2017, at 12:14 AM, Volker Simonis wrote: > > Hi Mikael, > > thanks for sharing more details. I agree that cleaning the linux/posix > parts up is desirable and a nice side effect of this project. > Will Alpine/musl be an Oracle-supported platform, i.e. will it be > tested by JPRT? > > Regards, > Volker > > > On Thu, Feb 23, 2017 at 7:58 PM, Mikael Vidstedt > wrote: >> >> Volker, >> >> Thank you for the excellent comments/questions. My bad on not bringing this up for discussion before sending out the CFV - I must have listened too closely to the violent agreement amongst all the voices in my head. >> >> I think we'd have to discover and discuss as part of the project how exactly to model the Alpine/musl port, but if it helps the preliminary investigation I did on linux/x64 before sending this CFV out tells me that the changes seem to mostly revolve around cleaning up various parts of the ?linux" (and ?posix") JDK sources, effectively just making the code base as a whole more portable. That preliminary work did not uncover anything inherently CPU architecture specific, so until proven otherwise I would assume that the musl supported platforms is the limiting factor. >> >> Hope this helps, >> Mikael >> >> >>> On Feb 23, 2017, at 2:05 AM, Volker Simonis wrote: >>> >>> Vote: yes >>> >>> As you can see from my vote, I'm all for this project, but I have >>> several comments and questions: >>> >>> 1. According to the OpenJDK guide lines "It is recommended (and I'd >>> consider it "good style") that any proposal for a new Project be >>> discussed publicly before being proposed for a vote. I haven't seen >>> such a discussion :) >>> 2. What is the scope of this "port" - will it be considered as a new >>> OS or will it be handled as a "linux" flavor? >>> 3. Which architectures will be supported? From a quick look at the >>> "musl" page I saw that s390 is not supported and aarch64 support is >>> only experimental. >>> >>> Thank you and best regards, >>> Volker >>> >>> [1] http://openjdk.java.net/projects/#new-project >>> >>> On Wed, Feb 22, 2017 at 7:17 PM, Mikael Vidstedt >>> wrote: >>>> >>>> I hereby propose the creation of Project Portola with myself as the >>>> Lead and the Porters group as the sponsoring group. >>>> >>>> This Project will provide a port of the JDK to the Alpine Linux [1] >>>> distribution, and in particular the "musl" C library [2]. >>>> >>>> About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 >>>> Committer, and also a Committer in the Panama project where he has >>>> been working on providing significantly improved support for >>>> foreign/native data and function access. He is working in the Hotspot >>>> team at Oracle, and has been working with JVMs for more than 15 years. >>>> >>>> The initial Reviewers and Committers will be: >>>> >>>> Mikael Vidstedt >>>> David Holmes >>>> Erik Joelsson >>>> Kumar Srinivasan >>>> Alan Bateman >>>> Vladimir Kozlov >>>> Sangheon Kim >>>> Poonam Bajaj >>>> Jini George >>>> >>>> The project will host at least the following mailing list: >>>> >>>> * portola-dev for development discussions and user feedback >>>> >>>> The initial source of this project will be based on a clone of a JDK >>>> 10 repository. Changes from the JDK 10 parent will be synced into >>>> Portola periodically. Similar to Projects Lambda and Valhalla, we will >>>> follow a "commit first, review later" policy, as code will not flow >>>> directly from the Portola repositories into the JDK repositories, but >>>> instead will be done by a "curated merge" where select changes are >>>> extracted into new changesets for incorporation into JDK repositories >>>> when they are ready for inclusion. >>>> >>>> Votes are due by March 8, 2017. >>>> >>>> Only current OpenJDK Members [3] are eligible to vote on this motion. >>>> Votes must be cast in the open on the discuss list. Replying to this >>>> message is sufficient if your mail program honors the Reply-To header. >>>> >>>> For Lazy Consensus voting instructions, see [4]. >>>> >>>> >>>> [1] https://www.alpinelinux.org >>>> [2] http://www.musl-libc.org >>>> [3] http://openjdk.java.net/census#members >>>> [4] http://openjdk.java.net/projects/#new-project-vote >> From stuart.marks at oracle.com Tue Feb 28 10:06:10 2017 From: stuart.marks at oracle.com (Stuart Marks) Date: Tue, 28 Feb 2017 10:06:10 +0000 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <77544392-3db9-bb6b-983f-e6845d5cf1aa@oracle.com> Vote: yes On 2/22/17 6:17 PM, Mikael Vidstedt wrote: > > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote > From logan at gedanken.org Tue Feb 28 16:35:26 2017 From: logan at gedanken.org (Logan O'Sullivan Bruns) Date: Tue, 28 Feb 2017 08:35:26 -0800 Subject: introduction and some questions Message-ID: <20170228083526.000061ea@gedanken.org> Hi, I just signed the OCA and had a couple of questions on how to best get started. I'm a software engineer and have been working in the industry for a number of years. I currently work for LinkedIn. If you are curious about the specifics or where else I've worked you can find most of it here (still need to finish filling in all role descriptions at some point): https://www.linkedin.com/in/loganbruns/ I have a few areas of interest in the JDK but I also just want to make more of an effort, in general, to contribute back to tools I use and value. To this end I figured I'd start with some small bug fixes. For a start I've noticed that jshell in jdk9 doesn't currently work well within the shell mode of my beloved Emacs. A very minor change to the terminal handling fixes this and I have a patch for the change. (Which might the dwindling group of emacs lovers happy if it is addressed before jdk9 goes out.) For other projects I might find a bug or enhancement possibility. Fix and test it. File a bug mentioning that I also have a suggested fix. Then create a pull request referencing the bug. In this case, I've signed the OCA but I don't see a way to create a bug? There doesn't seem to be a way to create an account on the bug database? Where would be the best place to start? Thanks, logan From neugens.limasoftware at gmail.com Tue Feb 28 17:22:35 2017 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Tue, 28 Feb 2017 18:22:35 +0100 Subject: introduction and some questions In-Reply-To: <20170228083526.000061ea@gedanken.org> References: <20170228083526.000061ea@gedanken.org> Message-ID: 2017-02-28 17:35 GMT+01:00 Logan O'Sullivan Bruns : > Hi, > > I just signed the OCA and had a couple of questions on how to best get > started. I'm a software engineer and have been working in the industry > for a number of years. I currently work for LinkedIn. If you are > curious about the specifics or where else I've worked you can find > most of it here (still need to finish filling in all role descriptions > at some point): > > https://www.linkedin.com/in/loganbruns/ > > I have a few areas of interest in the JDK but I also just want to make > more of an effort, in general, to contribute back to tools I use and > value. To this end I figured I'd start with some small bug > fixes. > > For a start I've noticed that jshell in jdk9 doesn't currently work > well within the shell mode of my beloved Emacs. A very minor change to > the terminal handling fixes this and I have a patch for the change. > (Which might the dwindling group of emacs lovers happy if it is > addressed before jdk9 goes out.) > > For other projects I might find a bug or enhancement > possibility. Fix and test it. File a bug mentioning that I also have a > suggested fix. Then create a pull request referencing the bug. > > In this case, I've signed the OCA but I don't see a way to create a > bug? There doesn't seem to be a way to create an account on the bug > database? Where would be the best place to start? Hello Logan, welcome! You need to be an Author[1] to file bug reports and create changesets o webrev. However, if the patch is small enough, you may be able to just post it inline with the email (not attached, mailing list strip attachments), you then will need a sponsor to do the heavy work of creating the bug report, reviewing the patch and pushing it on your behalf. When you have enough of those contributions you will be an Author and can do everything by yourself (pending approvals, of course); the process ramps up pretty quickly if you have a number of small patches or significant ones that pile up, but it has a slow warmup time. The best place to start would be to identify the area of the patch and propose it to the relative mailing list. The timing maybe unfortunate though, 9 is in a finalisation phase so only specific bugs are allowed to be pushed into the repositories, which also means everybody is super busy and response time is slower. In general you need to work your way from the latest and back port things, so you should start with 10 (which is semi-open at this stage). I do recommend to work directly on 10 nevertheless. This page highlights some of the process involved in more details: http://openjdk.java.net/contribute/ Cheers, Mario [1] http://openjdk.java.net/bylaws#author -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens Proud GNU Classpath developer: http://www.classpath.org/ OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From benjamin.john.evans at gmail.com Tue Feb 28 17:32:29 2017 From: benjamin.john.evans at gmail.com (Ben Evans) Date: Tue, 28 Feb 2017 12:32:29 -0500 Subject: introduction and some questions In-Reply-To: <20170228083526.000061ea@gedanken.org> References: <20170228083526.000061ea@gedanken.org> Message-ID: Hi Logan, Welcome to OpenJDK. One thing we recommend is that new developers coming from the community can contact the Adoption Group (http://openjdk.java.net/groups/adoption/), where we can provide more targetted help. In general, OpenJDK tends to be a bit more of an "earn your stripes" community than some others you may have participated in - and that's partly tied up with the release cycle of major versions. You've joined at a bit of an odd time, as the rampdown process for 9 is already well underway - so all the committers are very busy & there's not a lot of scope to get new changes in. However, I would still subscribe to kulla-dev (the group for jshell) and explain the bug & your patch there, and see if it can be classified as a bug of sufficient need to still make the initial SE 9 release (although, at a guess, I would say that's probably unlikely). Thanks, Ben On Tue, Feb 28, 2017 at 11:35 AM, Logan O'Sullivan Bruns wrote: > Hi, > > I just signed the OCA and had a couple of questions on how to best get > started. I'm a software engineer and have been working in the industry > for a number of years. I currently work for LinkedIn. If you are > curious about the specifics or where else I've worked you can find > most of it here (still need to finish filling in all role descriptions > at some point): > > https://www.linkedin.com/in/loganbruns/ > > I have a few areas of interest in the JDK but I also just want to make > more of an effort, in general, to contribute back to tools I use and > value. To this end I figured I'd start with some small bug > fixes. > > For a start I've noticed that jshell in jdk9 doesn't currently work > well within the shell mode of my beloved Emacs. A very minor change to > the terminal handling fixes this and I have a patch for the change. > (Which might the dwindling group of emacs lovers happy if it is > addressed before jdk9 goes out.) > > For other projects I might find a bug or enhancement > possibility. Fix and test it. File a bug mentioning that I also have a > suggested fix. Then create a pull request referencing the bug. > > In this case, I've signed the OCA but I don't see a way to create a > bug? There doesn't seem to be a way to create an account on the bug > database? Where would be the best place to start? > > Thanks, > logan From jonathan.gibbons at oracle.com Tue Feb 28 18:08:20 2017 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 28 Feb 2017 10:08:20 -0800 Subject: introduction and some questions In-Reply-To: References: <20170228083526.000061ea@gedanken.org> Message-ID: <58B5BC94.4080401@oracle.com> Although, as Ben noted, the rampdown process for 9 is already well underway, the repos for 10 are already open, so anything that may be too late for 9 may be a candidate for 10. -- Jon On 02/28/2017 09:32 AM, Ben Evans wrote: > Hi Logan, > > Welcome to OpenJDK. One thing we recommend is that new developers > coming from the community can contact the Adoption Group > (http://openjdk.java.net/groups/adoption/), where we can provide more > targetted help. > > In general, OpenJDK tends to be a bit more of an "earn your stripes" > community than some others you may have participated in - and that's > partly tied up with the release cycle of major versions. > > You've joined at a bit of an odd time, as the rampdown process for 9 > is already well underway - so all the committers are very busy & > there's not a lot of scope to get new changes in. > > However, I would still subscribe to kulla-dev (the group for jshell) > and explain the bug & your patch there, and see if it can be > classified as a bug of sufficient need to still make the initial SE 9 > release (although, at a guess, I would say that's probably unlikely). > > Thanks, > > Ben > > > On Tue, Feb 28, 2017 at 11:35 AM, Logan O'Sullivan Bruns > wrote: >> Hi, >> >> I just signed the OCA and had a couple of questions on how to best get >> started. I'm a software engineer and have been working in the industry >> for a number of years. I currently work for LinkedIn. If you are >> curious about the specifics or where else I've worked you can find >> most of it here (still need to finish filling in all role descriptions >> at some point): >> >> https://www.linkedin.com/in/loganbruns/ >> >> I have a few areas of interest in the JDK but I also just want to make >> more of an effort, in general, to contribute back to tools I use and >> value. To this end I figured I'd start with some small bug >> fixes. >> >> For a start I've noticed that jshell in jdk9 doesn't currently work >> well within the shell mode of my beloved Emacs. A very minor change to >> the terminal handling fixes this and I have a patch for the change. >> (Which might the dwindling group of emacs lovers happy if it is >> addressed before jdk9 goes out.) >> >> For other projects I might find a bug or enhancement >> possibility. Fix and test it. File a bug mentioning that I also have a >> suggested fix. Then create a pull request referencing the bug. >> >> In this case, I've signed the OCA but I don't see a way to create a >> bug? There doesn't seem to be a way to create an account on the bug >> database? Where would be the best place to start? >> >> Thanks, >> logan From jonathan.gibbons at oracle.com Tue Feb 28 18:13:24 2017 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 28 Feb 2017 10:13:24 -0800 Subject: CFV: Project Portola In-Reply-To: References: <7B5C2CBF-1659-44AF-9030-05700B09BBBB@oracle.com> Message-ID: <58B5BDC4.3060900@oracle.com> Vote: yes On 02/22/2017 10:17 AM, Mikael Vidstedt wrote: > I hereby propose the creation of Project Portola with myself as the > Lead and the Porters group as the sponsoring group. > > This Project will provide a port of the JDK to the Alpine Linux [1] > distribution, and in particular the "musl" C library [2]. > > About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9 > Committer, and also a Committer in the Panama project where he has > been working on providing significantly improved support for > foreign/native data and function access. He is working in the Hotspot > team at Oracle, and has been working with JVMs for more than 15 years. > > The initial Reviewers and Committers will be: > > Mikael Vidstedt > David Holmes > Erik Joelsson > Kumar Srinivasan > Alan Bateman > Vladimir Kozlov > Sangheon Kim > Poonam Bajaj > Jini George > > The project will host at least the following mailing list: > > * portola-dev for development discussions and user feedback > > The initial source of this project will be based on a clone of a JDK > 10 repository. Changes from the JDK 10 parent will be synced into > Portola periodically. Similar to Projects Lambda and Valhalla, we will > follow a "commit first, review later" policy, as code will not flow > directly from the Portola repositories into the JDK repositories, but > instead will be done by a "curated merge" where select changes are > extracted into new changesets for incorporation into JDK repositories > when they are ready for inclusion. > > Votes are due by March 8, 2017. > > Only current OpenJDK Members [3] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [4]. > > > [1] https://www.alpinelinux.org > [2] http://www.musl-libc.org > [3] http://openjdk.java.net/census#members > [4] http://openjdk.java.net/projects/#new-project-vote From forax at univ-mlv.fr Tue Feb 28 18:32:59 2017 From: forax at univ-mlv.fr (Remi Forax) Date: Tue, 28 Feb 2017 18:32:59 +0000 Subject: introduction and some questions In-Reply-To: <58B5BC94.4080401@oracle.com> References: <20170228083526.000061ea@gedanken.org> <58B5BC94.4080401@oracle.com> Message-ID: And the patch can be backported from 10 to 9 in an update release if necessary. Remi On February 28, 2017 7:08:20 PM GMT+01:00, Jonathan Gibbons wrote: >Although, as Ben noted, the rampdown process for 9 is already well >underway, >the repos for 10 are already open, so anything that may be too late for >9 >may be a candidate for 10. > >-- Jon > >On 02/28/2017 09:32 AM, Ben Evans wrote: >> Hi Logan, >> >> Welcome to OpenJDK. One thing we recommend is that new developers >> coming from the community can contact the Adoption Group >> (http://openjdk.java.net/groups/adoption/), where we can provide more >> targetted help. >> >> In general, OpenJDK tends to be a bit more of an "earn your stripes" >> community than some others you may have participated in - and that's >> partly tied up with the release cycle of major versions. >> >> You've joined at a bit of an odd time, as the rampdown process for 9 >> is already well underway - so all the committers are very busy & >> there's not a lot of scope to get new changes in. >> >> However, I would still subscribe to kulla-dev (the group for jshell) >> and explain the bug & your patch there, and see if it can be >> classified as a bug of sufficient need to still make the initial SE 9 >> release (although, at a guess, I would say that's probably unlikely). >> >> Thanks, >> >> Ben >> >> >> On Tue, Feb 28, 2017 at 11:35 AM, Logan O'Sullivan Bruns >> wrote: >>> Hi, >>> >>> I just signed the OCA and had a couple of questions on how to best >get >>> started. I'm a software engineer and have been working in the >industry >>> for a number of years. I currently work for LinkedIn. If you are >>> curious about the specifics or where else I've worked you can find >>> most of it here (still need to finish filling in all role >descriptions >>> at some point): >>> >>> https://www.linkedin.com/in/loganbruns/ >>> >>> I have a few areas of interest in the JDK but I also just want to >make >>> more of an effort, in general, to contribute back to tools I use and >>> value. To this end I figured I'd start with some small bug >>> fixes. >>> >>> For a start I've noticed that jshell in jdk9 doesn't currently work >>> well within the shell mode of my beloved Emacs. A very minor change >to >>> the terminal handling fixes this and I have a patch for the change. >>> (Which might the dwindling group of emacs lovers happy if it is >>> addressed before jdk9 goes out.) >>> >>> For other projects I might find a bug or enhancement >>> possibility. Fix and test it. File a bug mentioning that I also have >a >>> suggested fix. Then create a pull request referencing the bug. >>> >>> In this case, I've signed the OCA but I don't see a way to create a >>> bug? There doesn't seem to be a way to create an account on the bug >>> database? Where would be the best place to start? >>> >>> Thanks, >>> logan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.