[mojo-dev] [jira] Closed: (MOJO-1690) Transformation Documentation has wrong property listed

[ http://jira.codehaus.org/browse/MOJO-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann closed MOJO-1690. - Resolution: Fixed Fix Version/s: xml-maven-plugin 1.0.1 Thanks! Fixed in SVN and site. > Transf

[mojo-dev] [jira] Commented: (MGWT-300) Generated Async class does not reflect @RemoteServiceRelativePath annotation if Service is already compiled

[ http://jira.codehaus.org/browse/MGWT-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270482#comment-270482 ] Robert Scholte commented on MGWT-300: - This issue is a bit more complicated. It takes several step

[mojo-dev] [jira] Updated: (MGWT-300) Generated Async class does not reflect @RemoteServiceRelativePath annotation if Service is already compiled

[ http://jira.codehaus.org/browse/MGWT-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MGWT-300: Summary: Generated Async class does not reflect @RemoteServiceRelativePath annotation if Service is already

[mojo-dev] moving Mojo from svn to git (was: preparing 2.3.0 release -> github )

looks like this thread has come to a stop, although there are still some things to do. According to the docs [1] Codehaus is offering a git-repository, so technically there are no barriers. The only thing we still need to do is call for a vote before continuing, right? Arnaud, could you pick thi

[mojo-dev] [jira] Assigned: (MGWT-300) Generated Async class does not reflect @RemoteServiceRelativePath annotation

[ http://jira.codehaus.org/browse/MGWT-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MGWT-300: --- Assignee: Robert Scholte > Generated Async class does not reflect @RemoteServiceRelativePath annotati