Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 28843 invoked from network); 5 Nov 2008 07:57:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Nov 2008 07:57:13 -0000 Received: (qmail 43107 invoked by uid 500); 5 Nov 2008 07:57:19 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 43007 invoked by uid 500); 5 Nov 2008 07:57:18 -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 42995 invoked by uid 99); 5 Nov 2008 07:57:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Nov 2008 23:57:18 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Nov 2008 07:56:00 +0000 Received: from [192.168.0.193] (chello062178239020.5.15.vie.surfer.at [62.178.239.20]) by indoqa.com (Postfix) with ESMTP id 0793A254759 for ; Wed, 5 Nov 2008 08:56:10 +0100 (CET) Message-ID: <49115189.40803@apache.org> Date: Wed, 05 Nov 2008 08:55:53 +0100 From: =?ISO-8859-1?Q?Reinhard_P=F6tz?= User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Cocoon 3 trunk References: <738EA349-3E5E-4FB4-8901-2E68BE03F97B@reverycodes.com> <4910ACE8.1070006@indoqa.com> <49113AA3.3060104@indoqa.com> In-Reply-To: <49113AA3.3060104@indoqa.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Steven Dolg wrote: > Vadim Gritsenko schrieb: >> On Nov 4, 2008, at 3:13 PM, Steven Dolg wrote: >> >>> Hi Vadim, >>> >>> the port stated in the README is unfortunately wrong. >>> >>> However the demo is working correctly for me >> >> After a bit of poking around I figured out it was caused by a firefox >> cache (it cached a redirect). After clearing the cache I can see >> "Cocoon 3 Samples and Integration Tests: Overview" page. >> >> >>> as well as the generated project for IDEA (I tried IDEA 7.0.4 with a >>> JDK 1.6.0_06). >> >> It is not possible to generate a project file from cocoon-3 root >> directory itself, and so the next closest thing which I found is to do >> it in the ./parent directory. So, when running mvn idea:idea command >> there, it creates incorrect cocoon-parent.ipr file: >> >> >> >> >> > filepath="$PROJECT_DIR$//Users/vgritsenko/Projects/Apache/cocoon-3/cocoon-all/cocoon-all.iml"/> >> >> > filepath="$PROJECT_DIR$//Users/vgritsenko/Projects/Apache/cocoon-3/cocoon-controller/cocoon-controller.iml"/> >> >> >> So it seems like idea plugin appends absolute file paths to the >> $PROJECT_DIR$. I had to manually edit file so that it loads in IDEA. >> It now reads: >> >> >> >> >> >> > filepath="$PROJECT_DIR$/../cocoon-controller/cocoon-controller.iml"/> >> >> >> Short of hacking maven plugin, I think easiest way to fix that would >> be to add a pom to cocoon-3 directory. WDYT? > That is strange. > When I generate the IDEA project files from the parent directory I get > the following modules section: > > > > > > filepath="$PROJECT_DIR$/../cocoon-controller/cocoon-controller.iml"/> > filepath="$PROJECT_DIR$/../cocoon-optional/cocoon-optional.iml"/> > filepath="$PROJECT_DIR$/../cocoon-pipeline/cocoon-pipeline.iml"/> > > > filepath="$PROJECT_DIR$/../cocoon-servlet/cocoon-servlet.iml"/> > filepath="$PROJECT_DIR$/../cocoon-sitemap/cocoon-sitemap.iml"/> > filepath="$PROJECT_DIR$/../cocoon-stringtemplate/cocoon-stringtemplate.iml"/> > > > > After opening IDEA changes all that into absolute paths - but I guess > this is all right (I have absolutely no experience with IDEA). > > So the only thing I can image are different Maven and/or different > idea-plugin versions. > Mine are Maven 2.0.9 and maven-idea-plugin 2.2. > > > If everything fails moving the pom might be an option. Would that > produce a valid project file with your setup? If that solves the problem with IDEA, we can (re)introduce the root pom. Actually I also have problems with creating releases because the Maven release plugin doesn't support flat scenarios (although recommended by Maven AFAIU). Vadim, you can use cocoon3/trunk/release.pom.xml and rename it to pom.xml. Then go to parent/pom.xml and remove the section from there. Then invoke all mvn commands from cocoon3/trunk instead of cocoon3/trunk/parent. HTH Please let us know if that works for you! Thanks. -- Reinhard P�tz Managing Director, {Indoqa} GmbH http://www.indoqa.com/en/people/reinhard.poetz/ Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinhard@apache.org ________________________________________________________________________