[jira] (SCM-714) mvn release:prepare fails if the command line is too long on windows
[ https://jira.codehaus.org/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323287#comment-323287 ] Mark Struberg commented on SCM-714: --- Hi Felix! Please note that scm:add != git-add and scm:checkin != git-commit maven-scm is intended to work the same way on every SCM. Thus we 'mimic' svn and cvs like operations. In the maven-release-manager we already do some special things for GIT. We'd need to There is of course an option to move the 'splitting' of git-add to an own function internally and utilize this from the other operations which need it. mvn release:prepare fails if the command line is too long on windows Key: SCM-714 URL: https://jira.codehaus.org/browse/SCM-714 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.8.1 Reporter: Felix Simmendinger Priority: Blocker The issue from SCM-697 does not solve the issue as the gitprovider is not using the add command but the checkin command during a release. -- 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] (MSITE-682) Apostrophe's in Markdown are removed resulting in HTML full of spelling error
[ https://jira.codehaus.org/browse/MSITE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-682. --- Resolution: Fixed Assignee: Herve Boutemy Doxia fixed in DOXIA-480 m-site-p uses it in [r1436778|http://svn.apache.org/r1436778] IT added in [r1465212|http://svn.apache.org/r1465212] Apostrophe's in Markdown are removed resulting in HTML full of spelling error - Key: MSITE-682 URL: https://jira.codehaus.org/browse/MSITE-682 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.1 Reporter: Alex Collins Assignee: Herve Boutemy Fix For: 3.3 Repro: 1. Create Maven 3 project. 2. Add site 3.1 to plugins, add doxia-markdown-module:1.3 to plugin deps. 3. Create src/site/markdown/test.md containing a sentence with an apostrophe. 4. mvn site 5. Examine target/site/test.md. Expected: sentence would be reproduced with apos. Actual: sentence is missing apos. -- 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] (DOXIA-473) Quotes and double quotes are stripped from the HTML output.
[ https://jira.codehaus.org/browse/DOXIA-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed DOXIA-473. --- Resolution: Fixed Fix Version/s: 1.4 Assignee: Herve Boutemy fixed in DOXIA-489, checked by an end-to-end use in MSITE-682 's IT Quotes and double quotes are stripped from the HTML output. --- Key: DOXIA-473 URL: https://jira.codehaus.org/browse/DOXIA-473 Project: Maven Doxia Issue Type: Bug Components: Module - Markdown Affects Versions: 1.3 Reporter: Klaus Reimer Assignee: Herve Boutemy Priority: Minor Fix For: 1.4 Content of markdown file: Google's Closure Compiler Result in HTML: Googles Closure Compiler All quotes and double-quote characters are completely ignored for some reason. Other markdown processors support these characters correctly. -- 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] (MDEP-295) Add ability to strip classifier
[ https://jira.codehaus.org/browse/MDEP-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323293#comment-323293 ] Holger Mense commented on MDEP-295: --- This issue should be reopened. The commit by Olivier Lamy is for maven-site-plugin and has nothing do to with the in this issue requested feature. Add ability to strip classifier --- Key: MDEP-295 URL: https://jira.codehaus.org/browse/MDEP-295 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: copy-dependencies Reporter: Jason Smith Assignee: Olivier Lamy Fix For: 2.7 Attachments: 0002-stripClassifier-option-added-to-the-copy-dependency-.patch, episode3.patch, good.patch, stripClassifier.patch In addition to the ability to specify that the version be stripped from the artifact it would be helpful to be able to specify that the classifier be stripped also. -- 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] (MSHARED-280) reporting fails with Eclipse Aether
[ https://jira.codehaus.org/browse/MSHARED-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323295#comment-323295 ] Herve Boutemy commented on MSHARED-280: --- IT added in [r1465216|http://svn.apache.org/r1465216] reporting fails with Eclipse Aether --- Key: MSHARED-280 URL: https://jira.codehaus.org/browse/MSHARED-280 Project: Maven Shared Components Issue Type: Bug Components: maven-reporting-exec Affects Versions: maven-reporting-exec-1.0.2 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: maven-reporting-exec-1.1 cause of MSITE-683 [DefaultMavenReportExecutor line 128|http://maven.apache.org/shared/maven-reporting-exec/xref/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.html#128] is using Sonatype Aether ExclusionsDependencyFilter for MavenPluginManager.setupPluginRealm(...) API call at [line 267|http://maven.apache.org/shared/maven-reporting-exec/xref/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.html#267] which is affected by switching to Eclipse Aether We will need some tweaks in maven-reporting-exec to detect Eclipse Aether -- 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-981) Surefire hangs if forked test name ends with carriage return
[ https://jira.codehaus.org/browse/SUREFIRE-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-981: --- Assignee: Andreas Gudian Surefire hangs if forked test name ends with carriage return Key: SUREFIRE-981 URL: https://jira.codehaus.org/browse/SUREFIRE-981 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.14 Environment: linux, maven 3.0.5, jdk 1.7.0._17 Reporter: Christopher Mosher Assignee: Andreas Gudian Priority: Minor Attachments: mvn_hang.tar.gz Using Spock @Unroll, you can create a test whose name ends with a carriage return. After Surefire runs this test, it hangs. To reproduce, untar the attached mvn_hang.tar.gz, cd into mvn_hang directory, and run mvn test. -- 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-981) Surefire hangs if forked test name ends with carriage return
[ https://jira.codehaus.org/browse/SUREFIRE-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323298#comment-323298 ] Andreas Gudian commented on SUREFIRE-981: - Thanks for the report. I checked it and surefire crashes even without forking. The bug itself is in maven-shared-utils and is easily fixed. Surefire hangs if forked test name ends with carriage return Key: SUREFIRE-981 URL: https://jira.codehaus.org/browse/SUREFIRE-981 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.14 Environment: linux, maven 3.0.5, jdk 1.7.0._17 Reporter: Christopher Mosher Assignee: Andreas Gudian Priority: Minor Attachments: mvn_hang.tar.gz Using Spock @Unroll, you can create a test whose name ends with a carriage return. After Surefire runs this test, it hangs. To reproduce, untar the attached mvn_hang.tar.gz, cd into mvn_hang directory, and run mvn test. -- 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] (DOXIA-386) Snippet Macro: Reference file does not support UTF-8 file format to generate the page garbage
[
https://jira.codehaus.org/browse/DOXIA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated DOXIA-386:
-
Description:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
version2.1/version
configuration
localeszh_CN/locales
inputEncodingUTF-8/inputEncoding
outputEncodingUTF-8/outputEncoding
/configuration
/plugin
{code}
my sample apt file:
{noformat}
%{snippet|file=target/site/reference/html/sample.html|verbatim=false}
{noformat}
sample.html:
{code:xml}
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html
PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html
xmlns=http://www.w3.org/1999/xhtml;headtitle#20013;#25991;/title/headbody/body/html
{code}
{{org.apache.maven.doxia.macro.snippet.SnippetReader}}
readLines:
{code}
reader = new BufferedReader(new InputStreamReader(source.openStream()));
{code}
use {{InputStreamReader(InputStream in)}}
change to:
{code}
InputStreamReader(InputStream in, Charset cs)
{code}
was:
plugin
artifactIdmaven-site-plugin/artifactId
version2.1/version
configuration
localeszh_CN/locales
inputEncodingUTF-8/inputEncoding
outputEncodingUTF-8/outputEncoding
/configuration
/plugin
my sample apt file:
%{snippet|file=target/site/reference/html/sample.html|verbatim=false}
sample.html:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html
PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html
xmlns=http://www.w3.org/1999/xhtml;headtitle#20013;#25991;/title/headbody/body/html
org.apache.maven.doxia.macro.snippet.SnippetReader
readLines:
reader = new BufferedReader(new InputStreamReader(source.openStream()));
use InputStreamReader(InputStream in)
change to:
InputStreamReader(InputStream in, Charset cs)
Snippet Macro: Reference file does not support UTF-8 file format to generate
the page garbage
--
Key: DOXIA-386
URL: https://jira.codehaus.org/browse/DOXIA-386
Project: Maven Doxia
Issue Type: Bug
Components: Core
Affects Versions: 1.1.2
Environment: windows7 zh_CN
Reporter: pinghe
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
version2.1/version
configuration
localeszh_CN/locales
inputEncodingUTF-8/inputEncoding
outputEncodingUTF-8/outputEncoding
/configuration
/plugin
{code}
my sample apt file:
{noformat}
%{snippet|file=target/site/reference/html/sample.html|verbatim=false}
{noformat}
sample.html:
{code:xml}
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html
PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html
xmlns=http://www.w3.org/1999/xhtml;headtitle#20013;#25991;/title/headbody/body/html
{code}
{{org.apache.maven.doxia.macro.snippet.SnippetReader}}
readLines:
{code}
reader = new BufferedReader(new InputStreamReader(source.openStream()));
{code}
use {{InputStreamReader(InputStream in)}}
change to:
{code}
InputStreamReader(InputStream in, Charset cs)
{code}
--
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] (DOXIA-473) Quotes and double quotes are stripped from the HTML output.
[ https://jira.codehaus.org/browse/DOXIA-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323292#comment-323292 ] Herve Boutemy edited comment on DOXIA-473 at 4/6/13 5:28 AM: - fixed in DOXIA-480, checked by an end-to-end use in MSITE-682 's IT was (Author: hboutemy): fixed in DOXIA-489, checked by an end-to-end use in MSITE-682 's IT Quotes and double quotes are stripped from the HTML output. --- Key: DOXIA-473 URL: https://jira.codehaus.org/browse/DOXIA-473 Project: Maven Doxia Issue Type: Bug Components: Module - Markdown Affects Versions: 1.3 Reporter: Klaus Reimer Assignee: Herve Boutemy Priority: Minor Fix For: 1.4 Content of markdown file: Google's Closure Compiler Result in HTML: Googles Closure Compiler All quotes and double-quote characters are completely ignored for some reason. Other markdown processors support these characters correctly. -- 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] (MSHARED-282) StringIndexOutOfBoundsException in m-s-u XMLEncode if carriage-return is the last character
[
https://jira.codehaus.org/browse/MSHARED-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian updated MSHARED-282:
---
Fix Version/s: maven-shared-utils-0.4
StringIndexOutOfBoundsException in m-s-u XMLEncode if carriage-return is the
last character
---
Key: MSHARED-282
URL: https://jira.codehaus.org/browse/MSHARED-282
Project: Maven Shared Components
Issue Type: Bug
Components: maven-shared-utils
Affects Versions: maven-shared-utils-0.3
Reporter: Andreas Gudian
Assignee: Andreas Gudian
Fix For: maven-shared-utils-0.4
Reported with SUREFIRE-981
When adding an attribute that ends with '\r', we get the following exception:
{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 38
at java.lang.String.charAt(String.java:686)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextAsPCDATA(XMLEncode.java:166)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextForAttribute(XMLEncode.java:59)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:159)
{code}
--
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] (MSHARED-282) StringIndexOutOfBoundsException in m-s-u XMLEncode if carriage-return is the last character
[
https://jira.codehaus.org/browse/MSHARED-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian reassigned MSHARED-282:
--
Assignee: Andreas Gudian
StringIndexOutOfBoundsException in m-s-u XMLEncode if carriage-return is the
last character
---
Key: MSHARED-282
URL: https://jira.codehaus.org/browse/MSHARED-282
Project: Maven Shared Components
Issue Type: Bug
Components: maven-shared-utils
Affects Versions: maven-shared-utils-0.3
Reporter: Andreas Gudian
Assignee: Andreas Gudian
Reported with SUREFIRE-981
When adding an attribute that ends with '\r', we get the following exception:
{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 38
at java.lang.String.charAt(String.java:686)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextAsPCDATA(XMLEncode.java:166)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextForAttribute(XMLEncode.java:59)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:159)
{code}
--
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] (MSHARED-282) StringIndexOutOfBoundsException in m-s-u XMLEncode if carriage-return is the last character
Andreas Gudian created MSHARED-282:
--
Summary: StringIndexOutOfBoundsException in m-s-u XMLEncode if
carriage-return is the last character
Key: MSHARED-282
URL: https://jira.codehaus.org/browse/MSHARED-282
Project: Maven Shared Components
Issue Type: Bug
Components: maven-shared-utils
Affects Versions: maven-shared-utils-0.3
Reporter: Andreas Gudian
Reported with SUREFIRE-981
When adding an attribute that ends with '\r', we get the following exception:
{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 38
at java.lang.String.charAt(String.java:686)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextAsPCDATA(XMLEncode.java:166)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextForAttribute(XMLEncode.java:59)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:159)
{code}
--
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] (MSHARED-282) StringIndexOutOfBoundsException in m-s-u XMLEncode if carriage-return is the last character
[
https://jira.codehaus.org/browse/MSHARED-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian closed MSHARED-282.
--
Resolution: Fixed
fixed with r1465221
StringIndexOutOfBoundsException in m-s-u XMLEncode if carriage-return is the
last character
---
Key: MSHARED-282
URL: https://jira.codehaus.org/browse/MSHARED-282
Project: Maven Shared Components
Issue Type: Bug
Components: maven-shared-utils
Affects Versions: maven-shared-utils-0.3
Reporter: Andreas Gudian
Assignee: Andreas Gudian
Fix For: maven-shared-utils-0.4
Reported with SUREFIRE-981
When adding an attribute that ends with '\r', we get the following exception:
{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 38
at java.lang.String.charAt(String.java:686)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextAsPCDATA(XMLEncode.java:166)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.XMLEncode.xmlEncodeTextForAttribute(XMLEncode.java:59)
at
org.apache.maven.surefire.shade.org.apache.maven.shared.utils.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:159)
{code}
--
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-981) Surefire hangs if forked test name ends with carriage return
[ https://jira.codehaus.org/browse/SUREFIRE-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-981. --- Resolution: Fixed Fix Version/s: 2.15 Fixed with f00c32ec7df8ed58950fffd6a03bb1ab5924a840 Surefire hangs if forked test name ends with carriage return Key: SUREFIRE-981 URL: https://jira.codehaus.org/browse/SUREFIRE-981 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.14 Environment: linux, maven 3.0.5, jdk 1.7.0._17 Reporter: Christopher Mosher Assignee: Andreas Gudian Priority: Minor Fix For: 2.15 Attachments: mvn_hang.tar.gz Using Spock @Unroll, you can create a test whose name ends with a carriage return. After Surefire runs this test, it hangs. To reproduce, untar the attached mvn_hang.tar.gz, cd into mvn_hang directory, and run mvn test. -- 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] (MNG-5461) rename _maven.repositories tracking file to _remote.repositories
Herve Boutemy created MNG-5461: -- Summary: rename _maven.repositories tracking file to _remote.repositories Key: MNG-5461 URL: https://jira.codehaus.org/browse/MNG-5461 Project: Maven 2 3 Issue Type: Wish Components: Artifacts and Repositories Affects Versions: 3.0.5 Reporter: Herve Boutemy Priority: Minor information about an artifact's origin is stored in a _maven.repositories file (see [Resolution from Local Repository|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository]) renaming it to _remote.repositories will help users understand the role of this file -- 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-969) Log line on screen output
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323305#comment-323305 ] Nicolas Liochon commented on SUREFIRE-969: -- It seems there is a 2.14.1 in progress, it would be great if this could be integrated. I don't upload patch, but it's just a single line to remove. Thanks! Log line on screen output - Key: SUREFIRE-969 URL: https://jira.codehaus.org/browse/SUREFIRE-969 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.14 Reporter: Nicolas Liochon Priority: Trivial parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false This log line is more for debugging, it would be great if it would be removed. -- 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] (MNG-5461) rename _maven.repositories tracking file to _remote.repositories
[ https://jira.codehaus.org/browse/MNG-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5461. -- Resolution: Fixed Fix Version/s: 3.1.0-alpha-1 Assignee: Herve Boutemy job done through MNG-5354 since it is done in [Aethers's 399806 issue|https://bugs.eclipse.org/bugs/show_bug.cgi?id=399806] rename _maven.repositories tracking file to _remote.repositories Key: MNG-5461 URL: https://jira.codehaus.org/browse/MNG-5461 Project: Maven 2 3 Issue Type: Wish Components: Artifacts and Repositories Affects Versions: 3.0.5 Reporter: Herve Boutemy Assignee: Herve Boutemy Priority: Minor Fix For: 3.1.0-alpha-1 information about an artifact's origin is stored in a _maven.repositories file (see [Resolution from Local Repository|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository]) renaming it to _remote.repositories will help users understand the role of this file -- 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] (DOXIA-397) Cannot link to javadoc methods
[
https://jira.codehaus.org/browse/DOXIA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed DOXIA-397.
Resolution: Fixed
Fix Version/s: 1.4
Assignee: Robert Scholte
Fixed in [r1465234|http://svn.apache.org/r1465234]
A link with a single '#' will be translated to a Doxia-ID.
A link with '##' (which would normally be illegal) will copy the anchor as is.
This means that the developer is responsible for the correct URL encoding!
Cannot link to javadoc methods
--
Key: DOXIA-397
URL: https://jira.codehaus.org/browse/DOXIA-397
Project: Maven Doxia
Issue Type: Bug
Components: Core, Module - Apt, Module - Xdoc
Affects Versions: 1.1.3
Reporter: Lukas Theussl
Assignee: Robert Scholte
Fix For: 1.4
Attachments: apt-link-fix.diff
Using a link to a javadoc method like
{noformat}
{{{../apidocs/groovyx/net/http/ParserRegistry.html#parseText(org.apache.http.HttpResponse)}ParserRegistry}}
{noformat}
the apt parser removes the brackets of the anchor. The same thing happens
with xdocs and probably other formats. Note that non-ascii characters are not
legal in anchor names, but they should be replaced by their hex values, see
http://www.w3.org/TR/html401/appendix/notes.html#non-ascii-chars.
--
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] (MNG-5185) Improve missing dependency error message when _maven.repositories contains other repository ids than requested
[
https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5185:
---
Description:
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from remote
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo retricted
to some repository ids, but actual POM has no matching repository id declared),
Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository, and they just get frustrated and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from the
undeclared repository xxx, either configure this in your pom with {insert
sample XML block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
was:
Based on a discussion on the users list [1], Maven 3 has changed how it
resolves artifacts from remote repositories. Unfortunately, when conflicts
arise ( GAV is cached in local repo, but POM has no matching repository id
declared ), Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository, and they just get frustrated and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from the
undeclared repository xxx, either configure this in your pom with {insert
sample XML block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
Improve missing dependency error message when _maven.repositories contains
other repository ids than requested
Key: MNG-5185
URL: https://jira.codehaus.org/browse/MNG-5185
Project: Maven 2 3
Issue Type: Improvement
Affects Versions: 3.0.2, 3.0.3, 3.0.4
Reporter: Mark Derricutt
Assignee: Olivier Lamy
Fix For: 3.1.x
Attachments:
0001-MNG-5185-Warn-about-artifacts-present-but-not-availa.patch
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from remote
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo
retricted to some repository ids, but actual POM has no matching repository
id declared), Maven just tells the user that the artifact could not be
resolved.
This leads to confusion from users who find the .jar files in their local
repository, and they just get frustrated and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from the
undeclared repository xxx, either configure this in your pom with {insert
sample XML block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their
hair :)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
--
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-969) Log line on screen output
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323309#comment-323309 ] Andreas Gudian commented on SUREFIRE-969: - I'd like to keep the information, but move it to some actual debug logging. That requires some API change and is therefor not that suitable for a bug fix release. Is this issue a deal-breaker for some use case you have, or is it just annoying? :) Log line on screen output - Key: SUREFIRE-969 URL: https://jira.codehaus.org/browse/SUREFIRE-969 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.14 Reporter: Nicolas Liochon Priority: Trivial parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false This log line is more for debugging, it would be great if it would be removed. -- 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] (MNG-5185) Improve missing dependency error message when _maven.repositories contains other repository ids than requested
[
https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5185:
---
Description:
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from remote
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository id
declared), Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with {insert sample XML
block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
was:
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from remote
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo retricted
to some repository ids, but actual POM has no matching repository id declared),
Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository, and they just get frustrated and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from the
undeclared repository xxx, either configure this in your pom with {insert
sample XML block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
Improve missing dependency error message when _maven.repositories contains
other repository ids than requested
Key: MNG-5185
URL: https://jira.codehaus.org/browse/MNG-5185
Project: Maven 2 3
Issue Type: Improvement
Affects Versions: 3.0.2, 3.0.3, 3.0.4
Reporter: Mark Derricutt
Assignee: Olivier Lamy
Fix For: 3.1.x
Attachments:
0001-MNG-5185-Warn-about-artifacts-present-but-not-availa.patch
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from remote
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository
id declared), Maven just tells the user that the artifact could not be
resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with {insert sample XML
block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their
hair :)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
--
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] (MNG-5185) Improve missing dependency error message when _maven.repositories contains other repository ids than requested
[
https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5185:
---
Description:
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from local
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository id
declared), Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The (GAV) artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with (insert sample XML
block in error message), or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
was:
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from local
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository id
declared), Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with {insert sample XML
block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
Improve missing dependency error message when _maven.repositories contains
other repository ids than requested
Key: MNG-5185
URL: https://jira.codehaus.org/browse/MNG-5185
Project: Maven 2 3
Issue Type: Improvement
Affects Versions: 3.0.2, 3.0.3, 3.0.4
Reporter: Mark Derricutt
Assignee: Olivier Lamy
Fix For: 3.1.x
Attachments:
0001-MNG-5185-Warn-about-artifacts-present-but-not-availa.patch
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from local
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository
id declared), Maven just tells the user that the artifact could not be
resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The (GAV) artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with (insert sample XML
block in error message), or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their
hair :)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
--
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] (MNG-5185) Improve missing dependency error message when _maven.repositories contains other repository ids than requested
[
https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5185:
---
Description:
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from local
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository id
declared), Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with {insert sample XML
block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
was:
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from remote
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository id
declared), Maven just tells the user that the artifact could not be resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with {insert sample XML
block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their hair
:)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
Improve missing dependency error message when _maven.repositories contains
other repository ids than requested
Key: MNG-5185
URL: https://jira.codehaus.org/browse/MNG-5185
Project: Maven 2 3
Issue Type: Improvement
Affects Versions: 3.0.2, 3.0.3, 3.0.4
Reporter: Mark Derricutt
Assignee: Olivier Lamy
Fix For: 3.1.x
Attachments:
0001-MNG-5185-Warn-about-artifacts-present-but-not-availa.patch
Based on a discussion on the users list [1], [Maven 3 has changed how it
resolves artifacts from local
repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository].
Unfortunately, when conflicts arise (GAV is cached in local repo, but
restricted to some repository ids, and actual POM has no matching repository
id declared), Maven just tells the user that the artifact could not be
resolved.
This leads to confusion from users who find the .jar files in their local
repository without knowing this restriction feature: they just get frustrated
and complain that maven sucks.
It would be good if Maven was updated with some improved error messages along
the lines of:
The {GAV} artifact was found in your local repository, but came from remote
repository xxx: either configure this in your pom with {insert sample XML
block in error message}, or in your yyy mirror.
The mirror section of the error message should be included -if- the current
~/.m2/settings.xml declares a mirror. By improving the messages here we can
help the users move on to building software, rather than pulling out their
hair :)
[1]
http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html
--
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] (MSHARED-271) Multiple reportSets don't work
[
https://jira.codehaus.org/browse/MSHARED-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSHARED-271:
--
Description:
Having several report sets only the last one is created.
Example: Create java doc report twice, with different parameters. First time
with deprecated api list, second time without.
Expected behaviour: The two directories are created with the different javadocs.
However, currently onle one directory is created.
{code:xml}
...
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.9/version
reportSets
reportSet
idwithout-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-without-deprecations/destDir
nodeprecatedlisttrue/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
reportSet
idwith-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-with-deprecations/destDir
nodeprecatedlistfalse/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin
/plugins
/reporting{code}
was:
Having several report sets only the last one is created.
Example: Create java doc report twice, with different parameters. First time
with deprecated api list, second time without.
Expected behaviour: The two directories are created with the different javadocs.
However, currently onle one directory is created.
{code:xml}
...
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.9/version
reportSets
reportSet
idwithout-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-without-deprecations/destDir
nodeprecatedlisttrue/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
reportSet
idwith-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-with-deprecations/destDir
nodeprecatedlistfalse/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin
/plugins
/reporting{code}
Multiple reportSets don't work
--
Key: MSHARED-271
URL: https://jira.codehaus.org/browse/MSHARED-271
Project: Maven Shared Components
Issue Type: Bug
Components: maven-reporting-exec
Affects Versions: maven-reporting-exec-1.0.2
Environment: maven 3.0.4
maven-site-plugin 3.2
Reporter: Max Schaefer
Assignee: Olivier Lamy
Priority: Critical
Attachments: test.zip
Having several report sets only the last one is created.
Example: Create java doc report twice, with different parameters. First time
with deprecated api list, second time without.
Expected behaviour: The two directories are created with the different
javadocs.
However, currently onle one directory is created.
{code:xml}
...
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.9/version
reportSets
reportSet
idwithout-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-without-deprecations/destDir
nodeprecatedlisttrue/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
reportSet
idwith-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-with-deprecations/destDir
nodeprecatedlistfalse/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin
/plugins
/reporting{code}
--
This message is automatically generated by JIRA.
If you think it
[jira] (SUREFIRE-969) Log line on screen output
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323311#comment-323311 ] Nicolas Liochon commented on SUREFIRE-969: -- It's just annoying :-). But it would be annoying enough to justify another surefire version upgrade on our side, and upgrading surefire requires some testing work I would prefer to avoid (obviously). Log line on screen output - Key: SUREFIRE-969 URL: https://jira.codehaus.org/browse/SUREFIRE-969 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.14 Reporter: Nicolas Liochon Priority: Trivial parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false This log line is more for debugging, it would be great if it would be removed. -- 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-969) Log line on screen output
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323312#comment-323312 ] Kristian Rosenvold commented on SUREFIRE-969: - A lot of people running parallel tests (myself included!) have a need to see clearly which threading config is in use. The line is not going away ;) We might move it into the otherwise superfluous - TESTS bla bla bla - Log line on screen output - Key: SUREFIRE-969 URL: https://jira.codehaus.org/browse/SUREFIRE-969 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.14 Reporter: Nicolas Liochon Priority: Trivial parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false This log line is more for debugging, it would be great if it would be removed. -- 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] (MSHARED-271) Multiple reportSets don't work
[
https://jira.codehaus.org/browse/MSHARED-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSHARED-271.
-
Resolution: Fixed
Fix Version/s: maven-reporting-exec-1.1
Assignee: Herve Boutemy (was: Olivier Lamy)
fixed in [r1465279|http://svn.apache.org/r1465279]
Multiple reportSets don't work
--
Key: MSHARED-271
URL: https://jira.codehaus.org/browse/MSHARED-271
Project: Maven Shared Components
Issue Type: Bug
Components: maven-reporting-exec
Affects Versions: maven-reporting-exec-1.0.2
Environment: maven 3.0.4
maven-site-plugin 3.2
Reporter: Max Schaefer
Assignee: Herve Boutemy
Priority: Critical
Fix For: maven-reporting-exec-1.1
Attachments: test.zip
Having several report sets only the last one is created.
Example: Create java doc report twice, with different parameters. First time
with deprecated api list, second time without.
Expected behaviour: The two directories are created with the different
javadocs.
However, currently onle one directory is created.
{code:xml}
...
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.9/version
reportSets
reportSet
idwithout-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-without-deprecations/destDir
nodeprecatedlisttrue/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
reportSet
idwith-deprecations/id
configuration
reportOutputDirectory${project.reporting.outputDirectory}/myoutput/reportOutputDirectory
destDirmyapidocs-with-deprecations/destDir
nodeprecatedlistfalse/nodeprecatedlist
/configuration
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin
/plugins
/reporting{code}
--
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] (MJAVADOC-335) In Maven 3 it is impossible to generate several JavaDoc reports at once
[
https://jira.codehaus.org/browse/MJAVADOC-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MJAVADOC-335.
--
Resolution: Fixed
Assignee: Herve Boutemy
fixed by MSHARED-271, which will be included in m-site-p 3.3
In Maven 3 it is impossible to generate several JavaDoc reports at once
---
Key: MJAVADOC-335
URL: https://jira.codehaus.org/browse/MJAVADOC-335
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.8
Environment: Maven 3.0.3
Reporter: Anton Nikitin
Assignee: Herve Boutemy
When I try to generate several JavaDoc reports using mvn site(see pom.xml
fragment below), only last one is actually created.
It works perfectly in Maven 2.2.1 and looks broken in Maven 3.0.3. I tried to
change pom.xml to Maven 3 style (use Maven Site Plugin reportPlugins
section instead of reporting) but it didn't help.
Workaround: use Maven 2.2.1 for site generation.
{code:xml}reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.8/version
reportSets
reportSet
idreport-1/id
configuration
destDirdocs1/destDir
...
/configuration
reports
reportjavadoc/report
/reports
/reportSet
reportSet
idreport-2/id
configuration
destDirdocs2/destDir
...
/configuration
reports
reportjavadoc/report
/reports
/reportSet
/reportSets
/plugin
/plugins
/reporting
{code}
--
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] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323322#comment-323322 ] Andrei Pozolotin commented on MNG-3092: --- @Kunalkumar re: your changed maven code * can you please share where is it? * can we collaborate on releasing it? * can it be incorporated in a form of extension (so there is no need for maven 3 re-install)? thank you. Version ranges with non-snapshot bounds can contain snapshot versions - Key: MNG-3092 URL: https://jira.codehaus.org/browse/MNG-3092 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Reporter: Mark Hobson Assignee: Jason van Zyl Fix For: 3.1.1 Attachments: MNG-3092.patch, MNG-3092.patch Contrary to the 2.0 design docs: Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary. -- from http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification The following is equates to true: VersionRange.createFromVersionSpec( [1.0,1.1] ).containsVersion( new DefaultArtifactVersion( 1.1-SNAPSHOT ) ) The attached patch only allows snapshot versions to be contained in a range if they are equal to one of the boundaries. Note that this is a strict equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT. -- 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] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323323#comment-323323 ] Andrei Pozolotin commented on MNG-3092: --- @Jason 1) do you think maven should follow OSGI semantic version model more closely? http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf that could be a base ground for maven ranges rules. 2) do you think version range resolver could be made into an extension which could be replaced via user plugin? thank you. Version ranges with non-snapshot bounds can contain snapshot versions - Key: MNG-3092 URL: https://jira.codehaus.org/browse/MNG-3092 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Reporter: Mark Hobson Assignee: Jason van Zyl Fix For: 3.1.1 Attachments: MNG-3092.patch, MNG-3092.patch Contrary to the 2.0 design docs: Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary. -- from http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification The following is equates to true: VersionRange.createFromVersionSpec( [1.0,1.1] ).containsVersion( new DefaultArtifactVersion( 1.1-SNAPSHOT ) ) The attached patch only allows snapshot versions to be contained in a range if they are equal to one of the boundaries. Note that this is a strict equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT. -- 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] (DOXIA-416) Confluence monospaced text has backwards braces
[
https://jira.codehaus.org/browse/DOXIA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed DOXIA-416.
Resolution: Fixed
Fix Version/s: 1.4
Assignee: Robert Scholte
Fixed in [r1465300|http://svn.apache.org/r1465300]
Confluence monospaced text has backwards braces
---
Key: DOXIA-416
URL: https://jira.codehaus.org/browse/DOXIA-416
Project: Maven Doxia
Issue Type: Bug
Components: Module - Confluence
Affects Versions: 1.1
Reporter: Grant Gardner
Assignee: Robert Scholte
Fix For: 1.4
Attachments: conftest.apt
Using the converter
java -jar C:\dev\bin\doxia-converter-1.1-jar-with-dependencies.jar doxia -in
conftest.apt -out conftest.out -to confluence
Input: (conftest.apt)
Heading
monospaced text
Output: (conftest.out)
h1. Heading
}}monospaced text{{
--
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] (DOXIA-170) Confluence module should do something with non-doxia formatting
[ https://jira.codehaus.org/browse/DOXIA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323327#comment-323327 ] Robert Scholte commented on DOXIA-170: -- Writing to confluence markup is fixed in [r1465304|http://svn.apache.org/r1465304] Confluence module should do something with non-doxia formatting --- Key: DOXIA-170 URL: https://jira.codehaus.org/browse/DOXIA-170 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-8 Reporter: Dave Syer Assignee: Lukas Theussl These wiki formats are not recognised ??citation?? -strikethrough- +underlined+ ^superscript^ ~subscript~ -- 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-431) Configuration of policy for calculating next (release) version
[ https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323329#comment-323329 ] Andrei Pozolotin commented on MRELEASE-431: --- maven should implement semantic versioning in the core http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf some plugins which are doing this: https://github.com/apache/aries/tree/trunk/versioning https://github.com/jeluard/semantic-versioning Configuration of policy for calculating next (release) version -- Key: MRELEASE-431 URL: https://jira.codehaus.org/browse/MRELEASE-431 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: prepare Affects Versions: 2.0-beta-8 Reporter: Carsten Ziegeler Currently, when preparing the release, the version to release is always the next version which usually is the current version without the snapshot extension. There are quiet a lot projects (Apache Felix, Sling and others) following an even release numbering policy. So while the current development version is odd (like 1.2.3-SNAPSHOT), the next released version will be 1.2.4. It would be nice if this could be made configuration through some configuration property like versionPolicynext-even/versionPolicy (with possible values being: next (default, as-is), next-even, next-odd I briefly scanned through the code and it seems that adding support for this requires changes in both, the release-manager and the release-plugin. If this feature gets accepted and if someone could give me some minor hints how/where to add this I could come up with a patch. -- 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
