RE: [C3] Concurrency issues with ComponentProvider

Hi Igor,

I commented out the cocoon-maven-plugin and now jetty starts fine. But now the below configuration does not work anymore when executing mvn jetty:run

            <plugin>
                <groupId>org.mortbay.jetty</groupId>
                <artifactId>maven-jetty-plugin</artifactId>  <!-- jetty-maven-plugin -->
                <version>6.1.26</version>    <!-- 8.1.0.RC5 -->
                <configuration>
                    <connectors>
                        <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector"> <!-- org.eclipse.jetty.server.nio.SelectChannelConnector -->
                            <port>8888</port>
                            <maxIdleTime>30000</maxIdleTime>
                        </connector>
                    </connectors>
                    <webAppSourceDirectory>${project.build.directory}/rcl/webapp</webAppSourceDirectory>
                    <contextPath>/</contextPath>
                    <systemProperties>
                        <systemProperty>
                            <name>org.apache.cocoon.mode</name>
                            <value>dev</value>
                        </systemProperty>
                    </systemProperties>
                </configuration>
            </plugin>


It now can't find the webapp source directory anymore as I expect that the cocoon-maven-plugin copied over files to the target/rcl folder.

So my next question is.  How do you test (and start) an individual block?


[INFO] Final Memory: 26M/147M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) on project shared: Webapp source directory C:\development\workspaces\intell
ij11\CTPI-PX\spider2\shared\target\rcl\webapp does not exist -> [Help 1]


-----Original Message-----
From: Igor Malinin [mailto:igorzep@...]
Sent: Thursday, March 15, 2012 10:50 AM
To: dev@...
Subject: Re: [C3] Concurrency issues with ComponentProvider

I don't remember exactly all the steps, but basically Cocoon RCL is the
cocoon-maven-plugin, so you should remove this plugin from pom.xml then
RCL will not be used. Commenting out instructions in .rcl files will not
remove RCL itself from the build.

No modification of Cocoon is required, Cocoon RCL just sits on top of
'normal' Cocoon. And you should not go to production with RCL anyway, so
you should learn how to make builds that does not include RCL anyway...

On 2012-03-15 10:58, Robby Pelssers wrote:
> Could you elaborate a bit further how to remove all references to RCL?  Did you check out the Cocoon sources and modify those?  And where should I look for these references? Or are you referring to just commenting out all these instructions in the .rcl files?  Because the latter sure does not fix this apparently.
>
> Robby
>