[jira] Closed: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching closed MRM-61: --- Resolution: Fixed Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 13 hours Time Spent: 13 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-66) Repository configuration
[ http://jira.codehaus.org/browse/MRM-66?page=all ] Maria Odea Ching updated MRM-66: Summary: Repository configuration (was: Repoitory configuration) Repository configuration Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching closed MRM-52: --- Resolution: Fixed integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Original Estimate: 10 hours Remaining: 10 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-66) Repoitory configuration
Repoitory configuration --- Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-66) Repoitory configuration
[ http://jira.codehaus.org/browse/MRM-66?page=all ] Maria Odea Ching updated MRM-66: Remaining Estimate: 1 day Original Estimate: 1 day Repoitory configuration --- Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-67) Index maintenance
Index maintenance - Key: MRM-67 URL: http://jira.codehaus.org/browse/MRM-67 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Update of index is triggered by discovery, which is a scheduled task. A configuration file that contains the execution schedule of the discoverer will be retrieved and read. These values will be passed/set on the scheduler. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-67) Index maintenance
[ http://jira.codehaus.org/browse/MRM-67?page=all ] Maria Odea Ching updated MRM-67: Remaining Estimate: 1 day Original Estimate: 1 day Index maintenance - Key: MRM-67 URL: http://jira.codehaus.org/browse/MRM-67 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day Update of index is triggered by discovery, which is a scheduled task. A configuration file that contains the execution schedule of the discoverer will be retrieved and read. These values will be passed/set on the scheduler. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-68) Accomodate query everything in the index
Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-68) Accomodate query everything in the index
[ http://jira.codehaus.org/browse/MRM-68?page=all ] Maria Odea Ching updated MRM-68: Remaining Estimate: 20 hours Original Estimate: 20 hours Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 20 hours Remaining: 20 hours Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-69) Simple query everything search
Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Remaining Estimate: 15 hours Original Estimate: 15 hours Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 15 hours Remaining: 15 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-88) search by filename
search by filename -- Key: MRM-88 URL: http://jira.codehaus.org/browse/MRM-88 Project: Maven Repository Manager Type: Sub-task Reporter: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-88) search by filename
[ http://jira.codehaus.org/browse/MRM-88?page=all ] Maria Odea Ching updated MRM-88: Assign To: Maria Odea Ching Remaining Estimate: 2 hours Original Estimate: 2 hours search by filename -- Key: MRM-88 URL: http://jira.codehaus.org/browse/MRM-88 Project: Maven Repository Manager Type: Sub-task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 2 hours Remaining: 2 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-88) search by filename
[ http://jira.codehaus.org/browse/MRM-88?page=comments#action_57705 ] Maria Odea Ching commented on MRM-88: - The resolution for this issue is included in the patch file attached to issue MRM-44. search by filename -- Key: MRM-88 URL: http://jira.codehaus.org/browse/MRM-88 Project: Maven Repository Manager Type: Sub-task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 2 hours Remaining: 2 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching reopened MRM-61: - Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching updated MRM-61: Remaining Estimate: 13 hours Original Estimate: 13 hours Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 13 hours Remaining: 13 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching reopened MRM-52: - integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=comments#action_57713 ] Maria Odea Ching commented on MRM-52: - MRM-69 still needs to be done and integrated with indexing. integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching updated MRM-52: Remaining Estimate: 10 hours Original Estimate: 10 hours integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Original Estimate: 10 hours Remaining: 10 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-36) integration with discovery and scheduling
[ http://jira.codehaus.org/browse/MRM-36?page=all ] Maria Odea Ching updated MRM-36: Remaining Estimate: 15 hours Original Estimate: 15 hours integration with discovery and scheduling - Key: MRM-36 URL: http://jira.codehaus.org/browse/MRM-36 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Fix For: 1.0-alpha-1 Original Estimate: 15 hours Remaining: 15 hours I presume the regular indexer will process an individual file and add it to the index, or remove a file from the index. This should integrated with the discovery mechanism so that it can trigger the indexing of files (or removal - though this is not currently in the discovery mechanism). As for scheduling, it may be that the index updates are processed on a scheduled interval so that integration might be 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1593) Typo in settings doc
[ http://jira.codehaus.org/browse/MNG-1593?page=comments#action_57388 ] Maria Odea Ching commented on MNG-1593: --- This has already been updated in SVN. An xdoc must be generated and included in the maven settings site. Typo in settings doc Key: MNG-1593 URL: http://jira.codehaus.org/browse/MNG-1593 Project: Maven 2 Type: Bug Components: Documentation: General Versions: 2.0 Reporter: Carlos Sanchez Assignee: Maria Odea Ching Priority: Minor Fix For: documentation http://maven.apache.org/maven-settings/settings.html under repository and pluginRepository release should be releases snapshot should be snapshots -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1268) Complete the Introduction to the POM page
[ http://jira.codehaus.org/browse/MNG-1268?page=all ] Maria Odea Ching updated MNG-1268: -- Attachment: MNG-1268-documentation-instroductions.patch Complete the Introduction to the POM page - Key: MNG-1268 URL: http://jira.codehaus.org/browse/MNG-1268 Project: Maven 2 Type: Task Components: documentation - introductions Reporter: Srepfler Srgjan Assignee: Maria Odea Ching Priority: Minor Fix For: documentation Attachments: MNG-1268-documentation-instroductions.patch The Introduction to the POM page is there but empty. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1953) src/main/webapp should be added to Introduction to the Standard Directory Layout page
[ http://jira.codehaus.org/browse/MNG-1953?page=all ] Maria Odea Ching updated MNG-1953: -- Attachment: MNG-1953-documentation-introductions.patch src/main/webapp should be added to Introduction to the Standard Directory Layout page --- Key: MNG-1953 URL: http://jira.codehaus.org/browse/MNG-1953 Project: Maven 2 Type: Bug Components: documentation - introductions Reporter: Stephen Duncan Jr Assignee: Maria Odea Ching Priority: Minor Fix For: documentation Attachments: MNG-1953-documentation-introductions.patch Introduction to the Standard Directory Layout at http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html should add an entry for src/main/webapp as the standard for web app sources. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-55) don't add duplicates to the index
[ http://jira.codehaus.org/browse/MRM-55?page=all ] Maria Odea Ching updated MRM-55: Attachment: MRM-55-maven-repository-indexer.patch don't add duplicates to the index - Key: MRM-55 URL: http://jira.codehaus.org/browse/MRM-55 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-55-maven-repository-indexer.patch currently indexing an artifact that is already in the index will add it again. It should recognise its existence and update the existing record. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-55) don't add duplicates to the index
[ http://jira.codehaus.org/browse/MRM-55?page=all ] Maria Odea Ching updated MRM-55: Attachment: MRM-55-maven-repository-indexer.patch don't add duplicates to the index - Key: MRM-55 URL: http://jira.codehaus.org/browse/MRM-55 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-55-maven-repository-indexer.patch, MRM-55-maven-repository-indexer.patch Time Spent: 9 hours Remaining: 0 minutes currently indexing an artifact that is already in the index will add it again. It should recognise its existence and update the existing record. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-56) ability to delete documents from the index
[ http://jira.codehaus.org/browse/MRM-56?page=all ] Maria Odea Ching updated MRM-56: Attachment: MRM-56-maven-repository-indexer.patch ability to delete documents from the index -- Key: MRM-56 URL: http://jira.codehaus.org/browse/MRM-56 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-56-maven-repository-indexer.patch -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-35) add repository metadata indexer
[ http://jira.codehaus.org/browse/MRM-35?page=all ] Maria Odea Ching closed MRM-35: --- Resolution: Fixed add repository metadata indexer --- Key: MRM-35 URL: http://jira.codehaus.org/browse/MRM-35 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-35-maven-repository-indexer.patch, MRM-35-maven-repository-indexer.patch Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching closed MRM-61: --- Resolution: Fixed Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-35) add repository metadata indexer
[ http://jira.codehaus.org/browse/MRM-35?page=all ] Maria Odea Ching updated MRM-35: Attachment: MRM-35-maven-repository-indexer.patch add repository metadata indexer --- Key: MRM-35 URL: http://jira.codehaus.org/browse/MRM-35 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-35-maven-repository-indexer.patch, MRM-35-maven-repository-indexer.patch Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-35) add repository metadata indexer
[ http://jira.codehaus.org/browse/MRM-35?page=all ] Maria Odea Ching updated MRM-35: Attachment: MRM-35-maven-repository-indexer.patch add repository metadata indexer --- Key: MRM-35 URL: http://jira.codehaus.org/browse/MRM-35 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-35-maven-repository-indexer.patch Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-61) Searcher for metadata index
Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assigned to: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-44) search by group, artifact and version
[ http://jira.codehaus.org/browse/MRM-44?page=all ] Maria Odea Ching closed MRM-44: --- Resolution: Fixed The patch file attached also covers issues MRM-45, MRM-48 and MRM-52 search by group, artifact and version - Key: MRM-44 URL: http://jira.codehaus.org/browse/MRM-44 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-44-maven-repository-indexer.patch Time Spent: 2 hours, 30 minutes Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-45) search by class or package name
[ http://jira.codehaus.org/browse/MRM-45?page=all ] Maria Odea Ching closed MRM-45: --- Resolution: Fixed The resolution for this issue is included in the patch file attached to issue MRM-44. search by class or package name --- Key: MRM-45 URL: http://jira.codehaus.org/browse/MRM-45 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Time Spent: 3 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-48) search by checksum
[ http://jira.codehaus.org/browse/MRM-48?page=all ] Maria Odea Ching closed MRM-48: --- Resolution: Fixed The resolution for this issue is included in the patch file attached at issue MRM-44. search by checksum -- Key: MRM-48 URL: http://jira.codehaus.org/browse/MRM-48 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Time Spent: 4 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching closed MRM-52: --- Resolution: Fixed integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-44) search by group, artifact and version
[ http://jira.codehaus.org/browse/MRM-44?page=all ] Maria Odea Ching updated MRM-44: Attachment: MRM-44-maven-repository-indexer.patch search by group, artifact and version - Key: MRM-44 URL: http://jira.codehaus.org/browse/MRM-44 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-44-maven-repository-indexer.patch -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-3) The install plugin fails if there are only attached artifacts.
[ http://jira.codehaus.org/browse/MINSTALL-3?page=all ] Maria Odea Ching moved MNG-1616 to MINSTALL-3: -- Version: (was: 2.0) Fix Version: (was: 2.0.3) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-3 (was: MNG-1616) Project: Maven 2.x Install Plugin (was: Maven 2) The install plugin fails if there are only attached artifacts. Key: MINSTALL-3 URL: http://jira.codehaus.org/browse/MINSTALL-3 Project: Maven 2.x Install Plugin Type: Bug Reporter: Julien S Assignee: John Casey Original Estimate: 2 hours Remaining: 2 hours Usually, classifiers are used to produce attached artifacts, together with the main artifact. In some cases, however, it is not possible to produce the different flavors of the artifacts simultaneously (for example, for a version with debug and without debug). Then, in order to have a single artifact _with_ a classifier, one can configure the jar plugin as follow: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration classifiersomeclassifier/classifier /configuration /plugin However, this cause the install plugin (and probably also the deploy plugin) to fail, because it cannot find the main artifact: [INFO] [jar:jar] [INFO] Building jar: /home/julien/cvs/java/libs/attr/target/libattr-3.0-nodebug.jar [INFO] [install:install] [INFO] Installing /home/julien/cvs/java/libs/attr/target/classes to /home/julien/.m2/repository/unicity/libattr/3.0/libattr-3.0.jar -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-4) install:install-file makes reactor parse subprojects
[ http://jira.codehaus.org/browse/MINSTALL-4?page=all ] Maria Odea Ching moved MNG-1114 to MINSTALL-4: -- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-4 (was: MNG-1114) Project: Maven 2.x Install Plugin (was: Maven 2) install:install-file makes reactor parse subprojects Key: MINSTALL-4 URL: http://jira.codehaus.org/browse/MINSTALL-4 Project: Maven 2.x Install Plugin Type: Bug Reporter: Yann Le Du Assignee: Brett Porter Priority: Trivial When you execute m2 install:install-file -DgroupId=jdbc -DartifactId=jdbc -Dversion=2.0 -Dpackaging=jar -Dfile=/home/maven/repository-manual/jdbc/jdbc/2.0/jdbc-2.0.jar in a parent project, the reactor executes it again in every subproject. Harmless, but unexpected. Maybe somehow related to MNG-432 ? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-6) Add ability to generate a basic pom when installing a file.
[ http://jira.codehaus.org/browse/MINSTALL-6?page=all ] Maria Odea Ching moved MNG-1279 to MINSTALL-6: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-6 (was: MNG-1279) Project: Maven 2.x Install Plugin (was: Maven 2) Add ability to generate a basic pom when installing a file. --- Key: MINSTALL-6 URL: http://jira.codehaus.org/browse/MINSTALL-6 Project: Maven 2.x Install Plugin Type: New Feature Reporter: Philipp Meier Assignee: Brett Porter Attachments: generatePom.patch, install-file-fix.patch It's desireable to generate a basic pom for a library installed with install:install-file. The attached patch adds the parameter generatePom to the install:install-file. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-1) Install plugin installs a jar to repository with default name, even if name is overridden
[ http://jira.codehaus.org/browse/MINSTALL-1?page=all ]
Maria Odea Ching moved MNG-1657 to MINSTALL-1:
--
Version: (was: 2.0)
Component: (was: maven-install-plugin)
Workflow: jira (was: Maven)
Key: MINSTALL-1 (was: MNG-1657)
Project: Maven 2.x Install Plugin (was: Maven 2)
Install plugin installs a jar to repository with default name, even if name
is overridden
-
Key: MINSTALL-1
URL: http://jira.codehaus.org/browse/MINSTALL-1
Project: Maven 2.x Install Plugin
Type: Bug
Environment: winxp
Reporter: ruel loehr
Assignee: Brett Porter
When using the install plugin to install a jar to the repository, the default
name of the jar is used, even if the name is overridden. Also, if you
define your own type via a plugin ('myjar'), when installing, it will be
installed as 'myjar'. This should be overrideable otherwise it is impossible
for a user to override the default type plugins.
[INFO] [jar:jar]
[INFO] Building jar:
c:\projects\maven-jboss-head\jboss-head\common\namespace\ta
rget\testnamespace.doodad.jar.jar
[INFO] [install:install]
[INFO] Installing
c:\projects\maven-jboss-head\jboss-head\common\namespace\targe
t\testnamespace.doodad.jar.jar to C:\Documents and
Settings\ruel\.m2\repository\
org\jboss\server\common\namespace\namespace\5.0-SNAPSHOT\namespace-5.0-SNAPSHOT.
jar
[INFO]
-
This is pretty easy to reproduce all you have to do is give a finalName and
run the install plugin:
project
modelVersion4.0.0/modelVersion
groupIdorg.jboss.server.common.namespace/groupId
artifactIdnamespace/artifactId
packagingjar/packaging
version5.0-SNAPSHOT/version
nameJBoss-Common - namespace/name
parent
groupIdorg.jboss.server.common/groupId
artifactIdproject.common/artifactId
version5.0-SNAPSHOT/version
/parent
build
finalNametestnamespace.doodad.jar/finalName
/build
/project
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-5) non originality pom.xml on install or deploy
[ http://jira.codehaus.org/browse/MINSTALL-5?page=all ]
Maria Odea Ching moved MNG-1714 to MINSTALL-5:
--
Version: (was: 2.0)
Component: (was: maven-install-plugin)
Workflow: jira (was: Maven)
Key: MINSTALL-5 (was: MNG-1714)
Project: Maven 2.x Install Plugin (was: Maven 2)
non originality pom.xml on install or deploy
Key: MINSTALL-5
URL: http://jira.codehaus.org/browse/MINSTALL-5
Project: Maven 2.x Install Plugin
Type: Bug
Environment: windown 2000
Reporter: pinghe
Priority: Critical
Attachments: maven.error.png
for example my-test-plugin.
pom.xml:
project
modelVersion4.0.0/modelVersion
groupIdmy.test/groupId
artifactIdmytest-plugin-parent/artifactId
packagingpom/packaging
version${my.project.version}/version
urlhttp://${my.project.site.ip}/projects/mytest/url
properties
my.project.site.ip10.0.0.1/my.project.site.ip
my.project.version1.0/my.project.version
/properties
/project
-
installed.
mytest-plugin-parent-1.0.pom :
project
modelVersion4.0.0/modelVersion
groupIdmy.test/groupId
artifactIdmytest-plugin-parent/artifactId
packagingpom/packaging
version${my.project.version}/version ---without
replace
urlhttp://${my.project.site.ip}/projects/mytest/url
--- without replace
properties
my.project.site.ip10.0.0.1/my.project.site.ip
my.project.version1.0/my.project.version
/properties
/project
should similarity exported-pom.xml content.
version1.0/version ---replace
urlhttp://10.0.0.1/projects/mytest/url --- replace
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-2) Install-file zeros file if the source file is the target file.
[ http://jira.codehaus.org/browse/MINSTALL-2?page=all ] Maria Odea Ching moved MNG-1322 to MINSTALL-2: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-2 (was: MNG-1322) Project: Maven 2.x Install Plugin (was: Maven 2) Install-file zeros file if the source file is the target file. -- Key: MINSTALL-2 URL: http://jira.codehaus.org/browse/MINSTALL-2 Project: Maven 2.x Install Plugin Type: Bug Environment: linux 2.6.12, sun j2sdk 1.5.0_02-b09 Reporter: Philipp Meier Assignee: John Casey Attachments: MNG-1322-maven-install-plugin.patch Original Estimate: 2 hours Time Spent: 40 minutes Remaining: 0 minutes If the install plugins tries to install a file from the local repository to the same locate it overwrites this one with a zero bytes version. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-8) option on install-file to generate a skeleton pom
[ http://jira.codehaus.org/browse/MINSTALL-8?page=all ] Maria Odea Ching moved MNG-1407 to MINSTALL-8: -- Version: (was: 2.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-8 (was: MNG-1407) Project: Maven 2.x Install Plugin (was: Maven 2) option on install-file to generate a skeleton pom - Key: MINSTALL-8 URL: http://jira.codehaus.org/browse/MINSTALL-8 Project: Maven 2.x Install Plugin Type: Improvement Reporter: Matthew Pocock Assignee: Brett Porter Priority: Minor Sometimes I need to add jars to my local repo using something like: mvn install:install-file -Dfile=.. -DartifactId=.. -DgroupId=... -Dversion=... -Dtype=jar This doesn't generate a pom, which can cause trixinesses. Could we have a -DgeneratePom=true option that writes a skeleton pom in for the artifact? it would default to false. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-7) Add a parameter to install a custom pom when using install:install-file
[ http://jira.codehaus.org/browse/MINSTALL-7?page=all ] Maria Odea Ching moved MNG-1647 to MINSTALL-7: -- Fix Version: (was: 2.0.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-7 (was: MNG-1647) Project: Maven 2.x Install Plugin (was: Maven 2) Add a parameter to install a custom pom when using install:install-file --- Key: MINSTALL-7 URL: http://jira.codehaus.org/browse/MINSTALL-7 Project: Maven 2.x Install Plugin Type: Improvement Reporter: David Jackman Assignee: Allan Ramirez Priority: Minor Right now, I can install a 3rd party artifact to my repository using install:install-file then, in a separate command, install a custom pom for that artifact using install:install-file again with packaging set to pom and the file parameter pointing to my custom pom file. Since I can do this with two commands successfully, I made this a minor priority issue. It would be nice if the install:install-file goal took an additional parameter referencing my custom pom file and installed it at the same time. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-1) Manifest generation problems caused by valid POM information
[ http://jira.codehaus.org/browse/MJAR-1?page=all ] Maria Odea Ching moved MNG-1558 to MJAR-1: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-1 (was: MNG-1558) Project: Maven 2.x Jar Plugin (was: Maven 2) Manifest generation problems caused by valid POM information Key: MJAR-1 URL: http://jira.codehaus.org/browse/MJAR-1 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Bob Allison Assignee: John Casey Attachments: MNG-1558-plexus-archiver.patch It looks like we have some problems with the contents of manifests in jar files. According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced: 1) All text must be UTF-8 2) Lines are limited to 72 characters; longer lines must be continued 3) Sections are divided by blank lines Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking. Example: The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded. Workarounds for the present: -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters. -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt). -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-3) LICENSE.txt no longer saved in META-INF
[ http://jira.codehaus.org/browse/MJAR-3?page=all ] Maria Odea Ching moved MNG-1615 to MJAR-3: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-3 (was: MNG-1615) Project: Maven 2.x Jar Plugin (was: Maven 2) LICENSE.txt no longer saved in META-INF --- Key: MJAR-3 URL: http://jira.codehaus.org/browse/MJAR-3 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Joerg Schaible Priority: Minor The M1 jar plugin copied the LICENSE.txt file into the MTEA-INF folder of the resulting artifact. The jar plugin for M2 does this no longer. It should be at least configurable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-8) Maven creates jar for a project without java sources
[ http://jira.codehaus.org/browse/MJAR-8?page=all ] Maria Odea Ching moved MNG-1449 to MJAR-8: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-8 (was: MNG-1449) Project: Maven 2.x Jar Plugin (was: Maven 2) Maven creates jar for a project without java sources Key: MJAR-8 URL: http://jira.codehaus.org/browse/MJAR-8 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Giorgio Gallo Assignee: Brett Porter Priority: Minor Attachments: MNG-1449.zip A jar file is generated even for projects with no java sources (ie: no src/main/java directory) - this creates some problems with the current assembly implementation, since an horrible near-empty jar gets into the assembly. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-12) Missing support for adding sections to the manifest at build time
[ http://jira.codehaus.org/browse/MJAR-12?page=all ] Maria Odea Ching moved MNG-1202 to MJAR-12: --- Version: (was: 2.0 (RC)) Fix Version: (was: 2.0 (RC)) Component: (was: maven-jar-plugin) (was: maven-archiver) Workflow: jira (was: Maven) Key: MJAR-12 (was: MNG-1202) Project: Maven 2.x Jar Plugin (was: Maven 2) Missing support for adding sections to the manifest at build time - Key: MJAR-12 URL: http://jira.codehaus.org/browse/MJAR-12 Project: Maven 2.x Jar Plugin Type: Improvement Environment: Windows XP SP2 Java J2SE 1.4.2_08 Reporter: Mark Russell Assignee: Brett Porter Priority: Minor Attachments: ManifestSectionSupportChanges.zip Currently it is not possible to add additional sections to the manifest by configuring the maven-jar-plugin through the configuration section in the pom.xml. You can only add attributes to the main section using the manifestEntries tag.. Example... It is currently not possible to generate the manifest shown here: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: RUSM01 Package: org.com.foo.app Build-Jdk: 1.4.2_08 Extension-Name: my-app Specification-Vendor: MyCompany Inc Implementation-Vendor: MyCompany Inc Implementation-Title: my-app Implementation-Version: 1.0-SNAPSHOT Main-Class: org.com.foo.App mode: development url: http://maven.apache.org Name: SampleSectionNumberOne mode: development url: http://maven.apache.org Name: SampleSectionNumberTwo mode: development url: http://maven.apache.org Current workaround: Define the manifest in a seperate file and configure the maven-jar-plugin to use the file for the manifest. Attached to this defect is a zip file containing a potential fix. The zip file contains the changed version of the MavenArchiveConfiguration.java and MavenArchiver.java files, along with a patch file to update the originals. Additionally a new class was needed and is found in the ManifestSection.java file included in the zip. Last, a pom.xml example that shows how the feature would be used. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-7) jar plugin recreates jar files all the time
[ http://jira.codehaus.org/browse/MJAR-7?page=all ] Maria Odea Ching moved MNG-1838 to MJAR-7: -- Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-7 (was: MNG-1838) Project: Maven 2.x Jar Plugin (was: Maven 2) jar plugin recreates jar files all the time --- Key: MJAR-7 URL: http://jira.codehaus.org/browse/MJAR-7 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Jochen Wiedmann The jar plugin doesn't seem to check, whether rebuilding a jar file is actually required. For daily work, it would be faster to do what Ant's jar task does: Compare the timestamps of the input files with the timestamp of the target file. While this approach has the obvious advantage of being safe (and thus possibly well choosen as a default), it is not appropriate for large projects, where a single build requires a real lot of jar files being rebuilt, even if only a single source file has been changed. This applies, in particular, because comparable plugins like the war, ear, and assembly plugin are forced to behave in the same manner. Suggestion: - Introduce a new property, for example maven.build.force. The main idea of the property would be, that other plugins (install, war, assembly, ...) would listen to the same property. While they would possible ignore it initially, one could add support later on. - The default property value would be true. - If the property value is set to false, then the jar plugin compares the timestamps of the input files with the timestamp of the output file. If the latter is newer than the input timestamps, then the jar file isn't being rebuilt. I am ready to provide a patch, if my suggestion should find interest. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-10) dealing with licenses
[ http://jira.codehaus.org/browse/MJAR-10?page=all ] Maria Odea Ching moved MNG-1331 to MJAR-10: --- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-10 (was: MNG-1331) Project: Maven 2.x Jar Plugin (was: Maven 2) dealing with licenses - Key: MJAR-10 URL: http://jira.codehaus.org/browse/MJAR-10 Project: Maven 2.x Jar Plugin Type: New Feature Reporter: Jorg Heymans Priority: Minor maven could offer a configurable way to include project licenses in the jar, briefly discussed on IRC today jorgdoes m2 have anything built-in to deal with library licenses ? just wondering ... kenney license tag in the pom is all I think jorgah yep, i knew I saw something about it somewhere, tnx kenney kenney and just distribute poms for non-freely-distributable jars (like the sun ones), stating where you can download/purchase them jorgmmm Typically the licenses listed for the project are that of the project itself, and not of dependencies. jorgok so unless all our dependencies are good maven citizens this won't really work ... jorgno prob, we'll just include them ourselves then kenney do you have to? kenney if people distribute a jar/pom without a license, it's their fault jorgwell we (cocoon) have always done so jorgthat's true though , it's up to them to include them trygvis I think people are a bit slack when it comes to adding that information jorgdefinitely kenney what about the bundle upload system? jorgthat's why i was hoping for maven to be able enforce something trygvis we should probably start to enumerate the various licenses and give them IDs instead kenney bundles have to have a LICENSE file.. where does that go? trygvis not sure, ask carlos kenney yeah or maybe extend the license tag to name the license (ASL-2.0) and the online-url, or alternatively list the license content itself.. or just add a bla-X-LICENSE.txt on ibiblio per project jorgsomething like that yeah, and perhaps offering a configurable way of having the license file included in the jar ? jorgor is that a hairy legal thing maven shouldn't get into ? trygvis kenney: the name there (ASL-2.0) would be the id trygvis jorg: good idea jorgit would certainly advocate , albeit rather enforced, correct usage of libraries -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-9) Support jar signing.
[ http://jira.codehaus.org/browse/MJAR-9?page=all ] Maria Odea Ching moved MNG-1130 to MJAR-9: -- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-9 (was: MNG-1130) Project: Maven 2.x Jar Plugin (was: Maven 2) Support jar signing. Key: MJAR-9 URL: http://jira.codehaus.org/browse/MJAR-9 Project: Maven 2.x Jar Plugin Type: New Feature Environment: gentoo linux, jdk 1.4.2_06 Reporter: Corridor Software Developer Assignee: Brett Porter Attachments: MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130_jar-sign-verify.diff, MNG-1130_jar-sign-verify.diff, MNG-1130_jar-sign-verify.diff, jar-sign-verify.diff, mng-1130.tar.gz The Java webstart framework requires that jars used by a webstart application be signed. Create a new goal on the maven jar plugin called jar:sign. The goal would take a keystore file as input and sign the project artifact prior to installing it to the local repository or deploying it to the repo. The plugin should also allow a specific dependency or dependencies, as well as it's runtime dependencies to be signed. This functionality is required prior to finishing the webstart-maven-plugin. Two example test projects will be attached to the ticket shortly. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-6) dependencies woth scope test are included in Extension-List of the manifest
[ http://jira.codehaus.org/browse/MJAR-6?page=all ] Maria Odea Ching moved MNG-1821 to MJAR-6: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-6 (was: MNG-1821) Project: Maven 2.x Jar Plugin (was: Maven 2) dependencies woth scope test are included in Extension-List of the manifest - Key: MJAR-6 URL: http://jira.codehaus.org/browse/MJAR-6 Project: Maven 2.x Jar Plugin Type: Bug Environment: Any Reporter: Pascal Grange When activating the Extension-List generation for the jar-plugin : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration manifest addExtensionstrue/addExtensions /manifest ... Event the dependencies that have only a test scope such as junit, for instance, are included in the manifest. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-11) extention parametrization
[ http://jira.codehaus.org/browse/MJAR-11?page=all ] Maria Odea Ching moved MNG-1654 to MJAR-11: --- Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-11 (was: MNG-1654) Project: Maven 2.x Jar Plugin (was: Maven 2) extention parametrization - Key: MJAR-11 URL: http://jira.codehaus.org/browse/MJAR-11 Project: Maven 2.x Jar Plugin Type: Improvement Reporter: Dmitry Tsigelnik Please add parametrization of extention of building file. For example: I want to build ejb3 file or another archive special for concreate Jboss deployer likes .har or .spring -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-5) no Implementation-Vendor-Id in META-INF/MANIFEST.MF
[ http://jira.codehaus.org/browse/MJAR-5?page=all ] Maria Odea Ching moved MNG-1794 to MJAR-5: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-5 (was: MNG-1794) Project: Maven 2.x Jar Plugin (was: Maven 2) no Implementation-Vendor-Id in META-INF/MANIFEST.MF --- Key: MJAR-5 URL: http://jira.codehaus.org/browse/MJAR-5 Project: Maven 2.x Jar Plugin Type: Bug Environment: Linux 2.6.12-9-386 Kubuntu java version 1.4.2-02 Reporter: Pascal Grange Priority: Blocker mvn package does not generate an entry Implementation-Vendor-Id. This is a blocker when we use the extension mechanisme with tomcat. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-2) Output goes to the console because maven/plexus-archiver are not use as components
[ http://jira.codehaus.org/browse/MJAR-2?page=all ] Maria Odea Ching moved MNG-1071 to MJAR-2: -- Version: (was: 2.0-alpha-3) Fix Version: (was: 2.0-beta-3) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-2 (was: MNG-1071) Project: Maven 2.x Jar Plugin (was: Maven 2) Output goes to the console because maven/plexus-archiver are not use as components -- Key: MJAR-2 URL: http://jira.codehaus.org/browse/MJAR-2 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Jason van Zyl Assignee: Emmanuel Venisse Because the maven/plexus-archivers are instantiated directly they use some code that creates a console logger and will not have a logger handed to it from the logger manager that all the other components use. This creates inconsistent logging from maven-embedder where I'm trying to capture all logging in one place. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-4) Multiline description provides invalid header in the generated jar files
[ http://jira.codehaus.org/browse/MJAR-4?page=all ] Maria Odea Ching moved MNG-1869 to MJAR-4: -- Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-4 (was: MNG-1869) Project: Maven 2.x Jar Plugin (was: Maven 2) Multiline description provides invalid header in the generated jar files - Key: MJAR-4 URL: http://jira.codehaus.org/browse/MJAR-4 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Gilles Scokart When a description text is written on more than 1 line, the produced Manifest files are invalid. Indeed one of the header of this manifiest contains the description text as is. When the jar is loaded, we receive an error saying invalid headers. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-15) Excluding pom.properties and pom.xml from produced artifact
[ http://jira.codehaus.org/browse/MJAR-15?page=all ] Maria Odea Ching moved MNG-1520 to MJAR-15: --- Fix Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-15 (was: MNG-1520) Project: Maven 2.x Jar Plugin (was: Maven 2) Excluding pom.properties and pom.xml from produced artifact Key: MJAR-15 URL: http://jira.codehaus.org/browse/MJAR-15 Project: Maven 2.x Jar Plugin Type: Wish Reporter: Anuerin Diaz Assignee: Allan Ramirez Original Estimate: 1 hour Time Spent: 30 minutes Remaining: 30 minutes Although the files are supposed to be used in capturing as much build information as necessary, they are considered to be a security risk in some situations. There must be a way to exclude these files even during development packaging. The released Maven plugins do not contain these files so there is a way to remove them. The following configuration do not work when added to the project descriptor: plugin artifactIdmaven-jar-plugin/artifactId configuration excludes**/pom.*/excludes /configuration /plugin -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-13) configure test-jar to include only special classes of the test source
[ http://jira.codehaus.org/browse/MJAR-13?page=all ] Maria Odea Ching moved MNG-1674 to MJAR-13: --- Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-13 (was: MNG-1674) Project: Maven 2.x Jar Plugin (was: Maven 2) configure test-jar to include only special classes of the test source - Key: MJAR-13 URL: http://jira.codehaus.org/browse/MJAR-13 Project: Maven 2.x Jar Plugin Type: Improvement Reporter: Joerg Schaible Priority: Minor The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-14) pom.xml information automatically included in META-INF during jar
[ http://jira.codehaus.org/browse/MJAR-14?page=all ]
Maria Odea Ching moved MNG-1543 to MJAR-14:
---
Version: (was: 2.0)
Fix Version: (was: 2.0.3)
Component: (was: maven-jar-plugin)
Workflow: jira (was: Maven)
Key: MJAR-14 (was: MNG-1543)
Project: Maven 2.x Jar Plugin (was: Maven 2)
pom.xml information automatically included in META-INF during jar
--
Key: MJAR-14
URL: http://jira.codehaus.org/browse/MJAR-14
Project: Maven 2.x Jar Plugin
Type: Improvement
Reporter: Jorg Heymans
Assignee: John Casey
Attachments: MNG-1543-maven-archiver.patch
The jar plugin automatically adds a pom.xml in META-INF, which makes sense.
But this pom.xml also contains local paths ie
build
sourceDirectoryd:\src\excalibur-trunk\framework\api\src\java/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
testSourceDirectoryd:\src\excalibur-trunk\framework\api\src\test/testSourceDirectory
outputDirectoryd:\src\excalibur-trunk\framework\api\target\classes/outputDirectory
testOutputDirectoryd:\src\excalibur-trunk\framework\api\target\test-classes/testOutputDirectory
resources
resource
targetPathMETA-INF/targetPath
directoryd:\src\excalibur-trunk\framework\api\..\../directory
includes
includeLICENSE.txt/include
includeNOTICE.txt/include
/includes
/resource
/resources
testResources
testResource
directoryd:\src\excalibur-trunk\framework\api\src\test\resources/directory
I don't see how this information could be useful to anyone else, and i'ld
rather not have my local paths in distribution jars - call me paranoid :)
Conversation log from IRC :
jorgis there a way to tell maven not to include the pom.xml in
META-INF when creating jars ?
jesse hm, not that I know of
jesse might be a boolean to control it in there somewhere
jorgi looked at the jar plugin config .. didn't seem like it
jorgit's not a real problem, just funny that this is done by default
jesse I don't know, it makes it easier down the road to have
automated things interrogate the jar for dependencies of the things inside
trygvis yeah, you're right there jesse
jorgmmm well yes that makes sense ...
jorgthanks !
trygvis jorg: it's useful for the application itself
trygvis like reading out the version number from pom.properties
jorgtrygvis: yes, but the pom also had my local paths in it for
sourceDirectory and stuff, that's why i found it a bit strange
trygvis makes it easier making versioning-aware application and gives a
thigh integration with your project management tool (aka maven)
trygvis hm
trygvis that should possibly be changed indeed
trygvis File properties should be made relative to ${basedir} again
trygvis when writing out the pom that is
jorgi can understand about the dependencies , but the build
configuration probably shouldn't be in there
jorg
directoryd:\src\excalibur-trunk\framework\api\..\../directory
trygvis jorg: file an issue, it should be relative to ${basedir} if
there at all
trygvis IMO the build parts of a pom could be stripped from the repo
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-1) site-embedded report mode check always returns true
[ http://jira.codehaus.org/browse/MJAVADOC-1?page=all ] Maria Odea Ching moved MNG-1510 to MJAVADOC-1: -- Version: (was: 2.0) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-1 (was: MNG-1510) Project: Maven 2.x Javadoc Plugin (was: Maven 2) site-embedded report mode check always returns true --- Key: MJAVADOC-1 URL: http://jira.codehaus.org/browse/MJAVADOC-1 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Shinobu Kawai Yoshida Assignee: Allan Ramirez Attachments: MNG-1510.patch o.a.m.p.javadoc.JavadocReport#executeReport Line 685: if ( !javadocDirectory.equals( getOutputDirectory() ) ) javadocDirectory is a File and getOutputDirectory() is a String. This will never return false. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-3) plugin should honor proxy settings
[ http://jira.codehaus.org/browse/MJAVADOC-3?page=all ] Maria Odea Ching moved MNG-1829 to MJAVADOC-3: -- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-3 (was: MNG-1829) Project: Maven 2.x Javadoc Plugin (was: Maven 2) plugin should honor proxy settings -- Key: MJAVADOC-3 URL: http://jira.codehaus.org/browse/MJAVADOC-3 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: tested on Linux/Windows Reporter: Dirk Olmes Priority: Minor The maven2 plugin should honor the proxy settings. When specifying the link option, the forked javadoc process always tries to fetch the package-list directly. This fails on corporate networks, where all web access has to go through a proxy. I've tried to specify a proxy by using the additionalparam option but this does not work because all parameters for the javadoc process are written to an options file, which is passed to the forked javadoc process. By the time the javadoc process gets to see the arguments, it is already running so all VM parameters (-J-Dhttp.proxyHost...) cause errors. The most seamless integration would be to pass whatever proxy is configured to the forked javadoc process. Configuration options for specifying the proxy for the javadoc-plugin would be acceptable, too. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-8) group parameter seems hard to use
[ http://jira.codehaus.org/browse/MJAVADOC-8?page=all ] Maria Odea Ching moved MNG-1154 to MJAVADOC-8: -- Version: (was: 2.0-beta-3) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-8 (was: MNG-1154) Project: Maven 2.x Javadoc Plugin (was: Maven 2) group parameter seems hard to use --- Key: MJAVADOC-8 URL: http://jira.codehaus.org/browse/MJAVADOC-8 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Martin Desruisseaux Priority: Minor The group parameter is a comma-separated list. A looks into the source code suggest that the plugin uses StringTokenizer for splitting the String around comas, no matter if the coma were inside quotes or not. Next, the tokens are put between quotes if they contains spaces. This means that the following parameter: group Feature Geometry org.geotools.geometry* /group is translated into the following javadoc options: -group Feature Geometry org.geotools.geometry* when it should has been: -group Feature Geometry org.geotools.geometry* Putting Feature Geometry between quotes in the group parameter doesn't help (it produces an other unexpected result). We really need a space between the title and the packages; it is part of javadoc tools specification, and current maven-javadoc-plugin seems to prevent that. Furthermore, because of the coma-delimited nature of the group argument, we can't put coma in group title. I would like to suggest to replace the current group parameter syntax by the same one than Ant: group title=Feature Geometry packages=org.geotools.geometry*/ -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-5) Sending wrong parameters to -bottom
[ http://jira.codehaus.org/browse/MJAVADOC-5?page=all ]
Maria Odea Ching moved MNG-1029 to MJAVADOC-5:
--
Version: (was: 2.0-beta-2)
Fix Version: (was: 2.0-beta-2)
Component: (was: maven-javadoc-plugin)
Workflow: jira (was: Maven)
Key: MJAVADOC-5 (was: MNG-1029)
Project: Maven 2.x Javadoc Plugin (was: Maven 2)
Sending wrong parameters to -bottom
---
Key: MJAVADOC-5
URL: http://jira.codehaus.org/browse/MJAVADOC-5
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Matthew Beermann
Assignee: Brett Porter
Priority: Minor
My POM has inceptionYear2004/inceptionYear, yet the generated Javadoc has
the following footer: Copyright null MyTeamName. All Rights Reserved.
It could have something to do with the stated default for the plugin's
bottom parameter: Copyright ${project.inceptionYear-currentYear}
${project.organization.name}. All Rights Reserved. I could be imagining it,
but doesn't the dash belong outside the braces?
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-7) The project name can't have any spaces
[ http://jira.codehaus.org/browse/MJAVADOC-7?page=all ]
Maria Odea Ching moved MNG-1389 to MJAVADOC-7:
--
Component: (was: maven-javadoc-plugin)
Workflow: jira (was: Maven)
Key: MJAVADOC-7 (was: MNG-1389)
Project: Maven 2.x Javadoc Plugin (was: Maven 2)
The project name can't have any spaces
--
Key: MJAVADOC-7
URL: http://jira.codehaus.org/browse/MJAVADOC-7
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Alexandre Poitras
If you put space in your project name in your pom.xml file, there is an error
during the javadoc generation.
In my opinion, it looks like the plugin doesn't use string quotes on the
javadoc command line for the doctitle argument, wich default value is
${project.name} ${project.version} API.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-10) Javadoc report does not honor site directory when run from site:site
[ http://jira.codehaus.org/browse/MJAVADOC-10?page=all ] Maria Odea Ching moved MNG-873 to MJAVADOC-10: -- Version: (was: 2.0-beta-1) Fix Version: (was: 2.0-beta-1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-10 (was: MNG-873) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Javadoc report does not honor site directory when run from site:site Key: MJAVADOC-10 URL: http://jira.codehaus.org/browse/MJAVADOC-10 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Kenney Westerhof Assignee: Kenney Westerhof -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-17) Javadoc plugin add a spurious -excludePackageNames option on the javadoc command line
[ http://jira.codehaus.org/browse/MJAVADOC-17?page=all ] Maria Odea Ching moved MNG-1152 to MJAVADOC-17: --- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-17 (was: MNG-1152) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Javadoc plugin add a spurious -excludePackageNames option on the javadoc command line - Key: MJAVADOC-17 URL: http://jira.codehaus.org/browse/MJAVADOC-17 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Martin Desruisseaux Assignee: Allan Ramirez Priority: Minor Attachments: MNG-1152-maven-javadoc-plugin.patch When an excludePackageNames attribute is set in the POM file for the maven-javadoc-plugin configuration, the plugin add the two following arguments to the javadoc command line: -exclude the excludePackageNames value -excludePackageNames the excludePackageNames value The first one is correct. The second do not exists and seems to be an accidental copy-and-paste. It can be viewed there: http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-plugins/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java?rev=291371view=markup Search for excludePackageNames in the above-cited link. The last occurence should be removed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-6) Can't Create Javadocs for WAR project
[ http://jira.codehaus.org/browse/MJAVADOC-6?page=all ] Maria Odea Ching moved MNG-1269 to MJAVADOC-6: -- Version: (was: 2.0) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-6 (was: MNG-1269) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Can't Create Javadocs for WAR project - Key: MJAVADOC-6 URL: http://jira.codehaus.org/browse/MJAVADOC-6 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Stephen Duncan Jr Whlie I was able to create Javadocs in prior releases, for my WAR project, I know get the following message: [INFO] Not executing Javadoc as the project is not a Java classpath-capable package Javadocs for the java source part of a webapp should be considered perfectly valid. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-9) Additionalparam for javadoc shouldn't be put in with quotes
[ http://jira.codehaus.org/browse/MJAVADOC-9?page=all ] Maria Odea Ching moved MNG-1770 to MJAVADOC-9: -- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-9 (was: MNG-1770) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Additionalparam for javadoc shouldn't be put in with quotes --- Key: MJAVADOC-9 URL: http://jira.codehaus.org/browse/MJAVADOC-9 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: David Jackman Attachments: MNG-1770.patch Currently, the value of the additionalparam property is put into the Javadoc command line with quotes around the value. This does not work. It needs to be put in as-is (and any quoting of the value or portions thereof must be set by the user). -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-2) Plugin should be configured in reporting not build
[ http://jira.codehaus.org/browse/MJAVADOC-2?page=all ] Maria Odea Ching moved MNG-1863 to MJAVADOC-2: -- Version: (was: 2.0.1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-2 (was: MNG-1863) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Plugin should be configured in reporting not build -- Key: MJAVADOC-2 URL: http://jira.codehaus.org/browse/MJAVADOC-2 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: window xp, jdk 1.5, cygwin Reporter: Howard M. Lewis Ship The documentation at http://maven.apache.org/plugins/maven-javadoc-plugin/configuration.html indicates that you configure this plugin inside the build element of the pom; some research revealed that it is part of the reporting element. As a new Maven (2) user, this really caught me unawares. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-18) create a mojo goal named - javadoc:jar
[ http://jira.codehaus.org/browse/MJAVADOC-18?page=all ] Maria Odea Ching moved MNG-810 to MJAVADOC-18: -- Fix Version: (was: 2.0-beta-1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-18 (was: MNG-810) Project: Maven 2.x Javadoc Plugin (was: Maven 2) create a mojo goal named - javadoc:jar --- Key: MJAVADOC-18 URL: http://jira.codehaus.org/browse/MJAVADOC-18 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Edwin Punzalan Assignee: Edwin Punzalan Priority: Minor Attachments: maven-javadoc-plugin.patch, pom.patch create a javadoc:jar goal to enable install/deploy of javadoc reports -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-14) javadoc:javadoc fails with ioexception on Mac OSX due to wrong path to javadoc command.
[ http://jira.codehaus.org/browse/MJAVADOC-14?page=all ] Maria Odea Ching moved MNG-1155 to MJAVADOC-14: --- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-14 (was: MNG-1155) Project: Maven 2.x Javadoc Plugin (was: Maven 2) javadoc:javadoc fails with ioexception on Mac OSX due to wrong path to javadoc command. --- Key: MJAVADOC-14 URL: http://jira.codehaus.org/browse/MJAVADOC-14 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Mac OSX 10.4.2 Reporter: Dave Sag Assignee: John Casey Attachments: MNG-1155-macosx-support-for-javadoc-plugin.diff Original Estimate: 30 minutes Remaining: 30 minutes The javadoc:javadoc plugin has started failing on my Mac since the release of beta 3 of m2. the stacktrace is as follows: [INFO] [INFO] Diagnosis: An error has occurred in JavaDocs report generation. [INFO] [DEBUG] Trace: org.apache.maven.plugin.MojoExecutionException: An error has occurred in JavaDocs report generation. at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:98) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:307) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217) at org.apache.maven.cli.MavenCli.main(MavenCli.java:247) 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:324) 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.reporting.MavenReportException: An error has occurred in javadoc report generation. at org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:841) at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:583) at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:92) ... 16 more Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process. at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:679) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:69) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:56) at org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:831) ... 18 more Caused by: java.io.IOException: /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../bin/javadoc: not found at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.init(UNIXProcess.java:54) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:566) at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:674) ... 21 more the correct path should be $JAVA_HOME/bin/javadoc not $JAVA_HOME/../bin/javadoc at least that's on the mac. not sure where java ends up on other platforms. dave -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-16) linkoffline tag is not parsed properly
[ http://jira.codehaus.org/browse/MJAVADOC-16?page=all ] Maria Odea Ching moved MNG-968 to MJAVADOC-16: -- Version: (was: 2.0-beta-1) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-16 (was: MNG-968) Project: Maven 2.x Javadoc Plugin (was: Maven 2) linkoffline tag is not parsed properly -- Key: MJAVADOC-16 URL: http://jira.codehaus.org/browse/MJAVADOC-16 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: David DIDIER Assignee: John Casey Attachments: MNG-968.patch, MNG-968_b.patch, OfflineLink.java Original Estimate: 4 hours Time Spent: 5 hours Remaining: 0 minutes When using the javadoc plugin with linkoffline, my pom contains : reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.0-beta-1/version configuration linkofflinehttp://java.sun.com/j2se/1.4.2/docs/api/ path/to/package-list//linkoffline source1.4/source /configuration /plugin ... /plugins /reporting but the generated command is then : javadoc.exe ... -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/ path/to/package-list/ ... according to the javadoc documentation, it seems that the syntax should be : javadoc.exe ... -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/ path/to/package-list/ ... (without ) Here is the interesting part of the trace : [INFO] [javadoc:javadoc] [INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package-source 1.4 -sourcePath D:\projets\ndd\root\..\ndd14-base\src\main\java -classpath D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\commons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar -author -bottom Copyright null DD. All Rights Reserved. -charset ISO-8859-1 -d D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle NDD Base project 0.20-SNAPSHOT API -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/ ../root/src/javadoc/j2sdk-1.4.2/ -stylesheetfile D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use -version -windowtitle NDD Base project 0.20-SNAPSHOT API @files javadoc: Illegal package name: D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-19) Overview parameter isn't having backslashes fixed before writing out to arguments
[ http://jira.codehaus.org/browse/MJAVADOC-19?page=all ] Maria Odea Ching moved MNG-1765 to MJAVADOC-19: --- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-19 (was: MNG-1765) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Overview parameter isn't having backslashes fixed before writing out to arguments - Key: MJAVADOC-19 URL: http://jira.codehaus.org/browse/MJAVADOC-19 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: David Jackman Attachments: overviewparameter.patch When using the overview parameter for the Javadoc plugin, the value (which is a path) isn't correctly converted to use forward slashes instead of backslashes. The attached patch fixes the problem. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-12) Menu links to javadoc uses wrong link
[ http://jira.codehaus.org/browse/MJAVADOC-12?page=all ] Maria Odea Ching moved MNG-1864 to MJAVADOC-12: --- Version: (was: 2.0.1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-12 (was: MNG-1864) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Menu links to javadoc uses wrong link - Key: MJAVADOC-12 URL: http://jira.codehaus.org/browse/MJAVADOC-12 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: jdk 1.5, win xp, cygwin Reporter: Howard M. Lewis Ship Assignee: Brett Porter Got Maven to generate my javadoc, but in the menus it generates the wrong link. The link is generated as: href=../apidocs/index.html But this is a largely blank page; the JavaDoc is actually generated as ../apidocs/overview-summary.html -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-4) Regression: javadoc plugin fails when a maxmemory parameter is provided
[ http://jira.codehaus.org/browse/MJAVADOC-4?page=all ] Maria Odea Ching moved MNG-1237 to MJAVADOC-4: -- Version: (was: 2.0 (RC)) Fix Version: (was: 2.0.1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-4 (was: MNG-1237) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Regression: javadoc plugin fails when a maxmemory parameter is provided - Key: MJAVADOC-4 URL: http://jira.codehaus.org/browse/MJAVADOC-4 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Martin Desruisseaux Assignee: Lester Ecarma Attachments: MNG-1237-maven-javadoc-plugin.patch maven-javadoc-plugin fails when a maxmemory parameter is provided. This is a regression, since it was working in Maven 2 beta 3. This is caused by a change in the way parameters are handled in Maven 2 RC: the maven-javadoc-plugin now put them in an options file, and the command line now contains only: path to j2se tools/javadoc @options @files But the maxmemory maps to the -J-Xmx option, and all -J options are required to appear in the command line. They are not allowed to appear in the options file. See: http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#argumentfiles maven-javadoc-plugin should put all -J options on the command line instead of the options file. This constraint applies at least to the following parameters: maxmemory minmemory (I have not checked if it applied to other parameters). -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-11) site report generates an 'empty' target/site/apidocs/index.html
[ http://jira.codehaus.org/browse/MJAVADOC-11?page=all ] Maria Odea Ching moved MNG-1398 to MJAVADOC-11: --- Version: (was: 2.0 (RC)) Fix Version: (was: 2.0.1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-11 (was: MNG-1398) Project: Maven 2.x Javadoc Plugin (was: Maven 2) site report generates an 'empty' target/site/apidocs/index.html --- Key: MJAVADOC-11 URL: http://jira.codehaus.org/browse/MJAVADOC-11 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: John Allen Assignee: Brett Porter javadoc site report generates an 'empty' target/site/apidocs/index.html html head ... div id=bodyColumn div id=contentBox /div /div div class=clear hr/ /div div id=footer div class=xright#169; 2005 Acme Org /div div class=clear hr/ /div /div /body /html -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-13) locale parameter causes javadoc to fail
[ http://jira.codehaus.org/browse/MJAVADOC-13?page=all ] Maria Odea Ching moved MNG-1610 to MJAVADOC-13: --- Version: (was: 2.0) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-13 (was: MNG-1610) Project: Maven 2.x Javadoc Plugin (was: Maven 2) locale parameter causes javadoc to fail --- Key: MJAVADOC-13 URL: http://jira.codehaus.org/browse/MJAVADOC-13 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Maven 2.0, maven-javadoc-plugin v2.0-beta-2 Reporter: Anuerin Diaz Assignee: Allan Ramirez Using the following configuration plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId configuration localeen_US/locale /configuration /plugin the javadoc execution fails with: [INFO] An error has occurred in JavaDocs report generation. Embedded error: Exit code: 1 - javadoc: option -locale must be first on the command line. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-25) option -locale must be first on the command line.
[ http://jira.codehaus.org/browse/MJAVADOC-25?page=all ] Maria Odea Ching moved MNG-1163 to MJAVADOC-25: --- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-25 (was: MNG-1163) Project: Maven 2.x Javadoc Plugin (was: Maven 2) option -locale must be first on the command line. - Key: MJAVADOC-25 URL: http://jira.codehaus.org/browse/MJAVADOC-25 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Martin Desruisseaux Assignee: Brett Porter Priority: Minor Providing a locale parameter currently cause a javadoc failure because the maven-javadoc-plugin put the -locale option after some other options like -encoding. According the javadoc tool documentation (http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#locale), the -locale parameter must be first. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-23) Failure to launch Javadoc correctly
[ http://jira.codehaus.org/browse/MJAVADOC-23?page=all ] Maria Odea Ching moved MNG-1386 to MJAVADOC-23: --- Version: (was: 2.0) Fix Version: (was: 2.0) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-23 (was: MNG-1386) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Failure to launch Javadoc correctly --- Key: MJAVADOC-23 URL: http://jira.codehaus.org/browse/MJAVADOC-23 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Professional Reporter: Peter Pilgrim Assignee: Carlos Sanchez Running from the DOS command % mvn javadoc:javadoc Produces [INFO] [javadoc:javadoc] [INFO] C:\opt\j2sdk1.4.2_04\jre\..\bin\javadoc.exe @options @files usage: javadoc [options] [packagenames] [sourcefiles] [classnames] [EMAIL PROTECTED] -overview file Read overview documentation from HTML file -public Show only public classes and members -protectedShow protected/public classes and members (default) -package Show package/protected/public classes and members -private Show all classes and members -help Display command line options and exit -doclet class Generate output via alternate doclet -docletpath pathSpecify where to find doclet class files -sourcepath pathlistSpecify where to find source files -classpath pathlist Specify where to find user class files -exclude pkglistSpecify a list of packages to exclude -subpackages subpkglist Specify subpackages to recursively load -breakiteratorCompute 1st sentence with BreakIterator -bootclasspath pathlist Override location of class files loaded by the bootstrap class loader -source release Provide source compatibility with specified release -extdirs dirlistOverride location of installed extensions -verbose Output messages about what Javadoc is doing -locale nameLocale to be used, e.g. en_US or en_US_WIN -encoding name Source file encoding name -Jflag Pass flag directly to the runtime system Provided by Standard doclet: -d directoryDestination directory for output files -use Create class and package usage pages -version Include @version paragraphs -author Include @author paragraphs -docfilessubdirs Recursively copy doc-file subdirectories -splitindex Split index into one file per letter -windowtitle text Browser window title for the documenation -doctitle html-code Include title for the overview page -header html-code Include header text for each page -footer html-code Include footer text for each page -bottom html-code Include bottom text for each page -link url Create links to javadoc output at url -linkoffline url url2 Link to docs at url using package list at u rl2 -excludedocfilessubdir name1:.. Exclude any doc-files subdirectories with give n name. -group name p1:p2.. Group specified packages together in overview page -nocommentSupress description and tags, generate only de clarations. -nodeprecated Do not include @deprecated information -noqualifier name1:name2:... Exclude the list of qualifiers from the output . -nosince Do not include @since information -nodeprecatedlist Do not generate deprecated list -notree Do not generate class hierarchy -noindex Do not generate index -nohelp Do not generate help link -nonavbar Do not generate navigation bar -quietDo not display status messages to screen -serialwarn Generate warning about @serial tag -tag name:locations:header Specify single argument custom tags -taglet The fully qualified name of Taglet to register -tagletpath The path to Taglets -charset charsetCharset for cross-platform viewing of generate d documentation. -helpfile file Include file that help link links to -linksource Generate source in HTML -stylesheetfile pathFile to change style of the generated document ation -docencoding name Output encoding name 1 error [INFO] - --- [ERROR] BUILD ERROR [INFO
[jira] Moved: (MJAVADOC-28) [EMAIL PROTECTED] foo} doesn't work when foo is a package name
[ http://jira.codehaus.org/browse/MJAVADOC-28?page=all ] Maria Odea Ching moved MNG-1166 to MJAVADOC-28: --- Version: (was: 2.0-beta-3) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-28 (was: MNG-1166) Project: Maven 2.x Javadoc Plugin (was: Maven 2) [EMAIL PROTECTED] foo} doesn't work when foo is a package name - Key: MJAVADOC-28 URL: http://jira.codehaus.org/browse/MJAVADOC-28 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Martin Desruisseaux Priority: Minor See or link tags of the kind [EMAIL PROTECTED] org.mypackage} doesn't work with maven-javadoc-plugin (we get a Tag @link: reference not found: org.mypackage warning), while it work when using the javadoc tool from the command line or from an Ant script. I suspect that this is related to the way maven-javadoc-plugin work, which provides a list of source files as a @files argument. A possible workaround is to provide a way to use the maven-javadoc-plugin through the javadoc's -subpackages option, instead of letting maven-javadoc-plugin creates a @files. It would gives more control to the user, would allows the current excludePackageNames parameter to work (this parameter is currently useless since it is ignored when the files to process are provided in @files), and would solve the problem reported in this JIRA issue. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-34) don't evaluate links in offline mode
[ http://jira.codehaus.org/browse/MJAVADOC-34?page=all ] Maria Odea Ching moved MNG-1004 to MJAVADOC-34: --- Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-34 (was: MNG-1004) Project: Maven 2.x Javadoc Plugin (was: Maven 2) don't evaluate links in offline mode Key: MJAVADOC-34 URL: http://jira.codehaus.org/browse/MJAVADOC-34 Project: Maven 2.x Javadoc Plugin Type: Improvement Reporter: Brett Porter Assignee: John Casey -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-26) Javadoc:jar goal executes for non-Java projects
[ http://jira.codehaus.org/browse/MJAVADOC-26?page=all ] Maria Odea Ching moved MNG-1464 to MJAVADOC-26: --- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-26 (was: MNG-1464) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Javadoc:jar goal executes for non-Java projects --- Key: MJAVADOC-26 URL: http://jira.codehaus.org/browse/MJAVADOC-26 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: David Jackman Assignee: John Casey Attachments: JavadocJar.patch When the javadoc:javadoc goal is attempted for a project that does not have Java source, it correctly displays a message to this effect and jumps out. However, the javadoc:jar goal doesn't do this (although it does display a message)--it will build a javadoc jar containing no Javadocs. I've attached a patch that fixes the issue (very simple fix). -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-32) Add javadoc links to dependencies in project.xml
[ http://jira.codehaus.org/browse/MJAVADOC-32?page=all ] Maria Odea Ching moved MNG-405 to MJAVADOC-32: -- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-32 (was: MNG-405) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Add javadoc links to dependencies in project.xml Key: MJAVADOC-32 URL: http://jira.codehaus.org/browse/MJAVADOC-32 Project: Maven 2.x Javadoc Plugin Type: Improvement Reporter: Brett Porter (originally filed by Tim McCune) It would be nice to be able to specify the URLs that are currently in maven.javadoc.links in project.properties in my project.xml. For example: dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8/version apihttp://junit.sourceforge.net/javadoc/api /dependency It would also be nice to be able to specify a JDK version in project.xml and have Maven automatically link in the javadoc API for that version of the JDK. Specifying the JDK version in project.xml would also allow Maven to make intelligent assumptions about stuff like maven.compile.source, maven.compile.target, maven.javadoc.source, maven.test.source, etc. It's really annoying to have to specify at least 4 separate properties in project.properties for every project just because I'm using JDK 1.5. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-33) Provide new javadoc:aggregate goal to perform javadoc operation on project and subprojects.
[ http://jira.codehaus.org/browse/MJAVADOC-33?page=all ] Maria Odea Ching moved MNG-965 to MJAVADOC-33: -- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-33 (was: MNG-965) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Provide new javadoc:aggregate goal to perform javadoc operation on project and subprojects. --- Key: MJAVADOC-33 URL: http://jira.codehaus.org/browse/MJAVADOC-33 Project: Maven 2.x Javadoc Plugin Type: Improvement Reporter: John Allen Priority: Minor Provide new javadoc:aggregate goal to perform javadoc operation on a project and its subprojects, idea being that aggregate pulls together the classpath and sourcepath for all the project and subprojects and then churns out normal javadoc. i.e. projects:- /root/ /root/a/src/... /root/a/b/src/... /root/a/b/c/src/... /root/a/d/src/... /root/a/e/src/... @ /root/a- m2 javadoc:aggregate generates javadoc in /root/a/target/javadoc for src contained within projects a, b, c, d, and e. Note, javadoc does not currently provide support for this kind of aggregation and so people have traditionally written their own specialised tasks/scripts (in ant land say) to handle it. sun do refer to the idea of an incremental build in their FAQ which they say they are considering for the future (fat chance) (http://java.sun.com/j2se/javadoc/faq/#incrementalbuild) but that is about generating aggregate docs from already existing javadocs. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-22) Javadoc plugin fails when JAVA_HOME contains spaces
[ http://jira.codehaus.org/browse/MJAVADOC-22?page=all ] Maria Odea Ching moved MNG-620 to MJAVADOC-22: -- Version: (was: 2.0-alpha-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-22 (was: MNG-620) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Javadoc plugin fails when JAVA_HOME contains spaces --- Key: MJAVADOC-22 URL: http://jira.codehaus.org/browse/MJAVADOC-22 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Yann Le Du Assignee: Lester Ecarma Attachments: MNG-620.patch, MNG-620_b.patch, javadocTest.zip Original Estimate: 8 hours Time Spent: 4 hours, 1 minute Remaining: 3 hours, 59 minutes From now on, JDK is automatically installed in C:\Program Files\Java\jdk1.5.0_04, which contains spaces. site:site produces the following error : [INFO] Generate JavaDocs report. C:\Program Files\Java\jdk1.5.0_04\jre\..\bin\javadoc C:\Program Files\Java\jdk1.5.0_04\jre\..\bin\javadoc -use [...] -classpath [...] @files D:\SVN_Source\COMMON\trunk\common-framework\target\javadoc 'C:\Program' is not recognized as an internal or external command, operable program or batch file. The file cannot be found. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-27) Javadoc plugin defaults to showing package private items, but should default to protected
[ http://jira.codehaus.org/browse/MJAVADOC-27?page=all ] Maria Odea Ching moved MNG-1769 to MJAVADOC-27: --- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-27 (was: MNG-1769) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Javadoc plugin defaults to showing package private items, but should default to protected - Key: MJAVADOC-27 URL: http://jira.codehaus.org/browse/MJAVADOC-27 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: David Jackman Attachments: MNG-1769.patch The default access level for items shown in the Javadocs when using the Javadoc tool directly is protected (see http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#protected). However, the default access level for the Javadoc plugin is package. The default for the plugin should be the same as the tool. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-21) excludePackageNames property doesn't work
[ http://jira.codehaus.org/browse/MJAVADOC-21?page=all ] Maria Odea Ching moved MNG-1768 to MJAVADOC-21: --- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-21 (was: MNG-1768) Project: Maven 2.x Javadoc Plugin (was: Maven 2) excludePackageNames property doesn't work - Key: MJAVADOC-21 URL: http://jira.codehaus.org/browse/MJAVADOC-21 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: David Jackman Attachments: MNG-1768.patch The Javadoc plugin passes the excludePackageNames as the -exclude parameter for the execution of the Javadoc tool. However, because the Javadoc plugin passes the source file names on the command line, the -exclude parameter has no effect (it only excludes packages from the list specified by the -subpackages parameter). In order for package exclusion to work, the source files for these packages must be removed from the source file names list by the plugin. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-29) additionalparam parameter should not put an -additional on the javadoc command line.
[ http://jira.codehaus.org/browse/MJAVADOC-29?page=all ] Maria Odea Ching moved MNG-1164 to MJAVADOC-29: --- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-29 (was: MNG-1164) Project: Maven 2.x Javadoc Plugin (was: Maven 2) additionalparam parameter should not put an -additional on the javadoc command line. Key: MJAVADOC-29 URL: http://jira.codehaus.org/browse/MJAVADOC-29 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Martin Desruisseaux Assignee: John Casey Priority: Minor Original Estimate: 10 minutes Time Spent: 10 minutes Remaining: 0 minutes When using a additionalparam parameter, the maven-javadoc-plugin put -additionalparam in front of additional parameters. There is no such -additionalparam option in the javadoc tool. Maven-javadoc-plugin should just copy the additionalparam content without -additionalparam option. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-31) javadoc plugin doesn't honor multiple custom tags
[ http://jira.codehaus.org/browse/MJAVADOC-31?page=all ] Maria Odea Ching moved MNG-704 to MJAVADOC-31: -- Version: (was: 2.0-alpha-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-31 (was: MNG-704) Project: Maven 2.x Javadoc Plugin (was: Maven 2) javadoc plugin doesn't honor multiple custom tags - Key: MJAVADOC-31 URL: http://jira.codehaus.org/browse/MJAVADOC-31 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Indrajit Raychaudhuri Assignee: John Casey Priority: Minor Original Estimate: 30 minutes Time Spent: 30 minutes Remaining: 0 minutes M2 javaodc plugin doesn't honor multiple tag as it did with M1. In M1 we could specify this in project.properties: maven.javadoc.customtags = usage todo fixme usage.name = .usage usage.description = Usage: usage.enabled = true usage.scope = all todo.name = .todo todo.description = Todo: todo.enabled = false todo.scope = all fixme.name = .fixme fixme.description = Fixme: fixme.enabled = false fixme.scope = all However, in M2 the putting the tag/ switch isn't honor multiple times. Only the last one get passed to the javadoc -tag switch. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-36) Would like a way to get default javadoc behavior
[ http://jira.codehaus.org/browse/MJAVADOC-36?page=all ] Maria Odea Ching moved MNG-1156 to MJAVADOC-36: --- Version: (was: 2.0-beta-3) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-36 (was: MNG-1156) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Would like a way to get default javadoc behavior Key: MJAVADOC-36 URL: http://jira.codehaus.org/browse/MJAVADOC-36 Project: Maven 2.x Javadoc Plugin Type: Wish Environment: Windows XP Reporter: Martin Desruisseaux Priority: Minor The javadoc plugin overrides some Sun's javadoc default options with its own default. This is quite nice for options like -bottom, since Maven has informations that Sun's javadoc doesn't have. The -package option (which default to 'true' in maven-javadoc-plugin, while the default was 'false' in Sun's javadoc) sound a little bit more surprising to me, since it lead us to a situation where we have two set of default values to keep in mind: the Sun's ones, and the Maven ones. It is not a real problem for options like -package and -use. It is a little bit more disturbing for -stylesheet, since it seems hard to tell to Maven to not use the Maven's stylesheet, but to keep the Sun's default stylesheet instead. I understand that we can provide our own stylesheet with the stylesheet parameter, but in this case I have no file to point; I would just like to keep Sun's default stylesheet. I would like a way to disable completly the -stylesheet option in the javadoc plugin. Or alternatively, the plugin may use the Maven's stylesheet only when explicitly required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-24) javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path
[ http://jira.codehaus.org/browse/MJAVADOC-24?page=all ] Maria Odea Ching moved MNG-1035 to MJAVADOC-24: --- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-24 (was: MNG-1035) Project: Maven 2.x Javadoc Plugin (was: Maven 2) javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path --- Key: MJAVADOC-24 URL: http://jira.codehaus.org/browse/MJAVADOC-24 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Indrajit Raychaudhuri Assignee: Lester Ecarma Attachments: MNG-1035.patch Original Estimate: 4 hours Time Spent: 6 hours, 6 minutes Remaining: 0 minutes javadoc:javadoc exits with error due to white-space in C:\Documents and Settings\user.m2 path as it tries to include jars from repository. The same project used to work with M2-beta1. The changes in Revision 280832, 290370 might have something to do with this. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-37) specifying visibility levels other than package requires setting showPackage to false
[ http://jira.codehaus.org/browse/MJAVADOC-37?page=all ] Maria Odea Ching moved MNG-1513 to MJAVADOC-37: --- Version: (was: 2.0) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-37 (was: MNG-1513) Project: Maven 2.x Javadoc Plugin (was: Maven 2) specifying visibility levels other than package requires setting showPackage to false - Key: MJAVADOC-37 URL: http://jira.codehaus.org/browse/MJAVADOC-37 Project: Maven 2.x Javadoc Plugin Type: Wish Reporter: Shinobu Kawai Yoshida Priority: Minor In order to specify a visibility level other than package, you need to explicitly set showPackage to false. Otherwise, javadoc complains that error - More than one of -public, -private, -package, or -protected specified.. It would be nice if the default was handled in the code instead of the @parameter annotation. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-30) javadoc plugin does not work on war projects
[ http://jira.codehaus.org/browse/MJAVADOC-30?page=all ] Maria Odea Ching moved MNG-1257 to MJAVADOC-30: --- Version: (was: 2.0 (RC)) Fix Version: (was: 2.0.1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-30 (was: MNG-1257) Project: Maven 2.x Javadoc Plugin (was: Maven 2) javadoc plugin does not work on war projects - Key: MJAVADOC-30 URL: http://jira.codehaus.org/browse/MJAVADOC-30 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Linux/sun jdk 1.4.1_04 Reporter: Joe Shomphe Assignee: Brett Porter when mvn javadoc:javadoc is run, the following error occurs: [INFO] Not executing Javadoc as the project is not a Java classpath-capable package this only happens when my pom,xml has packagingwar/packaging declared When this is set to jar, javadoc works fine. The war project has java sources in it! -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-35) Include project dependencies to javadoc classpath
[ http://jira.codehaus.org/browse/MJAVADOC-35?page=all ] Maria Odea Ching moved MNG-909 to MJAVADOC-35: -- Version: (was: 2.0-beta-1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-35 (was: MNG-909) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Include project dependencies to javadoc classpath - Key: MJAVADOC-35 URL: http://jira.codehaus.org/browse/MJAVADOC-35 Project: Maven 2.x Javadoc Plugin Type: Improvement Reporter: Daniel Schömer Priority: Minor When calling m2 javadoc:javadoc, the classpath parameter of the javadoc tool only contains the target/classes/ directory. But if the project sources use external depencies (like log4j, jakarta commons, ...), the javadoc tool is not able to find the referenced classes of the dependencies and displays according warnings. The javadoc:javadoc goal should set the classpath of the javadoc tool to the target/classes/ directory and the project's dependencies in compile scope. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-15) JavadocReport throws NPE
[ http://jira.codehaus.org/browse/MJAVADOC-15?page=all ] Maria Odea Ching moved MNG-779 to MJAVADOC-15: -- Version: (was: 2.0-beta-1) Fix Version: (was: 2.0-beta-2) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-15 (was: MNG-779) Project: Maven 2.x Javadoc Plugin (was: Maven 2) JavadocReport throws NPE Key: MJAVADOC-15 URL: http://jira.codehaus.org/browse/MJAVADOC-15 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: SVN revision 239419 on Linux Reporter: Bob Allison Assignee: Brett Porter Running site:site on a project that was working yesterday (revision 235747), received teh following exception: [INFO] Generate JavaDocs report. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Error during report generation [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Error during report generation at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:492) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:441) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:316) 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:585) 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.reporting.MavenReportException: An error has occurred in javadoc report generation. at org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:852) at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:613) at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:298) ... 16 more Caused by: java.lang.NullPointerException at org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:795) ... 18 more The code in JavadocReport is: if ( this.doctitle.equals( DEFAULT_DOCTITLE ) ) I am assuming that doctitle is not being initialized properly. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-20) Javadoc plugin puts docletPath on commandline instead of docletpath
[ http://jira.codehaus.org/browse/MJAVADOC-20?page=all ] Maria Odea Ching moved MNG-1199 to MJAVADOC-20: --- Version: (was: 2.0-beta-3) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-20 (was: MNG-1199) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Javadoc plugin puts docletPath on commandline instead of docletpath --- Key: MJAVADOC-20 URL: http://jira.codehaus.org/browse/MJAVADOC-20 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: j2sdk 1.4.2_08 Reporter: Kees de Kooter Assignee: Allan Ramirez Attachments: MNG-1199-maven-javadoc-plugin.patch Original Estimate: 10 minutes Remaining: 10 minutes Javadoc plugin puts docletPath on commandline instead of docletpath. As a result the doclet class cannot be found. Following line in org/apache/maven/plugin/javadoc/JavadocReport should be corrected: addArgIfNotEmpty( arguments, -docletPath, quotedPathArgument( docletPath ) ); -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MPLUGIN-3) apparent race condition when installing a plugin and executing the same plugin in a single build session
[ http://jira.codehaus.org/browse/MPLUGIN-3?page=all ] Maria Odea Ching moved MNG-1089 to MPLUGIN-3: - Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: Plugins and Lifecycle) (was: maven-plugin-plugin) Workflow: jira (was: Maven) Key: MPLUGIN-3 (was: MNG-1089) Project: Maven 2.x Plugin Plugin (was: Maven 2) apparent race condition when installing a plugin and executing the same plugin in a single build session Key: MPLUGIN-3 URL: http://jira.codehaus.org/browse/MPLUGIN-3 Project: Maven 2.x Plugin Plugin Type: Bug Reporter: John Casey Assignee: John Casey Original Estimate: 6 hours Time Spent: 6 hours Remaining: 0 minutes Steps to reproduce: go into maven/maven-core-it/it0013 execute: m2 -cpl -e clean:clean install it0013:it0013 The first time around (if you have a clean local repo WRT it0013), it should simply install the plugin, and run it. HOWEVER, subsequent runs will intermittently result in an NPE in java.util.jar.JarFile. I believe this is a result of initializing the plugin container for it0013:it0013 early in the lifecycle executor in order to determine whether this mojo is an aggregator. When the install mojo completes, it will have overwritten the original artifact file used in this plugin container's classpath. I *think* this is what's causing the problem, though I can't exactly work out why it's intermittent. At any rate, we need to address this. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MPLUGIN-5) Need a way to set requiresReports to true by attributing my Mojo.
[ http://jira.codehaus.org/browse/MPLUGIN-5?page=all ]
Maria Odea Ching moved MNG-1298 to MPLUGIN-5:
-
Version: (was: 2.0)
Component: (was: Plugin API)
(was: Plugin Creation Tools)
(was: maven-plugin-plugin)
Workflow: jira (was: Maven)
Key: MPLUGIN-5 (was: MNG-1298)
Project: Maven 2.x Plugin Plugin (was: Maven 2)
Need a way to set requiresReports to true by attributing my Mojo.
-
Key: MPLUGIN-5
URL: http://jira.codehaus.org/browse/MPLUGIN-5
Project: Maven 2.x Plugin Plugin
Type: Improvement
Reporter: Dave Sag
Assignee: Brett Porter
I am writing a plugin that aggregates the reports from other plugins. It
therefore makes sense that the requresReports tag be set to true, as this
plugin does require that the other reports have been generated.
in dicussion on the [EMAIL PROTECTED] list Brett Porter suggested:
You need to use the reports, so declare:
@parameter expression=${reports}
That will trigger it. But are you sure you relly need access to the reports?
That's generally only for the site plugin.
but that's a parameter setting, and does not seem to be bound to the mojo
wide requiresReports tag.
I suggested:
What I need is acccess to the various checkstyle (etc) reports in an xml
format.
what you describe below doesn't seem appropriate to me. My parameters
already have various expressions and default values but i do need to ensure
that the checkstyle (etc) plugins have already been run, before
myplugin is run.
requiresReports is a goal-wide setting, not specific to a parameter, so i
guess what i am assking is
1) what is that tag actually for
2) how to set it to true
why not just let me set @requiresReports in the very top of my mojo where
the @goal, @phase and @requiresDependencyResolution tags live.
It's quite possible I have failed to properly understand the usage of the
requiresReports tag.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MPLUGIN-1) Maven fails while developing plugin with 1.5 compliant sources
[ http://jira.codehaus.org/browse/MPLUGIN-1?page=all ] Maria Odea Ching moved MNG-1651 to MPLUGIN-1: - Version: (was: 2.0) Component: (was: maven-plugin-plugin) Workflow: jira (was: Maven) Key: MPLUGIN-1 (was: MNG-1651) Project: Maven 2.x Plugin Plugin (was: Maven 2) Maven fails while developing plugin with 1.5 compliant sources -- Key: MPLUGIN-1 URL: http://jira.codehaus.org/browse/MPLUGIN-1 Project: Maven 2.x Plugin Plugin Type: Bug Reporter: Jose Gonzalez Gomez I'm developing a plugin for Maven, and my sources contains 1.5 features, such as use of generics. When I try to install the plugin in my local repository I get the following: [INFO] Scanning for projects... [INFO] [INFO] Building Maven Docbook plugin [INFO]task-segment: [install] [INFO] [INFO] [plugin:descriptor] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] syntax error @[129,64] in file:/C:/Documents and Settings/jgonzalez/Mis documentos/proyectos/otros/maven-opendocbook-plugin/src/ main/java/com/openinput/tools/maven/opendocbook/TransformMojo.java [INFO] [INFO] Trace com.thoughtworks.qdox.parser.ParseException: syntax error @[129,64] in file:/C:/Documents and Settings/jgonzalez/Mis documentos/proyectos/otros/maven-opendocbook-plugin/src/main/java/com/openinput/tools/maven/opendocbook/TransformMojo.java at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504) at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610) at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308) at com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) at com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:99) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke
[jira] Moved: (MPLUGIN-8) ability to cleanse local plugins
[ http://jira.codehaus.org/browse/MPLUGIN-8?page=all ] Maria Odea Ching moved MNG-1639 to MPLUGIN-8: - Fix Version: (was: 2.1) Component: (was: maven-plugin-plugin) Workflow: jira (was: Maven) Key: MPLUGIN-8 (was: MNG-1639) Project: Maven 2.x Plugin Plugin (was: Maven 2) ability to cleanse local plugins Key: MPLUGIN-8 URL: http://jira.codehaus.org/browse/MPLUGIN-8 Project: Maven 2.x Plugin Plugin Type: Improvement Reporter: Brett Porter it would be nice to have an option in the bootstrap + mojo in the plugin plugin that could walk the plugin groups and cleanse locally installed versions of plugins to ensure you get what is in the repository. This perhaps would not be necessary with better configuration of when to use/not to use development versions of plugins, which is under consideration for 2.1. Let's evaluate it though. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
