[mojo-dev] [jira] Closed: (MOJO-1686) [js-import-plugin] @import declarations and regular comments

[ http://jira.codehaus.org/browse/MOJO-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Hunt closed MOJO-1686. -- Resolution: Cannot Reproduce More information is required. > [js-import-plugin] @import declarations

[mojo-dev] [jira] Commented: (MJSPC-51) Compiling JSPs with tag libraries using tag-files causes NPE in JspC

[ http://jira.codehaus.org/browse/MJSPC-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269829#action_269829 ] Pavel Veselý commented on MJSPC-51: --- Issue can be corrected by upgrading property tomcatVersion in po

[mojo-dev] [jira] Created: (MJSPC-51) Compiling JSPs with tag libraries using tag-files causes NPE in JspC

Compiling JSPs with tag libraries using tag-files causes NPE in JspC Key: MJSPC-51 URL: http://jira.codehaus.org/browse/MJSPC-51 Project: Maven 2.x JSPC Plugin Issue Type:

[mojo-dev] [jira] Issue Comment Edited: (MOJO-1685) Allow template for description section that can include variables for filename, creation time etc.

[ http://jira.codehaus.org/browse/MOJO-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269824#action_269824 ] Farrukh Najmi edited comment on MOJO-1685 at 6/8/11 10:29 AM: -- It may als

[mojo-dev] [jira] Commented: (MOJO-1685) Allow template for description section that can include variables for filename, creation time etc.

[ http://jira.codehaus.org/browse/MOJO-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269824#action_269824 ] Farrukh Najmi commented on MOJO-1685: - It may also make sense to support additional variables for

[mojo-dev] [jira] Updated: (MOJO-1686) [js-import-plugin] @import declarations and regular comments

[ http://jira.codehaus.org/browse/MOJO-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Hunt updated MOJO-1686: --- Description: Looks as though @import declarations find it difficult to live with other comments e.g

[mojo-dev] [jira] Assigned: (MOJO-1686) [js-import-plugin] @import declarations and regular comments

[ http://jira.codehaus.org/browse/MOJO-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Hunt reassigned MOJO-1686: -- Assignee: Christopher Hunt > [js-import-plugin] @import declarations and regular comments > --

[mojo-dev] [jira] Created: (MOJO-1686) [js-import-plugin] @import declarations and regular comments

[js-import-plugin] @import declarations and regular comments Key: MOJO-1686 URL: http://jira.codehaus.org/browse/MOJO-1686 Project: Mojo Issue Type: Bug Reporter: Chris

[mojo-dev] [jira] Created: (MOJO-1685) Allow template for description section that can include variables for filename, creation time etc.

Allow template for description section that can include variables for filename, creation time etc. -- Key: MOJO-1685 URL: http://jira.codehaus.org/browse/MOJO-1685

[mojo-dev] Re: [Vote] gwt-maven-plugin 2.3.0

I promise, and I'm not joking :D 2011/6/8 Thomas Broyer > OK, cast my vote to a "0" then, as there are workarounds. But only if you > promise to release more often ;-) (joking!) > > -- > You received this message because you are subscribed to the Google Groups > "Codehaus Mojo gwt-maven-plugin U

[mojo-dev] [jira] Commented: (MGWT-186) Generic Interface is not generated correctly

[ http://jira.codehaus.org/browse/MGWT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269803#action_269803 ] nicolas de loof commented on MGWT-186: -- I've setup a job to check build with maven2 and maven3 and

[mojo-dev] Re: [Vote] gwt-maven-plugin 2.3.0

What if someone complains about another unresolved issue next week ? Shall we postpone a release until everything gets fixed ? I'd like to get more release on this plugin, with smaller changes. We can plan a new release in few weeks, maybe even adopt a jenkins-like release cycle, but the major com

[mojo-dev] [jira] Commented: (MGWT-186) Generic Interface is not generated correctly

[ http://jira.codehaus.org/browse/MGWT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269801#action_269801 ] Salvador Diaz commented on MGWT-186: Ken, FWIW, the build fails when using maven 3 (more specifica

[mojo-dev] [jira] Updated: (MGWT-284) Goal "gwt:eclipse" generates buggy launch configuration

[ http://jira.codehaus.org/browse/MGWT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof updated MGWT-284: - Fix Version/s: 2.3.0-1 > Goal "gwt:eclipse" generates buggy launch configuration > -

[mojo-dev] [jira] Commented: (MGWT-284) Goal "gwt:eclipse" generates buggy launch configuration

[ http://jira.codehaus.org/browse/MGWT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269800#action_269800 ] Salvador Diaz commented on MGWT-284: Fix is now merged, can we close this issue ? > Goal "gwt:ecli

[mojo-dev] [jira] Commented: (MGWT-277) add new gwt compiler option : -deploy

[ http://jira.codehaus.org/browse/MGWT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269799#action_269799 ] Thomas Broyer commented on MGWT-277: https://github.com/gwt-maven-plugin/gwt-maven-plugin/commit/c5