We can do this after 6.0.0 too. I personally use IDEA and I cannot help here.
On Fri, Jul 27, 2012 at 6:21 PM, Bertrand Guay-Paquet <[email protected]> wrote: > Since this will be the latest and greatest Wicket, would it be possible to > include updated project files for Eclipse Juno (4.2) based on the m2e > plugin? It would make the contribution of patch files much easier to not > have to manually exclude modifications to the project files. Currently, many > "org.eclipse.core.resources.prefs" and "org.eclipse.jdt.core.prefs" files > are marked as modified when Wicket is imported in Eclipse. > > Maybe I'm pushing it, but it would be nice to have less reported warnings in > the Wicket code to be able to detect "important" warnings. Fixing all > warnings is a huge task, but in order to at least filter out many unwanted > warnings, Wicket could use Eclipse`s ability to disable some of its > validation on specific files and folders. I'm specially referring to html > and missing serialID warnings in test code. I could do some work on this > part if updated project files are committed. > > Bertrand > > > On 27/07/2012 5:44 AM, Martijn Dashorst wrote: >> >> I intend to no longer keep wicket 6 hostage to updating the website. I >> am unable to find enough time to actually work on such a noble cause >> before we should release 6. >> >> Therefore I propose I start the release building process tonight/this >> weekend, or when I find a spare moment to wrestle with maven/git/gpg. >> >> Any objections? >> >> Martijn >> >> PS I have received a 3rd party design in my inbox. It hasn't escaped >> my attention, but my personal life, a work project schedule are in >> such a conflict that I am unable to attend to such suggestions. > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
