[jira] Commented: (SUREFIRE-683) Xref link generation regression with Maven 3
[ http://jira.codehaus.org/browse/SUREFIRE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251789#action_251789 ] Marc Rohlfs commented on SUREFIRE-683: -- I wasn't sure for which project(s) I should create an issue. As I think that a probable fix would require changes in the Site Plugin 3 branch *and* in the affected report plugins, I decided to create issues for the report plugins and let the plugin developers decide if they'd also need to create an issue item for the Site Plugin (see [Maven User List: Xref link generation regression with Maven 3|http://maven.40175.n5.nabble.com/Xref-link-generation-regression-with-Maven-3-td3336017.html]). BTW: The Taglist Plugin und the Findbugs Plugin are also affected. > Xref link generation regression with Maven 3 > > > Key: SUREFIRE-683 > URL: http://jira.codehaus.org/browse/SUREFIRE-683 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.7.1 > Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) > Java version: 1.6.0_20 > Java home: /usr/lib/jvm/java-6-openjdk/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-27-generic" arch: "i386" Family: "unix" >Reporter: Marc Rohlfs >Priority: Minor > Attachments: SUREFIRE-683_sample.zip > > > When the site reports are created with Maven 3, the this plugin doesn't > generate the links to the Source Xref pages, when the JXR Plugin hasn't been > executed before. > The plugin looks for the xrefLocation directory and if it doesn't exist, it > checks if the JXR plugin is configured for the project (see > http://maven.apache.org/plugins/maven-surefire-report-plugin/xref/org/apache/maven/plugins/surefire/report/SurefireReportMojo.html#203). > To properly generate the Xref links when the report is created with Maven 3, > the plugin should also check the reportPlugins paramerter of the Site plugin > configuration. -- 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: (MECLIPSE-636) MECLIPSE-156 wasn't resolved
[
http://jira.codehaus.org/browse/MECLIPSE-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251800#action_251800
]
Anthony O. commented on MECLIPSE-636:
-
I've seen a similar bug report here :
https://issues.sonatype.org/browse/MNGECLIPSE-1782
I've used this workaround :
{noformat}
org.apache.maven.plugins
maven-eclipse-plugin
2.8
true
true
true
false
2.0
.settings/org.eclipse.core.resources.prefs
{noformat}
> MECLIPSE-156 wasn't resolved
>
>
> Key: MECLIPSE-636
> URL: http://jira.codehaus.org/browse/MECLIPSE-636
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Workspace settings
>Affects Versions: 2.7
>Reporter: Ramiro Pereira de Magalhães
>Assignee: fabrizio giustina
> Attachments: MECLIPSE-636-withTests.patch, patch-MECLIPSE-636.patch
>
>
> Task MECLIPSE-156 wasn't correctly implemented and the proposed feature
> (namely, that the plugin should support setting file encoding) does not work.
> I think that only one of the proposed patches there were implemented (on
> IdeUtils.java) while the other (on EclipseUtils.java) one wasn't.
--
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: (MRESOURCES-134) EspaceString doesn't work
[
http://jira.codehaus.org/browse/MRESOURCES-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251801#action_251801
]
Rémy Sanlaville commented on MRESOURCES-134:
@Dennis: The text was taken from the documentation
(http://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html).
Thanks @Olivier for the fixed.
You can try with the attached example maven-resources-plugin-EscapeString.zip
If I remove the resource plugin configuration, I have this result (even with
the last 2.5-SNAPSHOT version)
{code:title=target/classes/properties/test.properties|borderStyle=solid}
#%comment: @toto
question=@message@
mailbox =cont...@toto.com
#%comment
other.question=A validation message ?
{code}
> EspaceString doesn't work
> -
>
> Key: MRESOURCES-134
> URL: http://jira.codehaus.org/browse/MRESOURCES-134
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: escape string
>Affects Versions: 2.5
> Environment: maven 2.2.1
>Reporter: Rémy Sanlaville
>Assignee: Olivier Lamy
> Attachments: maven-resources-plugin-EscapeString.zip
>
>
> if I configure the maven-resource-plugin in order to escape a delimiter in a
> comment, the escapeString is not removed in the target.
> {code:title=src/main/resources/properties/test.properties|borderStyle=solid}
> #%comment to espace:§@toto
> question=@message@
> {code}
> {code:title=pom.xml|borderStyle=solid}
>
>org.apache.maven.plugins
>maven-resources-plugin
>2.5-SNAPSHOT
>
> §
>
>
> {code}
> {code:title=target/classes/properties/test.properties|borderStyle=solid}
> #%comment to espace:§@toto
> question=A nice message...
> {code}
--
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: (MPDF-43) Maven PMD plug-in does not have "excludemarker" property that is available in PMD itself.
Maven PMD plug-in does not have "excludemarker" property that is available in PMD itself. - Key: MPDF-43 URL: http://jira.codehaus.org/browse/MPDF-43 Project: Maven 2.x PDF Plugin Issue Type: Improvement Affects Versions: 1.1, 1.0, 1.2 Reporter: Svetlomira Manova Hi all, I am trying to change the string that is used to suppress warnings in PMD report(the default one is NOPMD). I found out that for doing this in PMD itself i have to use "excludemarker" input param with the custom string. At the moment i think there is not such property in Maven PMD plugin. Best regards, Svetlomira -- 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: (SUREFIRE-685) Cannot pass multiple comma-separated includes
Cannot pass multiple comma-separated includes
-
Key: SUREFIRE-685
URL: http://jira.codehaus.org/browse/SUREFIRE-685
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.7.1
Reporter: Guillaume Jeudy
Cannot pass multiple comma-separated includes
as in
**/pattern.java,**/another.java
This is problematic because I was troubleshooting a build and injecting
variable include values through ${} property and profiles and can no longer do
so. Please reinstate this functionality, thanks!
--
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: (DOXIA-419) totally no rich formatting in generated PDFs/RTFs
totally no rich formatting in generated PDFs/RTFs
-
Key: DOXIA-419
URL: http://jira.codehaus.org/browse/DOXIA-419
Project: Maven Doxia
Issue Type: Bug
Components: Book
Affects Versions: 1.1.3
Reporter: Lazy Coder
We've decided to use Maven Doxia back in 2008.
2,5 years have passed but generated PDFs/RTFs still look unacceptably ugly.
Please see attached project.
PDFs/RTFs built from content
{code:xml}
No formatting.
font size 1: this
font size 20: this
font size=small: small
small: this
font color red: this
strike: strike
code line XXX
{code}
have totally no formatting while xhtml looks fine.
Frankly speaking I just can't believe Doxia Books plugin is so lame \- could
there be a misconfiguration in my sample project?
At least is there a workaround to make source code formatting differ from main
text in PDF (e.g. have smaller size)? We need this badly.
--
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: (DOXIA-419) totally no rich formatting in generated PDFs/RTFs
[
http://jira.codehaus.org/browse/DOXIA-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lazy Coder updated DOXIA-419:
-
Attachment: ugly_pdf_in_doxia.zip
> totally no rich formatting in generated PDFs/RTFs
> -
>
> Key: DOXIA-419
> URL: http://jira.codehaus.org/browse/DOXIA-419
> Project: Maven Doxia
> Issue Type: Bug
> Components: Book
>Affects Versions: 1.1.3
>Reporter: Lazy Coder
> Attachments: ugly_pdf_in_doxia.zip
>
>
> We've decided to use Maven Doxia back in 2008.
> 2,5 years have passed but generated PDFs/RTFs still look unacceptably ugly.
> Please see attached project.
> PDFs/RTFs built from content
> {code:xml}
> No formatting.
> font size 1: this
> font size 20: this
> font size=small: small
> small: this
> font color red: this
> strike: strike
> code line XXX
> {code}
> have totally no formatting while xhtml looks fine.
> Frankly speaking I just can't believe Doxia Books plugin is so lame \- could
> there be a misconfiguration in my sample project?
> At least is there a workaround to make source code formatting differ from
> main text in PDF (e.g. have smaller size)? We need this badly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHANGES-207) Jira-Report: Allow specification of a version-prefix
[ http://jira.codehaus.org/browse/MCHANGES-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-207. Resolution: Fixed Fixed properly in [r1060048|http://svn.apache.org/viewvc?view=revision&revision=1060048]. New 2.4-SNAPSHOT deployed. Please test it. > Jira-Report: Allow specification of a version-prefix > > > Key: MCHANGES-207 > URL: http://jira.codehaus.org/browse/MCHANGES-207 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: jira >Reporter: Michael Wenig >Assignee: Dennis Lundberg > Fix For: 2.4 > > > Currently it is possible to auto-suggest the version in jira. Therefore the > version of the pom is used with '-SNAPSHOT' stripped. > If you have a product in jira with several components it is a often used > pattern to prefix the version (e.g. component1-2.0, component2-1.0 etc.) > Currently these versions are not auto-recognized. > It would be better if it would be possible to optionally define a prefix (in > this case 'component1-'). > This would allow to use this feature also in prefixed-version-numbers -- 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: (MRESOURCES-134) EspaceString doesn't work
[
http://jira.codehaus.org/browse/MRESOURCES-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MRESOURCES-134:
---
Attachment: MRESOURCES-134.zip
Rémy,
Here's a sample project that looks like the one you are describing. This is
working nicely for me. Can you please try it and see if it works for you?
> EspaceString doesn't work
> -
>
> Key: MRESOURCES-134
> URL: http://jira.codehaus.org/browse/MRESOURCES-134
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: escape string
>Affects Versions: 2.5
> Environment: maven 2.2.1
>Reporter: Rémy Sanlaville
>Assignee: Olivier Lamy
> Attachments: maven-resources-plugin-EscapeString.zip,
> MRESOURCES-134.zip
>
>
> if I configure the maven-resource-plugin in order to escape a delimiter in a
> comment, the escapeString is not removed in the target.
> {code:title=src/main/resources/properties/test.properties|borderStyle=solid}
> #%comment to espace:§@toto
> question=@message@
> {code}
> {code:title=pom.xml|borderStyle=solid}
>
>org.apache.maven.plugins
>maven-resources-plugin
>2.5-SNAPSHOT
>
> §
>
>
> {code}
> {code:title=target/classes/properties/test.properties|borderStyle=solid}
> #%comment to espace:§@toto
> question=A nice message...
> {code}
--
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: (SUREFIRE-685) Cannot pass multiple comma-separated includes
[
http://jira.codehaus.org/browse/SUREFIRE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251833#action_251833
]
Kristian Rosenvold commented on SUREFIRE-685:
-
Just out of curiosity, what was the last version of surefire that supported
this ?
> Cannot pass multiple comma-separated includes
> -
>
> Key: SUREFIRE-685
> URL: http://jira.codehaus.org/browse/SUREFIRE-685
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Guillaume Jeudy
>
> Cannot pass multiple comma-separated includes
> as in
>
> **/pattern.java,**/another.java
>
> This is problematic because I was troubleshooting a build and injecting
> variable include values through ${} property and profiles and can no longer
> do so. Please reinstate this functionality, thanks!
--
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: (SUREFIRE-685) Cannot pass multiple comma-separated includes
[
http://jira.codehaus.org/browse/SUREFIRE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251834#action_251834
]
Guillaume Jeudy commented on SUREFIRE-685:
--
Sorry this issue is for specifically the failsafe 2.7.1 plugin. The last
failsafe plugin version that supported this was 2.6.
I don't know about surefire plugin.
> Cannot pass multiple comma-separated includes
> -
>
> Key: SUREFIRE-685
> URL: http://jira.codehaus.org/browse/SUREFIRE-685
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Guillaume Jeudy
>
> Cannot pass multiple comma-separated includes
> as in
>
> **/pattern.java,**/another.java
>
> This is problematic because I was troubleshooting a build and injecting
> variable include values through ${} property and profiles and can no longer
> do so. Please reinstate this functionality, thanks!
--
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: (SUREFIRE-685) Cannot pass multiple comma-separated includes
[
http://jira.codehaus.org/browse/SUREFIRE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated SUREFIRE-685:
Fix Version/s: 2.7.2
Assignee: Kristian Rosenvold
> Cannot pass multiple comma-separated includes
> -
>
> Key: SUREFIRE-685
> URL: http://jira.codehaus.org/browse/SUREFIRE-685
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Guillaume Jeudy
>Assignee: Kristian Rosenvold
> Fix For: 2.7.2
>
>
> Cannot pass multiple comma-separated includes
> as in
>
> **/pattern.java,**/another.java
>
> This is problematic because I was troubleshooting a build and injecting
> variable include values through ${} property and profiles and can no longer
> do so. Please reinstate this functionality, thanks!
--
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: (SUREFIRE-686) maven reported "BUILD FAILURE" even if all tests passed
maven reported "BUILD FAILURE" even if all tests passed --- Key: SUREFIRE-686 URL: http://jira.codehaus.org/browse/SUREFIRE-686 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.7.1 Environment: windows 2003 zh_CN jdk 1.5.0_07 maven 2.2.1, 3.0.1, 3.0.2 Reporter: panxiaobo Attachments: build-output.txt I tried to build a project with maven, the project contains junit test. maven reported "BUILD FAILURE" even if all tests passed. maven output: = Results : Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. = one of the tests is using jacob 1.14.3 to instance a COM, and after deleting the test, maven build successfully. more detail output are attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-686) maven reported "BUILD FAILURE" even if all tests passed
[ http://jira.codehaus.org/browse/SUREFIRE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251871#action_251871 ] Kristian Rosenvold commented on SUREFIRE-686: - Which test framework and version are you using ? > maven reported "BUILD FAILURE" even if all tests passed > --- > > Key: SUREFIRE-686 > URL: http://jira.codehaus.org/browse/SUREFIRE-686 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.1 > Environment: windows 2003 zh_CN > jdk 1.5.0_07 > maven 2.2.1, 3.0.1, 3.0.2 >Reporter: panxiaobo > Attachments: build-output.txt > > > I tried to build a project with maven, the project contains junit test. > maven reported "BUILD FAILURE" even if all tests passed. > maven output: > = > Results : > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > = > one of the tests is using jacob 1.14.3 to instance a COM, and after deleting > the test, maven build successfully. > more detail output are attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-686) maven reported "BUILD FAILURE" even if all tests passed
[ http://jira.codehaus.org/browse/SUREFIRE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251872#action_251872 ] Kristian Rosenvold commented on SUREFIRE-686: - This somehow seems like a version of SUREFIRE-500, which has been fixed in the current 2.7.2-SNAPSHOT version (this would only be the case relevant if you're using junit4). Could you give that a spin to see if it helps ? > maven reported "BUILD FAILURE" even if all tests passed > --- > > Key: SUREFIRE-686 > URL: http://jira.codehaus.org/browse/SUREFIRE-686 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.1 > Environment: windows 2003 zh_CN > jdk 1.5.0_07 > maven 2.2.1, 3.0.1, 3.0.2 >Reporter: panxiaobo > Attachments: build-output.txt > > > I tried to build a project with maven, the project contains junit test. > maven reported "BUILD FAILURE" even if all tests passed. > maven output: > = > Results : > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > = > one of the tests is using jacob 1.14.3 to instance a COM, and after deleting > the test, maven build successfully. > more detail output are attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
