[jira] [Created] (MCHANGES-362) Check for rest api failed if webuser used
Guillaume Boucherie created MCHANGES-362:
Summary: Check for rest api failed if webuser used
Key: MCHANGES-362
URL: https://issues.apache.org/jira/browse/MCHANGES-362
Project: Maven Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.11
Environment: JIRA 7
Reporter: Guillaume Boucherie
If changes plugin is configure to used webUser/webPassword method
setupWebClient always add an AuthorizationPolicy.
But call of "/rest/api/2/serverInfo", to check if rest api available in Jira
failed if authorization header is set (maybe since Jira 7.0 ?)
See log
{noformat}
[INFO] Address: https://mediametrie.atlassian.net/rest/api/2/serverInfo
[INFO] Http-Method: GET
[INFO] Content-Type: */*
[INFO] Headers: {Accept=[application/json], Content-Type=[*/*],
Authorization=[Basic **]}
[INFO] --
[INFO] [DEBUG] Accept: application/json
[INFO] [DEBUG] Authorization: Basic amVua2luczpWbG1wSkEqNA==
[INFO] [DEBUG] Content-Type: */*
[INFO] [DEBUG] No Trust Decider for Conduit
'{https://mediametrie.atlassian.net}WebClient.http-conduit'. An afirmative
Trust Decision is assumed.
[INFO] [DEBUG] Response Code: 401 Conduit:
{https://mediametrie.atlassian.net}WebClient.http-conduit
[INFO] [DEBUG] Content length: -1
[INFO] [DEBUG] Header fields:
[INFO] null: [HTTP/1.1 401 Unauthorized]
[INFO] WWW-Authenticate: [OAuth
realm="https%3A%2F%2Fmediametrie.atlassian.net"]
[INFO] X-ASESSIONID: [1tm29ul]
[INFO] Set-Cookie: [studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, JSESSIONID=D8CDB54F8A1710254DC25A7897129DE1; Path=/;
Secure; HttpOnly]
[INFO] Connection: [keep-alive]
[INFO] Server: [nginx]
[INFO] X-Seraph-LoginReason: [AUTHENTICATED_FAILED, AUTHENTICATED_FAILED,
OUT]
[INFO] X-Content-Type-Options: [nosniff]
[INFO] Transfer-Encoding: [chunked]
[INFO] Date: [Mon, 26 Oct 2015 13:03:16 GMT]
[INFO] X-ASEN: [SEN-2238151]
[INFO] Content-Type: [text/html;charset=UTF-8]
[INFO] X-Seraph-PasswordResetRequired: [true, true]
[INFO] X-AREQUESTID: [843x31125x1]
[INFO]
[INFO] [DEBUG] Adding interceptor
org.apache.cxf.interceptor.LoggingInInterceptor@1f0fde7d to phase receive
[INFO] [DEBUG] Chain org.apache.cxf.phase.PhaseInterceptorChain@4ad7f079 was
created. Current flow:
[INFO] receive [LoggingInInterceptor]
[INFO]
[INFO] [DEBUG] Invoking handleMessage on interceptor
org.apache.cxf.interceptor.LoggingInInterceptor@1f0fde7d
[INFO] [INFO] Inbound Message
[INFO]
[INFO] ID: 1
[INFO] Response-Code: 401
[INFO] Encoding: UTF-8
[INFO] Content-Type: text/html;charset=UTF-8
[INFO] Headers: {connection=[keep-alive],
content-type=[text/html;charset=UTF-8], Date=[Mon, 26 Oct 2015 13:03:16 GMT],
Server=[nginx], Set-Cookie=[studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
Path=/; Secure; HttpOnly, JSESSIONID=D8CDB54F8A1710254DC25A7897129DE1; Path=/;
Secure; HttpOnly], transfer-encoding=[chunked], WWW-Authenticate=[OAuth
realm="https%3A%2F%2Fmediametrie.atlassian.net"], X-AREQUESTID=[843x31125x1],
X-ASEN=[SEN-2238151], X-ASESSIONID=[1tm29ul], X-Content-Type-Options=[nosniff],
X-Seraph-LoginReason=[AUTHENTICATED_FAILED, AUTHENTICATED_FAILED, OUT],
X-Seraph-PasswordResetRequired=[true, true]}
[INFO] Payload:
[INFO]
[INFO]
[INFO]
[INFO]
[INFO]
[INFO]
[INFO]
[INFO]
[INFO]
[INFO]
[INFO] Unauthorized (401)
[INFO]
[INFO]
[INFO]
[INFO]
[INFO] var contextPath = '';
[INFO]
[INFO]
window.WRM=window.WRM||{};window.WRM._unparsedData=window.WRM._unparsedData||{};
[INFO]
WRM._unparsedData["com.atlassian.jira.plugins.jira-admin-helper-plugin:permissions-provider.permissions-data"]="[{\"permissions\":[{\"name\":\"Administer
Projects\",\"key\":\"ADMINISTER_PROJECTS\"},{\"name\":\"Browse
Projects\",\"key\":\"BROWSE_PROJECTS\"},{\"name\":\"View Development
Tools\",\"key\":\"VIEW_DEV_TOOLS\"},{\"name\":\"View Read-Only
Workflow\",\"
[jira] [Closed] (MCHANGES-362) Check for rest api failed if webuser used
[
https://issues.apache.org/jira/browse/MCHANGES-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Boucherie closed MCHANGES-362.
Resolution: Not A Problem
Sorry my password was just blocked due to changes in password policy last month
ago ...
Sorry for the noise.
> Check for rest api failed if webuser used
> -
>
> Key: MCHANGES-362
> URL: https://issues.apache.org/jira/browse/MCHANGES-362
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.11
> Environment: JIRA 7
>Reporter: Guillaume Boucherie
>
> If changes plugin is configure to used webUser/webPassword method
> setupWebClient always add an AuthorizationPolicy.
> But call of "/rest/api/2/serverInfo", to check if rest api available in Jira
> failed if authorization header is set (maybe since Jira 7.0 ?)
> See log
> {noformat}
> [INFO] Address: https://mediametrie.atlassian.net/rest/api/2/serverInfo
> [INFO] Http-Method: GET
> [INFO] Content-Type: */*
> [INFO] Headers: {Accept=[application/json], Content-Type=[*/*],
> Authorization=[Basic **]}
> [INFO] --
> [INFO] [DEBUG] Accept: application/json
> [INFO] [DEBUG] Authorization: Basic amVua2luczpWbG1wSkEqNA==
> [INFO] [DEBUG] Content-Type: */*
> [INFO] [DEBUG] No Trust Decider for Conduit
> '{https://mediametrie.atlassian.net}WebClient.http-conduit'. An afirmative
> Trust Decision is assumed.
> [INFO] [DEBUG] Response Code: 401 Conduit:
> {https://mediametrie.atlassian.net}WebClient.http-conduit
> [INFO] [DEBUG] Content length: -1
> [INFO] [DEBUG] Header fields:
> [INFO] null: [HTTP/1.1 401 Unauthorized]
> [INFO] WWW-Authenticate: [OAuth
> realm="https%3A%2F%2Fmediametrie.atlassian.net"]
> [INFO] X-ASESSIONID: [1tm29ul]
> [INFO] Set-Cookie: [studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, JSESSIONID=D8CDB54F8A1710254DC25A7897129DE1;
> Path=/; Secure; HttpOnly]
> [INFO] Connection: [keep-alive]
> [INFO] Server: [nginx]
> [INFO] X-Seraph-LoginReason: [AUTHENTICATED_FAILED, AUTHENTICATED_FAILED,
> OUT]
> [INFO] X-Content-Type-Options: [nosniff]
> [INFO] Transfer-Encoding: [chunked]
> [INFO] Date: [Mon, 26 Oct 2015 13:03:16 GMT]
> [INFO] X-ASEN: [SEN-2238151]
> [INFO] Content-Type: [text/html;charset=UTF-8]
> [INFO] X-Seraph-PasswordResetRequired: [true, true]
> [INFO] X-AREQUESTID: [843x31125x1]
> [INFO]
> [INFO] [DEBUG] Adding interceptor
> org.apache.cxf.interceptor.LoggingInInterceptor@1f0fde7d to phase receive
> [INFO] [DEBUG] Chain org.apache.cxf.phase.PhaseInterceptorChain@4ad7f079 was
> created. Current flow:
> [INFO] receive [LoggingInInterceptor]
> [INFO]
> [INFO] [DEBUG] Invoking handleMessage on interceptor
> org.apache.cxf.interceptor.LoggingInInterceptor@1f0fde7d
> [INFO] [INFO] Inbound Message
> [INFO]
> [INFO] ID: 1
> [INFO] Response-Code: 401
> [INFO] Encoding: UTF-8
> [INFO] Content-Type: text/html;charset=UTF-8
> [INFO] Headers: {connection=[keep-alive],
> content-type=[text/html;charset=UTF-8], Date=[Mon, 26 Oct 2015 13:03:16 GMT],
> Server=[nginx], Set-Cookie=[studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, studio.crowd.tokenkey="";
> Domain=.mediametrie.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT;
> Path=/; Secure; HttpOnly, JSESSIONID=D8CDB54F8A1710254DC25A7897129DE1;
> Path=/; Secure; HttpOnly], transfer-encoding=[chunked],
> WWW-Authenticate=[OAuth realm="https%3A%2F%2Fmediametrie.atlassian.net"],
> X-AREQUESTID=[843x31125x1], X-ASEN=[SEN-2238151], X-ASESSIONID=[1tm29ul],
> X-Content-Type-Options=[nosniff], X-Seraph-LoginReason=[AUTHENTICATED_FAILED,
> AUTHENTICATED_FAILED, OUT], X-Seraph-PasswordResetRequired=[true, true]}
> [INFO] Payload:
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO] Unauthorized (401)
> [INFO]
> [INFO]
> [INFO]
> [INFO]
> [INFO] var
[jira] Updated: (ARCHETYPE-258) Support excluding files from to-be-created archetype
[ https://jira.codehaus.org/browse/ARCHETYPE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boucherie updated ARCHETYPE-258: -- Attachment: ARCHETYPE-258.patch I just add a path for this case. Its add a property archetypeExcludedPatterns to the mojo, this value will be used by FilesetArchetypeCreator in resolveFileNames in addition to default exclude patterns. > Support excluding files from to-be-created archetype > > > Key: ARCHETYPE-258 > URL: https://jira.codehaus.org/browse/ARCHETYPE-258 > Project: Maven Archetype > Issue Type: Wish > Components: Creator >Affects Versions: 2.0-alpha-4 >Reporter: Stevo Slavic > Attachments: ARCHETYPE-258.patch > > > Please support configuration option for archetype:create-from-project mojo to > exclude ((eclipse) IDE specific) files and directories (like .project, > .classpath, .settings, .svn) when creating an archetype. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (ARCHETYPE-258) Support excluding files from to-be-created archetype
[ https://jira.codehaus.org/browse/ARCHETYPE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280740#comment-280740 ] Guillaume Boucherie edited comment on ARCHETYPE-258 at 10/7/11 2:19 AM: I just add a patch for this case. Its add a property archetypeExcludedPatterns to the mojo, this value will be used by FilesetArchetypeCreator in resolveFileNames in addition to default exclude patterns. was (Author: clettebou): I just add a path for this case. Its add a property archetypeExcludedPatterns to the mojo, this value will be used by FilesetArchetypeCreator in resolveFileNames in addition to default exclude patterns. > Support excluding files from to-be-created archetype > > > Key: ARCHETYPE-258 > URL: https://jira.codehaus.org/browse/ARCHETYPE-258 > Project: Maven Archetype > Issue Type: Wish > Components: Creator >Affects Versions: 2.0-alpha-4 >Reporter: Stevo Slavic > Attachments: ARCHETYPE-258.patch > > > Please support configuration option for archetype:create-from-project mojo to > exclude ((eclipse) IDE specific) files and directories (like .project, > .classpath, .settings, .svn) when creating an archetype. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-334) RestJiraDownloader doesn't honor proxy settings
Guillaume Boucherie created MCHANGES-334: Summary: RestJiraDownloader doesn't honor proxy settings Key: MCHANGES-334 URL: https://jira.codehaus.org/browse/MCHANGES-334 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.10 Reporter: Guillaume Boucherie Priority: Critical Trying to generate an announcement mail with Jira I get a connection timeout exception. When I activate debug trace I see that no proxy is used. By debugging method setupWebClient (line 547) in RestJiraDownloader class I see that the field proxyHost is always null so the WebClient proxy will never be initialized properly. I think we must add a call to getProxyInfo in doExecute method of RestJiraDownloader before the call to setupWebClient -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-334) RestJiraDownloader doesn't honor proxy settings
[ https://jira.codehaus.org/browse/MCHANGES-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boucherie updated MCHANGES-334: - Attachment: MCHANGES-334.patch Attached MCHANGES-334.patch that call getProxyInfo(jiraUrl) before setupWebClient(jiraUrl). > RestJiraDownloader doesn't honor proxy settings > --- > > Key: MCHANGES-334 > URL: https://jira.codehaus.org/browse/MCHANGES-334 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.10 >Reporter: Guillaume Boucherie >Priority: Critical > Attachments: MCHANGES-334.patch > > > Trying to generate an announcement mail with Jira I get a connection timeout > exception. > When I activate debug trace I see that no proxy is used. > By debugging method setupWebClient (line 547) in RestJiraDownloader class I > see that the field proxyHost is always null so the WebClient proxy will never > be initialized properly. > I think we must add a call to getProxyInfo in doExecute method of > RestJiraDownloader before the call to setupWebClient -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-334) RestJiraDownloader doesn't honor proxy settings
[ https://jira.codehaus.org/browse/MCHANGES-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345859#comment-345859 ] Guillaume Boucherie edited comment on MCHANGES-334 at 5/6/14 10:47 AM: --- Attached [^MCHANGES-334.patch] that call getProxyInfo(jiraUrl) before setupWebClient(jiraUrl). was (Author: clettebou): Attached MCHANGES-334.patch that call getProxyInfo(jiraUrl) before setupWebClient(jiraUrl). > RestJiraDownloader doesn't honor proxy settings > --- > > Key: MCHANGES-334 > URL: https://jira.codehaus.org/browse/MCHANGES-334 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.10 >Reporter: Guillaume Boucherie >Priority: Critical > Attachments: MCHANGES-334.patch > > > Trying to generate an announcement mail with Jira I get a connection timeout > exception. > When I activate debug trace I see that no proxy is used. > By debugging method setupWebClient (line 547) in RestJiraDownloader class I > see that the field proxyHost is always null so the WebClient proxy will never > be initialized properly. > I think we must add a call to getProxyInfo in doExecute method of > RestJiraDownloader before the call to setupWebClient -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-340) Retrieve Jira user/password from settings.xml
Guillaume Boucherie created MCHANGES-340: Summary: Retrieve Jira user/password from settings.xml Key: MCHANGES-340 URL: https://jira.codehaus.org/browse/MCHANGES-340 Project: Maven Changes Plugin Issue Type: New Feature Components: jira Reporter: Guillaume Boucherie Add a mechanism to get jira credentials from settings.xml instead from pom only. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-345) archetype:create-from-project do not process and sections into EAR's pom.xml
[
https://jira.codehaus.org/browse/ARCHETYPE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Boucherie updated ARCHETYPE-345:
--
Attachment: ARCHETYPE-345.patch
I create a patch for this issue. Main modification are in class
FilesetArchetypeCreator that now parse maven-ear-plugin modules configuration
section (groupId, artifactId, bundleFileName, moduleId and contextRoot).
Patch is based on tag 2.2
Regards
> archetype:create-from-project do not process and
> sections into EAR's pom.xml
>
>
> Key: ARCHETYPE-345
> URL: https://jira.codehaus.org/browse/ARCHETYPE-345
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.0-alpha-5, 2.0
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_20
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 2003" version: "5.2" arch: "x86" Family: "windows"
>Reporter: amber
> Attachments: ARCHETYPE-345.patch
>
>
> During the "archetype:create-from-project" phase, the plugin ignore the
> jarModule and EjbModule maven's sections in the EAR pom.xml (multi modules):
> Into section, "com.mycompany.myApp" should be "${groupId}", and
> "myApp-x" should be "${rootArtifactId}-x"
> EAR pom.xml founded into
> target\generated-sources\archetype\src\main\resources\archetype-resources\__rootArtifactId__-ear
> :
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> ${groupId}
> ${rootArtifactId}
> ${version}
>
> 4.0.0
>
> ${artifactId}
> ear
> ${project.artifactId}-${project.version}
>
>
> ${groupId}
> ${rootArtifactId}-services
> ${version}
> ejb
>
>
> ${groupId}
> ${rootArtifactId}-model
> ${version}
> jar
>
>
> ${groupId}
> ${rootArtifactId}-webmodule
> ${version}
> war
>
>
>
>
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.4.2
>
> lib
>
>
> true
>
>
>
>
> ==> com.mycompany.myApp
> ==> myApp-model
>
>
> ==> com.mycompany.myApp
> ==> myApp-services
>
>
> ==> com.mycompany.myApp
> ==> myApp-webmodule
> ==> /myApp-webModule
> true
>
>
>
>
>
>
> [...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-162) skinnyWars with wars without manifest Class-Path attribute
[ https://jira.codehaus.org/browse/MEAR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317489#comment-317489 ] Guillaume Boucherie commented on MEAR-162: -- In fact I think that the MANIFEST.MF will never be update because the org.codehaus.plexus.archiver.jar.Manifest getters (getMainSection and getSection) return new instance of Section object, so changes made on this instance will never impact current Manifest instance. If it could help I create a patch (it include the one provided by Laszlo Varadi) that contains an update skinny war it test, that test the MANIFEST.MF generated classpath. > skinnyWars with wars without manifest Class-Path attribute > -- > > Key: MEAR-162 > URL: https://jira.codehaus.org/browse/MEAR-162 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Laszlo Varadi > Attachments: EarMojo.patch, MEAR-162.patch > > > The classpath attribute should be set after populating with values, otherwise > the classpath will be empty in the war manifest in case when the attribute is > a newly created attribute. See patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-162) skinnyWars with wars without manifest Class-Path attribute
[ https://jira.codehaus.org/browse/MEAR-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boucherie updated MEAR-162: - Attachment: MEAR-162.patch > skinnyWars with wars without manifest Class-Path attribute > -- > > Key: MEAR-162 > URL: https://jira.codehaus.org/browse/MEAR-162 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Laszlo Varadi > Attachments: EarMojo.patch, MEAR-162.patch > > > The classpath attribute should be set after populating with values, otherwise > the classpath will be empty in the war manifest in case when the attribute is > a newly created attribute. See patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-353) release:prepare failed after a refactoring
release:prepare failed after a refactoring -- Key: MRELEASE-353 URL: http://jira.codehaus.org/browse/MRELEASE-353 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-7 Environment: Windows XP Pro SP2, maven-2.0.9, svn-1.4.5, java-1.6.0_03 Reporter: Guillaume Boucherie The goal release:prepare failed if it is launched after a refactoring of a project. By refactoring I mean change a package name or delete a directory. So after doing this kind of refactoring if you try do to a release:prepare you got an error when the plugin try to create the tag in svn : [INFO] Tagging release with the label maven-header-plugin-1.1... [INFO] Executing: svn --non-interactive copy --file C:\DOCUME~1\GUILLA~1.IDE\LOCALS~1\Temp\maven-scm-896035269.commit . http://s-neptune/subversion2/sweetdev-forge/tags/maven-header-plugin-1.1 [INFO] Working directory: E:\projects\sweetdev-forge\trunk\maven-plugins\maven-header-plugin [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Directory 'E:\projects\sweetdev-forge\trunk\maven-plugins\maven-header-plugin\src\main\java\com\ideo\sweetdevria' is missing I must create a fresh checkout of my project for the release:prepare goal to work. -- 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
