[jira] (MWAR-164) Support for specifying which encoding to use when filtering resources
[
https://jira.codehaus.org/browse/MWAR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309393#comment-309393
]
Dennis Lundberg commented on MWAR-164:
--
I have committed a fix for this in
http://svn.apache.org/viewvc?view=revision&revision=1388368 complete with an
IT. The default encoding used is project.build.sourceEncoding, as suggested.
I went the more difficult path and did not set the configured encoding for xml
files. Intead for xml files (currently files ending in ".xml") the encoding is
read from the files themselves. This means that you can have a mix of encodings
in your resource files. The IT has a properties file encoded in ISO-8859-1 and
an xml file encoded in UTF-8 which is also specified in the files xml header.
Apart from the IT I've successfully tried this on several local projects that
suffer from this bug.
I have not yet deployed a new SNAPSHOT, but will do so later today. Please help
test this.
Also I want to add some documentation for this, apart from the parameter
documentation that went in with this commit, before I close the issue.
> Support for specifying which encoding to use when filtering resources
> -
>
> Key: MWAR-164
> URL: https://jira.codehaus.org/browse/MWAR-164
> Project: Maven 2.x WAR Plugin
> Issue Type: Improvement
> Components: filtering
>Affects Versions: 2.1-alpha-1
>Reporter: kai lilleby
>Assignee: Dennis Lundberg
> Fix For: 2.3
>
> Attachments: MWAR-164-maven-war-plugin.patch
>
>
> Quoting Hervé:
> {quote}
> Maven filtering provides an encoding parameter to set encoding used when
> reading/writing files. But war plugin uses null value, which means platform
> encoding... Sorry, encoding support won't be totally "free" ;)
> I added TODOs in the code.
> For web.xml and container config XML file, I set encoding to UTF-8, which is a
> better default value than platform encoding.
> For other filtered resources, you'll need to add an encoding attribute to
> o.a.m.model.Resource class, to let the user define which encoding he wants to
> use when filtering. Perhaps using project.build.sourceEncoding as a default
> value is a good idea.
> Seems like this is worth a Jira issue to track this new feature.
> {quote}
--
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-580) Allow "fail fast" or stop running on first failure
[ https://jira.codehaus.org/browse/SUREFIRE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309395#comment-309395 ] Tomislav Nakic-Alfirevic commented on SUREFIRE-580: --- It would even be useful if test execution was not interrupted, but the result of each test be output after the test, not after the entire test suite. Something that would work like this: $ mvn test | grep FAIL SuiteA.test2 FAILED SuiteA.test11 FAILED SuiteB.test1 FAILED [surefire still running] I imagine that should be fairly easy to implement, yet it would still provide quick information about any test failures... > Allow "fail fast" or stop running on first failure > -- > > Key: SUREFIRE-580 > URL: https://jira.codehaus.org/browse/SUREFIRE-580 > Project: Maven Surefire > Issue Type: New Feature > Components: Junit 4.x support >Reporter: Paul Curren > > We have some slow Selenium builds. Waiting for indication of failure can take > a long time. It would be helpful if there was an option to finish the test > run on the first failure. > We could configure this on some of our slower builds so improve the speed of > the feedback loop in the cases where there are failures. -- 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-254) Distinguish 'active development branch' in SCM report from 'release tag'
Benson Margulies created MPIR-254: - Summary: Distinguish 'active development branch' in SCM report from 'release tag' Key: MPIR-254 URL: https://jira.codehaus.org/browse/MPIR-254 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: scm Affects Versions: 2.5.1 Reporter: Benson Margulies There's a certain amount of chronic minor confusion caused by the SCM report for a released version. The release plugin puts the tag into both the user and developer urls, and the report reports them. This has the unfortunate effect of suggesting that the way to 'develop' is to check out the tag. One might argue that this is, in fact, a release plugin issue; that it should leave the source branch (typically the trunk) in the developer URL and only mess with the other ones. Leaving that aside, it would be an improvement for the SCM reporter to be capable of clearly distinguishing 'this is the release tag' from 'here is where development is happening'. Since we can't add to the POM scm element easily, it would seem to be a job for plugin config. -- 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] (WAGON-356) java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
[
https://jira.codehaus.org/browse/WAGON-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309431#comment-309431
]
Lorenzo Bigagli commented on WAGON-356:
---
I had the same problem with Maven 3.0.3, maven-site-plugin 3.1,
wagon-webdav-jackrabbit 2.2.
I confirm that setting jackrabbit as an extension solves the problem.
However, I would avoid extensions and keep jackrabbit as a maven-site-plugin
dependency, so I worked around the issue forcing slf4j 1.6.1 (the policy of
binding changed with 1.6, see
http://www.slf4j.org/codes.html#StaticLoggerBinder).
I suggest future versions of jackrabbit update their dependency on slf4j, to
avoid all this.
org.apache.maven.plugins
maven-site-plugin
3.1
org.apache.maven.wagon
wagon-webdav-jackrabbit
2.2
org.slf4j
slf4j-api
1.6.1
> java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
> ---
>
> Key: WAGON-356
> URL: https://jira.codehaus.org/browse/WAGON-356
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-webdav
>Affects Versions: 2.0
> Environment: Maven 3.0.3, maven-site-plugin 3.0,
> wagon-webdav-jackrabbit 2.0
>Reporter: Daniel Spilker
>Assignee: Olivier Lamy
>
> When performing a release the site deployment fails due to a
> ClassNotFoundException.
> {noformat}
> [INFO] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> [INFO] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
> further details.
> [INFO] Nov 8, 2011 10:28:56 AM org.sonatype.guice.bean.reflect.NamedClass
> [INFO] WARNING: Error injecting:
> org.apache.maven.wagon.providers.webdav.WebDavWagon
> [INFO] com.google.inject.ProvisionException: Guice provision errors:
> [INFO]
> [INFO] 1) Error injecting constructor, java.lang.NoClassDefFoundError:
> org/slf4j/impl/StaticLoggerBinder
> [INFO] at
> org.apache.maven.wagon.providers.webdav.WebDavWagon.(Unknown Source)
> [INFO] while locating org.apache.maven.wagon.providers.webdav.WebDavWagon
> [INFO]
> [INFO] [INFO] [ERROR]
> 1 error
> [INFO] Unsupported protocol: 'dav' for site deployment to
> distributionManagement.site.url=dav:https://repository.coremedia.com/...
> [INFO] at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:977)
> [INFO] at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1003)
> [INFO] at
> org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:47)
> [INFO] at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
> [INFO] at
> com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:968)
> [INFO] at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1014)
> [INFO] at
> com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:964)
> [INFO] at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> [INFO] at
> org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:79)
> [INFO] at
> org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:53)
> [INFO] at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243)
> [INFO] at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235)
> [INFO] at
> org.apache.maven.repository.legacy.DefaultWagonManager.getWagon(DefaultWagonManager.java:764)
> [INFO] at
> org.apache.maven.repository.legacy.DefaultWagonManager.getWagon(DefaultWagonManager.java:747)
> [INFO] at
> org.apache.maven.plugins.site.AbstractDeployMojo.getWagon(AbstractDeployMojo.java:354)
> [INFO] at
> org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:264)
> at
> org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:257)
> [INFO] at
> org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:165)
> [INFO] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> [INFO] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> [INFO] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> [INFO] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> [INFO] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> [INFO] at
> org.apache.maven.lifecycl
[jira] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils
Mark Struberg created MSHARED-244: - Summary: Add EMPTY__ARRAY from commons-lang to our CollectionsUtils Key: MSHARED-244 URL: https://jira.codehaus.org/browse/MSHARED-244 Project: Maven Shared Components Issue Type: New Feature Components: maven-shared-utils Reporter: Mark Struberg There are a lot of Classes which need constants for empty arrays like String[0]. We shall add such constants to our CollectionUtils. -- 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] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils
[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned MSHARED-244: - Assignee: Mark Struberg > Add EMPTY__ARRAY from commons-lang to our CollectionsUtils > -- > > Key: MSHARED-244 > URL: https://jira.codehaus.org/browse/MSHARED-244 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > There are a lot of Classes which need constants for empty arrays like > String[0]. > We shall add such constants to our CollectionUtils. -- 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] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils
[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHARED-244. - Resolution: Fixed fixed in r1388452 by adding an ArrayUtils class with the constants taken from commons-lang. > Add EMPTY__ARRAY from commons-lang to our CollectionsUtils > -- > > Key: MSHARED-244 > URL: https://jira.codehaus.org/browse/MSHARED-244 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > There are a lot of Classes which need constants for empty arrays like > String[0]. > We shall add such constants to our CollectionUtils. -- 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] (MSHARED-245) add IncrementalBuildHelper
Mark Struberg created MSHARED-245: - Summary: add IncrementalBuildHelper Key: MSHARED-245 URL: https://jira.codehaus.org/browse/MSHARED-245 Project: Maven Shared Components Issue Type: New Feature Components: maven-shared-incremental Reporter: Mark Struberg add a module and utility class to make incremental builds easier. -- 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] (MSHARED-245) add IncrementalBuildHelper
[ https://jira.codehaus.org/browse/MSHARED-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309441#comment-309441 ] Mark Struberg commented on MSHARED-245: --- initial version committed in r1388456. Tests are still missing. > add IncrementalBuildHelper > -- > > Key: MSHARED-245 > URL: https://jira.codehaus.org/browse/MSHARED-245 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-incremental >Reporter: Mark Struberg > > add a module and utility class to make incremental builds easier. -- 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-912) A NPE is thrown when some test case fails in the ConcurrentReporterManager
Cristian Vazzolla created SUREFIRE-912: -- Summary: A NPE is thrown when some test case fails in the ConcurrentReporterManager Key: SUREFIRE-912 URL: https://jira.codehaus.org/browse/SUREFIRE-912 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Environment: Windows 7 Reporter: Cristian Vazzolla Attachments: ConcurrentReporterManager.patch, log_bug_surefire.txt When using JUnit categories for testing some of the tests that fail will result in a NULL pointer exception being thrown from the ConcurrentReporterManager class and this breaks the surefire plugin execution so the tests that follow this will not get executed anymore. The root cause of the problem is that in the testFailed method the getOrCreateTestMethod method is called which on one of the flows returns null which is not treated in the testFailed method and gives a null pointer exception. I've created a patch for this issue in which I've modified the testFailed and the testAssumptionFailure methods to treat nicely the case when null is returned from getOrCreateTestMethod. I've also attached the log file with the exception. I have not included any test because this issue happens randomly not on a particular test case. -- 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-912) A NPE is thrown when some test case fails in the ConcurrentReporterManager
[ https://jira.codehaus.org/browse/SUREFIRE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309442#comment-309442 ] Cristian Vazzolla commented on SUREFIRE-912: Could the patch be applied and an internal/ intermediary release could be done so that we can use JUnit categories with Surefire ? As for now we are blocked because of this issue. Regards, Cristian > A NPE is thrown when some test case fails in the ConcurrentReporterManager > -- > > Key: SUREFIRE-912 > URL: https://jira.codehaus.org/browse/SUREFIRE-912 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support > Environment: Windows 7 >Reporter: Cristian Vazzolla > Attachments: ConcurrentReporterManager.patch, log_bug_surefire.txt > > > When using JUnit categories for testing some of the tests that fail will > result in a NULL pointer exception being thrown from the > ConcurrentReporterManager class and this breaks the surefire plugin execution > so the tests that follow this will not get executed anymore. > The root cause of the problem is that in the testFailed method the > getOrCreateTestMethod method is called which on one of the flows returns null > which is not treated in the testFailed method and gives a null pointer > exception. > I've created a patch for this issue in which I've modified the testFailed and > the testAssumptionFailure methods to treat nicely the case when null is > returned from getOrCreateTestMethod. > I've also attached the log file with the exception. > I have not included any test because this issue happens randomly not on a > particular test case. -- 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] (MENFORCER-141) Show correct version of the enforcer api / plugin in example
[ https://jira.codehaus.org/browse/MENFORCER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-141. Resolution: Fixed Fix Version/s: 1.2 Assignee: Robert Scholte Fixed in [r1388614|http://svn.apache.org/viewvc?rev=1388614&view=rev] Thanks! > Show correct version of the enforcer api / plugin in example > > > Key: MENFORCER-141 > URL: https://jira.codehaus.org/browse/MENFORCER-141 > Project: Maven 2.x Enforcer Plugin > Issue Type: Improvement > Components: Rule API >Affects Versions: 1.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Robert Scholte >Priority: Minor > Fix For: 1.2 > > Attachments: patch-MENFORCER-144.patch > > > I have observed that the version of the maven-enforcer-plugin in the > [example|http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html] > is not correctly shown. Currently the 1.0-beta-1 is shown which should be > changed to the current one. -- 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] (MJAVADOC-318) detectLinks should work together with links, or allow overrides for docs it can't locate
[ https://jira.codehaus.org/browse/MJAVADOC-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MJAVADOC-318: -- Comment: was deleted (was: ONLINE STORE : http://ppt.cc/g9nI n2012 comes, in order to thank everyone, characteristic, novel style, varieties, low price and good quality, and the low sale price. Thank everyone free shipping competitive price any size available accept the paypal jordan shoes $32 nike shox $32 Christan Audigier bikini $23 Ed Hardy Bikini $23 Smful short_t-shirt_woman $15 ed hardy short_tank_woman $16 Sandal $32 christian louboutin $80 Sunglass $15 COACH_Necklace $27 handbag $33 AF tank woman $17 puma slipper woman $30 http://ppt.cc/g9nI ) > detectLinks should work together with links, or allow overrides for docs it > can't locate > > > Key: MJAVADOC-318 > URL: https://jira.codehaus.org/browse/MJAVADOC-318 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Reporter: Jenni Syed >Assignee: Herve Boutemy > > When detectLinks is true, it tends to find the correct javadoc link for 80%+ > of the referenced classes. If I add the few locations that are not able to be > detected to the links section, these will be ignored. Ideally, detectLinks > would find whatever it could automatically, but work in conjuction with an > override that can be provided for the locations you know it won't be able to > find. -- 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] (MDEP-376) -Dincludes and -Dexcludes filtering not working anymore
[
https://jira.codehaus.org/browse/MDEP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reassigned MDEP-376:
-
Assignee: Olivier Lamy
> -Dincludes and -Dexcludes filtering not working anymore
> ---
>
> Key: MDEP-376
> URL: https://jira.codehaus.org/browse/MDEP-376
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 2.5.1
>Reporter: Ryan Gardner
>Assignee: Olivier Lamy
> Attachments: maven-dependency-plugin-includes.jpg
>
>
> running
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:tree -Dincludes=foo
> {code}
> will restrict the tree that is printed to just show the artifacts that match
> the includes pattern (a much smaller tree)
> in version 2.5+
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.5.1:tree -Dincludes=foo
> {code}
> on a project will show the entire tree with no filtering.
--
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] (MDEP-376) -Dexcludes filtering not working anymore
[
https://jira.codehaus.org/browse/MDEP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MDEP-376:
--
Summary: -Dexcludes filtering not working anymore (was: -Dincludes and
-Dexcludes filtering not working anymore)
AFAIK excludes works
> -Dexcludes filtering not working anymore
>
>
> Key: MDEP-376
> URL: https://jira.codehaus.org/browse/MDEP-376
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 2.5.1
>Reporter: Ryan Gardner
>Assignee: Olivier Lamy
> Attachments: maven-dependency-plugin-includes.jpg
>
>
> running
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:tree -Dincludes=foo
> {code}
> will restrict the tree that is printed to just show the artifacts that match
> the includes pattern (a much smaller tree)
> in version 2.5+
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.5.1:tree -Dincludes=foo
> {code}
> on a project will show the entire tree with no filtering.
--
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] (MENFORCER-131) DependencyConvergence log statement should be debug instead of info
[ https://jira.codehaus.org/browse/MENFORCER-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-131. Resolution: Duplicate > DependencyConvergence log statement should be debug instead of info > --- > > Key: MENFORCER-131 > URL: https://jira.codehaus.org/browse/MENFORCER-131 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Andrew Ruch >Priority: Minor > Attachments: MENFORCER-131-enforcer-rules.patch > > > In the DependencyVersionMap on line 87, an log prints every dependency and > its version information. This seems unnecessary as an info level log. -- 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] (MDEP-376) -Dexcludes filtering not working anymore
[
https://jira.codehaus.org/browse/MDEP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MDEP-376.
-
Resolution: Fixed
Fix Version/s: 2.6
fixed r1388658
> -Dexcludes filtering not working anymore
>
>
> Key: MDEP-376
> URL: https://jira.codehaus.org/browse/MDEP-376
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 2.5.1
>Reporter: Ryan Gardner
>Assignee: Olivier Lamy
> Fix For: 2.6
>
> Attachments: maven-dependency-plugin-includes.jpg
>
>
> running
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:tree -Dincludes=foo
> {code}
> will restrict the tree that is printed to just show the artifacts that match
> the includes pattern (a much smaller tree)
> in version 2.5+
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.5.1:tree -Dincludes=foo
> {code}
> on a project will show the entire tree with no filtering.
--
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-912) A NPE is thrown when some test case fails in the ConcurrentReporterManager
[ https://jira.codehaus.org/browse/SUREFIRE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-912. --- Resolution: Fixed Fix Version/s: 2.13 Assignee: Kristian Rosenvold Fixed in 9c6abc2acf75e93f01596683a60c426810c7e7ee, thanks for the patch ! 2.12.4 coming "soon" > A NPE is thrown when some test case fails in the ConcurrentReporterManager > -- > > Key: SUREFIRE-912 > URL: https://jira.codehaus.org/browse/SUREFIRE-912 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support > Environment: Windows 7 >Reporter: Cristian Vazzolla >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: ConcurrentReporterManager.patch, log_bug_surefire.txt > > > When using JUnit categories for testing some of the tests that fail will > result in a NULL pointer exception being thrown from the > ConcurrentReporterManager class and this breaks the surefire plugin execution > so the tests that follow this will not get executed anymore. > The root cause of the problem is that in the testFailed method the > getOrCreateTestMethod method is called which on one of the flows returns null > which is not treated in the testFailed method and gives a null pointer > exception. > I've created a patch for this issue in which I've modified the testFailed and > the testAssumptionFailure methods to treat nicely the case when null is > returned from getOrCreateTestMethod. > I've also attached the log file with the exception. > I have not included any test because this issue happens randomly not on a > particular test case. -- 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-863) NPE in ConcurrentReporterManager
[ https://jira.codehaus.org/browse/SUREFIRE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-863. --- Resolution: Fixed Assignee: Kristian Rosenvold Fixed in 9c6abc2acf75e93f01596683a60c426810c7e7ee, patch supplied in SUREFIRE-912 > NPE in ConcurrentReporterManager > > > Key: SUREFIRE-863 > URL: https://jira.codehaus.org/browse/SUREFIRE-863 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.12 >Reporter: Mark Struberg >Assignee: Kristian Rosenvold > Fix For: 2.13 > > Attachments: SUREFIRE-863.patch > > > I have a wird NPE in surefire with one of my projects: > Caused by: java.lang.NullPointerException > at > java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:768) > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.getTestSet(ConcurrentReporterManager.java:157) > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.getOrCreateTestMethod(ConcurrentReporterManager.java:127) > at > org.apache.maven.surefire.junitcore.ConcurrentReporterManager.testError(ConcurrentReporterManager.java:83) > at > org.apache.maven.surefire.common.junit4.JUnit4RunListener.testFailure(JUnit4RunListener.java:110) > at > org.junit.runner.notification.RunNotifier$4.notifyListener(RunNotifier.java:100) -- 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] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils
[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309475#comment-309475 ] Dennis Lundberg commented on MSHARED-244: - Mark, I'm sorry but I fail to see the point of this. If there is good code that we want to use in commons-lang, why don't we just use that code instead of copying it? commons-lang is an Apache project with an Apache license and solid tests. We should just add a dependency on commons-lang and use that code. > Add EMPTY__ARRAY from commons-lang to our CollectionsUtils > -- > > Key: MSHARED-244 > URL: https://jira.codehaus.org/browse/MSHARED-244 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > There are a lot of Classes which need constants for empty arrays like > String[0]. > We shall add such constants to our CollectionUtils. -- 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] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils
[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309477#comment-309477 ] Mark Struberg commented on MSHARED-244: --- The reason is pretty simple: binary compatibility! There are quite some different versions of various commons-*, logger APIs etc around. Not all of those versions are binary compatible. In some plugins and all of maven-core we do not know which other dependencies end up in the chain. Imagine what would happen if a commons-lang.jar is available in both a custom plugin dependency and in maven core. We could end up with those funny "Class X cannot be cast to Class X" errors. > Add EMPTY__ARRAY from commons-lang to our CollectionsUtils > -- > > Key: MSHARED-244 > URL: https://jira.codehaus.org/browse/MSHARED-244 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > There are a lot of Classes which need constants for empty arrays like > String[0]. > We shall add such constants to our CollectionUtils. -- 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] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils
[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309479#comment-309479 ] Dennis Lundberg commented on MSHARED-244: - When it comes to commons-* components they take binary compatibility extremely seriously. Without having checked I'd go out on a limb and say that the 2.x range of commons-lang are probably binary compatible. That's fairly easy to check with the help of Clirr. commons-lang 3.x has its own package space and is therefor shielded from such problems. > Add EMPTY__ARRAY from commons-lang to our CollectionsUtils > -- > > Key: MSHARED-244 > URL: https://jira.codehaus.org/browse/MSHARED-244 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > There are a lot of Classes which need constants for empty arrays like > String[0]. > We shall add such constants to our CollectionUtils. -- 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] (MENFORCER-140) DependencyConvergence: upgrade maven-dependency-tree dependency to 2.0 for better Maven 3 support
[ https://jira.codehaus.org/browse/MENFORCER-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-140. Resolution: Fixed Fix Version/s: 1.2 Assignee: Robert Scholte Fixed in [r1388685|http://svn.apache.org/viewvc?rev=1388685&view=rev] > DependencyConvergence: upgrade maven-dependency-tree dependency to 2.0 for > better Maven 3 support > - > > Key: MENFORCER-140 > URL: https://jira.codehaus.org/browse/MENFORCER-140 > Project: Maven 2.x Enforcer Plugin > Issue Type: Improvement > Components: Standard Rules >Affects Versions: 1.1.1 >Reporter: Herve Boutemy >Assignee: Robert Scholte > Fix For: 1.2 > > > previous version sometimes gives wrong information when run with Maven 3 -- 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] (MCHANGES-289) Please add support for HTTP digest authentication to the 'trac-report' plugin.
Christian Schulte created MCHANGES-289: -- Summary: Please add support for HTTP digest authentication to the 'trac-report' plugin. Key: MCHANGES-289 URL: https://jira.codehaus.org/browse/MCHANGES-289 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: trac Affects Versions: 2.8 Reporter: Christian Schulte Priority: Trivial Currently the 'trac-report' supports only basic HTTP authentication transmitting clear-text credentials. The 'trac-report' should also support the digest HTTP authentication scheme. -- 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] (MCHANGES-289) Please add support for HTTP digest authentication to the 'trac-report' plugin.
[ https://jira.codehaus.org/browse/MCHANGES-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MCHANGES-289: --- Attachment: MCHANGES-289.patch This patch exchanges the default JDK based 'XmlRpcTransportFactory' implementation with the 'commons-httpclient' based implementation supporting HTTP digest authentication. > Please add support for HTTP digest authentication to the 'trac-report' plugin. > -- > > Key: MCHANGES-289 > URL: https://jira.codehaus.org/browse/MCHANGES-289 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: trac >Affects Versions: 2.8 >Reporter: Christian Schulte >Priority: Trivial > Attachments: MCHANGES-289.patch > > > Currently the 'trac-report' supports only basic HTTP authentication > transmitting clear-text credentials. The 'trac-report' should also support > the digest HTTP authentication scheme. -- 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] (DOXIATOOLS-41) Update to Doxia base 1.3
Dennis Lundberg created DOXIATOOLS-41: - Summary: Update to Doxia base 1.3 Key: DOXIATOOLS-41 URL: https://jira.codehaus.org/browse/DOXIATOOLS-41 Project: Maven Doxia Tools Issue Type: Task Components: Doxia Integration Tools Affects Versions: doxia-integration-tools-1.4 Reporter: Dennis Lundberg -- 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] (DOXIATOOLS-42) Upgrade to doxia-sitetools-1.3
Dennis Lundberg created DOXIATOOLS-42: - Summary: Upgrade to doxia-sitetools-1.3 Key: DOXIATOOLS-42 URL: https://jira.codehaus.org/browse/DOXIATOOLS-42 Project: Maven Doxia Tools Issue Type: Task Components: Doxia Integration Tools Affects Versions: doxia-integration-tools-1.4 Reporter: Dennis Lundberg -- 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] (DOXIATOOLS-42) Upgrade to doxia-sitetools-1.3
[ https://jira.codehaus.org/browse/DOXIATOOLS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIATOOLS-42. - Resolution: Fixed Fix Version/s: doxia-integration-tools-1.5 Assignee: Dennis Lundberg Fixed in [r1388697|http://svn.apache.org/viewvc?view=revision&revision=1388697]. > Upgrade to doxia-sitetools-1.3 > -- > > Key: DOXIATOOLS-42 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-42 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Integration Tools >Affects Versions: doxia-integration-tools-1.4 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: doxia-integration-tools-1.5 > > -- 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] (DOXIATOOLS-41) Update to Doxia base 1.3
[ https://jira.codehaus.org/browse/DOXIATOOLS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIATOOLS-41. - Resolution: Fixed Fix Version/s: doxia-integration-tools-1.5 Assignee: Dennis Lundberg Fixed in [r1388696|http://svn.apache.org/viewvc?view=revision&revision=1388696]. > Update to Doxia base 1.3 > > > Key: DOXIATOOLS-41 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-41 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Integration Tools >Affects Versions: doxia-integration-tools-1.4 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: doxia-integration-tools-1.5 > > -- 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] (MWAR-164) Support for specifying which encoding to use when filtering resources
[
https://jira.codehaus.org/browse/MWAR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309488#comment-309488
]
Dennis Lundberg commented on MWAR-164:
--
A new 2.3-SNAPSHOT has now been deployed.
Please help us test this issue.
> Support for specifying which encoding to use when filtering resources
> -
>
> Key: MWAR-164
> URL: https://jira.codehaus.org/browse/MWAR-164
> Project: Maven 2.x WAR Plugin
> Issue Type: Improvement
> Components: filtering
>Affects Versions: 2.1-alpha-1
>Reporter: kai lilleby
>Assignee: Dennis Lundberg
> Fix For: 2.3
>
> Attachments: MWAR-164-maven-war-plugin.patch
>
>
> Quoting Hervé:
> {quote}
> Maven filtering provides an encoding parameter to set encoding used when
> reading/writing files. But war plugin uses null value, which means platform
> encoding... Sorry, encoding support won't be totally "free" ;)
> I added TODOs in the code.
> For web.xml and container config XML file, I set encoding to UTF-8, which is a
> better default value than platform encoding.
> For other filtered resources, you'll need to add an encoding attribute to
> o.a.m.model.Resource class, to let the user define which encoding he wants to
> use when filtering. Perhaps using project.build.sourceEncoding as a default
> value is a good idea.
> Seems like this is worth a Jira issue to track this new feature.
> {quote}
--
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] (MSHARED-244) Add EMPTY_xxxx_ARRAY from commons-lang to our CollectionsUtils
[ https://jira.codehaus.org/browse/MSHARED-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309491#comment-309491 ] Mark Struberg commented on MSHARED-244: --- yes, commons is really good in those regards. But that doesn't help you if we use a method from a newer commons release and some plugin adds in an old jar which doesnt have this method. I think we still do client-Classloader-first in maven. So I expect a few "Class X cannot be cast to Class X". We would need to check, but I have a bad gut feeling. > Add EMPTY__ARRAY from commons-lang to our CollectionsUtils > -- > > Key: MSHARED-244 > URL: https://jira.codehaus.org/browse/MSHARED-244 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-shared-utils >Reporter: Mark Struberg >Assignee: Mark Struberg > > There are a lot of Classes which need constants for empty arrays like > String[0]. > We shall add such constants to our CollectionUtils. -- 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] (MCHANGELOG-131) Resource bundle for Spanish Argentina
[ https://jira.codehaus.org/browse/MCHANGELOG-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309492#comment-309492 ] Olivier Lamy commented on MCHANGELOG-131: - can you please use escape unicode ? Your patch has a wrong encoding. Thanks. > Resource bundle for Spanish Argentina > - > > Key: MCHANGELOG-131 > URL: https://jira.codehaus.org/browse/MCHANGELOG-131 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Gabriel Belingueres >Priority: Minor > Attachments: scm-activity_es_AR.properties > > > I created an scm-activity_es_AR.properties file to support Spanish Argentina, > which I attach to this issue. > Regards, > Gabriel -- 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] (MCHANGELOG-130) NullPointerException when no SCM is defined
[ https://jira.codehaus.org/browse/MCHANGELOG-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCHANGELOG-130. --- Resolution: Fixed Fix Version/s: 2.3 Assignee: Olivier Lamy Fixed. Thanks! > NullPointerException when no SCM is defined > - > > Key: MCHANGELOG-130 > URL: https://jira.codehaus.org/browse/MCHANGELOG-130 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: Win 7, Java 6, Maven 3.0.4 >Reporter: Gabriel Belingueres >Assignee: Olivier Lamy >Priority: Minor > Fix For: 2.3 > > > A NullPointerException occurs on line 1495 of class ChangeLogReport, when the > pom.xml file does not specify a scm tag, even if the > is specified. > From what I saw in the code, the offending line is (in generateLinks() > method): > if ( !scmUrl.equals( linkFile ) ) > reversing the comparison should be sufficient (I think): > if ( !linkFile.equals( scmUrl ) ) > Regards, > Gabriel -- 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-70) external.png is used in css but not present in code base
[ https://jira.codehaus.org/browse/MSKINS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSKINS-70. -- Resolution: Fixed Fix Version/s: fluido-1.3.1 patch applied. Thanks! > external.png is used in css but not present in code base > > > Key: MSKINS-70 > URL: https://jira.codehaus.org/browse/MSKINS-70 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Eric Barboni >Assignee: Olivier Lamy >Priority: Trivial > Fix For: fluido-1.3.1 > > Attachments: maven-theme.css.patch > > > Proposed patch is to remove reference in css. > But can be the other way around adding external.png to code base. -- 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] (MCHANGELOG-131) Resource bundle for Spanish Argentina
[ https://jira.codehaus.org/browse/MCHANGELOG-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Belingueres updated MCHANGELOG-131: --- Attachment: scm-activity_es_AR.properties Hi: Changed the unicode chars for their codes. Also changed some translations. I checked out the plugin src and tested the site generation with "es" locale. Worked OK. Thanks!!! > Resource bundle for Spanish Argentina > - > > Key: MCHANGELOG-131 > URL: https://jira.codehaus.org/browse/MCHANGELOG-131 > Project: Maven 2.x Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Gabriel Belingueres >Priority: Minor > Attachments: scm-activity_es_AR.properties, > scm-activity_es_AR.properties > > > I created an scm-activity_es_AR.properties file to support Spanish Argentina, > which I attach to this issue. > Regards, > Gabriel -- 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
