RE: [mojo-dev] [RESULT] [VOTE] Retire xslt-maven-plugin

If you take a look at this page (http://mojo.codehaus.org/plugins.html) you'll see the plugins are devided in several sections: production-plugins (non alpha or beta) pre-release plugins sandbox graveyard The xslt-plugin was already available as production plugin, while the xml-plugin is st

[mojo-dev] [jira] Commented: (MNBMODULE-72) missing update-tracking files in the created nbm-application

[ http://jira.codehaus.org/browse/MNBMODULE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203277#action_203277 ] Jesse Glick commented on MNBMODULE-72: -- "the hard part is figuring what jar within the nbm is

Re: [mojo-dev] [apt] requesting a patch apply and release MOJO-1478

Hi Mark, thanks for taking interest in my troubles. See my updates to the issue with a new patch. If you run the tests with the new patch applied then the changes get suitably exercised by the ITs. Preferably you can run it on something other than OSX to verify. Let me know if I can be of more he

[mojo-dev] [jira] Updated: (MOJO-1478) apt -s does not work reliably, should be -d

[ http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MOJO-1478: -- Attachment: (was: outputdir.patch) > apt -s does not work reliably, should be -d > ---

[mojo-dev] [jira] Commented: (MOJO-1478) apt -s does not work reliably, should be -d

[ http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203259#action_203259 ] Peter Lynch commented on MOJO-1478: --- This may be a Mac OSX, jdk 1.6(64bit) specific issue. I have

[mojo-dev] [jira] Updated: (MOJO-1478) apt -s does not work reliably, should be -d

[ http://jira.codehaus.org/browse/MOJO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MOJO-1478: -- Attachment: MOJO-1478.patch USE THIS Patch, passes both -s and -d with same value to deal with what appears t

[mojo-dev] [jira] Updated: (MNBMODULE-72) missing update-tracking files in the created nbm-application

[ http://jira.codehaus.org/browse/MNBMODULE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milos Kleint updated MNBMODULE-72: -- Fix Version/s: 3.2 http://fisheye.codehaus.org/changelog/mojo/?cs=11498 should be a good start. St

[mojo-dev] [jira] Issue Comment Edited: (MJSPC-4) JSPs Cannot Be Compiled if They Depend on Tag Files

[ http://jira.codehaus.org/browse/MJSPC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203230#action_203230 ] Laurent Martelli edited comment on MJSPC-4 at 12/17/09 11:12 AM: - I'm ru

[mojo-dev] [jira] Issue Comment Edited: (MJSPC-4) JSPs Cannot Be Compiled if They Depend on Tag Files

[ http://jira.codehaus.org/browse/MJSPC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203230#action_203230 ] Laurent Martelli edited comment on MJSPC-4 at 12/17/09 11:06 AM: - I'm ru

[mojo-dev] [jira] Issue Comment Edited: (MJSPC-4) JSPs Cannot Be Compiled if They Depend on Tag Files

[ http://jira.codehaus.org/browse/MJSPC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203230#action_203230 ] Laurent Martelli edited comment on MJSPC-4 at 12/17/09 11:05 AM: - I'm ru

[mojo-dev] [jira] Commented: (MJSPC-4) JSPs Cannot Be Compiled if They Depend on Tag Files

[ http://jira.codehaus.org/browse/MJSPC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203230#action_203230 ] Laurent Martelli commented on MJSPC-4: -- I'm running maven 2.0.10 with "[DEBUG] jspc-maven-plugin: r

Re: [mojo-dev] [RESULT] [VOTE] Retire xslt-maven-plugin

On Tue, Dec 15, 2009 at 8:34 PM, Robert Scholte wrote: > Right now the xml-maven-plugin is still in the pre-release phase, so I would > suggest to wait untill the xml-maven-plugin has an official release before > removing the xslt-plugin. I can't follow you here. From my point of view, there are

[mojo-dev] [jira] Commented: (MRPM-54) prefix project version qualifier to the release name of rpm

[ http://jira.codehaus.org/browse/MRPM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203218#action_203218 ] Brett Okken commented on MRPM-54: - See MRPM-32 for previous discussion on this topic. > prefix project

[mojo-dev] [jira] Issue Comment Edited: (MRPM-54) prefix project version qualifier to the release name of rpm

[ http://jira.codehaus.org/browse/MRPM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203209#action_203209 ] Brett Okken edited comment on MRPM-54 at 12/17/09 8:33 AM: --- The current behavi

[mojo-dev] [jira] Commented: (MRPM-54) prefix project version qualifier to the release name of rpm

[ http://jira.codehaus.org/browse/MRPM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203209#action_203209 ] Brett Okken commented on MRPM-54: - The current behavior has been present for quite some time and is clea

[mojo-dev] [jira] Commented: (MRPM-54) prefix project version qualifier to the release name of rpm

[ http://jira.codehaus.org/browse/MRPM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203205#action_203205 ] Antonio D commented on MRPM-54: --- another example would be with a project version as X.Y.Z-N-SNAPSHOT and n

[mojo-dev] [jira] Created: (MOJO-1479) Add option to not generate client class

Add option to not generate client class --- Key: MOJO-1479 URL: http://jira.codehaus.org/browse/MOJO-1479 Project: Mojo Issue Type: Wish Reporter: Geert Schuring Priority: Minor w

[mojo-dev] [jira] Created: (MRPM-54) prefix project version qualifier to the release name of rpm

prefix project version qualifier to the release name of rpm --- Key: MRPM-54 URL: http://jira.codehaus.org/browse/MRPM-54 Project: Mojo RPM Plugin Issue Type: Improvement Comp

[mojo-dev] [jira] Updated: (MSELENIUM-59) Selenium server could not be stopped from stop-server goal

[ http://jira.codehaus.org/browse/MSELENIUM-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated MSELENIUM-59: - Attachment: patch.diff Provided patch for changing selenium-stop server command. > Selenium server c

[mojo-dev] [jira] Created: (MSELENIUM-59) Selenium server could not be stopped from stop-server goal

Selenium server could not be stopped from stop-server goal -- Key: MSELENIUM-59 URL: http://jira.codehaus.org/browse/MSELENIUM-59 Project: Maven 2.x Selenium Plugin Issue Type: Bug

Re: [mojo-dev] [apt] requesting a patch apply and release MOJO-1478

Hi Peter, I've never had a problem with apt generating resources in the wrong directory. Can you attach an example test project to demonstrate the problem here? Cheers, Mark 2009/12/17 Peter Lynch : > Hi, > > I created jira http://jira.codehaus.org/browse/MOJO-1478 and provided the > patch to