[mojo-dev] [jira] Created: (MOJO-1577) Some bundle names create DMGs with invisible apps

Some bundle names create DMGs with invisible apps - Key: MOJO-1577 URL: http://jira.codehaus.org/browse/MOJO-1577 Project: Mojo Issue Type: Bug Components: osxappbundle Envir

Re: [mojo-dev] A fix for MSITE-459 that needs to be tested

On 2010-10-01 15:11, Brett Porter wrote: > did you mean to send it to d...@maven? No, it was intended for Mojo. The reason being that the Mojo project uses webdav as the transport when deploying sites. If my conclusions are correct, MSITE-459 only affects people using webdav. > On 01/10/2010, at

Re: [mojo-dev] A fix for MSITE-459 that needs to be tested

did you mean to send it to d...@maven? On 01/10/2010, at 7:58 PM, Dennis Lundberg wrote: > Hi > > I've seen a lot of commits and discussions about MSITE-459 lately. After > some serious digging I think I have found a fix for it, but I need some > field testing of the fix before I can mark it as

[mojo-dev] [jira] Created: (MNBMODULE-98) Stop using modules/{autoload,eager}

Stop using modules/{autoload,eager} --- Key: MNBMODULE-98 URL: http://jira.codehaus.org/browse/MNBMODULE-98 Project: Maven NetBeans Module Plugin Issue Type: Bug Affects Versions: 3.3 Reporter:

[mojo-dev] [jira] Created: (MOJO-1576) Update links of javadoc-m-p for java-ee and java-se

Update links of javadoc-m-p for java-ee and java-se Key: MOJO-1576 URL: http://jira.codehaus.org/browse/MOJO-1576 Project: Mojo Issue Type: Task Components: _Mojo Parent

[mojo-dev] [jira] Closed: (MSQL-59) Update statement failed

[ http://jira.codehaus.org/browse/MSQL-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSQL-59. -- Resolution: Cannot Reproduce Assignee: Robert Scholte > Update statement failed > ---

[mojo-dev] [jira] Issue Comment Edited: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

[ http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237085#action_237085 ] Geoffrey De Smet edited comment on MGWT-219 at 10/1/10 10:15 AM: - Attac

[mojo-dev] [jira] Issue Comment Edited: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

[ http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237085#action_237085 ] Geoffrey De Smet edited comment on MGWT-219 at 10/1/10 10:15 AM: - Attac

[mojo-dev] [jira] Commented: (MWEBSTART-138) The number of signed artifacts differ from the number of modified artifacts

[ http://jira.codehaus.org/browse/MWEBSTART-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237148#action_237148 ] Fotis Paraskevopoulos commented on MWEBSTART-138: - I am having the same issue, and

[mojo-dev] [jira] Created: (MGWT-221) The localWorkers parameter should be configurable to "the number of CPU's minus 1"

The localWorkers parameter should be configurable to "the number of CPU's minus 1" -- Key: MGWT-221 URL: http://jira.codehaus.org/browse/MGWT-221 Project: Maven 2.x GWT P

[mojo-dev] [jira] Commented: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true

[ http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237142#action_237142 ] Olivier Lamy commented on MTOMCAT-55: - thanks ! (response time can vary it depends on spare time

[mojo-dev] [jira] Commented: (MVERSIONS-125) Set dependencies to a specific version

[ http://jira.codehaus.org/browse/MVERSIONS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237139#action_237139 ] Stephen Connolly commented on MVERSIONS-125: I'll see about applying this patch once I

[mojo-dev] [jira] Commented: (MVERSIONS-127) lock-snapshots does not work on Maven 3.0-RC3

[ http://jira.codehaus.org/browse/MVERSIONS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237138#action_237138 ] Stephen Connolly commented on MVERSIONS-127: @author Paul Gier We should ask paul!

[mojo-dev] [jira] Closed: (MVERSIONS-127) lock-snapshots does not work on Maven 3.0-RC3

[ http://jira.codehaus.org/browse/MVERSIONS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly closed MVERSIONS-127. -- Resolution: Fixed Fix Version/s: 1.3 Assignee: Benjamin Bentmann r12747 >

[mojo-dev] [jira] Commented: (MVERSIONS-127) lock-snapshots does not work on Maven 3.0-RC3

[ http://jira.codehaus.org/browse/MVERSIONS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237135#action_237135 ] Stephen Connolly commented on MVERSIONS-127: I didn't write this goal, somebody else d

[mojo-dev] [jira] Updated: (MVERSIONS-127) lock-snapshots does not work on Maven 3.0-RC3

[ http://jira.codehaus.org/browse/MVERSIONS-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MVERSIONS-127: Attachment: VERSIONS-127.patch @Stephen: Is there a reason why you opted to look for m

[mojo-dev] [jira] Issue Comment Edited: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

5 AM: Nicolas, might you have a link to that issue in the GWT tracker that has the more compliant SDK, so I can track it? Until 2.1 is released (and it fixes the classpath issue), we 'll release a fork of the gwt-maven-plugin with version 2.1-20101001.MGWT219 to the jboss repo, so we can build droo

[mojo-dev] [jira] Commented: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

GWT tracker that has the more compliant SDK, so I can track it? Until 2.1 is released (and it fixes the classpath issue), we 'll release a fork of the gwt-maven-plugin with version 2.1-20101001.MGWT219 to the jboss repo, so we can build drools-guvnor (and which can be reused by anyone wh

[mojo-dev] [jira] Commented: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true

[ http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237094#action_237094 ] Mark Michaelis commented on MTOMCAT-55: --- Thanks a lot. Your code is easy to read and to underst

[mojo-dev] [jira] Commented: (MAPPASM-102) Nullpointer AssembleMojo.validate(AssembleMojo.java:227)

[ http://jira.codehaus.org/browse/MAPPASM-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237092#action_237092 ] Jochen Stiepel commented on MAPPASM-102: sorry, it's too long ago. I don't have access to th

[mojo-dev] [jira] Commented: (MGWT-220) Don't hardcode the project version as the gwt version in the IT tests but reuse the gwt.version property from the main pom (easy patch attached)

[ http://jira.codehaus.org/browse/MGWT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237088#action_237088 ] Geoffrey De Smet commented on MGWT-220: --- PS: I needed to do that, to do a inner release which has

[mojo-dev] A fix for MSITE-459 that needs to be tested

Hi I've seen a lot of commits and discussions about MSITE-459 lately. After some serious digging I think I have found a fix for it, but I need some field testing of the fix before I can mark it as closed and start releasing stuff. It'd be great if some of you could test the fix, which is describe

[mojo-dev] [jira] Updated: (MGWT-220) Don't hardcode the project version as the gwt version in the IT tests but reuse the gwt.version property from the main pom (easy patch attached)

[ http://jira.codehaus.org/browse/MGWT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey De Smet updated MGWT-220: -- Attachment: MGWT-220.patch > Don't hardcode the project version as the gwt version in the IT tests but

[mojo-dev] [jira] Created: (MGWT-220) Don't hardcode the project version as the gwt version in the IT tests but reuse the gwt.version property from the main pom (easy patch attached)

Don't hardcode the project version as the gwt version in the IT tests but reuse the gwt.version property from the main pom (easy patch attached)

[mojo-dev] [jira] Closed: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

[ http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MGWT-219. Resolution: Won't Fix Won't fix. Relying on classpath ordering is definitly a hack, Google MUST come with

[mojo-dev] [jira] Updated: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

[ http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey De Smet updated MGWT-219: -- Attachment: MGWT-219.patch Attached patch to set gwt-dev library first on the classpath given to the GW

[mojo-dev] [jira] Closed: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true

[ http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MTOMCAT-55. --- Resolution: Fixed Fix Version/s: 1.1 Assignee: Olivier Lamy fixed [rev 12745|http://fisheye

[mojo-dev] [jira] Commented: (MTOMCAT-55) Can't shutdown tomcat started with tomcat:run with fork=true

[ http://jira.codehaus.org/browse/MTOMCAT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237080#action_237080 ] ant elder commented on MTOMCAT-55: -- This is terrific Mark, really looking forward to it getting out

[mojo-dev] [jira] Issue Comment Edited: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

[ http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237075#action_237075 ] Geoffrey De Smet edited comment on MGWT-219 at 10/1/10 3:22 AM: Reopeni

[mojo-dev] [jira] Reopened: (MGWT-219) In gwt:compile the gwt-dev library should be on the classpath before the project dependencies

[ http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey De Smet reopened MGWT-219: --- Reopening: In the Eclipse and IntelliJ plugin we can set the order of the entry's in the classpath given

[mojo-dev] [jira] Created: (MOJO-1575) In POM the schema is not specified, and since then code completion dont work in Eclipse for example

In POM the schema is not specified, and since then code completion dont work in Eclipse for example --- Key: MOJO-1575 URL: http://jira.codehaus.org/browse/MOJO-1575

[mojo-dev] [jira] Commented: (MOJO-1574) I cannot specify JVM to run on, and the -server argument is wired into the code. This will fail running on JRE

[ http://jira.codehaus.org/browse/MOJO-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237071#action_237071 ] Gábor Lipták commented on MOJO-1574: And a comment: this is mainly because JRE do not have -server

[mojo-dev] [jira] Created: (MOJO-1574) I cannot specify JVM to run on, and the -server argument is wired into the code. This will fail running on JRE

I cannot specify JVM to run on, and the -server argument is wired into the code. This will fail running on JRE -- Key: MOJO-1574 URL: http://jira.codehaus.