[jira] (MPLUGIN-197) Subversion sources of 'maven-plugin-tools-model' doesn't correspond with binary package (missing classes).
Tinguaro Barreno created MPLUGIN-197: Summary: Subversion sources of 'maven-plugin-tools-model' doesn't correspond with binary package (missing classes). Key: MPLUGIN-197 URL: https://jira.codehaus.org/browse/MPLUGIN-197 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: Metadata Model Affects Versions: 2.9, 2.7, 2.6 Environment: Any Reporter: Tinguaro Barreno Priority: Trivial Hi, I've checked-out the Maven Plugin Tools from SubVersion on Eclipse and it warns about missing classes. The 'maven-plugin-tools-model' (in trunk or any-tag) only includes: -- . |-- pom.xml |-- src | |-- main | | |-- java | | | `-- org | | | `-- apache | | | `-- maven | | | `-- plugin | | | `-- tools | | | `-- model | | | |-- PluginMetadataParseException.java | | | `-- PluginMetadataParser.java | | `-- mdo | | `-- plugin-metadata.mdo ... -- However, the 'maven-plugin-tools-model-2.9-sources.jar' contains: -- . ... `-- org `-- apache `-- maven `-- plugin `-- tools `-- model |-- Component.java |-- io | `-- xpp3 | |-- PluginMetadataXpp3Reader.java | `-- PluginMetadataXpp3Writer.java |-- LifecycleExecution.java |-- Mojo.java |-- Parameter.java |-- PluginMetadata.java |-- PluginMetadataParseException.java `-- PluginMetadataParser.java -- Maybe a forgotten 'svn add'? Best wishes. -- 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-122) Analyze target does not work correctly when only using a constant defined in a different module
[
https://jira.codehaus.org/browse/MDEP-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298909#comment-298909
]
Mark Michaelis commented on MDEP-122:
-
For now I am using a workaround for this issue: I use the classes once in my
code. For example with such a (most of the time) hidden log-statement (here:
slf4j):
{code:java}
// Workaround for MDEP-122: Use class once.
LOG.trace("Using constants from {}.", ConstantsClass.class.getName());
{code}
> Analyze target does not work correctly when only using a constant defined in
> a different module
> ---
>
> Key: MDEP-122
> URL: https://jira.codehaus.org/browse/MDEP-122
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
>Affects Versions: 2.0-alpha-4
> Environment: Windows.
> Maven 2.0.6
> Java 1.5 compiler
>Reporter: Iker Almandoz
>Assignee: Brian Fox
>Priority: Minor
> Attachments: analyze.zip, maven_bug.zip
>
>
> I have 2 projects as seen in the attached files.
> My first project contains a single interface that defines a String constant.
> My second project, uses the String constant from my first project.
> When i try to use dependency:analyze to fail the build as seen below, i can't
> make the system work.
> If i add the dependency from project 2 to project 1, i get:
> [INFO] [dependency:analyze {execution: analyze}]
> [INFO] Used declared dependencies:
> [INFO]None
> [INFO] Used undeclared dependencies:
> [WARNING]None
> [INFO] Unused declared dependencies:
> [INFO]test:project1:jar: 1.0-SNAPSHOT:compile
> [WARNING] Potential problems discovered.
> But if i remove it, i get:
> If i remove the supposedly unused dependency, then I get a compile error:
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
> C:\ASSIA\development\maven_bug\project2\src\main\java\project2\NamesUser.java:[6
> ,24] package project1 does not exist
> Here is the build definition i have...
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> analyze
> package
>
> analyze
>
>
> true
> false
>
>
>
>
>
>
--
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] (MPLUGIN-198) Missing 'Requirements' class in Subversion code
Tinguaro Barreno created MPLUGIN-198: Summary: Missing 'Requirements' class in Subversion code Key: MPLUGIN-198 URL: https://jira.codehaus.org/browse/MPLUGIN-198 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: Plugin Plugin Affects Versions: 2.9, 2.8, 2.7, 2.6, 2.5 Environment: Any Reporter: Tinguaro Barreno Priority: Trivial Hi, The 'Requirements.java' file is missing in SubVersion sources but it exists in the sources package. Maybe a forgotten 'svn add'. Best wishes. -- 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] (MPLUGIN-198) Missing 'Requirements' class in Subversion code
[
https://jira.codehaus.org/browse/MPLUGIN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPLUGIN-198.
--
Resolution: Not A Bug
Assignee: Robert Scholte
Try {{mvn generate-sources}} first, this will uhm... generate the sources based
on the .mdo file. Read http://modello.codehaus.org/index.html for details.
> Missing 'Requirements' class in Subversion code
> ---
>
> Key: MPLUGIN-198
> URL: https://jira.codehaus.org/browse/MPLUGIN-198
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 2.5, 2.6, 2.7, 2.8, 2.9
> Environment: Any
>Reporter: Tinguaro Barreno
>Assignee: Robert Scholte
>Priority: Trivial
>
> Hi,
> The 'Requirements.java' file is missing in SubVersion sources but it exists
> in the sources package.
> Maybe a forgotten 'svn add'.
> Best wishes.
--
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] (MPLUGIN-197) Subversion sources of 'maven-plugin-tools-model' doesn't correspond with binary package (missing classes).
[ https://jira.codehaus.org/browse/MPLUGIN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MPLUGIN-197. -- Resolution: Duplicate Assignee: Robert Scholte Duplicate of MPLUGIN-198 > Subversion sources of 'maven-plugin-tools-model' doesn't correspond with > binary package (missing classes). > -- > > Key: MPLUGIN-197 > URL: https://jira.codehaus.org/browse/MPLUGIN-197 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: Metadata Model >Affects Versions: 2.6, 2.7, 2.9 > Environment: Any >Reporter: Tinguaro Barreno >Assignee: Robert Scholte >Priority: Trivial > > Hi, > I've checked-out the Maven Plugin Tools from SubVersion on Eclipse and it > warns about missing classes. > The 'maven-plugin-tools-model' (in trunk or any-tag) only includes: > -- > . > |-- pom.xml > |-- src > | |-- main > | | |-- java > | | | `-- org > | | | `-- apache > | | | `-- maven > | | | `-- plugin > | | | `-- tools > | | | `-- model > | | | |-- PluginMetadataParseException.java > | | | `-- PluginMetadataParser.java > | | `-- mdo > | | `-- plugin-metadata.mdo > ... > -- > However, the 'maven-plugin-tools-model-2.9-sources.jar' contains: > -- > . > ... > `-- org > `-- apache > `-- maven > `-- plugin > `-- tools > `-- model > |-- Component.java > |-- io > | `-- xpp3 > | |-- PluginMetadataXpp3Reader.java > | `-- PluginMetadataXpp3Writer.java > |-- LifecycleExecution.java > |-- Mojo.java > |-- Parameter.java > |-- PluginMetadata.java > |-- PluginMetadataParseException.java > `-- PluginMetadataParser.java > -- > Maybe a forgotten 'svn add'? > Best wishes. -- 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-639) sub-project tries to fetch a site_en.xml even though no locales are configured
[ https://jira.codehaus.org/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298936#comment-298936 ] JoelC commented on MSITE-639: - I have the same issue running Maven 3.0.4 and Java 5. Big impediment to moving to Maven 3 since my company has thousands of Maven projects. A workaround is to add an empty (or one line) site_en.xml file to each parent pom project, but that is a real pain. > sub-project tries to fetch a site_en.xml even though no locales are configured > -- > > Key: MSITE-639 > URL: https://jira.codehaus.org/browse/MSITE-639 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-3 > Environment: Windows 7 64bit, Sun JDK 1.6.0_27 >Reporter: Martin Goldhahn > Attachments: parent-project.zip, sub-project.zip > > > I have a parent project that has a site descriptor and a pom project that has > the parent project as parent. Neither of them defines the locales parameter > of the site plugin. > When I try to build the sub-project, I get an error that Maven cannot find > the site_en.xml descriptor of the parent project. Why doesn't it just use the > site.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] (MCLEAN-48) Failure cleaning files containing special characters
[ https://jira.codehaus.org/browse/MCLEAN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298938#comment-298938 ] Robert Scholte commented on MCLEAN-48: -- I can't reproduce it on my Win7 machine. I've created on IT in [r1339305|http://svn.apache.org/viewvc?rev=1339305&view=rev] for it. Maybe somebody can verify it for Linux. > Failure cleaning files containing special characters > > > Key: MCLEAN-48 > URL: https://jira.codehaus.org/browse/MCLEAN-48 > Project: Maven 2.x Clean Plugin > Issue Type: Bug >Affects Versions: 2.4.1 > Environment: Ubuntu 10.10 > LANG=en_DK.utf8 >Reporter: Stefan Meisner Larsen > > I am not able to clean my project which contains files named with special > characters. It seems as though the plugin does not handle UTF-8 correctly. > Name of file as reported by find command: > ./ewp-fr/ewp-fr.war/src/main/webapp/secure/fr/Conditions_générales_d'isalaire.pdf > Output from clean: > . > . > . > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean (default-clean) on > project ewp-fr.war: Failed to clean project: Failed to delete > /home/stefan/trifork/lessor/ewp-clean/trunk/ewp-fr/ewp-fr.war/target/ewp-fr.war-1.69-SNAPSHOT/secure/fr/Conditions_g??n??rales_d'isalaire.pdf > -> [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] (MRELEASE-654) Release:perform fails on releasing a tag from an empty directory
[
https://jira.codehaus.org/browse/MRELEASE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298941#comment-298941
]
Robert Scholte commented on MRELEASE-654:
-
James,
look at your log once more:
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli)
{quote}
So you're using version 2.0, so please lock the version to 2.3 and try again.
> Release:perform fails on releasing a tag from an empty directory
>
>
> Key: MRELEASE-654
> URL: https://jira.codehaus.org/browse/MRELEASE-654
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix"
>Reporter: Giacomo Boccardo
>
> If we release our project from the same directory when we executed the
> release:prepare the perform phase completes successfully, while performing a
> release from a tag (in an empty directory) we have the following stack trace:
> {noformat}
> $ mvn release:perform -Dtag=unilet-base-5.3.13
> -DconnectionUrl=scm:svn:https://srvdevel.unimatica.lan/svn/unilet -X
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix"
> [INFO] Error stacktraces are turned on.
> [DEBUG] Reading global settings from /usr/local/app/maven/conf/settings.xml
> [DEBUG] Reading user settings from /home/gboccardo/.m2/settings.xml
> [DEBUG] Using local repository at /home/gboccardo/.m2/repository
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
> /home/gboccardo/.m2/repository
> [INFO] Scanning for projects...
> [DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1:
> (none)
> [DEBUG] Looking up lifecyle mappings for packaging pom from
> ClassRealm[plexus.core, parent: null]
> [DEBUG] Resolving plugin prefix release from [org.apache.maven.plugins,
> org.codehaus.mojo]
> [DEBUG] Resolved plugin prefix release to
> org.apache.maven.plugins:maven-release-plugin from POM
> org.apache.maven:standalone-pom:pom:1
> [DEBUG] === REACTOR BUILD PLAN
>
> [DEBUG] Project: org.apache.maven:standalone-pom:pom:1
> [DEBUG] Tasks: [release:perform]
> [DEBUG] Style: Aggregating
> [DEBUG]
> ===
> [INFO]
>
> [INFO]
>
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
>
> [DEBUG] Resolving plugin prefix release from [org.apache.maven.plugins,
> org.codehaus.mojo]
> [DEBUG] Resolved plugin prefix release to
> org.apache.maven.plugins:maven-release-plugin from POM
> org.apache.maven:standalone-pom:pom:1
> [DEBUG] Lifecycle default -> [validate, initialize, generate-sources,
> process-sources, generate-resources, process-resources, compile,
> process-classes, generate-test-sources, process-test-sources,
> generate-test-resources, process-test-resources, test-compile,
> process-test-classes, test, prepare-package, package, pre-integration-test,
> integration-test, post-integration-test, verify, install, deploy]
> [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
> [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
> [DEBUG] === PROJECT BUILD PLAN
>
> [DEBUG] Project: org.apache.maven:standalone-pom:1
> [DEBUG] Dependencies (collect): []
> [DEBUG] Dependencies (resolve): []
> [DEBUG] Repositories (dependencies): [unimatica-m2-snapshot-repository
> (http://coderepository.unimatica.lan/dev2/maven2-snapshot, releases=true,
> snapshots=true, managed=false), unimatica-m2-coderepository
> (http://coderepository.unimatica.lan/dev2/maven2, releases=true,
> snapshots=true, managed=false), central (http://repo1.maven.org/maven2,
> releases=true, snapshots=false, managed=false)]
> [DEBUG] Repositories (plugins) : [central (http://repo1.maven.org/maven2,
> releases=true, snapshots=false, managed=false)]
> [DEBUG]
> ---
> [DEBUG] Goal:
> org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli)
> [DEBUG] Style: Aggregating
> [DEBU
[jira] (MRELEASE-654) Release:perform fails on releasing a tag from an empty directory
[
https://jira.codehaus.org/browse/MRELEASE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-654:
Comment: was deleted
(was: James,
look at your log once more:
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli)
{quote}
So you're using version 2.0, so please lock the version to 2.3 and try again.)
> Release:perform fails on releasing a tag from an empty directory
>
>
> Key: MRELEASE-654
> URL: https://jira.codehaus.org/browse/MRELEASE-654
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix"
>Reporter: Giacomo Boccardo
>
> If we release our project from the same directory when we executed the
> release:prepare the perform phase completes successfully, while performing a
> release from a tag (in an empty directory) we have the following stack trace:
> {noformat}
> $ mvn release:perform -Dtag=unilet-base-5.3.13
> -DconnectionUrl=scm:svn:https://srvdevel.unimatica.lan/svn/unilet -X
> Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.35-25-generic", arch: "amd64", family: "unix"
> [INFO] Error stacktraces are turned on.
> [DEBUG] Reading global settings from /usr/local/app/maven/conf/settings.xml
> [DEBUG] Reading user settings from /home/gboccardo/.m2/settings.xml
> [DEBUG] Using local repository at /home/gboccardo/.m2/repository
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
> /home/gboccardo/.m2/repository
> [INFO] Scanning for projects...
> [DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1:
> (none)
> [DEBUG] Looking up lifecyle mappings for packaging pom from
> ClassRealm[plexus.core, parent: null]
> [DEBUG] Resolving plugin prefix release from [org.apache.maven.plugins,
> org.codehaus.mojo]
> [DEBUG] Resolved plugin prefix release to
> org.apache.maven.plugins:maven-release-plugin from POM
> org.apache.maven:standalone-pom:pom:1
> [DEBUG] === REACTOR BUILD PLAN
>
> [DEBUG] Project: org.apache.maven:standalone-pom:pom:1
> [DEBUG] Tasks: [release:perform]
> [DEBUG] Style: Aggregating
> [DEBUG]
> ===
> [INFO]
>
> [INFO]
>
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
>
> [DEBUG] Resolving plugin prefix release from [org.apache.maven.plugins,
> org.codehaus.mojo]
> [DEBUG] Resolved plugin prefix release to
> org.apache.maven.plugins:maven-release-plugin from POM
> org.apache.maven:standalone-pom:pom:1
> [DEBUG] Lifecycle default -> [validate, initialize, generate-sources,
> process-sources, generate-resources, process-resources, compile,
> process-classes, generate-test-sources, process-test-sources,
> generate-test-resources, process-test-resources, test-compile,
> process-test-classes, test, prepare-package, package, pre-integration-test,
> integration-test, post-integration-test, verify, install, deploy]
> [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
> [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
> [DEBUG] === PROJECT BUILD PLAN
>
> [DEBUG] Project: org.apache.maven:standalone-pom:1
> [DEBUG] Dependencies (collect): []
> [DEBUG] Dependencies (resolve): []
> [DEBUG] Repositories (dependencies): [unimatica-m2-snapshot-repository
> (http://coderepository.unimatica.lan/dev2/maven2-snapshot, releases=true,
> snapshots=true, managed=false), unimatica-m2-coderepository
> (http://coderepository.unimatica.lan/dev2/maven2, releases=true,
> snapshots=true, managed=false), central (http://repo1.maven.org/maven2,
> releases=true, snapshots=false, managed=false)]
> [DEBUG] Repositories (plugins) : [central (http://repo1.maven.org/maven2,
> releases=true, snapshots=false, managed=false)]
> [DEBUG]
> ---
> [DEBUG] Goal:
> org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli)
> [DEBUG] Style: Aggregating
> [DEBUG] Configuration:
>
> ${argu
[jira] (SUREFIRE-866) concurrent execution exception, I'm asked to look in a log but I'm not seeing anything very illuminating
Benson Margulies created SUREFIRE-866:
-
Summary: concurrent execution exception, I'm asked to look in a
log but I'm not seeing anything very illuminating
Key: SUREFIRE-866
URL: https://jira.codehaus.org/browse/SUREFIRE-866
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.13
Reporter: Benson Margulies
I can provide, of course, more log in an attachment:
{noformat}
Caused by: java.util.concurrent.ExecutionException:
org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred in
starting fork, check output in log
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:171)
... 24 more
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: Error
occurred in starting fork, check output in log
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:281)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$100(ForkStarter.java:71)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:160)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:157)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
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:680)
{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
[jira] (SUREFIRE-866) concurrent execution exception, I'm asked to look in a log but I'm not seeing anything very illuminating
[
https://jira.codehaus.org/browse/SUREFIRE-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed SUREFIRE-866.
-
Resolution: Not A Bug
> concurrent execution exception, I'm asked to look in a log but I'm not seeing
> anything very illuminating
>
>
> Key: SUREFIRE-866
> URL: https://jira.codehaus.org/browse/SUREFIRE-866
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Benson Margulies
>
> I can provide, of course, more log in an attachment:
> {noformat}
> Caused by: java.util.concurrent.ExecutionException:
> org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred
> in starting fork, check output in log
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:171)
> ... 24 more
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException:
> Error occurred in starting fork, check output in log
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:281)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$100(ForkStarter.java:71)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:160)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter$1.call(ForkStarter.java:157)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 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:680)
> {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
[jira] (MCLEAN-48) Failure cleaning files containing special characters
[ https://jira.codehaus.org/browse/MCLEAN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298944#comment-298944 ] Dennis Lundberg commented on MCLEAN-48: --- The IT runs fine on my virtual Ubuntu 10.04, with both the default LANG setting and with LANG set as in the reporter's environment. > Failure cleaning files containing special characters > > > Key: MCLEAN-48 > URL: https://jira.codehaus.org/browse/MCLEAN-48 > Project: Maven 2.x Clean Plugin > Issue Type: Bug >Affects Versions: 2.4.1 > Environment: Ubuntu 10.10 > LANG=en_DK.utf8 >Reporter: Stefan Meisner Larsen > > I am not able to clean my project which contains files named with special > characters. It seems as though the plugin does not handle UTF-8 correctly. > Name of file as reported by find command: > ./ewp-fr/ewp-fr.war/src/main/webapp/secure/fr/Conditions_générales_d'isalaire.pdf > Output from clean: > . > . > . > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean (default-clean) on > project ewp-fr.war: Failed to clean project: Failed to delete > /home/stefan/trifork/lessor/ewp-clean/trunk/ewp-fr/ewp-fr.war/target/ewp-fr.war-1.69-SNAPSHOT/secure/fr/Conditions_g??n??rales_d'isalaire.pdf > -> [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] (MCLEAN-48) Failure cleaning files containing special characters
[ https://jira.codehaus.org/browse/MCLEAN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298949#comment-298949 ] Joerg Schaible commented on MCLEAN-48: -- Notice that the reporter did the find on src/main/webapp/, while clean fails for the file in target/. So the culprit might be a buggy plugin that generates the file with that problematic name in target. > Failure cleaning files containing special characters > > > Key: MCLEAN-48 > URL: https://jira.codehaus.org/browse/MCLEAN-48 > Project: Maven 2.x Clean Plugin > Issue Type: Bug >Affects Versions: 2.4.1 > Environment: Ubuntu 10.10 > LANG=en_DK.utf8 >Reporter: Stefan Meisner Larsen > > I am not able to clean my project which contains files named with special > characters. It seems as though the plugin does not handle UTF-8 correctly. > Name of file as reported by find command: > ./ewp-fr/ewp-fr.war/src/main/webapp/secure/fr/Conditions_générales_d'isalaire.pdf > Output from clean: > . > . > . > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean (default-clean) on > project ewp-fr.war: Failed to clean project: Failed to delete > /home/stefan/trifork/lessor/ewp-clean/trunk/ewp-fr/ewp-fr.war/target/ewp-fr.war-1.69-SNAPSHOT/secure/fr/Conditions_g??n??rales_d'isalaire.pdf > -> [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] (MCLEAN-48) Failure cleaning files containing special characters
[
https://jira.codehaus.org/browse/MCLEAN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298958#comment-298958
]
Robert Scholte commented on MCLEAN-48:
--
The output looks like the result of a {{war:exploded}}, even then I can't
reproduce it.
> Failure cleaning files containing special characters
>
>
> Key: MCLEAN-48
> URL: https://jira.codehaus.org/browse/MCLEAN-48
> Project: Maven 2.x Clean Plugin
> Issue Type: Bug
>Affects Versions: 2.4.1
> Environment: Ubuntu 10.10
> LANG=en_DK.utf8
>Reporter: Stefan Meisner Larsen
>
> I am not able to clean my project which contains files named with special
> characters. It seems as though the plugin does not handle UTF-8 correctly.
> Name of file as reported by find command:
> ./ewp-fr/ewp-fr.war/src/main/webapp/secure/fr/Conditions_générales_d'isalaire.pdf
> Output from clean:
> .
> .
> .
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean (default-clean) on
> project ewp-fr.war: Failed to clean project: Failed to delete
> /home/stefan/trifork/lessor/ewp-clean/trunk/ewp-fr/ewp-fr.war/target/ewp-fr.war-1.69-SNAPSHOT/secure/fr/Conditions_g??n??rales_d'isalaire.pdf
> -> [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] (MARCHETYPES-39) xml definition in the stock pom.xml
Ion Iovu created MARCHETYPES-39: --- Summary: xml definition in the stock pom.xml Key: MARCHETYPES-39 URL: https://jira.codehaus.org/browse/MARCHETYPES-39 Project: Maven Archetype Bundles Issue Type: Improvement Components: Maven Quickstart Archetype Affects Versions: 5 Environment: N/A Reporter: Ion Iovu Priority: Trivial It would be very nice to have the xml definition added to the pom.xml archetype resource such that it doesn't have to be added after each project created. Patch attached Thank you -- 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
