Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 74165 invoked from network); 6 Sep 2006 11:15:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Sep 2006 11:15:57 -0000 Received: (qmail 89213 invoked by uid 500); 6 Sep 2006 11:15:56 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 88748 invoked by uid 500); 6 Sep 2006 11:15:55 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 88737 invoked by uid 99); 6 Sep 2006 11:15:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2006 04:15:55 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2006 04:15:54 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CFF45410017 for ; Wed, 6 Sep 2006 11:12:23 +0000 (GMT) Message-ID: <17450536.1157541143849.JavaMail.jira@brutus> Date: Wed, 6 Sep 2006 04:12:23 -0700 (PDT) From: "Leszek Gawron (JIRA)" To: dev@cocoon.apache.org Subject: [jira] Commented: (COCOON-1910) cocoon deployer fails when deploying cocoon-core In-Reply-To: <1687295.1157535862815.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/COCOON-1910?page=comments#action_12432823 ] Leszek Gawron commented on COCOON-1910: --------------------------------------- Fixed with a hacky trick. I'll refactor SingleFileDeployer a little bit later. > cocoon deployer fails when deploying cocoon-core > ------------------------------------------------ > > Key: COCOON-1910 > URL: http://issues.apache.org/jira/browse/COCOON-1910 > Project: Cocoon > Issue Type: Bug > Components: - Build System: Maven > Affects Versions: 2.2-dev (Current SVN) > Reporter: Lars Trieloff > Assigned To: Leszek Gawron > > Running mvn cocoon:deploy on my application's blocks or the cocoon-webapp leads to following results: > The deployer fails to deploy cocoon-core, because WEB-INF/cocoon/properties/core.properties is already deployed. > [INFO] Deploying cocoon-core > [INFO] ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] ------------------------------------------------------------------------ > [INFO] File '/Users/lars/Documents/coccon/core/cocoon-webapp/target/cocoon-webapp/WEB-INF/cocoon/properties/core.properties' already exists! > [INFO] ------------------------------------------------------------------------ > [INFO] Trace > org.apache.cocoon.maven.deployer.monolithic.FileAlreadyDeployedException: File '/Users/lars/Documents/coccon/core/cocoon-webapp/target/cocoon-webapp/WEB-INF/cocoon/properties/core.properties' already exists! > at org.apache.cocoon.maven.deployer.monolithic.SingleFileDeployer.writeResource(SingleFileDeployer.java:99) > at org.apache.cocoon.maven.deployer.monolithic.MonolithicServer22.extract(MonolithicServer22.java:84) > at org.apache.cocoon.maven.deployer.monolithic.MonolithicCocoonDeployer.deploy(MonolithicCocoonDeployer.java:84) > at org.apache.cocoon.maven.deployer.monolithic.MonolithicCocoonDeployer.deploy(MonolithicCocoonDeployer.java:57) > at org.apache.cocoon.maven.deployer.AbstractDeployMojo.deployMonolithicCocoonAppAsWebapp(AbstractDeployMojo.java:180) > at org.apache.cocoon.maven.deployer.DeployExplodedMojo.execute(DeployExplodedMojo.java:62) > at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) > 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:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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:585) > 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira