[jira] Created: (MNG-2529) it0063... FAILED
it0063... FAILED Key: MNG-2529 URL: http://jira.codehaus.org/browse/MNG-2529 Project: Maven 2 Issue Type: Bug Components: Bootstrap & Build Affects Versions: 2.1 Environment: blackdown-jdk-1.4.2.03 / GNU/LInux Reporter: Hilco Wijbenga 1 of the 101 integration tests fails. it0063... FAILED - Standard Out - Command: /home/maven/bin/maven/current/bin/mvn -e --no-plugin-registry --batch-mode -Dmaven.repo.local=/home/maven/.m2/repository clean:clean package - Standard Error - Exit code: 1 >> Error Stacktrace: org.apache.maven.it.VerificationException at org.apache.maven.it.Verifier.executeGoals(Verifier.java:732) at org.apache.maven.it.Verifier.main(Verifier.java:964) << Error Stacktrace Log file contents: + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] [INFO] Building Unnamed - org.apache.maven.it:maven-core-it0063:jar:1.0 [INFO]task-segment: [clean:clean, package] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /home/maven/maven/components/maven-core-it/it0063/target [INFO] Deleting directory /home/maven/maven/components/maven-core-it/it0063/target/classes [INFO] Deleting directory /home/maven/maven/components/maven-core-it/it0063/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 1 source file to /home/maven/maven/components/maven-core-it/it0063/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/maven/maven/components/maven-core-it/it0063/src/main/java/org/apache/maven/it0001/Person.java:[3,27] package com.sun.tools.javac does not exist [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:747) at org.apache.maven.cli.MavenCli.main(MavenCli.java:380) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 17 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Fri Aug 25 02:00:21 GMT 2006 FATAL ERROR: Unable to configure the Maven application Error stacktrace: org.apache.maven.reactor.MavenExecutionException: Compilation failure at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:206) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:747) at org.apache.maven.cli.MavenCli.main(MavenCli.java:380) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[jira] Created: (SCM-300) CVS doesn't close it's session after checkout
CVS doesn't close it's session after checkout - Key: SCM-300 URL: http://jira.codehaus.org/browse/SCM-300 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-cvs Affects Versions: future Environment: Linux, Sun JDK 1.4. Continuum built from trunk. Reporter: Hilco Wijbenga We've been trying to set up Continuum and consequently we started running some builds. It all worked nicely until the CVS server ran out of inodes in its /tmp directory. It looks like it's not the normal checkouts that people do that's causing this ... it appears to be Continuum. We tried a small build with Continuum and lo and behold: /tmp had a new directory that was not deleted at the end of the checkout. So we're fairly certain it's something Continuum related. CVS creates a sort of cache directory (in /tmp) for each checkout (it stores the CVS directories, not any of the files that are being checked out) and this directory (and all of its *many* subdirectories) are not being deleted. Apparently, it doesn't notice that the checkout has finished. Something like a session not being closed. After three days of this our server runs out of inodes and nothing works anymore. We've created a cron job to remove these CVS directories from /tmp at the end of the day so we have a workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MENFORCER-29) Enforcer complains about its own version
Enforcer complains about its own version
Key: MENFORCER-29
URL: http://jira.codehaus.org/browse/MENFORCER-29
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Plugin
Affects Versions: 1.0
Environment: GNU/Linux
Reporter: Hilco Wijbenga
Assignee: Brian Fox
Attachments: pom.xml
The attached POM uses the latest version of the Enforcer (revision 611262),
i.e. 1.0-SNAPSHOT. I've called it 1.0-Local-1, so that's what's defined in the
POM.
If I use the Enforcer normally, without a profile, everything works
beautifully. The attached POM, however, tries to use the Enforcer from a
profile ("enforce"). If you now try something like "mvn compile -Penforce" it
complains about its own version not being set, even though it's specified
*twice*.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3448) Infinite Loop When Using project.version in Modules Build
Infinite Loop When Using project.version in Modules Build
-
Key: MNG-3448
URL: http://jira.codehaus.org/browse/MNG-3448
Project: Maven 2
Issue Type: Bug
Components: POM
Affects Versions: 2.0.8
Reporter: Hilco Wijbenga
I have the following setup:
org.example.pom/pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";
>
4.0.0
org.example
pom
pom
1
POM
${project.version}
and org.example.jar/pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";
>
4.0.0
org.example
pom
1
../org.example.pom/pom.xml
org.example
jar
jar
${webapp.version}
JAR
Running "mvn clean" in org.example.jar yields just
[INFO] Scanning for projects...
and then Maven hangs. Replacing "${project.version}" with a simple "0.1" allows
things to work properly.
My environment:
Maven version: 2.0.8
Java version: 1.5.0_14
OS name: "linux" version: "2.6.24-gentoo-r2" arch: "i386" Family: "unix"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1167) Patch to add JBoss support
Patch to add JBoss support -- Key: CONTINUUM-1167 URL: http://jira.codehaus.org/browse/CONTINUUM-1167 Project: Continuum Issue Type: Wish Reporter: Hilco Wijbenga Priority: Minor Attachments: continuum_jboss.patch I've been bold enough to prepare a little patch that adds explicit support for JBoss to the Continuum WAR. The patch adds a jboss-web.xml file (this should be totally harmless) and adds two s to web.xml. I get the impression that this latter change is harmless as well, or would it break other app servers? Anyway, here's the patch. I hope it can get applied, otherwise I'll just keep on doing it by hand. :-) With this applied the only thing left to do is add a derby-ds.xml file to the JBoss deployment directory. And make sure JBoss has a Derby driver, of course. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
