Re: incremental compiler questions
I am not sure I understand your questions, maybe you can explain you what you are trying to achieve and I can tell how to do it. Few general comments As I tried to explain in the hangout, proper incremental compilation requires type reference information. Consider two classes, A and B extends A, and C. When A.java changes, it is not enough to recompile just this source, it is also necessary to recompile B.java. Javac does not provide type reference information, so the only safe way to handle any change is to recompile everything. Eclipse JDT compiler is production ready and it produces spec-compliant class files. I believe all eclipse ecosystem is built with this compiler and I've seen many projects outside of eclipse use it too. "Eclipse jdt" is a name of Eclipse project that produces Java Development Tools (hence the name). Spec-compliant java compiler is one of deliverables of this project. -- Regards, Igor On 2015-01-09 20:02, Martin Gainty wrote: Good Evening Igor- Instead of implementing eclipe jdt for incremental java compilation is there: 1)any ability to refactor/reconfigure javac to read Last Modified Date of source file to enable incremental compilation? 2)any concerns over generated class files..are they the same? any deltas ..if so ...what are they? 3)can we implement a static settings.xml or other static configuration file that manfred suggested for eclipse jdt? 4)any ability to switch compiler from javac to jdt as an attribute in maven-compiler-plugin? Thanks for a great presentation on Maven Dev hangout Martin __ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
incremental compiler questions
Good Evening Igor- Instead of implementing eclipe jdt for incremental java compilation is there: 1)any ability to refactor/reconfigure javac to read Last Modified Date of source file to enable incremental compilation? 2)any concerns over generated class files..are they the same? any deltas ..if so ...what are they? 3)can we implement a static settings.xml or other static configuration file that manfred suggested for eclipse jdt? 4)any ability to switch compiler from javac to jdt as an attribute in maven-compiler-plugin? Thanks for a great presentation on Maven Dev hangout Martin __
Re: Releasing the Checkstyle Plugin
Definitely does not count as a regression, although like all fixed bugs it has end user value. You call, I say go for 1.6 and use the extra time & energy elsewhere :) K The only fixed issue that could I see that could have a direct benefit to end users is: http://jira.codehaus.org/browse/MCHECKSTYLE-254 Update plexus-interpolation to avoid thread safety issues But I don't know if anyone has had any problems with this specifically regarding the Checkstyle Plugin, or if it is just a part of the regular "use the latest version to be on the safe side" maintenance. On Fri, Jan 9, 2015 at 2:13 PM, Kristian Rosenvold wrote: > As long as we're not regressed on the latest version I'd say that's > your call right now. > > Kristian > > > 2015-01-09 13:29 GMT+01:00 Dennis Lundberg : >> I've started going through the open issues and have found a problem >> that I need som help with. It turns out that Checkstyle 5.9 uses Java >> 6 classes, even though it is not mentioned in the release notes. How >> do we want to handle this? I see two possible options: >> >> 1. Make version 2.14 of the plugin require Java 6, and update it to >> use the latest available version of Checkstyle that runs on Java 6. >> >> 2. Revert the plugin back to Checkstyle 5.8 and release 2.14 of the >> plugin with a Java 5 requirement. After that release 2.15 of the >> plugin fairly straight away with a Java 6 requirement, and using the >> latest available version of Checkstyle that runs on Java 6. It should >> be noted that Checkstyle 5.8 does NOT work on Java 8 source code. >> >> Perhaps there are other alternatives? What do you think? >> >> On Thu, Jan 8, 2015 at 3:51 PM, Dennis Lundberg wrote: >>> Hi, >>> >>> I'd like to release version 2.14 of Maven Checkstyle Plugin. The main >>> motive for 2.14 is the ability to check Java 8 source code. >>> >>> According to the road map there are 5 unresolved issues scheduled for 2.14. >>> >>> https://jira.codehaus.org/browse/MCHECKSTYLE#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel >>> >>> If anyone is interested in fixing one or more of these for 2.14 now >>> would be a good time to do it. Just reply here with an estimated time >>> frame. If noone has the time for this now, I'll reschedule those >>> issues for 2.15, which will require Java 6. >>> >>> -- >>> Dennis Lundberg >> >> >> >> -- >> Dennis Lundberg >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the Checkstyle Plugin
The only fixed issue that could I see that could have a direct benefit to end users is: http://jira.codehaus.org/browse/MCHECKSTYLE-254 Update plexus-interpolation to avoid thread safety issues But I don't know if anyone has had any problems with this specifically regarding the Checkstyle Plugin, or if it is just a part of the regular "use the latest version to be on the safe side" maintenance. On Fri, Jan 9, 2015 at 2:13 PM, Kristian Rosenvold wrote: > As long as we're not regressed on the latest version I'd say that's > your call right now. > > Kristian > > > 2015-01-09 13:29 GMT+01:00 Dennis Lundberg : >> I've started going through the open issues and have found a problem >> that I need som help with. It turns out that Checkstyle 5.9 uses Java >> 6 classes, even though it is not mentioned in the release notes. How >> do we want to handle this? I see two possible options: >> >> 1. Make version 2.14 of the plugin require Java 6, and update it to >> use the latest available version of Checkstyle that runs on Java 6. >> >> 2. Revert the plugin back to Checkstyle 5.8 and release 2.14 of the >> plugin with a Java 5 requirement. After that release 2.15 of the >> plugin fairly straight away with a Java 6 requirement, and using the >> latest available version of Checkstyle that runs on Java 6. It should >> be noted that Checkstyle 5.8 does NOT work on Java 8 source code. >> >> Perhaps there are other alternatives? What do you think? >> >> On Thu, Jan 8, 2015 at 3:51 PM, Dennis Lundberg wrote: >>> Hi, >>> >>> I'd like to release version 2.14 of Maven Checkstyle Plugin. The main >>> motive for 2.14 is the ability to check Java 8 source code. >>> >>> According to the road map there are 5 unresolved issues scheduled for 2.14. >>> >>> https://jira.codehaus.org/browse/MCHECKSTYLE#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel >>> >>> If anyone is interested in fixing one or more of these for 2.14 now >>> would be a good time to do it. Just reply here with an estimated time >>> frame. If noone has the time for this now, I'll reschedule those >>> issues for 2.15, which will require Java 6. >>> >>> -- >>> Dennis Lundberg >> >> >> >> -- >> Dennis Lundberg >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the Checkstyle Plugin
+1 On Jan 9, 2015, at 8:13 AM, Kristian Rosenvold wrote: > As long as we're not regressed on the latest version I'd say that's > your call right now. > > Kristian > > > 2015-01-09 13:29 GMT+01:00 Dennis Lundberg : >> I've started going through the open issues and have found a problem >> that I need som help with. It turns out that Checkstyle 5.9 uses Java >> 6 classes, even though it is not mentioned in the release notes. How >> do we want to handle this? I see two possible options: >> >> 1. Make version 2.14 of the plugin require Java 6, and update it to >> use the latest available version of Checkstyle that runs on Java 6. >> >> 2. Revert the plugin back to Checkstyle 5.8 and release 2.14 of the >> plugin with a Java 5 requirement. After that release 2.15 of the >> plugin fairly straight away with a Java 6 requirement, and using the >> latest available version of Checkstyle that runs on Java 6. It should >> be noted that Checkstyle 5.8 does NOT work on Java 8 source code. >> >> Perhaps there are other alternatives? What do you think? >> >> On Thu, Jan 8, 2015 at 3:51 PM, Dennis Lundberg wrote: >>> Hi, >>> >>> I'd like to release version 2.14 of Maven Checkstyle Plugin. The main >>> motive for 2.14 is the ability to check Java 8 source code. >>> >>> According to the road map there are 5 unresolved issues scheduled for 2.14. >>> >>> https://jira.codehaus.org/browse/MCHECKSTYLE#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel >>> >>> If anyone is interested in fixing one or more of these for 2.14 now >>> would be a good time to do it. Just reply here with an estimated time >>> frame. If noone has the time for this now, I'll reschedule those >>> issues for 2.15, which will require Java 6. >>> >>> -- >>> Dennis Lundberg >> >> >> >> -- >> Dennis Lundberg >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We all have problems. How we deal with them is a measure of our worth. -- Unknown
Re: Releasing the Checkstyle Plugin
As long as we're not regressed on the latest version I'd say that's your call right now. Kristian 2015-01-09 13:29 GMT+01:00 Dennis Lundberg : > I've started going through the open issues and have found a problem > that I need som help with. It turns out that Checkstyle 5.9 uses Java > 6 classes, even though it is not mentioned in the release notes. How > do we want to handle this? I see two possible options: > > 1. Make version 2.14 of the plugin require Java 6, and update it to > use the latest available version of Checkstyle that runs on Java 6. > > 2. Revert the plugin back to Checkstyle 5.8 and release 2.14 of the > plugin with a Java 5 requirement. After that release 2.15 of the > plugin fairly straight away with a Java 6 requirement, and using the > latest available version of Checkstyle that runs on Java 6. It should > be noted that Checkstyle 5.8 does NOT work on Java 8 source code. > > Perhaps there are other alternatives? What do you think? > > On Thu, Jan 8, 2015 at 3:51 PM, Dennis Lundberg wrote: >> Hi, >> >> I'd like to release version 2.14 of Maven Checkstyle Plugin. The main >> motive for 2.14 is the ability to check Java 8 source code. >> >> According to the road map there are 5 unresolved issues scheduled for 2.14. >> >> https://jira.codehaus.org/browse/MCHECKSTYLE#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel >> >> If anyone is interested in fixing one or more of these for 2.14 now >> would be a good time to do it. Just reply here with an estimated time >> frame. If noone has the time for this now, I'll reschedule those >> issues for 2.15, which will require Java 6. >> >> -- >> Dennis Lundberg > > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the Checkstyle Plugin
I've started going through the open issues and have found a problem that I need som help with. It turns out that Checkstyle 5.9 uses Java 6 classes, even though it is not mentioned in the release notes. How do we want to handle this? I see two possible options: 1. Make version 2.14 of the plugin require Java 6, and update it to use the latest available version of Checkstyle that runs on Java 6. 2. Revert the plugin back to Checkstyle 5.8 and release 2.14 of the plugin with a Java 5 requirement. After that release 2.15 of the plugin fairly straight away with a Java 6 requirement, and using the latest available version of Checkstyle that runs on Java 6. It should be noted that Checkstyle 5.8 does NOT work on Java 8 source code. Perhaps there are other alternatives? What do you think? On Thu, Jan 8, 2015 at 3:51 PM, Dennis Lundberg wrote: > Hi, > > I'd like to release version 2.14 of Maven Checkstyle Plugin. The main > motive for 2.14 is the ability to check Java 8 source code. > > According to the road map there are 5 unresolved issues scheduled for 2.14. > > https://jira.codehaus.org/browse/MCHECKSTYLE#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel > > If anyone is interested in fixing one or more of these for 2.14 now > would be a good time to do it. Just reply here with an estimated time > frame. If noone has the time for this now, I'll reschedule those > issues for 2.15, which will require Java 6. > > -- > Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
