[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Børre Dalhaug updated MRELEASE-841:
---
Attachment: Maven version.jpg
As requested
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
> Attachments: Error.jpg, Maven version.jpg
>
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326515#comment-326515
]
Børre Dalhaug edited comment on MRELEASE-841 at 6/11/13 12:08 AM:
--
As you can see in the screenshot the quotes are messed up.
was (Author: borre):
As you can see the quotes are messed up.
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
> Attachments: Error.jpg, Maven version.jpg
>
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326516#comment-326516
]
Børre Dalhaug edited comment on MRELEASE-841 at 6/11/13 12:09 AM:
--
I have added the output from mvn -v as requested
was (Author: borre):
As requested
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
> Attachments: Error.jpg, Maven version.jpg
>
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Børre Dalhaug updated MRELEASE-841:
---
Attachment: Error.jpg
As you can see the quotes are messed up.
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
> Attachments: Error.jpg
>
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326514#comment-326514
]
Børre Dalhaug commented on MRELEASE-841:
Sorry - had to sleep a bit :-)
I'm using mercurial. I'll attach screenshots of the error message...
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-205) maven-compiler-plugin: incremental compilation broken
[
https://jira.codehaus.org/browse/MCOMPILER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326507#comment-326507
]
SebbASF commented on MCOMPILER-205:
---
I'd forgotten about annotations.
Ordinary Java source files may depend on each other, and therefore multiple
files may need to be compiled if one source file changes.
Is that true of package-info files, or are they independent?
If so, there is no need to recompile anything else if one is found to be out of
date, only the p-i file itself.
This would reduce the recompilation needed.
Ideally the package-info files would not be recompiled either if they won't
generate class files, but that may be much harder to detect.
Undesirable workrounds include: don't use p-i files; ensure every p-i file
contains a package annotation.
> maven-compiler-plugin: incremental compilation broken
> -
>
> Key: MCOMPILER-205
> URL: https://jira.codehaus.org/browse/MCOMPILER-205
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Lukas Fryc
> Attachments: hello.tgz, no-class-in-java-file.zip
>
>
> When we do {{clean}} -> {{compile}} -> {{compile}}, all Java sources are
> re-compiled for second compilation steps:
> {code}
> [framework]$ mvn clean
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> {code}
> The source code of the affected project:
> https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-205) maven-compiler-plugin: incremental compilation broken
[
https://jira.codehaus.org/browse/MCOMPILER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326505#comment-326505
]
SebbASF edited comment on MCOMPILER-205 at 6/10/13 7:38 PM:
I'm seeing same with Commons builds.
Looks like it might be due to the new way of defining Javadoc for packages:
useIncrementalCompilation enabled
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\whois\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\imap\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\finger\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\tftp\package-info.java
Since these -never- rarely generate .class files, they will -always- usually
cause the compile to be re-run
was (Author: sebbasf):
I'm seeing same with Commons builds.
Looks like it might be due to the new way of defining Javadoc for packages:
useIncrementalCompilation enabled
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\whois\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\imap\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\finger\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\tftp\package-info.java
Since these never generate .class files, they will always cause the compile to
be re-run
> maven-compiler-plugin: incremental compilation broken
> -
>
> Key: MCOMPILER-205
> URL: https://jira.codehaus.org/browse/MCOMPILER-205
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Lukas Fryc
> Attachments: hello.tgz, no-class-in-java-file.zip
>
>
> When we do {{clean}} -> {{compile}} -> {{compile}}, all Java sources are
> re-compiled for second compilation steps:
> {code}
> [framework]$ mvn clean
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> {code}
> The source code of the affected project:
> https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-205) maven-compiler-plugin: incremental compilation broken
[
https://jira.codehaus.org/browse/MCOMPILER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326506#comment-326506
]
Oliver Gierke commented on MCOMPILER-205:
-
Just to be precise, {{package-info.java}} can generate {{.class}} files, e.g.
if they contain package annotations. So these sources shouldn't just be plainly
neglected.
> maven-compiler-plugin: incremental compilation broken
> -
>
> Key: MCOMPILER-205
> URL: https://jira.codehaus.org/browse/MCOMPILER-205
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Lukas Fryc
> Attachments: hello.tgz, no-class-in-java-file.zip
>
>
> When we do {{clean}} -> {{compile}} -> {{compile}}, all Java sources are
> re-compiled for second compilation steps:
> {code}
> [framework]$ mvn clean
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> {code}
> The source code of the affected project:
> https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-205) maven-compiler-plugin: incremental compilation broken
[
https://jira.codehaus.org/browse/MCOMPILER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326505#comment-326505
]
SebbASF commented on MCOMPILER-205:
---
I'm seeing same with Commons builds.
Looks like it might be due to the new way of defining Javadoc for packages:
useIncrementalCompilation enabled
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\whois\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\imap\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\finger\package-info.java
Stale source detected:
D:\eclipseworkspaces\main\commons-net\src\main\java\org\apache\commons\net\tftp\package-info.java
Since these never generate .class files, they will always cause the compile to
be re-run
> maven-compiler-plugin: incremental compilation broken
> -
>
> Key: MCOMPILER-205
> URL: https://jira.codehaus.org/browse/MCOMPILER-205
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Lukas Fryc
> Attachments: hello.tgz, no-class-in-java-file.zip
>
>
> When we do {{clean}} -> {{compile}} -> {{compile}}, all Java sources are
> re-compiled for second compilation steps:
> {code}
> [framework]$ mvn clean
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> {code}
> The source code of the affected project:
> https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-841:
Component/s: (was: perform)
prepare
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326504#comment-326504
]
Robert Scholte commented on MRELEASE-841:
-
Which SCM are you using?
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:prepare fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-841:
Summary: On windows mvn release:prepare fails trying commit changed pom.xml
files. (was: On windows mvn release:perform fails trying commit changed
pom.xml files.)
> On windows mvn release:prepare fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-282) Allow customisation via a parent POM
SebbASF created MPIR-282:
Summary: Allow customisation via a parent POM
Key: MPIR-282
URL: https://jira.codehaus.org/browse/MPIR-282
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Reporter: SebbASF
Individual projects can easily customise the PIR report text by providing
replacement properties in a custom bundle at
${project.basedir}/src/site/custom/project-info-report.properties
It would be useful for projects which share a common parent pom (e.g. Apache
Commons) to be able to share a custom bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-281) Misleading SCM report title
SebbASF created MPIR-281: Summary: Misleading SCM report title Key: MPIR-281 URL: https://jira.codehaus.org/browse/MPIR-281 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: scm Affects Versions: 2.7 Reporter: SebbASF The entry for the SCM report in the Project information page says: >>> Source Repository This is a link to the online source repository that can be viewed via a web browser. <<< The Decsription entry is misleading: it's not a link, and it's not only about web browser access. It should say something like: This document lists ways to access to the online source repository -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:perform fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326503#comment-326503
]
Børre Dalhaug commented on MRELEASE-841:
My bad - I meant release:prepare...
I wrote the following in the command line and pressed enter:
mvn release:perform -DpushChanges=false
The operation fails when trying to commit the changes to the poms. This is
because the double quotes (") surrounding the commit message is not escaped. On
Mac (and Linux?) the commit message is in single quotes (') so that works.
> On windows mvn release:perform fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-280) Clarify that Web Access SCM link is not suitable for SCM checkout
SebbASF created MPIR-280: Summary: Clarify that Web Access SCM link is not suitable for SCM checkout Key: MPIR-280 URL: https://jira.codehaus.org/browse/MPIR-280 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: scm Affects Versions: 2.7 Reporter: SebbASF The details for the viewvc section say (for example): >>> Web Access The following is a link to the online source repository. http://svn.apache.org/viewvc/commons/proper/lang/trunk <<< This has been taken by some readers to imply that the URL is suitable for SVN client access, and there have been complaints on mailing lists when it does not work. It would be useful to clarify the text to reduce user frustration and unnecessary mailing list traffic. The text "The following is a link to the online source repository." applies equally to a proper SVN link. It does not indicate that URL is intended for Web Brower (HTTP) access only. The section header "Web Access" does not really help either, as "Web" is often used as a synonym for "Internet". I can see how readers who don't know about ViewVC could easily not notice that distinction. I suggest that the default text is changed as follows: report.scm.webaccess.title=Web Server (HTTP) Access report.scm.webaccess.url= The following is a link to a browsable version of the source repository. Please use the "Anonymous Access" or "Developer Access" URL if you want to check out the source using your SCM client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:perform fails trying commit changed pom.xml files.
[
https://jira.codehaus.org/browse/MRELEASE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326500#comment-326500
]
Robert Scholte commented on MRELEASE-841:
-
I'm a Windows 64bit user too and haven't faced this problem.
Also, the {{release:perform}} doesn't commit, only the {{release:prepare}} does.
You're saying {{commandline}} as environment (next time just add the result of
{{mvn -v}} ;) ) so it seems like you're tweeking the message, right?
So what did you exactly execute? It would be nice to have your usecase as
example to reproduce the issue.
> On windows mvn release:perform fails trying commit changed pom.xml files.
> -
>
> Key: MRELEASE-841
> URL: https://jira.codehaus.org/browse/MRELEASE-841
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.4.1
> Environment: Windows 64 bit - command line.
>Reporter: Børre Dalhaug
>Priority: Blocker
>
> The commit includes a commit message, but the double quotes (") is not
> escaped so the command fails. On Mac (and Linux?) the commit message is in
> single quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-841) On windows mvn release:perform fails trying commit changed pom.xml files.
Børre Dalhaug created MRELEASE-841:
--
Summary: On windows mvn release:perform fails trying commit
changed pom.xml files.
Key: MRELEASE-841
URL: https://jira.codehaus.org/browse/MRELEASE-841
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: perform
Affects Versions: 2.4.1
Environment: Windows 64 bit - command line.
Reporter: Børre Dalhaug
Priority: Blocker
The commit includes a commit message, but the double quotes (") is not escaped
so the command fails. On Mac (and Linux?) the commit message is in single
quotes (') so that works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1003) Does not run test ThreeTestFour.java which matches the include **/*Test*.java
[
https://jira.codehaus.org/browse/SUREFIRE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian closed SUREFIRE-1003.
Resolution: Fixed
Fix Version/s: 2.16
Fixed with commit 7a0783637542d1bb0b3c191755748b2d3764fd50.
Thanks for the report!
> Does not run test ThreeTestFour.java which matches the include **/*Test*.java
> -
>
> Key: SUREFIRE-1003
> URL: https://jira.codehaus.org/browse/SUREFIRE-1003
> Project: Maven Surefire
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.14.1
>Reporter: SebbASF
>Assignee: Andreas Gudian
> Fix For: 2.16
>
>
> The page
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html says
> that the default includes are
> {code}
>
> **/*Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> The first of the include REs matches ThreeTestFour.java which does not get
> run.
> It also matches the other two include lines which could therefore be removed
> - however the first include line is wrong, it should be:
> {code}
> **/Test*.java
> {code}
> so the list should be:
> {code}
>
> **/Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> [Note: the first include covers **/TestCase*.java]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1003) Does not run test ThreeTestFour.java which matches the include **/*Test*.java
[
https://jira.codehaus.org/browse/SUREFIRE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian reassigned SUREFIRE-1003:
Assignee: Andreas Gudian
> Does not run test ThreeTestFour.java which matches the include **/*Test*.java
> -
>
> Key: SUREFIRE-1003
> URL: https://jira.codehaus.org/browse/SUREFIRE-1003
> Project: Maven Surefire
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.14.1
>Reporter: SebbASF
>Assignee: Andreas Gudian
>
> The page
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html says
> that the default includes are
> {code}
>
> **/*Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> The first of the include REs matches ThreeTestFour.java which does not get
> run.
> It also matches the other two include lines which could therefore be removed
> - however the first include line is wrong, it should be:
> {code}
> **/Test*.java
> {code}
> so the list should be:
> {code}
>
> **/Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> [Note: the first include covers **/TestCase*.java]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1003) Does not run test ThreeTestFour.java which matches the include **/*Test*.java
[
https://jira.codehaus.org/browse/SUREFIRE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326497#comment-326497
]
Andreas Gudian commented on SUREFIRE-1003:
--
You're right, the documentation for that parameter is wrong.
Should be, as you write:
{code}
**/Test*.java
**/*Test.java
**/*TestCase.java
{code}
> Does not run test ThreeTestFour.java which matches the include **/*Test*.java
> -
>
> Key: SUREFIRE-1003
> URL: https://jira.codehaus.org/browse/SUREFIRE-1003
> Project: Maven Surefire
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.14.1
>Reporter: SebbASF
>
> The page
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html says
> that the default includes are
> {code}
>
> **/*Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> The first of the include REs matches ThreeTestFour.java which does not get
> run.
> It also matches the other two include lines which could therefore be removed
> - however the first include line is wrong, it should be:
> {code}
> **/Test*.java
> {code}
> so the list should be:
> {code}
>
> **/Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> [Note: the first include covers **/TestCase*.java]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1003) Does not run test ThreeTestFour.java which matches the include **/*Test*.java
[
https://jira.codehaus.org/browse/SUREFIRE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian updated SUREFIRE-1003:
-
Description:
The page http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html
says that the default includes are
{code}
**/*Test*.java
**/*Test.java
**/*TestCase.java
{code}
The first of the include REs matches ThreeTestFour.java which does not get run.
It also matches the other two include lines which could therefore be removed -
however the first include line is wrong, it should be:
{code}
**/Test*.java
{code}
so the list should be:
{code}
**/Test*.java
**/*Test.java
**/*TestCase.java
{code}
[Note: the first include covers **/TestCase*.java]
was:
The page http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html
says that the default includes are
{code}
**/*Test*.java
**/*Test.java
**/*TestCase.java
{code}
The first of the include REs matches ThreeTestFour.java which does not get run.
It also matches the other two include lines which could therefore be removed -
however the first include line is wrong, it should be:
{code}
**/Test*.java
{code}
so the list should be:
**/Test*.java
**/*Test.java
**/*TestCase.java
{code}
[Note: the first include covers **/TestCase*.java]
> Does not run test ThreeTestFour.java which matches the include **/*Test*.java
> -
>
> Key: SUREFIRE-1003
> URL: https://jira.codehaus.org/browse/SUREFIRE-1003
> Project: Maven Surefire
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.14.1
>Reporter: SebbASF
>
> The page
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html says
> that the default includes are
> {code}
>
> **/*Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> The first of the include REs matches ThreeTestFour.java which does not get
> run.
> It also matches the other two include lines which could therefore be removed
> - however the first include line is wrong, it should be:
> {code}
> **/Test*.java
> {code}
> so the list should be:
> {code}
>
> **/Test*.java
> **/*Test.java
> **/*TestCase.java
>
> {code}
> [Note: the first include covers **/TestCase*.java]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MENFORCER-49) Add a rule to verify encoding of source files
[ https://jira.codehaus.org/browse/MENFORCER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326495#comment-326495 ] Baptiste Mathus commented on MENFORCER-49: -- Hi Vincent, Not sure how you would do that. Would just like for example to check that xml prolog is in fact specifying some expected encoding? What would you expect for java source code? Cheers > Add a rule to verify encoding of source files > - > > Key: MENFORCER-49 > URL: https://jira.codehaus.org/browse/MENFORCER-49 > Project: Maven 2.x Enforcer Plugin > Issue Type: New Feature > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Vincent Siveton >Assignee: Brian Fox > > This new rule will verify that all sources (java/xml/apt/xodc...) respects a > given encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-829) junit | Support inheritance while running test cases belonging to a particular category/group
[ https://jira.codehaus.org/browse/SUREFIRE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326492#comment-326492 ] Kristian Rosenvold commented on SUREFIRE-829: - @Jesse; Yeah, you're probably right. This is just another version of SUREFIRE-833, or at least the same type of problem. > junit | Support inheritance while running test cases belonging to a > particular category/group > - > > Key: SUREFIRE-829 > URL: https://jira.codehaus.org/browse/SUREFIRE-829 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.12 >Reporter: Gayathri Muralidharan >Assignee: Andreas Gudian > Fix For: 2.15 > > Attachments: SUREFIRE-829-common-junit48-20130506.patch, > SUREFIRE-829-common-junit48-new.patch, SUREFIRE-829-common-junit48.patch > > > We have a parent class which is extended by all the unit test cases (multi > module maven based project) > It would be great if surefire plugin config looks for the category in parent > class as well. This will avoid redundant @Category(UnitTestCategory.class) > annotations, as we expect all unit test cases to extend the corresponding > base class and the base class will alone be annotated with > @Category(UnitTestCategory.class) > Please let me know if this can be achieved by any other config. > Thanks, > Gayathri -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1003) Does not run test ThreeTestFour.java which matches the include **/*Test*.java
SebbASF created SUREFIRE-1003:
-
Summary: Does not run test ThreeTestFour.java which matches the
include **/*Test*.java
Key: SUREFIRE-1003
URL: https://jira.codehaus.org/browse/SUREFIRE-1003
Project: Maven Surefire
Issue Type: Bug
Components: documentation
Affects Versions: 2.14.1
Reporter: SebbASF
The page http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html
says that the default includes are
{code}
**/*Test*.java
**/*Test.java
**/*TestCase.java
{code}
The first of the include REs matches ThreeTestFour.java which does not get run.
It also matches the other two include lines which could therefore be removed -
however the first include line is wrong, it should be:
{code}
**/Test*.java
{code}
so the list should be:
**/Test*.java
**/*Test.java
**/*TestCase.java
{code}
[Note: the first include covers **/TestCase*.java]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-829) junit | Support inheritance while running test cases belonging to a particular category/group
[
https://jira.codehaus.org/browse/SUREFIRE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326485#comment-326485
]
Jesse Glick commented on SUREFIRE-829:
--
Seems wrong to me. If the authors of {{Category}} had intended it to be
inherited, they would have marked it {{@Inherited}}. If they simply never
thought of this use case but agree that it should work, then a new JUnit
release should add the annotation. In neither case should Surefire be patched.
> junit | Support inheritance while running test cases belonging to a
> particular category/group
> -
>
> Key: SUREFIRE-829
> URL: https://jira.codehaus.org/browse/SUREFIRE-829
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
>Affects Versions: 2.12
>Reporter: Gayathri Muralidharan
>Assignee: Andreas Gudian
> Fix For: 2.15
>
> Attachments: SUREFIRE-829-common-junit48-20130506.patch,
> SUREFIRE-829-common-junit48-new.patch, SUREFIRE-829-common-junit48.patch
>
>
> We have a parent class which is extended by all the unit test cases (multi
> module maven based project)
> It would be great if surefire plugin config looks for the category in parent
> class as well. This will avoid redundant @Category(UnitTestCategory.class)
> annotations, as we expect all unit test cases to extend the corresponding
> base class and the base class will alone be annotated with
> @Category(UnitTestCategory.class)
> Please let me know if this can be achieved by any other config.
> Thanks,
> Gayathri
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
