[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353023#comment-353023
]
Meunier Frederic commented on MJAVADOC-408:
---
I encounter the same blocker issue. To fix it, I added the following property
in my POMs:
false
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
>Reporter: Volker Seibt
>Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] Closed: (MCHANGES-205) jira 4 support
[ http://jira.codehaus.org/browse/MCHANGES-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederic closed MCHANGES-205. - Resolution: Not A Bug The problem was due to the user used to connect to Jira who had not enough access rights. > jira 4 support > -- > > Key: MCHANGES-205 > URL: http://jira.codehaus.org/browse/MCHANGES-205 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.3 > Environment: Maven 2.2.1, Jira 4.1.2 >Reporter: Frederic >Priority: Critical > > Hello, > we've just upgraded to the latest Jira version 4.1.2, and it seems as if the > maven-changes-plugin can't handle Jira 4 (we had no problems before when > using Jira 3.12.x). Now however, I receive the following lines in the log > file. Note that the pid "1" is not correct for the active project. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\surefire-report.html > [INFO] Generate "Maven Surefire Report" report. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\jira-report.html > [INFO] Generate "JIRA Report" report. > [DEBUG] JIRA lives at: http://jira.mycompany.be > [DEBUG] The JIRA URL http://jira.mycompany.be/browse/PROJECTKEY doesn't > include a pid, trying to extract it from JIRA. > [DEBUG] Successfully reached JIRA. > [DEBUG] Found the pid 1 at http://jira.mycompany.be/browse/PROJECTKEY > [DEBUG] download jira issues from url > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [INFO] Downloading from JIRA at: > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [WARNING] Downloading from JIRA failed. Received: [400] > So I seem to receive an http error where the server 400 indicating that the > request is not valid. > I assume Jira 4 URL's are different from previous Jira versions. > Can you add Jira 4 support? > I'd be glad to provide extra information if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-205) jira 4 support
[ http://jira.codehaus.org/browse/MCHANGES-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237631#action_237631 ] Frederic commented on MCHANGES-205: --- Seems there is no problem at all when using Jira 4. I've been misled by the Jira http error code 400. After the Jira migration our user had no longer access to the specific projects. So this was not a bug. > jira 4 support > -- > > Key: MCHANGES-205 > URL: http://jira.codehaus.org/browse/MCHANGES-205 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.3 > Environment: Maven 2.2.1, Jira 4.1.2 >Reporter: Frederic >Priority: Critical > > Hello, > we've just upgraded to the latest Jira version 4.1.2, and it seems as if the > maven-changes-plugin can't handle Jira 4 (we had no problems before when > using Jira 3.12.x). Now however, I receive the following lines in the log > file. Note that the pid "1" is not correct for the active project. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\surefire-report.html > [INFO] Generate "Maven Surefire Report" report. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\jira-report.html > [INFO] Generate "JIRA Report" report. > [DEBUG] JIRA lives at: http://jira.mycompany.be > [DEBUG] The JIRA URL http://jira.mycompany.be/browse/PROJECTKEY doesn't > include a pid, trying to extract it from JIRA. > [DEBUG] Successfully reached JIRA. > [DEBUG] Found the pid 1 at http://jira.mycompany.be/browse/PROJECTKEY > [DEBUG] download jira issues from url > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [INFO] Downloading from JIRA at: > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [WARNING] Downloading from JIRA failed. Received: [400] > So I seem to receive an http error where the server 400 indicating that the > request is not valid. > I assume Jira 4 URL's are different from previous Jira versions. > Can you add Jira 4 support? > I'd be glad to provide extra information if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-205) jira 4 support
[ http://jira.codehaus.org/browse/MCHANGES-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237542#action_237542 ] Frederic commented on MCHANGES-205: --- Okay. Seems I'm not passing the correct authentication parameters anymore. Fixed that, and now it seems to work correctly. So one question is remaining: for almost all of our projects we are currently specifying the Jira URL in this format: http://jira.mycompany.be/browse/PROJECTKEY, which seemed to work correct before. However with Jira 4, the plugin is no longer capable of determining the project ID. So do we have to use another format which includes the jiraID, like this: http://jira.mycompany.be/BrowseProject.jspa?id=10141 . Or is there some way to keep the old format working ? > jira 4 support > -- > > Key: MCHANGES-205 > URL: http://jira.codehaus.org/browse/MCHANGES-205 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.3 > Environment: Maven 2.2.1, Jira 4.1.2 >Reporter: Frederic >Priority: Critical > > Hello, > we've just upgraded to the latest Jira version 4.1.2, and it seems as if the > maven-changes-plugin can't handle Jira 4 (we had no problems before when > using Jira 3.12.x). Now however, I receive the following lines in the log > file. Note that the pid "1" is not correct for the active project. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\surefire-report.html > [INFO] Generate "Maven Surefire Report" report. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\jira-report.html > [INFO] Generate "JIRA Report" report. > [DEBUG] JIRA lives at: http://jira.mycompany.be > [DEBUG] The JIRA URL http://jira.mycompany.be/browse/PROJECTKEY doesn't > include a pid, trying to extract it from JIRA. > [DEBUG] Successfully reached JIRA. > [DEBUG] Found the pid 1 at http://jira.mycompany.be/browse/PROJECTKEY > [DEBUG] download jira issues from url > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [INFO] Downloading from JIRA at: > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [WARNING] Downloading from JIRA failed. Received: [400] > So I seem to receive an http error where the server 400 indicating that the > request is not valid. > I assume Jira 4 URL's are different from previous Jira versions. > Can you add Jira 4 support? > I'd be glad to provide extra information if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-205) jira 4 support
[ http://jira.codehaus.org/browse/MCHANGES-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237534#action_237534 ] Frederic commented on MCHANGES-205: --- After sniffing, I obtain exactly the same results, but the last call fails: SNIFFER GET /secure/IssueNavigator.jspa?view=rss&pid=10141&statusIds=6&resolutionIds=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 Location: IssueNavigator.jspa?view=rss&pid=10141&statusIds=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none GET /secure/IssueNavigator.jspa?view=rss&pid=10141&statusIds=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 Location: IssueNavigator.jspa?view=rss&pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none GET /secure/IssueNavigator.jspa?view=rss&pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 Location: ../sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none GET /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 HTTP/1.1 400 , message: The value 'PROJECTKEY' does not exist for the field 'project'. Not quite sure how to continue now. > jira 4 support > -- > > Key: MCHANGES-205 > URL: http://jira.codehaus.org/browse/MCHANGES-205 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.3 > Environment: Maven 2.2.1, Jira 4.1.2 >Reporter: Frederic >Priority: Critical > > Hello, > we've just upgraded to the latest Jira version 4.1.2, and it seems as if the > maven-changes-plugin can't handle Jira 4 (we had no problems before when > using Jira 3.12.x). Now however, I receive the following lines in the log > file. Note that the pid "1" is not correct for the active project. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\surefire-report.html > [INFO] Generate "Maven Surefire Report" report. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\jira-report.html > [INFO] Generate "JIRA Report" report. > [DEBUG] JIRA lives at: http://jira.mycompany.be > [DEBUG] The JIRA URL http://jira.mycompany.be/browse/PROJECTKEY doesn't > include a pid, trying to extract it from JIRA. > [DEBUG] Successfully reached JIRA. > [DEBUG] Found the pid 1 at http://jira.mycompany.be/browse/PROJECTKEY > [DEBUG] download jira issues from url > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [INFO] Downloading from JIRA at: > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [WARNING] Downloading from JIRA failed. Received: [400] > So I seem to receive an http error where the server 400 indicating that the > request is not valid. > I assume Jira 4 URL's are different from previous Jira versions. > Can you add Jira 4 support? > I'd be glad to provide extra information if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-205) jira 4 support
[ http://jira.codehaus.org/browse/MCHANGES-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237532#action_237532 ] Frederic commented on MCHANGES-205: --- I've done some extra tests, jira seems to be doing several redirects: (these are the redirects captured when I browse to the URL maven requests): GET http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=10141&statusIds=6&resolutionIds=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 Redirect to Location: IssueNavigator.jspa?view=rss&pid=10141&statusIds=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none GET http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=10141&statusIds=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 Redirect to Location: IssueNavigator.jspa?view=rss&pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none GET http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 Redirect to Location: ../sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none http://jira.mycompany.be/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid=10141&status=6&resolution=1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none HTTP/1.1 200 OK I'm not sure if Maven will handle all these redirects. I'll try to put a proxy logger between Maven and Jira (or has maven a debug option for all network calls)? I guess Maven handles the redirects not corretly and hence result in the http 400 error code. > jira 4 support > -- > > Key: MCHANGES-205 > URL: http://jira.codehaus.org/browse/MCHANGES-205 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.3 > Environment: Maven 2.2.1, Jira 4.1.2 >Reporter: Frederic >Priority: Critical > > Hello, > we've just upgraded to the latest Jira version 4.1.2, and it seems as if the > maven-changes-plugin can't handle Jira 4 (we had no problems before when > using Jira 3.12.x). Now however, I receive the following lines in the log > file. Note that the pid "1" is not correct for the active project. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\surefire-report.html > [INFO] Generate "Maven Surefire Report" report. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\jira-report.html > [INFO] Generate "JIRA Report" report. > [DEBUG] JIRA lives at: http://jira.mycompany.be > [DEBUG] The JIRA URL http://jira.mycompany.be/browse/PROJECTKEY doesn't > include a pid, trying to extract it from JIRA. > [DEBUG] Successfully reached JIRA. > [DEBUG] Found the pid 1 at http://jira.mycompany.be/browse/PROJECTKEY > [DEBUG] download jira issues from url > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [INFO] Downloading from JIRA at: > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [WARNING] Downloading from JIRA failed. Received: [400] > So I seem to receive an http error where the server 400 indicating that the > request is not valid. > I assume Jira 4 URL's are different from previous Jira versions. > Can you add Jira 4 support? > I'd be glad to provide extra information if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-205) jira 4 support
[ http://jira.codehaus.org/browse/MCHANGES-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237510#action_237510 ] Frederic commented on MCHANGES-205: --- I've took a look at the html source, and I see where pid 1 comes from: http://support.atlassian.com/secure/CreateIssue.jspa?issuetype=1&pid=1";>Report a problem > jira 4 support > -- > > Key: MCHANGES-205 > URL: http://jira.codehaus.org/browse/MCHANGES-205 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.3 > Environment: Maven 2.2.1, Jira 4.1.2 >Reporter: Frederic >Priority: Critical > > Hello, > we've just upgraded to the latest Jira version 4.1.2, and it seems as if the > maven-changes-plugin can't handle Jira 4 (we had no problems before when > using Jira 3.12.x). Now however, I receive the following lines in the log > file. Note that the pid "1" is not correct for the active project. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\surefire-report.html > [INFO] Generate "Maven Surefire Report" report. > [DEBUG] Generating > C:\javadev\prj\project\subproject\target\site\jira-report.html > [INFO] Generate "JIRA Report" report. > [DEBUG] JIRA lives at: http://jira.mycompany.be > [DEBUG] The JIRA URL http://jira.mycompany.be/browse/PROJECTKEY doesn't > include a pid, trying to extract it from JIRA. > [DEBUG] Successfully reached JIRA. > [DEBUG] Found the pid 1 at http://jira.mycompany.be/browse/PROJECTKEY > [DEBUG] download jira issues from url > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [INFO] Downloading from JIRA at: > http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none > [WARNING] Downloading from JIRA failed. Received: [400] > So I seem to receive an http error where the server 400 indicating that the > request is not valid. > I assume Jira 4 URL's are different from previous Jira versions. > Can you add Jira 4 support? > I'd be glad to provide extra information if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-205) jira 4 support
jira 4 support -- Key: MCHANGES-205 URL: http://jira.codehaus.org/browse/MCHANGES-205 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.3 Environment: Maven 2.2.1, Jira 4.1.2 Reporter: Frederic Priority: Critical Hello, we've just upgraded to the latest Jira version 4.1.2, and it seems as if the maven-changes-plugin can't handle Jira 4 (we had no problems before when using Jira 3.12.x). Now however, I receive the following lines in the log file. Note that the pid "1" is not correct for the active project. [DEBUG] Generating C:\javadev\prj\project\subproject\target\site\surefire-report.html [INFO] Generate "Maven Surefire Report" report. [DEBUG] Generating C:\javadev\prj\project\subproject\target\site\jira-report.html [INFO] Generate "JIRA Report" report. [DEBUG] JIRA lives at: http://jira.mycompany.be [DEBUG] The JIRA URL http://jira.mycompany.be/browse/PROJECTKEY doesn't include a pid, trying to extract it from JIRA. [DEBUG] Successfully reached JIRA. [DEBUG] Found the pid 1 at http://jira.mycompany.be/browse/PROJECTKEY [DEBUG] download jira issues from url http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none [INFO] Downloading from JIRA at: http://jira.mycompany.be/secure/IssueNavigator.jspa?view=rss&pid=1&statusIds=1&statusIds=3&statusIds=4&statusIds=5&resolutionIds=1&component=10106&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=100&reset=true&decorator=none [WARNING] Downloading from JIRA failed. Received: [400] So I seem to receive an http error where the server 400 indicating that the request is not valid. I assume Jira 4 URL's are different from previous Jira versions. Can you add Jira 4 support? I'd be glad to provide extra information if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-257) java.lang.ArrayIndexOutOfBoundsException: 0 when deploying via scp
[ http://jira.codehaus.org/browse/WAGON-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233819#action_233819 ] Esnault Frederic commented on WAGON-257: Could you check your id_rsa private key? Make sure it's only made of the first and ending lines with ONLY the key in between : -BEGIN RSA PRIVATE KEY- BljdivnlmkVCLJvxdkvxjKxdv(...)dfvdfv -END RSA PRIVATE KEY- For example, this key is wrong for Jsch (used by maven) (see the Proc-Type and DEK-Info headers, remove them and the empty line): -BEGIN RSA PRIVATE KEY- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,0AB406BADE9247B3 BljdivnlmkVCLJvxdkvxjKxdv(...)dfvdfv -END RSA PRIVATE KEY- > java.lang.ArrayIndexOutOfBoundsException: 0 when deploying via scp > -- > > Key: WAGON-257 > URL: http://jira.codehaus.org/browse/WAGON-257 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh >Affects Versions: 1.0-beta-5 > Environment: Mac OS X 10.4 >Reporter: Thomas Vandahl > Fix For: 1.0 > > > (Not sure about the version of wagon, I am using Maven 2.1.0 release) > When I try to deploy something that is supposed to use scp as the protocol, > for example "mvn site:deploy", I get the following exception > ---8<--- > [INFO] [site:deploy] > Using private key: /xxx/.ssh/id_rsa > scp://people.apache.org/www/turbine.apache.org/fulcrum/fulcrum-localization/ > - Session: Connection refused > scp://people.apache.org/www/turbine.apache.org/fulcrum/fulcrum-localization/ > - Session: Disconnecting > scp://people.apache.org/www/turbine.apache.org/fulcrum/fulcrum-localization/ > - Session: Disconnected > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error uploading site > Embedded error: Cannot connect. Reason: > java.lang.ArrayIndexOutOfBoundsException: 0 > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) > 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.plugin.MojoExecutionException: Error uploading > site > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:215) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > ... 16 more > Caused by: org.apache.maven.wagon.authentication.AuthenticationException: > Cannot connect. Reason: java.lang.ArrayIndexOutOfBoundsException: 0 > at > org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnectionInternal(AbstractJschWagon.java:137) > at > org.apache.maven.wagon.AbstractWagon.openConnection(AbstractWagon.java:105) > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:207) > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:142) > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184) > ... 18 mo
[jira] Commented: (MJAR-62) Build-Jdk in Manifest.mf does not reflect which compiler version actually compiled the classes in the jar
[
http://jira.codehaus.org/browse/MJAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210191#action_210191
]
Frederic commented on MJAR-62:
--
Is it possible for the jar plugin to support the toolchain features?
The manifest information (Build-Jdk) would then be correct.
> Build-Jdk in Manifest.mf does not reflect which compiler version actually
> compiled the classes in the jar
> -
>
> Key: MJAR-62
> URL: http://jira.codehaus.org/browse/MJAR-62
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Reporter: Stefan Magnus Landrø
>
> Manifest.mf does not reflect the version of the compiler that built the jar,
> but defaults to the version that maven runs under: Build-Jdk:
> ${java.version}.
> I believe this makes users uncertain of which compiler was actually used to
> build the classes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-359) Release plugin depends on mvn being in the path of the shell that started the current build
[ http://jira.codehaus.org/browse/MRELEASE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190522#action_190522 ] Frederic commented on MRELEASE-359: --- Do I understand that the mavenExecutorId could be a way that the release plugin runs without forking a maven to support it's integration when it is launched through the maven embedder? Does not seems to work for me with through m2e using maven-release-plugin 2.0-beta-9 see: http://jira.codehaus.org/browse/MRELEASE-310 > Release plugin depends on mvn being in the path of the shell that started the > current build > --- > > Key: MRELEASE-359 > URL: http://jira.codehaus.org/browse/MRELEASE-359 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-7 >Reporter: John Casey >Assignee: John Casey >Priority: Critical > Fix For: 2.0-beta-8 > > > It's impossible to run a project release from an environment that uses maven > without putting it in the path environment variable. This causes problems > with build servers like Hudson, where you want to be able to configure on a > project-by-project basis the version of Maven being used. The only > alternative is to choose a version of Maven to put into the shell environment > PATH used to start the appserver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-310) ForkedMavenExecutor assumes mvn is on command-line path
[ http://jira.codehaus.org/browse/MRELEASE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190520#action_190520 ] Frederic commented on MRELEASE-310: --- is there a way that the release plugin could run without forking a maven to support it's integration when it is launched through the maven embedder? > ForkedMavenExecutor assumes mvn is on command-line path > --- > > Key: MRELEASE-310 > URL: http://jira.codehaus.org/browse/MRELEASE-310 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform, prepare, stage >Affects Versions: 2.0-beta-7 >Reporter: Brian Jackson > Attachments: ForkedMavenExecutor.patch > > > The ForkedMavenExecutor assumes the mvn executable is on the command-line > path. This will cause the release goals to fail if mvn is run from an > explicit path and the PATH environment variable has not be set to contain a > mvn executable. More dangerously though is the case where the release goal > is started with an explicit mvn executable of one version (for instance > 2.0.8) but a different version of the mvn executable is available on the > PATH. The forked processes will run a different version of Maven2 that the > parent process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-310) ForkedMavenExecutor assumes mvn is on command-line path
[ http://jira.codehaus.org/browse/MRELEASE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190517#action_190517 ] Frederic commented on MRELEASE-310: --- issue on m2e side: https://issues.sonatype.org/browse/MNGECLIPSE-1660 > ForkedMavenExecutor assumes mvn is on command-line path > --- > > Key: MRELEASE-310 > URL: http://jira.codehaus.org/browse/MRELEASE-310 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform, prepare, stage >Affects Versions: 2.0-beta-7 >Reporter: Brian Jackson > Attachments: ForkedMavenExecutor.patch > > > The ForkedMavenExecutor assumes the mvn executable is on the command-line > path. This will cause the release goals to fail if mvn is run from an > explicit path and the PATH environment variable has not be set to contain a > mvn executable. More dangerously though is the case where the release goal > is started with an explicit mvn executable of one version (for instance > 2.0.8) but a different version of the mvn executable is available on the > PATH. The forked processes will run a different version of Maven2 that the > parent process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155516#action_155516 ] Frederic commented on ARCHETYPE-191: So, folks from m2eclipse answered me that it can't work since it is now yet part of maven core: ??"Unfortunately we can't pickup new version of archetype component and have to wait until Maven core will be ready. "?? Hope that they will add this kind of flexibility on m2eclipse side, but in the meantime, do we know when 2.0-alpha-4 fixes will be included in maven core? thx Frederic > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: mytest-1.0.1.jar, mytest-1.0.1.pom, > ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Commented: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153826#action_153826 ] Frederic commented on ARCHETYPE-191: I discovered that it works fine with command line. But it does not work when I try it using maven integration plugin for eclipse. I have open a ticket on their side: http://jira.codehaus.org/browse/MNGECLIPSE-1054 > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: mytest-1.0.1.jar, mytest-1.0.1.pom, > ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Commented: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153716#action_153716 ] Frederic commented on ARCHETYPE-191: I have tried this but it still does not replace the filename tokens. Anyways, as specified in pom of the example attached, the plugin's version was already enforced with 2.0-alpha-4. > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: mytest-1.0.1.jar, mytest-1.0.1.pom, > ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Issue Comment Edited: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152459#action_152459 ] frederic.tardif edited comment on ARCHETYPE-191 at 10/30/08 8:58 AM: -- I have moved my archetype to the new version. BTW, the create-from-project goal is really cool! Unfortunately, the replacement of filename token still does not work. I have attached in the ticket a simple archetype (and its pom) in which I try to apply filename filtering. Maybe you can have a glimpse on it and point out what I am doing wrong for to take advantage of filename filtering. thanks Frederic was (Author: frederic.tardif): I have moved my archetype to the new version. BTW, the create-from-project goal is really cool! Unfortunately, the replacement of filename token still does not work. I have attached in the ticket a simple archetype (and its pom) in which I try to apply filename filtering. Maybe you can have a glimpse on it and point out what I am doing wrong for the take advantage of filename filtering. thanks Frederic > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: mytest-1.0.1.jar, mytest-1.0.1.pom, > ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Updated: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederic updated ARCHETYPE-191: --- Attachment: mytest-1.0.1.jar > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: mytest-1.0.1.jar, mytest-1.0.1.pom, > ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Updated: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederic updated ARCHETYPE-191: --- Attachment: mytest-1.0.1.pom > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: mytest-1.0.1.jar, mytest-1.0.1.pom, > ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Commented: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152459#action_152459 ] Frederic commented on ARCHETYPE-191: I have moved my archetype to the new version. BTW, the create-from-project goal is really cool! Unfortunately, the replacement of filename token still does not work. I have attached in the ticket a simple archetype (and its pom) in which I try to apply filename filtering. Maybe you can have a glimpse on it and point out what I am doing wrong for the take advantage of filename filtering. thanks Frederic > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Commented: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152334#action_152334 ] Frederic commented on ARCHETYPE-191: I am still not able to enjoy the new feature... First, to enable it, I uderstand that i must configure the plugin against 2.0-alpha-4 in the pom of ,y archetype??? and then, I configure in my archetype.xml something like: src/main/config/setup/__artifactId__.properties but it still does not replace the token with generating the file. Any Idea? > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
[jira] Issue Comment Edited: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152334#action_152334 ] frederic.tardif edited comment on ARCHETYPE-191 at 10/29/08 2:29 PM: -- I am still not able to enjoy the new feature... First, to enable it, I uderstand that i must configure the plugin against 2.0-alpha-4 in the pom of my archetype??? and then, I configure in my archetype.xml something like: src/main/config/setup/__artifactId__.properties but it still does not replace the token with generating the file. Any Idea? was (Author: frederic.tardif): I am still not able to enjoy the new feature... First, to enable it, I uderstand that i must configure the plugin against 2.0-alpha-4 in the pom of ,y archetype??? and then, I configure in my archetype.xml something like: src/main/config/setup/__artifactId__.properties but it still does not replace the token with generating the file. Any Idea? > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > Attachments: ReplaceAnyContextPropertyEnhancement-v2.patch, > ReplaceAnyContextPropertyEnhancement.patch > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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
