[mojo-dev] [jira] Created: (MOJO-1031) site:site fails if there are jsunit tests that fail or error

site:site fails if there are jsunit tests that fail or error Key: MOJO-1031 URL: http://jira.codehaus.org/browse/MOJO-1031 Project: Mojo Issue Type: Bug Components: javas

Re: [mojo-dev] Re: [mojo-scm] [6130] tags/keytool-maven-plugin-1.0/src/site/fml/faq.fml: Patch on tag (Sorry svn diff ) to allow for release:perform to work.

On Jan 31, 2008 11:32 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > If you don't have any frequently asked questions, you shouldn't have an > FAQ file at all. If I remember correctly, docck:check requires one. J - To unsubscr

[mojo-dev] [jira] Closed: (MJAVACC-71) JTB mojo fails to move output files to proper directory on Windows

[ http://jira.codehaus.org/browse/MJAVACC-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MJAVACC-71. Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.4 Committed in r61

[mojo-dev] Issue MOJO-1022 status...

http://jira.codehaus.org/browse/MOJO-1022 Did you guys get a chance to take a look at this yet? What do you think, is it worthy? --Chad Lyon This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it i

[mojo-dev] Re: [mojo-scm] [6130] tags/keytool-maven-plugin-1.0/src/site/fml/faq.fml: Patch on tag (Sorry svn diff ) to allow for release:perform to work.

If you don't have any frequently asked questions, you shouldn't have an FAQ file at all. [EMAIL PROTECTED] wrote: Revision 6130 Author lacostej Date 2008-01-30 16:13:39 -0600 (Wed, 30 Jan 2008) Log Message Patch on tag (

Re: [mojo-dev] New plugin for continuous performancetesting?

Hi guys. The code is now attached to http://jira.codehaus.org/browse/MOJO-1030. Install the plugin (mvn install) and have a look at the generated site documentation. It contains sort of a "getting started" guide. We find it really useful, and hope that others do too! Please do not hesitate

[mojo-dev] [jira] Closed: (MJAVACC-74) JTB mojo fails to move output files if workingDirectory != baseDir

[ http://jira.codehaus.org/browse/MJAVACC-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MJAVACC-74. Resolution: Fixed Fix Version/s: 2.4 Committed in r6146. > JTB mojo fails to move output

[mojo-dev] [jira] Created: (MJAVACC-74) JTB mojo fails to move output files if workingDirectory != baseDir

JTB mojo fails to move output files if workingDirectory != baseDir -- Key: MJAVACC-74 URL: http://jira.codehaus.org/browse/MJAVACC-74 Project: Maven 2.x JavaCC Plugin Issue Type

[mojo-dev] [jira] Created: (MOJO-1030) Chronos: A plugin for contiuous performancetesting

Chronos: A plugin for contiuous performancetesting -- Key: MOJO-1030 URL: http://jira.codehaus.org/browse/MOJO-1030 Project: Mojo Issue Type: New Feature Components: Plugin Submission

[mojo-dev] [jira] Closed: (MJAVACC-72) The jtb mojo throws StringIndexOutOfBoundsException when visitor/node package has no dots

[ http://jira.codehaus.org/browse/MJAVACC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MJAVACC-72. Resolution: Fixed Fix Version/s: 2.4 Committed in r6144. > The jtb mojo throws StringInde

[mojo-dev] [jira] Assigned: (MJAVACC-72) The jtb mojo throws StringIndexOutOfBoundsException when visitor/node package has no dots

[ http://jira.codehaus.org/browse/MJAVACC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reassigned MJAVACC-72: Assignee: Benjamin Bentmann > The jtb mojo throws StringIndexOutOfBoundsException when vi

[mojo-dev] [jira] Created: (MJAVACC-73) Make JTB mojo use package of input grammar by default

Make JTB mojo use package of input grammar by default - Key: MJAVACC-73 URL: http://jira.codehaus.org/browse/MJAVACC-73 Project: Maven 2.x JavaCC Plugin Issue Type: Improvement Co

[mojo-dev] Issue MOJO-1022 status...

http://jira.codehaus.org/browse/MOJO-1022 Did you guys get a chance to take a look at this yet? What do you think, is it worthy? Chad Lyon This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in

[mojo-dev] [jira] Created: (MJAVACC-72) The jtb mojo throws StringIndexOutOfBoundsException when visitor/node package has no dots

The jtb mojo throws StringIndexOutOfBoundsException when visitor/node package has no dots - Key: MJAVACC-72 URL: http://jira.codehaus.org/browse/MJAVACC-72 Projec

[mojo-dev] [jira] Updated: (MOJO-1022) javahelp plugin...

[ http://jira.codehaus.org/browse/MOJO-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chad Lyon updated MOJO-1022: Attachment: maven-javahelp-plugin.zip This one actually works! The first one I uploaded was building the Search DB

[mojo-dev] [jira] Created: (MJAVACC-71) JTB mojo fails to move output files to proper directory on Windows

JTB mojo fails to move output files to proper directory on Windows -- Key: MJAVACC-71 URL: http://jira.codehaus.org/browse/MJAVACC-71 Project: Maven 2.x JavaCC Plugin Issue Type

Re: [mojo-dev] New plugin for continuous performancetesting?

Looks interesting. 2008/1/30, Kent Sølvsten <[EMAIL PROTECTED]>: > > Hi developers. > > At my company, we have developed a Maven2 plugin which we use for > "continuous performancetesting". > We use it to integrate performancetesting in our nightly Maven builds. > > The tests are performed using JM

[mojo-dev] [jira] Commented: (MJAVACC-57) Allow jjtree to automatically execute javacc

[ http://jira.codehaus.org/browse/MJAVACC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121920 ] Paul Gier commented on MJAVACC-57: -- So we would need something like {code:java} if (skipJavacc && outputDirectory != default

[mojo-dev] [jira] Closed: (MJAVACC-70) Make mojos fail if invoked tools reports non-zero exit code

[ http://jira.codehaus.org/browse/MJAVACC-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MJAVACC-70. Resolution: Fixed Fix Version/s: 2.4 Committed in r6142. > Make mojos fail if invoked too

[mojo-dev] [jira] Commented: (MJAVACC-57) Allow jjtree to automatically execute javacc

[ http://jira.codehaus.org/browse/MJAVACC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121916 ] Benjamin Bentmann commented on MJAVACC-57: -- bq. If we do include a flag to skip the javacc execution and default it

[mojo-dev] [jira] Commented: (MJAVACC-57) Allow jjtree to automatically execute javacc

[ http://jira.codehaus.org/browse/MJAVACC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121904 ] Paul Gier commented on MJAVACC-57: -- {quote} To my knowledge, Maven itself does not care whether we call the next version 2.

[mojo-dev] [jira] Updated: (MOJO-1028) Add ability to pass activateLightweightDelegates to AspectJ compiler

[ http://jira.codehaus.org/browse/MOJO-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated MOJO-1028: - Attachment: aspectj-maven-plugin-1.0-beta-2-activateLightweightDelegates.diff Patch from my col

[mojo-dev] [jira] Created: (MJAVACC-70) Make mojos fail if invoked tools reports non-zero exit code

Make mojos fail if invoked tools reports non-zero exit code --- Key: MJAVACC-70 URL: http://jira.codehaus.org/browse/MJAVACC-70 Project: Maven 2.x JavaCC Plugin Issue Type: Bug

[mojo-dev] [jira] Commented: (MJAVACC-57) Allow jjtree to automatically execute javacc

[ http://jira.codehaus.org/browse/MJAVACC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121896 ] Benjamin Bentmann commented on MJAVACC-57: -- bq. [...] you can probably just replace the current jjtree mojo with thi

[mojo-dev] [jira] Closed: (MOJO-1029) paramater to set context path

[ http://jira.codehaus.org/browse/MOJO-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MOJO-1029. - Assignee: nicolas de loof Resolution: Fixed "webPath" parameter added to the Mojo > paramater to

[mojo-dev] [jira] Created: (MOJO-1029) paramater to set context path

paramater to set context path - Key: MOJO-1029 URL: http://jira.codehaus.org/browse/MOJO-1029 Project: Mojo Issue Type: Improvement Components: sysdeo-tomcat Reporter: nicolas de loof

[mojo-dev] [jira] Commented: (MOJO-746) Add ability to pass extra params to AspectJ compiler

[ http://jira.codehaus.org/browse/MOJO-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121865 ] Dennis Kieselhorst commented on MOJO-746: - Created new issue for activateLightweightDelegates: MOJO-1028 > Add ability

[mojo-dev] [jira] Created: (MOJO-1028) Add ability to pass activateLightweightDelegates to AspectJ compiler

Add ability to pass activateLightweightDelegates to AspectJ compiler Key: MOJO-1028 URL: http://jira.codehaus.org/browse/MOJO-1028 Project: Mojo Issue Type: Improvement

[mojo-dev] [jira] Commented: (MOJO-862) eclipseInstall is ignored in favour of build.properties for product builds

[ http://jira.codehaus.org/browse/MOJO-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121863 ] Lutz Huehnken commented on MOJO-862: Just wondering - is this really a bug? In my understanding, eclipseInstall points to

[mojo-dev] [jira] Commented: (MOJO-919) No product launcher application generated on linux

[ http://jira.codehaus.org/browse/MOJO-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121859 ] Lutz Huehnken commented on MOJO-919: This is not linux-specific. I have the same problem on Win XP, with both 1.0-alpha-1

[mojo-dev] [jira] Commented: (MOJO-1016) support for eclipse 3.3 building

[ http://jira.codehaus.org/browse/MOJO-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121857 ] Lutz Huehnken commented on MOJO-1016: - I think this is a duplicate of http://jira.codehaus.org/browse/MOJO-730 and has be