[jira] (MASSEMBLY-618) use maven-plugin-tools' java 5 annotations
[
https://jira.codehaus.org/browse/MASSEMBLY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302040#comment-302040
]
Tony Chemit commented on MASSEMBLY-618:
---
Tests are ok using a jdk 1.6.0_32 but not with a 1.7.0_04 with this message :
{code}
Tests in error:
testGetOutputDir_ShouldResolveGroupIdInOutDir_UseArtifactInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71's mock: null
testGetOutputDir_ShouldResolveArtifactIdInOutDir_UseArtifactInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_2's mock:
null
testGetOutputDir_ShouldResolveVersionInOutDir_UseArtifactInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_3's mock:
null
testGetOutputDir_ShouldResolveBuildFinalNameInOutDir_UseArtifactInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_4's mock:
null
testGetOutputDir_ShouldResolveGroupIdInOutDir_UseModuleInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_5's mock:
null
testGetOutputDir_ShouldResolveArtifactIdInOutDir_UseModuleInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_6's mock:
null
testGetOutputDir_ShouldResolveVersionInOutDir_UseModuleInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_7's mock:
null
testGetOutputDir_ShouldResolveBuildFinalNameInOutDir_UseModuleInfo(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_8's mock:
null
testGetOutputDir_ShouldResolveGroupIdInOutDir_UseExplicitMainProject(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_9's mock:
null
testGetOutputDir_ShouldResolveArtifactIdInOutDir_UseExplicitMainProject(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_10's mock:
null
testGetOutputDir_ShouldResolveVersionInOutDir_UseExplicitMainProject(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_11's mock:
null
testGetOutputDir_ShouldResolveBuildFinalNameInOutDir_UseExplicitMainProject(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_12's mock:
null
testGetOutputDir_ShouldResolveGroupIdInOutDir_UseExplicitMainProject_projectRef(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_13's mock:
null
testGetOutputDir_ShouldResolveArtifactIdInOutDir_UseExplicitMainProject_projectRef(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_14's mock:
null
testGetOutputDir_ShouldResolveVersionInOutDir_UseExplicitMainProject_projectRef(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_15's mock:
null
testGetOutputDir_ShouldResolveBuildFinalNameInOutDir_UseExplicitMainProject_projectRef(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_16's mock:
null
testGetOutputDir_ShouldNotAlterOutDirWhenIncludeBaseFalseAndNoExpressions(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_17's mock:
null
testGetOutputDir_ShouldNotAlterOutDirWhenIncludeBaseFalseAndNoExpressions_CheckWithBackslash(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
org.apache.maven.execution.ReactorManager$$EnhancerByCGLIB$$3243d71_18's mock:
null
testGetOutputDir_ShouldAppendSlashToOutDirWhenMissingAndIncludeBaseFalseAndNoExpressions(org.apache.maven.plugin.assembly.utils.AssemblyFormatUtilsTest):
Failed to instantiate
[jira] (MPMD-152) Update to PMD 5.0.0
[ https://jira.codehaus.org/browse/MPMD-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] D. closed MPMD-152. --- Resolution: Duplicate Fix Version/s: 2.8 > Update to PMD 5.0.0 > --- > > Key: MPMD-152 > URL: https://jira.codehaus.org/browse/MPMD-152 > Project: Maven 2.x PMD Plugin > Issue Type: Wish > Components: PMD >Affects Versions: 2.7.1 >Reporter: D. > Fix For: 2.8 > > > Please update the Maven 2.x PMD Plugin to the latest PMD version (version > 5.0.0) which was released 2012-05-01 and supports additional languages. > Warning from the upstream website "Note: PMD 5 is not backwards compatible > with PMD 4.x." as such "Maven coordinates have been changed: > net.sourceforge.pmd:pmd". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-618) use maven-plugin-tools' java 5 annotations
[
https://jira.codehaus.org/browse/MASSEMBLY-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MASSEMBLY-618:
--
Attachment: MASSEMBLY-618.diff
Here is a patch for this task.
Note that I changed
UnpackMojo#workDirectory
{code}
@parameter expression="${project.build.directory}/assembly/work"
@required
{code}
to
{code}
@Parameter( defaultValue = "${project.build.directory}/assembly/work", required
= true )
{code}
there is still some tests to fix, I will have a look tomorow if possible.
> use maven-plugin-tools' java 5 annotations
> --
>
> Key: MASSEMBLY-618
> URL: https://jira.codehaus.org/browse/MASSEMBLY-618
> Project: Maven 2.x Assembly Plugin
> Issue Type: Task
>Affects Versions: 2.3
>Reporter: Tony Chemit
> Attachments: MASSEMBLY-618.diff
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-152) Update to PMD 5.0.0
D. created MPMD-152: --- Summary: Update to PMD 5.0.0 Key: MPMD-152 URL: https://jira.codehaus.org/browse/MPMD-152 Project: Maven 2.x PMD Plugin Issue Type: Wish Components: PMD Affects Versions: 2.7.1 Reporter: D. Please update the Maven 2.x PMD Plugin to the latest PMD version (version 5.0.0) which was released 2012-05-01 and supports additional languages. Warning from the upstream website "Note: PMD 5 is not backwards compatible with PMD 4.x." as such "Maven coordinates have been changed: net.sourceforge.pmd:pmd". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-618) use maven-plugin-tools' java 5 annotations
Tony Chemit created MASSEMBLY-618: - Summary: use maven-plugin-tools' java 5 annotations Key: MASSEMBLY-618 URL: https://jira.codehaus.org/browse/MASSEMBLY-618 Project: Maven 2.x Assembly Plugin Issue Type: Task Affects Versions: 2.3 Reporter: Tony Chemit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-11) targetJdk parameter cannot be set in maven 2
[ https://jira.codehaus.org/browse/MPMD-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302038#comment-302038 ] D. commented on MPMD-11: Same problem here, targetJdk works with build plugin but not with reporting. > targetJdk parameter cannot be set in maven 2 > > > Key: MPMD-11 > URL: https://jira.codehaus.org/browse/MPMD-11 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Reporter: Tony Nys > > My code is java 5 and has the special for-loop syntax > pmd says that the for loop is incorrect in jdk1.4 mode > However, there is a parameter targetJdk but it cannot be set , > plugin.xml does not define it and there is no setter in the sourcecode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-643) use maven-plugin-tools' java 5 annotations
[
https://jira.codehaus.org/browse/MSITE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MSITE-643:
--
Attachment: MSITE-643.diff
Here is the patch for this task.
Note that the SiteRunMojo#tempWebappDirectory
{code}
@parameter expression="${project.build.directory}/site-webapp"
{code}
to
{code}
@Parameter( defaultValue = "${project.build.directory}/site-webapp" )
{code}
Note also, I saw some failing ITS:
* full-reporting/pom.xml
* MSITE-506/pom.xml
> use maven-plugin-tools' java 5 annotations
> --
>
> Key: MSITE-643
> URL: https://jira.codehaus.org/browse/MSITE-643
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Task
>Affects Versions: 3.1
>Reporter: Herve Boutemy
> Attachments: MSITE-643.diff
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-171) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MCOMPILER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302036#comment-302036 ] Tony Chemit commented on MCOMPILER-171: --- I check the code and it seems to be already done. should then be closed? Perharps wait the m-plugin-p 3.1 be released to use it directly before closing the task ? > use maven-plugin-tools' java 5 annotations > -- > > Key: MCOMPILER-171 > URL: https://jira.codehaus.org/browse/MCOMPILER-171 > Project: Maven 2.x Compiler Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Herve Boutemy > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MVERIFIER-13) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MVERIFIER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MVERIFIER-13: - Attachment: MVERIFIER-13.diff Here is the patch to do this task. > use maven-plugin-tools' java 5 annotations > -- > > Key: MVERIFIER-13 > URL: https://jira.codehaus.org/browse/MVERIFIER-13 > Project: Maven 2.x Verifier Plugin > Issue Type: Task >Affects Versions: 1.3 >Reporter: Herve Boutemy > Attachments: MVERIFIER-13.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCLEAN-51) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MCLEAN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302033#comment-302033 ] Tony Chemit commented on MCLEAN-51: --- I check the code and it seems to be already done (olamy done it). should then be closed :) > use maven-plugin-tools' java 5 annotations > -- > > Key: MCLEAN-51 > URL: https://jira.codehaus.org/browse/MCLEAN-51 > Project: Maven 2.x Clean Plugin > Issue Type: Task >Reporter: Herve Boutemy > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-246) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MPIR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302028#comment-302028 ] Tony Chemit edited comment on MPIR-246 at 6/27/12 7:31 PM: --- Oups the MINSTALL patch is not for this project. My bad. was (Author: tchemit): Here is a patch for it. Note that I upgrade to maven-plugins 22 to have jdk 5 requirement as it did not work with maven-plugins 21... while configuration of m-compiler-p is the same (from maven-parent 20 and 21). Something to be clarified I think. > use maven-plugin-tools' java 5 annotations > -- > > Key: MPIR-246 > URL: https://jira.codehaus.org/browse/MPIR-246 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Herve Boutemy > Attachments: MINSTALL-88.diff, MPIR-246.diff > > > see MPLUGIN-203 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-88) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MINSTALL-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MINSTALL-88: Attachment: MINSTALL-88.diff Here is a patch for it. Note that I upgrade to maven-plugins 22 to have jdk 5 requirement as it did not work with maven-plugins 21... while configuration of m-compiler-p is the same (from maven-parent 20 and 21). Something to be clarified I think. > use maven-plugin-tools' java 5 annotations > -- > > Key: MINSTALL-88 > URL: https://jira.codehaus.org/browse/MINSTALL-88 > Project: Maven 2.x Install Plugin > Issue Type: Task >Affects Versions: 2.3.1 >Reporter: Herve Boutemy > Attachments: MINSTALL-88.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-246) use maven-plugin-tools' java 5 annotations
[
https://jira.codehaus.org/browse/MPIR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MPIR-246:
-
Attachment: MPIR-246.diff
Here is a patch for it.
Note that I change
AbstractProjectInfoReport#customBundle
{code}
* @parameter
expression="${project.basedir}/src/site/custom/project-info-report.properties"
{code}
to
{code}
@Parameter( defaultValue =
"${project.basedir}/src/site/custom/project-info-report.properties" )
{code}
there is alos a @plexus.component on ProjectSummaryReport, is it normal ?
> use maven-plugin-tools' java 5 annotations
> --
>
> Key: MPIR-246
> URL: https://jira.codehaus.org/browse/MPIR-246
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Task
>Affects Versions: 2.4
>Reporter: Herve Boutemy
> Attachments: MINSTALL-88.diff, MPIR-246.diff
>
>
> see MPLUGIN-203
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-246) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MPIR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MPIR-246: - Attachment: MINSTALL-88.diff Here is a patch for it. Note that I upgrade to maven-plugins 22 to have jdk 5 requirement as it did not work with maven-plugins 21... while configuration of m-compiler-p is the same (from maven-parent 20 and 21). Something to be clarified I think. > use maven-plugin-tools' java 5 annotations > -- > > Key: MPIR-246 > URL: https://jira.codehaus.org/browse/MPIR-246 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Herve Boutemy > Attachments: MINSTALL-88.diff > > > see MPLUGIN-203 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-151) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MDEPLOY-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MDEPLOY-151: Attachment: MDEPLOY-151.diff Here is a patch for it. > use maven-plugin-tools' java 5 annotations > -- > > Key: MDEPLOY-151 > URL: https://jira.codehaus.org/browse/MDEPLOY-151 > Project: Maven 2.x and 3.x Deploy Plugin > Issue Type: Task >Reporter: Herve Boutemy > Attachments: MDEPLOY-151.diff > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-53) add hook for custom script
[ https://jira.codehaus.org/browse/MSKINS-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302025#comment-302025 ] Paolo Mariotti commented on MSKINS-53: -- sorry! i didn't see that. thanks a lot! > add hook for custom script > -- > > Key: MSKINS-53 > URL: https://jira.codehaus.org/browse/MSKINS-53 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Reporter: Paolo Mariotti >Assignee: Robert Scholte > > would it be possible to add to the site.vm an hook for a custom script > (something like site.js) as it happens for the css? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-53) add hook for custom script
[
https://jira.codehaus.org/browse/MSKINS-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MSKINS-53.
Resolution: Won't Fix
Assignee: Robert Scholte
You can use the
[head|http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Inject_xhtml_into_head]
of the {{site.xml}} for that.
> add hook for custom script
> --
>
> Key: MSKINS-53
> URL: https://jira.codehaus.org/browse/MSKINS-53
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Reporter: Paolo Mariotti
>Assignee: Robert Scholte
>
> would it be possible to add to the site.vm an hook for a custom script
> (something like site.js) as it happens for the css?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-51) Github ribbon image broken
[ https://jira.codehaus.org/browse/MSKINS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSKINS-51. Resolution: Fixed Assignee: Robert Scholte Fixed in [r1354723|http://svn.apache.org/viewvc?rev=1354723&view=rev] > Github ribbon image broken > -- > > Key: MSKINS-51 > URL: https://jira.codehaus.org/browse/MSKINS-51 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.2.1 >Reporter: Julien Nicoulaud >Assignee: Robert Scholte > > The Github ribbon image has changed address (example here: > http://nicoulaj.github.com/checksum-maven-plugin) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-36) Website license link missing / incorrect
[
https://jira.codehaus.org/browse/MSKINS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MSKINS-36.
Resolution: Won't Fix
Assignee: Robert Scholte
http://www.apache.org/licenses/ is a general page for all licenses, while now
we include a page containing exactly the content of the used license (which
contains the URL of the Apache license page you mentioned)
The {{license.html}} is generated the
[license-report|http://maven.apache.org/plugins/maven-project-info-reports-plugin/license-mojo.html],
the link is generated by the maven-site-plugin.
By replacing the link (if possible, I doubt it) you've lost the information
under which license the skin was released.
> Website license link missing / incorrect
>
>
> Key: MSKINS-36
> URL: https://jira.codehaus.org/browse/MSKINS-36
> Project: Maven Skins
> Issue Type: Bug
>Reporter: SebbASF
>Assignee: Robert Scholte
>
> All ASF product websites should have a prominent link to the Apache License
> at
> http://www.apache.org/licenses/
> The "project documentation / project information" page has a link to
> http://maven.apache.org/skins/maven-fluido-skin/license.html but that is
> incorrect, the only license link should be to http://www.apache.org/licenses/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-54) Upgrade to bootstrap-2.0.4
[ https://jira.codehaus.org/browse/MSKINS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSKINS-54. Resolution: Fixed Fix Version/s: fluido-1.2.2 Assignee: Robert Scholte Fixed in [r1354699|http://svn.apache.org/viewvc?rev=1354699&view=rev] Fix of MSKINS-40 already repaired the searchbox. Box does has much smaller rounded corners, but I don't think that's an issue. > Upgrade to bootstrap-2.0.4 > -- > > Key: MSKINS-54 > URL: https://jira.codehaus.org/browse/MSKINS-54 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.2.1 >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: fluido-1.2.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-681) Git blame fails to report line authors on windows with core.autocrlf = true
[
https://jira.codehaus.org/browse/SCM-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed SCM-681.
Resolution: Fixed
fixed.
You will now have
{code}
BlameScmResult blame( BlameScmRequest blameScmRequest )
with blameScmRequest.setIgnoreWhitespace( true/false )
{code}
Have fun !
> Git blame fails to report line authors on windows with core.autocrlf = true
> ---
>
> Key: SCM-681
> URL: https://jira.codehaus.org/browse/SCM-681
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.7
> Environment: Windows
> git configured with core.autocrlf = true
>Reporter: David Gageot
>Assignee: Olivier Lamy
> Fix For: 1.8
>
>
> Git blame cannot report line authors when each line is modified locally by
> the autocrlf parameter. It thinks every line is Not Yet Committed.
> The fix is to use git blame -w instead of plain git blame, to ignore
> whitespaces.
> See discussion here:
> http://stackoverflow.com/questions/4638500/git-blame-showing-no-history
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-40) left column is too big since fluido 1.2
[ https://jira.codehaus.org/browse/MSKINS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSKINS-40. Resolution: Fixed The fix in [r1354676|http://svn.apache.org/viewvc?rev=1354676&view=rev] should do the trick > left column is too big since fluido 1.2 > --- > > Key: MSKINS-40 > URL: https://jira.codehaus.org/browse/MSKINS-40 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.2, fluido-1.2.1 >Reporter: Herve Boutemy >Assignee: Robert Scholte > Fix For: fluido-1.2.2 > > > if you compare the rendered result from > 1. fuido 1.1: http://maven.apache.org/skins/maven-fluido-skin-1.1/ > 2. and fluido 1.2: http://maven.apache.org/skins/maven-fluido-skin-1.2/ > the left column was well sized in 1.1 but has grown in 1.2 for non-obvious > reasons -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-103) maven-shade-plugin does not resolve from user-defined repositories
[ https://jira.codehaus.org/browse/MSHADE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MSHADE-103. --- Resolution: Fixed Fix Version/s: 2.0 Thank you for the patch. r1354665 | bimargulies | 2012-06-27 14:51:17 -0400 (Wed, 27 Jun 2012) | 3 lines MSHADE-103: maven-shade-plugin does not resolve from user-defined repositories o note: trunk now requires Maven 3.0. > maven-shade-plugin does not resolve from user-defined repositories > -- > > Key: MSHADE-103 > URL: https://jira.codehaus.org/browse/MSHADE-103 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.3.3, 1.4 > Environment: Maven 3.0.3 (works with 2.2.1) >Reporter: Lukas Fryc >Assignee: Benson Margulies > Fix For: 2.0 > > Attachments: > 0001-MSHADE-103-Use-the-ProjectBuilder-API-to-include-rem.patch, > MSHADE-103.tar.gz > > > maven-shade-plugin doesn't consult repositories defined in > settings.xml when trying to resolve parents of given pom. It contacts > only central repo: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:1.4:shade (default) on > project richfaces-components-api: Error creating shaded jar: 1 problem > was encountered while building the effective model for > org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT > [ERROR] [FATAL] Non-resolvable parent POM for > org.richfaces:richfaces-bom:4.1.0-SNAPSHOT: Could not find artifact > org.richfaces:richfaces-parent:pom:10 in central > (http://repo1.maven.org/maven2) and 'parent.relativePath' points at > wrong local POM @ org.richfaces:richfaces-bom:4.1.0-SNAPSHOT, > /home/lfryc/workspaces/richfaces/build/bom/pom.xml, line 24, column 10 > [ERROR] for project > org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at > /home/lfryc/workspaces/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml > > for project org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at > /home/lfryc/workspaces/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml > > [ERROR] -> [Help 1] > There is affected project (it references version 1.3.3, but the behavior is > same with 1.4) if you would like to try at own: > https://github.com/richfaces/components/blob/develop/dist/richfaces-components-api/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-103) maven-shade-plugin does not resolve from user-defined repositories
[ https://jira.codehaus.org/browse/MSHADE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned MSHADE-103: --- Assignee: Benson Margulies > maven-shade-plugin does not resolve from user-defined repositories > -- > > Key: MSHADE-103 > URL: https://jira.codehaus.org/browse/MSHADE-103 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.3.3, 1.4 > Environment: Maven 3.0.3 (works with 2.2.1) >Reporter: Lukas Fryc >Assignee: Benson Margulies > Attachments: > 0001-MSHADE-103-Use-the-ProjectBuilder-API-to-include-rem.patch, > MSHADE-103.tar.gz > > > maven-shade-plugin doesn't consult repositories defined in > settings.xml when trying to resolve parents of given pom. It contacts > only central repo: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:1.4:shade (default) on > project richfaces-components-api: Error creating shaded jar: 1 problem > was encountered while building the effective model for > org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT > [ERROR] [FATAL] Non-resolvable parent POM for > org.richfaces:richfaces-bom:4.1.0-SNAPSHOT: Could not find artifact > org.richfaces:richfaces-parent:pom:10 in central > (http://repo1.maven.org/maven2) and 'parent.relativePath' points at > wrong local POM @ org.richfaces:richfaces-bom:4.1.0-SNAPSHOT, > /home/lfryc/workspaces/richfaces/build/bom/pom.xml, line 24, column 10 > [ERROR] for project > org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at > /home/lfryc/workspaces/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml > > for project org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at > /home/lfryc/workspaces/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml > > [ERROR] -> [Help 1] > There is affected project (it references version 1.3.3, but the behavior is > same with 1.4) if you would like to try at own: > https://github.com/richfaces/components/blob/develop/dist/richfaces-components-api/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-681) Git blame fails to report line authors on windows with core.autocrlf = true
[ https://jira.codehaus.org/browse/SCM-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned SCM-681: Assignee: Olivier Lamy > Git blame fails to report line authors on windows with core.autocrlf = true > --- > > Key: SCM-681 > URL: https://jira.codehaus.org/browse/SCM-681 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.7 > Environment: Windows > git configured with core.autocrlf = true >Reporter: David Gageot >Assignee: Olivier Lamy > Fix For: 1.8 > > > Git blame cannot report line authors when each line is modified locally by > the autocrlf parameter. It thinks every line is Not Yet Committed. > The fix is to use git blame -w instead of plain git blame, to ignore > whitespaces. > See discussion here: > http://stackoverflow.com/questions/4638500/git-blame-showing-no-history -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-681) Git blame fails to report line authors on windows with core.autocrlf = true
[ https://jira.codehaus.org/browse/SCM-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-681: - Fix Version/s: 1.8 > Git blame fails to report line authors on windows with core.autocrlf = true > --- > > Key: SCM-681 > URL: https://jira.codehaus.org/browse/SCM-681 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.7 > Environment: Windows > git configured with core.autocrlf = true >Reporter: David Gageot >Assignee: Olivier Lamy > Fix For: 1.8 > > > Git blame cannot report line authors when each line is modified locally by > the autocrlf parameter. It thinks every line is Not Yet Committed. > The fix is to use git blame -w instead of plain git blame, to ignore > whitespaces. > See discussion here: > http://stackoverflow.com/questions/4638500/git-blame-showing-no-history -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-879) maven-surefire-report-plugin fails some times with ConcurrentModificationException when running parallel TestNG
[ https://jira.codehaus.org/browse/SUREFIRE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301979#comment-301979 ] Adrian Nistor commented on SUREFIRE-879: I pushed a fix to github and made a pull request: https://github.com/apache/maven-surefire/pull/5 Thanks > maven-surefire-report-plugin fails some times with > ConcurrentModificationException when running parallel TestNG > --- > > Key: SUREFIRE-879 > URL: https://jira.codehaus.org/browse/SUREFIRE-879 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.12 > Environment: Java version: 1.6.0_32 > Maven version: 3.0.4 > maven-surefire-report-plugin: 2.12 > TestNG: 5.14.10 >Reporter: Adrian Nistor > Attachments: surefire-879-bug.zip > > > I'm running TestNG tests in parallel and get this exception > ConcurrentModificationException. > My quick analysis is that at the end of the test the method > TestSetRunListener.getAsString is accessing the list of captured output while > another thread (a stray thread spawned by the test or a completely different > concurrent test) generates some more console output causing an append to the > list which results in ConcurrentModificationException. > To fix this we need to ensure getAsString accesses the list atomically. A > possible solution is to copy/clone the list before iterating over it. > Here is the stakctrace I get. > java.util.ConcurrentModificationException > at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) > at java.util.AbstractList$Itr.next(AbstractList.java:343) > at > org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:209) > at > org.apache.maven.plugin.surefire.report.TestSetRunListener.testFailed(TestSetRunListener.java:168) > at > org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:104) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1796) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1780) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:749) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170) > at > org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1147) > at org.testng.TestRunner.privateRun(TestRunner.java:749) > at org.testng.TestRunner.run(TestRunner.java:600) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:34) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351) > at > org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-123) 1.7 Causes failures in other plugins make "basedir" point to the build dir
[ https://jira.codehaus.org/browse/MSHADE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301978#comment-301978 ] Benson Margulies commented on MSHADE-123: - r1354439 | bimargulies | 2012-06-27 07:42:24 -0400 (Wed, 27 Jun 2012) | 3 lines MSHADE-123: 1.7 Causes failures in other plugins make "basedir" point to the build dir o forgot to document the situation in the main checkin. > 1.7 Causes failures in other plugins make "basedir" point to the build dir > -- > > Key: MSHADE-123 > URL: https://jira.codehaus.org/browse/MSHADE-123 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Reporter: Shay Banon >Assignee: Benson Margulies >Priority: Blocker > Fix For: 1.7.1 > > Attachments: mvn-shade.zip > > > Upgrading the 1.7 causes other plugins to have basedir now pointing to build > dir, or something similar. The attached test case shows that with shade > plugin 1.5, the assembly plugins successfully finds the sample.txt file (in > basedir), while upgrading to 1.7 shade plugin causes the assembly plugin not > to find it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-124) Need better plan for getting dependency-reduced-pom.xml out of basedir
Benson Margulies created MSHADE-124: --- Summary: Need better plan for getting dependency-reduced-pom.xml out of basedir Key: MSHADE-124 URL: https://jira.codehaus.org/browse/MSHADE-124 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 1.7.1 Reporter: Benson Margulies MSHADE-123 reported that putting the d-r-p into some location other than 'basedir' causes 'basedir' to follow it around, which can break builds. This is hard to fix, given the core maven definition of basedir as 'the dir containing the pom' with no option to change it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-123) 1.7 Causes failures in other plugins make "basedir" point to the build dir
[ https://jira.codehaus.org/browse/MSHADE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MSHADE-123. --- Resolution: Fixed Fix Version/s: 1.7.1 r1354435 | bimargulies | 2012-06-27 07:37:39 -0400 (Wed, 27 Jun 2012) | 3 lines MSHADE-123: 1.7 Causes failures in other plugins make "basedir" point to the build dir o revert the default back to basedir until and unless we come up with something better. > 1.7 Causes failures in other plugins make "basedir" point to the build dir > -- > > Key: MSHADE-123 > URL: https://jira.codehaus.org/browse/MSHADE-123 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Reporter: Shay Banon >Assignee: Benson Margulies >Priority: Blocker > Fix For: 1.7.1 > > Attachments: mvn-shade.zip > > > Upgrading the 1.7 causes other plugins to have basedir now pointing to build > dir, or something similar. The attached test case shows that with shade > plugin 1.5, the assembly plugins successfully finds the sample.txt file (in > basedir), while upgrading to 1.7 shade plugin causes the assembly plugin not > to find it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-879) maven-surefire-report-plugin fails some times with ConcurrentModificationException when running parallel TestNG
[ https://jira.codehaus.org/browse/SUREFIRE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Nistor updated SUREFIRE-879: --- Attachment: surefire-879-bug.zip This is a small project (a pom.xml + a simple TestNG test) that helps reproduce the issue. Please see instructions in README.txt from zip. > maven-surefire-report-plugin fails some times with > ConcurrentModificationException when running parallel TestNG > --- > > Key: SUREFIRE-879 > URL: https://jira.codehaus.org/browse/SUREFIRE-879 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.12 > Environment: Java version: 1.6.0_32 > Maven version: 3.0.4 > maven-surefire-report-plugin: 2.12 > TestNG: 5.14.10 >Reporter: Adrian Nistor > Attachments: surefire-879-bug.zip > > > I'm running TestNG tests in parallel and get this exception > ConcurrentModificationException. > My quick analysis is that at the end of the test the method > TestSetRunListener.getAsString is accessing the list of captured output while > another thread (a stray thread spawned by the test or a completely different > concurrent test) generates some more console output causing an append to the > list which results in ConcurrentModificationException. > To fix this we need to ensure getAsString accesses the list atomically. A > possible solution is to copy/clone the list before iterating over it. > Here is the stakctrace I get. > java.util.ConcurrentModificationException > at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) > at java.util.AbstractList$Itr.next(AbstractList.java:343) > at > org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:209) > at > org.apache.maven.plugin.surefire.report.TestSetRunListener.testFailed(TestSetRunListener.java:168) > at > org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:104) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1796) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1780) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:749) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170) > at > org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1147) > at org.testng.TestRunner.privateRun(TestRunner.java:749) > at org.testng.TestRunner.run(TestRunner.java:600) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:34) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351) > at > org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-879) maven-surefire-report-plugin fails some times with ConcurrentModificationException when running parallel TestNG
[ https://jira.codehaus.org/browse/SUREFIRE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301971#comment-301971 ] Adrian Nistor commented on SUREFIRE-879: An important note, to reproduce this bug you must have at least one failing test in your suite. This can also be seen in the above stacktrace. > maven-surefire-report-plugin fails some times with > ConcurrentModificationException when running parallel TestNG > --- > > Key: SUREFIRE-879 > URL: https://jira.codehaus.org/browse/SUREFIRE-879 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.12 > Environment: Java version: 1.6.0_32 > Maven version: 3.0.4 > maven-surefire-report-plugin: 2.12 > TestNG: 5.14.10 >Reporter: Adrian Nistor > > I'm running TestNG tests in parallel and get this exception > ConcurrentModificationException. > My quick analysis is that at the end of the test the method > TestSetRunListener.getAsString is accessing the list of captured output while > another thread (a stray thread spawned by the test or a completely different > concurrent test) generates some more console output causing an append to the > list which results in ConcurrentModificationException. > To fix this we need to ensure getAsString accesses the list atomically. A > possible solution is to copy/clone the list before iterating over it. > Here is the stakctrace I get. > java.util.ConcurrentModificationException > at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) > at java.util.AbstractList$Itr.next(AbstractList.java:343) > at > org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:209) > at > org.apache.maven.plugin.surefire.report.TestSetRunListener.testFailed(TestSetRunListener.java:168) > at > org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:104) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1796) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1780) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:749) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170) > at > org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1147) > at org.testng.TestRunner.privateRun(TestRunner.java:749) > at org.testng.TestRunner.run(TestRunner.java:600) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:34) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351) > at > org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-40) left column is too big since fluido 1.2
[ https://jira.codehaus.org/browse/MSKINS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reopened MSKINS-40: --- The fix for this does not always work. Generate the site for Fluido Skin using the command 'mvn verify site -Prun-its,reporting' and have a look at the site for the MSKINS-14 IT. Depending on the width of the browser the sitesearch input field sometimes extends outside the right edge of the leftColumn. > left column is too big since fluido 1.2 > --- > > Key: MSKINS-40 > URL: https://jira.codehaus.org/browse/MSKINS-40 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.2, fluido-1.2.1 >Reporter: Herve Boutemy >Assignee: Robert Scholte > Fix For: fluido-1.2.2 > > > if you compare the rendered result from > 1. fuido 1.1: http://maven.apache.org/skins/maven-fluido-skin-1.1/ > 2. and fluido 1.2: http://maven.apache.org/skins/maven-fluido-skin-1.2/ > the left column was well sized in 1.1 but has grown in 1.2 for non-obvious > reasons -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-35) Website typo in footer
[ https://jira.codehaus.org/browse/MSKINS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301961#comment-301961 ] Dennis Lundberg commented on MSKINS-35: --- This problem seems to be related to the siteskinner-maven-plugin, that was used to redeploy the site. Generating the site in trunk for Fluido Skin works fine, and has the correct footer. The deployed site will be correct when the next version of Fluido Skin is released. > Website typo in footer > -- > > Key: MSKINS-35 > URL: https://jira.codehaus.org/browse/MSKINS-35 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin > Environment: http://maven.apache.org/skins/maven-fluido-skin/ >Reporter: SebbASF >Assignee: Simone Tripodi > Fix For: fluido-1.2.2 > > > The website footer says: > bq. Apache Maven, Apache Apache Maven Fluido Skin, Apache, the Apache feather > logo ... > There's a duplicated Apache. > Also, the page title says just "Introduction" which isn't very informative. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
[
https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301960#comment-301960
]
Manuel AUGUSTO commented on MRELEASE-679:
-
Hello,
I had the same problem and i resolved it was fixed this line in a pom.xml of
parent project.
scm:svn:svn://repo/trunk/parent
scm:svn:svn://repo/trunk/parent
and is not necessary to fixed a tag connectionUrl in configuration of
maven-release-plugin.
It work correctly whith the last version =>2.3.2.
good day. bye
> CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/
> instead of project/trunk
> --
>
> Key: MRELEASE-679
> URL: https://jira.codehaus.org/browse/MRELEASE-679
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0
> Environment: Maven 2.2.1
>Reporter: Claus Gebert
>Priority: Critical
>
> We have switched to the release plug-in 2.0 and are using the prepare goal as
> we did before using version 2.0-beta-9. Unfortunately, the tag which is now
> created is copied from the project level, and from the trunk. With version
> 2.0-beta-9, the tag was correctly copied from the trunk.
> With 2.0-beta-9:
> {noformat}
> /project
>|-- trunk/
> |-- pom.xml
> |-- src/
>|-- tags/
> |-- 4.0.1/ (<-- copied from trunk
> |-- pom.xml
> |-- src/
> {noformat}
> With 2.0:
> {noformat}
> /project
>|-- trunk/
> |-- pom.xml
> |-- src/
>|-- tags/
> |-- 4.0.1/ (<-- copied from trunk
> |-- trunk/
>|-- pom.xml
>|-- src/
> |-- tags/
> |-- branches/
> {noformat}
> Our _pom.xml_ SCM information is declared as follow:
> {noformat}
>
>
> scm:svn:svn://host/path/project/trunk
>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
