[jira] Created: (MANTLR-26) antlr does not find *.tokens if libDirectory did not exist before calling the plugin
antlr does not find *.tokens if libDirectory did not exist before calling the plugin Key: MANTLR-26 URL: http://jira.codehaus.org/browse/MANTLR-26 Project: Maven 2.x Antlr Plugin Issue Type: Bug Reporter: Philippe Faes Attachments: antlr3-maven-plugin.patch When a libDirectory is defined in the plugin configuration, and it does not exist when the plugin is called, an error is generated and antlr does not find *.tokens files in the given libDirectory. In most cases, the libDirectory is somewhere in target/generated-code/antlr so after cleaning the project (mvn clean) it should not exits. Hence, the current behavior is not desirable. A patch is attached that checks if the libdir exists, and creates the dir if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTLR-27) plugin translates grammar files in arbitrary order, but some grammars may depend on eachother
plugin translates grammar files in arbitrary order, but some grammars may depend on eachother - Key: MANTLR-27 URL: http://jira.codehaus.org/browse/MANTLR-27 Project: Maven 2.x Antlr Plugin Issue Type: Improvement Reporter: Philippe Faes Attachments: antlr3-maven-plugin_sorting.patch When creating a parser and a treewalker, say CMinus.g and CMinusWalker.g, antlr needs to translate the parser first. During this translation, a *.tokens file is created, which is needed for the translation of the treewalker. The plugin currently deals with grammar files in arbitrary order (because files are stored in a Map, which is not sorted). I propose the plugin sorts the files alphabetically before processing. This way, the developer can determine the compilation order by choosing alphabetically sorted grammar names. Note that using the anltr naming convention (foobar.g and foobarWalker.g) the files are sorted correctly. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTLR-26) antlr does not find *.tokens if libDirectory did not exist before calling the plugin
[ http://jira.codehaus.org/browse/MANTLR-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philippe Faes closed MANTLR-26. --- Resolution: Won't Fix Posted at the wrong place. It was meant for antlr3-maven-plugin. > antlr does not find *.tokens if libDirectory did not exist before calling the > plugin > > > Key: MANTLR-26 > URL: http://jira.codehaus.org/browse/MANTLR-26 > Project: Maven 2.x Antlr Plugin > Issue Type: Bug >Reporter: Philippe Faes > Attachments: antlr3-maven-plugin.patch > > > When a libDirectory is defined in the plugin configuration, and it does not > exist when the plugin is called, an error is generated and antlr does not > find *.tokens files in the given libDirectory. > In most cases, the libDirectory is somewhere in target/generated-code/antlr > so after cleaning the project (mvn clean) it should not exits. Hence, the > current behavior is not desirable. > A patch is attached that checks if the libdir exists, and creates the dir if > needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTLR-28) [antlr3-maven-plugin] plugin translates grammar files in arbitrary order, but some grammars may depend on eachother
[antlr3-maven-plugin] plugin translates grammar files in arbitrary order, but some grammars may depend on eachother --- Key: MANTLR-28 URL: http://jira.codehaus.org/browse/MANTLR-28 Project: Maven 2.x Antlr Plugin Issue Type: Improvement Reporter: Philippe Faes Attachments: antlr3-maven-plugin_sorting.patch When creating a parser and a treewalker, say CMinus.g and CMinusWalker.g, antlr needs to translate the parser first. During this translation, a *.tokens file is created, which is needed for the translation of the treewalker. The plugin currently deals with grammar files in arbitrary order (because files are stored in a Map, which is not sorted). I propose the plugin sorts the files alphabetically before processing. This way, the developer can determine the compilation order by choosing alphabetically sorted grammar names. Note that using the anltr naming convention (foobar.g and foobarWalker.g) the files are sorted correctly. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTLR-27) plugin translates grammar files in arbitrary order, but some grammars may depend on eachother
[ http://jira.codehaus.org/browse/MANTLR-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philippe Faes closed MANTLR-27. --- Resolution: Won't Fix Posted at the wrong place. It was meant for antlr3-maven-plugin. > plugin translates grammar files in arbitrary order, but some grammars may > depend on eachother > - > > Key: MANTLR-27 > URL: http://jira.codehaus.org/browse/MANTLR-27 > Project: Maven 2.x Antlr Plugin > Issue Type: Improvement >Reporter: Philippe Faes > Attachments: antlr3-maven-plugin_sorting.patch > > > When creating a parser and a treewalker, say CMinus.g and CMinusWalker.g, > antlr needs to translate the parser first. During this translation, a > *.tokens file is created, which is needed for the translation of the > treewalker. > The plugin currently deals with grammar files in arbitrary order (because > files are stored in a Map, which is not sorted). I propose the plugin sorts > the files alphabetically before processing. This way, the developer can > determine the compilation order by choosing alphabetically sorted grammar > names. > Note that using the anltr naming convention (foobar.g and foobarWalker.g) the > files are sorted correctly. > Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-261) Local Parent POM not found if specifies a directory
[
http://jira.codehaus.org/browse/MSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119643
]
Benjamin Bentmann commented on MSITE-261:
-
A simpler workaround should be to just specify the path to the parent POM
directly, e.g. "../parent/pom.xml" instead of "../parent". That's how I
successfully get the plugin to work properly.
> Local Parent POM not found if specifies a directory
> --
>
> Key: MSITE-261
> URL: http://jira.codehaus.org/browse/MSITE-261
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5
> Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
>Reporter: Benjamin Bentmann
>Priority: Minor
> Attachments: site-parent-pom.patch
>
>
> The Maven core allows to specify a directory for the element
> in a module POM to locate the parent POM, e.g.{code:xml}
> ...
> ../parent
> {code}will properly find the parent POM in "../parent/pom.xml".
> However, the Site plugin does not follow this lookup strategy:{code}
> [INFO] [site:site]
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file '[SNIP]\..\parent'. for project unknown
> [INFO] Parent project loaded from repository.{code}
> This log output is actually from 2.0-beta-6-SNAPSHOT, 2.0-beta-5 outputs a
> different message but fails, too.
> The attached patch fixes this although I wonder whether this functionality is
> not already included somewhere in the Maven core (where is belongs IMHO).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-261) Local Parent POM not found if specifies a directory
[
http://jira.codehaus.org/browse/MSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MSITE-261:
Attachment: site-parent-pom.patch
Needed to fix my first patch which was sensitive to the current working
directory.
> Local Parent POM not found if specifies a directory
> --
>
> Key: MSITE-261
> URL: http://jira.codehaus.org/browse/MSITE-261
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5
> Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
>Reporter: Benjamin Bentmann
>Priority: Minor
> Attachments: site-parent-pom.patch, site-parent-pom.patch
>
>
> The Maven core allows to specify a directory for the element
> in a module POM to locate the parent POM, e.g.{code:xml}
> ...
> ../parent
> {code}will properly find the parent POM in "../parent/pom.xml".
> However, the Site plugin does not follow this lookup strategy:{code}
> [INFO] [site:site]
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file '[SNIP]\..\parent'. for project unknown
> [INFO] Parent project loaded from repository.{code}
> This log output is actually from 2.0-beta-6-SNAPSHOT, 2.0-beta-5 outputs a
> different message but fails, too.
> The attached patch fixes this although I wonder whether this functionality is
> not already included somewhere in the Maven core (where is belongs IMHO).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPMD-73) Report generated even when no input files present
Report generated even when no input files present - Key: MPMD-73 URL: http://jira.codehaus.org/browse/MPMD-73 Project: Maven 2.x PMD Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Simon Kitching Priority: Minor Most maven report plugins will not generate a report if there are no input files. For example, a pom that defines the javadoc report plugin but has no source does not get a javadoc report. However the pmd plugin generates empty pmd and cmd reports even for projects that have no source. In particular this means that parent poms that want to define pmd reports for the child modules get a "project reports" menu with pointless pmd/cmd pages. Given that poms lack a "pluginManagement" pom section, this is quite annoying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINSTALL-46) remove plexus utils sources
remove plexus utils sources --- Key: MINSTALL-46 URL: http://jira.codehaus.org/browse/MINSTALL-46 Project: Maven 2.x Install Plugin Issue Type: Task Affects Versions: 2.3 Reporter: Herve Boutemy Priority: Minor need to upgrade prerequisite to Maven 2.0.6 see http://docs.codehaus.org/display/MAVENUSER/XML+encoding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEPLOY-70) remove plexus utils sources
remove plexus utils sources --- Key: MDEPLOY-70 URL: http://jira.codehaus.org/browse/MDEPLOY-70 Project: Maven 2.x Deploy Plugin Issue Type: Task Affects Versions: 2.4 Reporter: Herve Boutemy Priority: Minor need to upgrade prerequisite to Maven 2.0.6 see http://docs.codehaus.org/display/MAVENUSER/XML+encoding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-316) remove plexus utils sources
remove plexus utils sources --- Key: MRELEASE-316 URL: http://jira.codehaus.org/browse/MRELEASE-316 Project: Maven 2.x Release Plugin Issue Type: Task Affects Versions: 2.0-beta-8 Reporter: Herve Boutemy Priority: Minor need to upgrade prerequisite to Maven 2.0.6 see http://docs.codehaus.org/display/MAVENUSER/XML+encoding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEPLOY-70) remove plexus utils sources
[ http://jira.codehaus.org/browse/MDEPLOY-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119658 ] Olivier Lamy commented on MDEPLOY-70: - Oh yes please do it ! some much line of codes to copy when fixing an issue in p-u ! > remove plexus utils sources > --- > > Key: MDEPLOY-70 > URL: http://jira.codehaus.org/browse/MDEPLOY-70 > Project: Maven 2.x Deploy Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Herve Boutemy >Priority: Minor > > need to upgrade prerequisite to Maven 2.0.6 > see http://docs.codehaus.org/display/MAVENUSER/XML+encoding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEPLOY-70) remove plexus utils sources
[ http://jira.codehaus.org/browse/MDEPLOY-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119659 ] Herve Boutemy commented on MDEPLOY-70: -- yes, it will be a Good Thing (TM) when they are removed But as discussed before on the dev mailing list, this would require upgrading prerequisite to Maven 2.0.6, which is not wanted for now Now, please don't over-react: "only" XML encoding related classes are copied, which I'm maintaining and don't change much. Today was the first change in 6 months, and yes, I had to copy the change to 4 components: it was a known compromise, I assume it and did the changes. This time, I created corresponding issues in Jira to track it, and made links in the Wiki entry, so that everything is tracked as much as possible. If you convince everybody to upgrade Maven prerequisite to 2.0.6 for one of the 4 plugins, I'll be the first to drop the copy :) > remove plexus utils sources > --- > > Key: MDEPLOY-70 > URL: http://jira.codehaus.org/browse/MDEPLOY-70 > Project: Maven 2.x Deploy Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Herve Boutemy >Priority: Minor > > need to upgrade prerequisite to Maven 2.0.6 > see http://docs.codehaus.org/display/MAVENUSER/XML+encoding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEPLOY-70) remove plexus utils sources
[ http://jira.codehaus.org/browse/MDEPLOY-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119663 ] Olivier Lamy commented on MDEPLOY-70: - 2.0.6 is 9 months old. And 2.0.8 has fixed some issues introduced in 2.0.6/2.0.7. I think users has migrated to 2.0.8. If not lock the plugin version in a pom is a solution. And it's not an over-react ;-). FYI the next maven-jar-plugin will use last p-u -> 2.0.6 prerequisite. > remove plexus utils sources > --- > > Key: MDEPLOY-70 > URL: http://jira.codehaus.org/browse/MDEPLOY-70 > Project: Maven 2.x Deploy Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Herve Boutemy >Priority: Minor > > need to upgrade prerequisite to Maven 2.0.6 > see http://docs.codehaus.org/display/MAVENUSER/XML+encoding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1894) Sync com.discursive repository
Sync com.discursive repository -- Key: MAVENUPLOAD-1894 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1894 Project: maven-upload-requests Issue Type: Task Reporter: Tim O'Brien Attachments: com.discursive.sh Would like to synchronize the repository at http://www.discursive.com/maven2 with the central maven repository. I've attached the appropriate script and added the maven public key to authorized keys for the mvnrepo user. Whois for domain: Registrar Name: REGISTER.COM, INC. Registrar Whois...: whois.register.com Registrar Homepage: www.register.com Domain Name: discursive.com Created on..: Wed, Nov 11, 1998 Expires on..: Mon, Nov 10, 2008 Record last updated on..: Tue, Sep 18, 2007 Administrative Contact: Tim O'Brien Phone: (847) 864-7045 Email: [EMAIL PROTECTED] Technical Contact: Tim O'Brien Phone: (847) 864-7045 Email: [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3362) not able to install plugins
not able to install plugins --- Key: MNG-3362 URL: http://jira.codehaus.org/browse/MNG-3362 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.8 Reporter: D.T.Rajendra Prasad I am learning maven,after downloading and setting the path,i tried to create a directory structure mvn -e archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=org.htc.javaee.mavens -DartifactId=helloWorld + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1286) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1522) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:386) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:229) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:167) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1257) ... 14 more [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Sun Jan 13 08:21:27 IST 2008 [INFO] Final Memory: 1M/4M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-92) JIRA Report Improvements
[ http://jira.codehaus.org/browse/MCHANGES-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niall Pemberton updated MCHANGES-92: Attachment: MCHANGES-92-jira-column-configuration.patch Thanks Dennis, seems you have partially applied the fix for 1 and 2 (changes to JiraXML and JiraIssue to harvest the additional columns) would be really good to be able to 1) Configure which columns are shown and 2) specify the order in which they are rendered, which is what the rest of the patch does. I tested this out quite a bit with Commons IO and I think it really makes the report more useable. I've refreshed with your changes and am attaching a new patch with the remainder for 1 and 2 - in case it makes your life easier, and more likely yo apply :) - its slightly different (I moved one line from JiraMojo to JiraReportGenerator). If theres anything about it you don't like, let me know and I'll try to fix/re-submit a new patch. tia Niall > JIRA Report Improvements > > > Key: MCHANGES-92 > URL: http://jira.codehaus.org/browse/MCHANGES-92 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: jira-report >Affects Versions: 2.0-beta-3 >Reporter: Niall Pemberton > Attachments: maven-changes-jira-report-improvements.patch, > MCHANGES-92-jira-column-configuration.patch > > > OK heres my wish-list to improve the JIRA report: > - Be able to configure which columns are shown on the report > - Make the following additional columns available on the report: Reporter, > Type, Priority, Version, Fix Version and Component > - Be able to configure the "Fix Version" to show on the report (rather than > all versions) > - Be able to configure which "types" are shown on the report (rather than > all types) > - Currently the configurable Status, Resolution and Priority values are > ignored (because of bugs in the url parameters used) > I realize the Fix Version and Types can be configured using the existing > "filter" - but thats not a very user friendly feature. > Attaching a patch which does all of the above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
