[jira] (MEJB-58) Documentation fails to mention where and how the plugin gets ejb-jar.xml from
paul hinds created MEJB-58: -- Summary: Documentation fails to mention where and how the plugin gets ejb-jar.xml from Key: MEJB-58 URL: https://jira.codehaus.org/browse/MEJB-58 Project: Maven 2.x EJB Plugin Issue Type: Improvement Affects Versions: 2.3 Environment: na Reporter: paul hinds Priority: Minor I have a build failing since the ejb plugin can not find ejb-jar.xml and the documentation conspicuously fails to mention where it needs to be. http://maven.apache.org/plugins/maven-ejb-plugin/index.html All this plugin does is make a jar with some predefined resources so it is important that the docs explain what it is doing. Maven3 hardcodes various locations of files and if they are not documented it is not possible to use the system. Previous maven versions let you defined where ejb-jar.xml comes from, now it has to be somewhere specific but where it needs to be is only specified in the source code. -- 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-876) surefire-junit47 does not work in an OSGi classloader environment
Jan Sievers created SUREFIRE-876: Summary: surefire-junit47 does not work in an OSGi classloader environment Key: SUREFIRE-876 URL: https://jira.codehaus.org/browse/SUREFIRE-876 Project: Maven Surefire Issue Type: Improvement Components: classloading, Junit 4.7+ (parallel) support Affects Versions: 2.10 Reporter: Jan Sievers while trying to port JUnitCoreProvider to tycho, I noticed that it fails with an NPE when run inside an OSGi environment. The root cause is really JUnit bug https://github.com/KentBeck/junit/issues/364 JUnit uses Class.forName() to load the test class which assumes the JUnit classloader can always load test classes, which is not true in an OSGi classloader environment. While this should be fixed in JUnit, it's easy to work around this issue in surefire. It's not necessary to use the offending org.junit.runner.Description.getTestClass() in JUnitCoreRunListener.fillTestCountMap(). We can use String getClassName() instead to circumvent classloading issues as we only need the class name anyway. I will attach a patch. -- 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-644) NullPointerException when site URL is not defined in distributionManagement
[
https://jira.codehaus.org/browse/MSITE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301209#comment-301209
]
Lukas Theussl commented on MSITE-644:
-
What's the point in having a distributionManagement.site with only an id?
NullPointerException when site URL is not defined in distributionManagement
---
Key: MSITE-644
URL: https://jira.codehaus.org/browse/MSITE-644
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.0, 3.1
Reporter: Samuel Langlois
Priority: Minor
Attachments: pom.xml
If you forget to specify the url in the site section:
{code}
distributionManagement
site
idalfresco.website/id
/site
/distributionManagement
{code}
you get a nasty NullPointerException.
{code}
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project
alfresco: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
project alfresco: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site
failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.NullPointerException
at java.io.File.init(File.java:222)
at
org.apache.maven.doxia.tools.DefaultSiteTool.urlEncode(DefaultSiteTool.java:1478)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDistMgmntSiteUrl(DefaultSiteTool.java:1451)
at
org.apache.maven.doxia.tools.DefaultSiteTool.appendMenuItem(DefaultSiteTool.java:1380)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenuItemsFromModels(DefaultSiteTool.java:1344)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:905)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:488)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:286)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
{code}
You can try executing {{mvn site -N}} with the attached pom file.
--
This message is
[jira] (MRELEASE-772) mvn release:prepare fails with IOException and a write error (Access is denied)
[
https://jira.codehaus.org/browse/MRELEASE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301211#comment-301211
]
Svend Hansen commented on MRELEASE-772:
---
Hmm... It looks like it creates the basic p4 command:
{{Commandline command = PerforceScmProvider.createP4Command( repo,
workingDirectory );}}
then it adds the edit:
{{command.createArg().setValue( edit );}}
and _then_ it has a try-catch where it tries to add the files, where it looks
like this line:
{{String canfile = file.getCanonicalPath();}}
is throwing an exception:
{{java.io.IOException: The filename, directory name, or volume label syntax is
incorrect}}
So I guess it's just the first exception that matters, and the following errors
are just caused by that one.
But why is it failing to canonicalize the file path?
mvn release:prepare fails with IOException and a write error (Access is
denied)
---
Key: MRELEASE-772
URL: https://jira.codehaus.org/browse/MRELEASE-772
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.3.1
Environment: Windows 7 both command prompt and cygwin using Perforce
for SCM
Reporter: Svend Hansen
Attachments: maven-release-error.txt,
mvn_release_output_x_client_env.txt, mvn_release_output_x.txt
When running
{{mvn release:prepare -Dusername=perforce_user
-Dpassword=perforce_password}}
I get the errors:
* java.io.IOException: The filename, directory name, or volume label syntax
is incorrect
* [ERROR] CommandLineException Exit code: 1 - Usage: add/edit/delete [-c
changelist#] [ -d -f -k -n -v ] [-t type] files...
Missing/wrong number of arguments.
* [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.1:prepare (default-cli) on
project root-project: Error writing POM: D:\Server\pom.xml (Access is denied)
- [Help 1]
The full output is attached.
Sometimes I also get the error:
* [ERROR] D:\Server\pom.xml - file(s) not in client view.
Though I created the client in the same location I'm running from, and I'm
not sure that error is related to the others (as the others also occur when
that one doesn't).
It's been suggested (on stackoverflow:
http://stackoverflow.com/questions/10999403/maven-releaseprepare-ioexception)
that the error has to do with my D drive being a mapped drive, though I don't
think it is as it's not listed if I run {{subst}}. However, I think it _must_
be at least a partition on the same hard drive, unless my PC has three
physical drives :P (work PC), but I guess that shouldn't make any difference
to the program?
--
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-644) NullPointerException when site URL is not defined in distributionManagement
[
https://jira.codehaus.org/browse/MSITE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301212#comment-301212
]
Samuel Langlois commented on MSITE-644:
---
I completely agree that it makes no sense!
It's just that if the error had been a little nicer, I would not have spent one
hour searching why the site generation failed :-)
Anyway, even if it is never fixed, people who google this error will hopefully
get to this page now...
NullPointerException when site URL is not defined in distributionManagement
---
Key: MSITE-644
URL: https://jira.codehaus.org/browse/MSITE-644
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.0, 3.1
Reporter: Samuel Langlois
Priority: Minor
Attachments: pom.xml
If you forget to specify the url in the site section:
{code}
distributionManagement
site
idalfresco.website/id
/site
/distributionManagement
{code}
you get a nasty NullPointerException.
{code}
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project
alfresco: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
project alfresco: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site
failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.NullPointerException
at java.io.File.init(File.java:222)
at
org.apache.maven.doxia.tools.DefaultSiteTool.urlEncode(DefaultSiteTool.java:1478)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDistMgmntSiteUrl(DefaultSiteTool.java:1451)
at
org.apache.maven.doxia.tools.DefaultSiteTool.appendMenuItem(DefaultSiteTool.java:1380)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenuItemsFromModels(DefaultSiteTool.java:1344)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenu(DefaultSiteTool.java:905)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:488)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:286)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:154)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
[jira] (SUREFIRE-876) surefire-junit47 does not work in an OSGi classloader environment
[ https://jira.codehaus.org/browse/SUREFIRE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301222#comment-301222 ] Jan Sievers commented on SUREFIRE-876: -- I created pull request https://github.com/apache/maven-surefire/pull/4 surefire-junit47 does not work in an OSGi classloader environment - Key: SUREFIRE-876 URL: https://jira.codehaus.org/browse/SUREFIRE-876 Project: Maven Surefire Issue Type: Improvement Components: classloading, Junit 4.7+ (parallel) support Affects Versions: 2.10 Reporter: Jan Sievers while trying to port JUnitCoreProvider to tycho, I noticed that it fails with an NPE when run inside an OSGi environment. The root cause is really JUnit bug https://github.com/KentBeck/junit/issues/364 JUnit uses Class.forName() to load the test class which assumes the JUnit classloader can always load test classes, which is not true in an OSGi classloader environment. While this should be fixed in JUnit, it's easy to work around this issue in surefire. It's not necessary to use the offending org.junit.runner.Description.getTestClass() in JUnitCoreRunListener.fillTestCountMap(). We can use String getClassName() instead to circumvent classloading issues as we only need the class name anyway. I will attach a patch. -- 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] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301225#comment-301225 ] Kristoffer Peterhansel commented on MNG-3092: - Like [~soeren.chittka] and [~herder] said. It makes no sense for the pre-release version of an excluded version to be included in the build. Just had to work around this myself with using a very high (sub next major) version for the range boundary. Version ranges with non-snapshot bounds can contain snapshot versions - Key: MNG-3092 URL: https://jira.codehaus.org/browse/MNG-3092 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Reporter: Mark Hobson Attachments: MNG-3092.patch Contrary to the 2.0 design docs: Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary. -- from http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification The following is equates to true: VersionRange.createFromVersionSpec( [1.0,1.1] ).containsVersion( new DefaultArtifactVersion( 1.1-SNAPSHOT ) ) The attached patch only allows snapshot versions to be contained in a range if they are equal to one of the boundaries. Note that this is a strict equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-847) surefire cannot run single testng test
[
https://jira.codehaus.org/browse/SUREFIRE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301227#comment-301227
]
Gabriele Catania commented on SUREFIRE-847:
---
We are having the same issue.
On Linux machines the {{-Dtest=TestCassName}} argument is honored, while on
Windows machines it fails the build with no tests found.
surefire cannot run single testng test
---
Key: SUREFIRE-847
URL: https://jira.codehaus.org/browse/SUREFIRE-847
Project: Maven Surefire
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.12
Environment: Windows 7 x64
Reporter: Nikita Makarov
Priority: Minor
Trying to run single testng test class with command mvn test -Dtest=SomeTest
fails with message
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
project web-integration-tests: No tests were executed!
(Set -DfailIfNoTests=false to ignore this error.) - [Help 1].
--
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-844) test parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11)
[ https://jira.codehaus.org/browse/SUREFIRE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301228#comment-301228 ] Gabriele Catania commented on SUREFIRE-844: --- I can confirm that it works on Linux (ubuntu precise) but doesn't on windows test parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11) Key: SUREFIRE-844 URL: https://jira.codehaus.org/browse/SUREFIRE-844 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.12 Environment: JDK 1.7.0_02, Windows 7. Reporter: Mark Ziesemer Attachments: SUREFIRE-844-2.11.txt, SUREFIRE-844-2.12.txt, SUREFIRE-844.zip Maven is configured with JUnit 4.10. Assume a 'MyTest' class with public, non-static, 0-arg methods annotated with org.junit.Test. This was working with Surefire 2.9, 2.10, and 2.11 (and probably earlier): plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.11/version configuration testcom.example.MyTest/test /configuration /plugin With only updating the Surefire version from 2.11 to 2.12, the tests no longer execute: --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 I don't see anything in the release announcement that should account for this. If I remove the 'test' parameter entirely, it will again successfully run - but will run all tests that it finds instead of what I'm expecting it to run. I can't attach any additional details from what I'm currently working on, but will work on providing a proper minimal test case over the weekend. -- 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-827) Surefire 2.12 cannot run a single test, regression from 2.11
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301229#comment-301229 ] Gabriele Catania commented on SUREFIRE-827: --- It works on my linux installation, but doesn't on my colleagues' windows ones. we are using TestNG with surefire 2.12. Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul Assignee: Kristian Rosenvold Attachments: BUG-827.zip # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- 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-774) CLONE - mvn release:prepare fails with IOException and a write error (Access is denied)
Robert Scholte created MRELEASE-774:
---
Summary: CLONE - mvn release:prepare fails with IOException and a
write error (Access is denied)
Key: MRELEASE-774
URL: https://jira.codehaus.org/browse/MRELEASE-774
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.3.1
Environment: Windows 7 both command prompt and cygwin using Perforce
for SCM
Reporter: Robert Scholte
Attachments: maven-release-error.txt,
mvn_release_output_x_client_env.txt, mvn_release_output_x.txt
When running
{{mvn release:prepare -Dusername=perforce_user
-Dpassword=perforce_password}}
I get the errors:
* java.io.IOException: The filename, directory name, or volume label syntax is
incorrect
* [ERROR] CommandLineException Exit code: 1 - Usage: add/edit/delete [-c
changelist#] [ -d -f -k -n -v ] [-t type] files...
Missing/wrong number of arguments.
* [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.1:prepare (default-cli) on
project root-project: Error writing POM: D:\Server\pom.xml (Access is denied)
- [Help 1]
The full output is attached.
Sometimes I also get the error:
* [ERROR] D:\Server\pom.xml - file(s) not in client view.
Though I created the client in the same location I'm running from, and I'm not
sure that error is related to the others (as the others also occur when that
one doesn't).
It's been suggested (on stackoverflow:
http://stackoverflow.com/questions/10999403/maven-releaseprepare-ioexception)
that the error has to do with my D drive being a mapped drive, though I don't
think it is as it's not listed if I run {{subst}}. However, I think it _must_
be at least a partition on the same hard drive, unless my PC has three physical
drives :P (work PC), but I guess that shouldn't make any difference to the
program?
--
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-678) CLONE - mvn release:prepare fails with IOException and a write error (Access is denied)
[
https://jira.codehaus.org/browse/SCM-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte moved MRELEASE-774 to SCM-678:
-
Complexity: Intermediate
Component/s: (was: prepare)
maven-scm-provider-perforce
Affects Version/s: (was: 2.3.1)
1.7
Key: SCM-678 (was: MRELEASE-774)
Project: Maven SCM (was: Maven 2.x Release Plugin)
CLONE - mvn release:prepare fails with IOException and a write error (Access
is denied)
---
Key: SCM-678
URL: https://jira.codehaus.org/browse/SCM-678
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-perforce
Affects Versions: 1.7
Environment: Windows 7 both command prompt and cygwin using Perforce
for SCM
Reporter: Robert Scholte
Attachments: maven-release-error.txt,
mvn_release_output_x_client_env.txt, mvn_release_output_x.txt
When running
{{mvn release:prepare -Dusername=perforce_user
-Dpassword=perforce_password}}
I get the errors:
* java.io.IOException: The filename, directory name, or volume label syntax
is incorrect
* [ERROR] CommandLineException Exit code: 1 - Usage: add/edit/delete [-c
changelist#] [ -d -f -k -n -v ] [-t type] files...
Missing/wrong number of arguments.
* [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.1:prepare (default-cli) on
project root-project: Error writing POM: D:\Server\pom.xml (Access is denied)
- [Help 1]
The full output is attached.
Sometimes I also get the error:
* [ERROR] D:\Server\pom.xml - file(s) not in client view.
Though I created the client in the same location I'm running from, and I'm
not sure that error is related to the others (as the others also occur when
that one doesn't).
It's been suggested (on stackoverflow:
http://stackoverflow.com/questions/10999403/maven-releaseprepare-ioexception)
that the error has to do with my D drive being a mapped drive, though I don't
think it is as it's not listed if I run {{subst}}. However, I think it _must_
be at least a partition on the same hard drive, unless my PC has three
physical drives :P (work PC), but I guess that shouldn't make any difference
to the program?
--
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-161) Exclude ignored for sources generated during the generate-sources phase
[
https://jira.codehaus.org/browse/MCOMPILER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301250#comment-301250
]
Chris Eineke commented on MCOMPILER-161:
Same problem exists with v2.2.1 (rdebian-8).
Exclude ignored for sources generated during the generate-sources phase
---
Key: MCOMPILER-161
URL: https://jira.codehaus.org/browse/MCOMPILER-161
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.3.2
Environment: Win7, JDK 7, maven 3.0.3,
Reporter: Laurent Foret
I try in a pom to excludes an unwanted generated package during the
generate-sources phase, but without success.
Indeed according to the following pom.xml :
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
excludes
exclude**/generated/*/exclude
/excludes
/configuration
/plugin
plugin
groupIdorg.apache.cxf/groupId
artifactIdcxf-codegen-plugin/artifactId
version${cxf.version}/version
executions
execution
idregistry/id
phasegenerate-sources/phase
goals
goalwsdl2java/goal
/goals
/execution
/executions
I expected to have every generated java source file in a package which is
called *.generated.* not to be compiled.
Exclusion works for all package in my normal src/main/java source directory
but not in my target/generated-sources/cxf generated source directory.
--
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-161) Exclude ignored for sources generated during the generate-sources phase
[
https://jira.codehaus.org/browse/MCOMPILER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301250#comment-301250
]
Chris Eineke edited comment on MCOMPILER-161 at 6/15/12 1:25 PM:
-
Same problem exists with v2.2.1 (rdebian-8). Maven compiler plugin is v2.5.
was (Author: ceineke):
Same problem exists with v2.2.1 (rdebian-8).
Exclude ignored for sources generated during the generate-sources phase
---
Key: MCOMPILER-161
URL: https://jira.codehaus.org/browse/MCOMPILER-161
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.3.2
Environment: Win7, JDK 7, maven 3.0.3,
Reporter: Laurent Foret
I try in a pom to excludes an unwanted generated package during the
generate-sources phase, but without success.
Indeed according to the following pom.xml :
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
excludes
exclude**/generated/*/exclude
/excludes
/configuration
/plugin
plugin
groupIdorg.apache.cxf/groupId
artifactIdcxf-codegen-plugin/artifactId
version${cxf.version}/version
executions
execution
idregistry/id
phasegenerate-sources/phase
goals
goalwsdl2java/goal
/goals
/execution
/executions
I expected to have every generated java source file in a package which is
called *.generated.* not to be compiled.
Exclusion works for all package in my normal src/main/java source directory
but not in my target/generated-sources/cxf generated source directory.
--
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-848) NPE in org.apache.maven.plugin.surefire.report.AbstractTextReporter
[
https://jira.codehaus.org/browse/SUREFIRE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301255#comment-301255
]
Zemian Deng commented on SUREFIRE-848:
--
I get this same error intermittently on our java project build. We are using
maven-surefire-plugin:2.11 with maven-3.0.4. When this happens our build seems
to take same amount of time, but the test counts and output are way off.
Exception in thread ThreadedStreamConsumer java.lang.NullPointerException
at
org.apache.maven.surefire.report.AbstractFileReporter.testSetCompleted(AbstractFileReporter.java:111)
at
org.apache.maven.surefire.report.MulticastingReporter.testSetCompleted(MulticastingReporter.java:51)
at
org.apache.maven.surefire.report.TestSetRunListener.testSetCompleted(TestSetRunListener.java:121)
at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:97)
at
org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67)
at java.lang.Thread.run(Thread.java:619)
NPE in org.apache.maven.plugin.surefire.report.AbstractTextReporter
---
Key: SUREFIRE-848
URL: https://jira.codehaus.org/browse/SUREFIRE-848
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.x support, Maven Surefire Plugin
Affects Versions: 2.12
Reporter: Stephan Schroevers
Attachments: example.tbz
The combination Surefire/JUnit 4 causes a {{NullPointerException}} in
{{org.apache.maven.plugin.surefire.report.AbstractTextReporter}} if one has a
{{RunListener}} configured which (for whatever reason) throws an exception
in its {{#testRunStarted(Description)}} method.
I have [attached|^example.tbz] a dummy project; run {{`mvn test`}} to see the
problem. The cause of this issue is that {{AbstractTextReporter}} initializes
its {{testResults}} field when
{{AbstractTextReporter#testSetStarting(ReportEntry)}} is called, which (it
seems) doesn't happen until JUnit invokes
{{RunNotifier#fireTestStarted(Description)}}. This is too late, because an
exception during the invocation of
{{RunNotifier#fireTestRunStarted(Description)}} causes
{{AbstractTextReporter#testError(ReportEntry, String, String)}} to be
invoked. The result is an NPE on line 103.
Stacktrace:
{noformat}
Exception in thread ThreadedStreamConsumer java.lang.NullPointerException
at
org.apache.maven.plugin.surefire.report.AbstractTextReporter.testError(AbstractTextReporter.java:103)
at
org.apache.maven.plugin.surefire.report.MulticastingReporter.testError(MulticastingReporter.java:87)
at
org.apache.maven.plugin.surefire.report.TestSetRunListener.testError(TestSetRunListener.java:150)
at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:115)
at
org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67)
at java.lang.Thread.run(Thread.java:619)
{noformat}
Note that this issue seems to have been the root cause of SUREFIRE-157; the
[last
comment|jira.codehaus.org/browse/SUREFIRE-157?focusedCommentId=197215#comment-197215]
to that ticket also pointed to the late initialisation of the
{{testResults}} field.
--
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-877) Surefire doesn't support mixed TestNG 6.5.x config parameter
Oleg Rekutin created SUREFIRE-877: - Summary: Surefire doesn't support mixed TestNG 6.5.x config parameter Key: SUREFIRE-877 URL: https://jira.codehaus.org/browse/SUREFIRE-877 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.12 Reporter: Oleg Rekutin Priority: Minor Specifying: property namemixed/name valuetrue/value /property causes org.apache.maven.surefire.util.SurefireReflectionException: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean at org.testng.TestNG.configure(TestNG.java:1522) at org.apache.maven.surefire.testng.conf.TestNGMapConfigurator.configure(TestNGMapConfigurator.java:95) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:73) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115) ... 9 more -- 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
