You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Leszek Gawron <lg...@mobilebox.pl> on 2006/11/07 23:08:02 UTC
Re: svn commit: r472224 - /cocoon/trunk/core/cocoon-webapp/pom.xml
ltrieloff@apache.org wrote:
> Author: ltrieloff
> Date: Tue Nov 7 11:48:15 2006
> New Revision: 472224
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=472224
> Log:
> use newest jetty plugin. From now on mvn cocoon:deploy jetty:run
>
> Modified:
> cocoon/trunk/core/cocoon-webapp/pom.xml
>
> Modified: cocoon/trunk/core/cocoon-webapp/pom.xml
> URL: http://svn.apache.org/viewvc/cocoon/trunk/core/cocoon-webapp/pom.xml?view=diff&rev=472224&r1=472223&r2=472224
> ==============================================================================
> --- cocoon/trunk/core/cocoon-webapp/pom.xml (original)
> +++ cocoon/trunk/core/cocoon-webapp/pom.xml Tue Nov 7 11:48:15 2006
> @@ -58,8 +58,8 @@
> </plugin>
> <plugin>
> <groupId>org.mortbay.jetty</groupId>
> - <artifactId>maven-jetty6-plugin</artifactId>
> - <version>6.0.0beta10</version>
> + <artifactId>maven-jetty-plugin</artifactId>
> + <version>6.0.0rc4</version>
That probably won't work. I have done it once and reverted the change.
New jetty plugin has some classloader issues (i.e. puts all webapp jar
on classpath so shielding does not work as it is supposed).
Maybe something changed though...
--
Leszek Gawron CTO at MobileBox Ltd.
Re: svn commit: r472224 - /cocoon/trunk/core/cocoon-webapp/pom.xml
Posted by Leszek Gawron <lg...@mobilebox.pl>.
Lars Trieloff wrote:
>
> Am 07.11.2006 um 23:08 schrieb Leszek Gawron:
>
>> ltrieloff@apache.org wrote:
>>> Author: ltrieloff
>>> Date: Tue Nov 7 11:48:15 2006
>>> New Revision: 472224
>>>
>>> URL: http://svn.apache.org/viewvc?view=rev&rev=472224
>>> Log:
>>> use newest jetty plugin. From now on mvn cocoon:deploy jetty:run
>>>
>>> Modified:
>>> cocoon/trunk/core/cocoon-webapp/pom.xml
>>>
>>> Modified: cocoon/trunk/core/cocoon-webapp/pom.xml
>>> URL:
>>> http://svn.apache.org/viewvc/cocoon/trunk/core/cocoon-webapp/pom.xml?view=diff&rev=472224&r1=472223&r2=472224
>>>
>>> ==============================================================================
>>>
>>> --- cocoon/trunk/core/cocoon-webapp/pom.xml (original)
>>> +++ cocoon/trunk/core/cocoon-webapp/pom.xml Tue Nov 7 11:48:15 2006
>>> @@ -58,8 +58,8 @@
>>> </plugin>
>>> <plugin>
>>> <groupId>org.mortbay.jetty</groupId>
>>> - <artifactId>maven-jetty6-plugin</artifactId>
>>> - <version>6.0.0beta10</version>
>>> + <artifactId>maven-jetty-plugin</artifactId>
>>> + <version>6.0.0rc4</version>
>>
>> That probably won't work. I have done it once and reverted the change.
>> New jetty plugin has some classloader issues (i.e. puts all webapp jar
>> on classpath so shielding does not work as it is supposed).
>>
>> Maybe something changed though...
>>
>
> I see. We are using the newer Jetty plugins exclusively as they fix a
> bug with reloading jar files from the local repository. Is there a Jetty
> bug for the problem you experienced?
No idea, I was to lazy to check and simply reverted to the working version.
--
Leszek Gawron CTO at MobileBox Ltd.
Re: svn commit: r472224 - /cocoon/trunk/core/cocoon-webapp/pom.xml
Posted by Lars Trieloff <la...@trieloff.net>.
Am 07.11.2006 um 23:08 schrieb Leszek Gawron:
> ltrieloff@apache.org wrote:
>> Author: ltrieloff
>> Date: Tue Nov 7 11:48:15 2006
>> New Revision: 472224
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=472224
>> Log:
>> use newest jetty plugin. From now on mvn cocoon:deploy jetty:run
>>
>> Modified:
>> cocoon/trunk/core/cocoon-webapp/pom.xml
>>
>> Modified: cocoon/trunk/core/cocoon-webapp/pom.xml
>> URL: http://svn.apache.org/viewvc/cocoon/trunk/core/cocoon-webapp/
>> pom.xml?view=diff&rev=472224&r1=472223&r2=472224
>> =====================================================================
>> =========
>> --- cocoon/trunk/core/cocoon-webapp/pom.xml (original)
>> +++ cocoon/trunk/core/cocoon-webapp/pom.xml Tue Nov 7 11:48:15 2006
>> @@ -58,8 +58,8 @@
>> </plugin>
>> <plugin>
>> <groupId>org.mortbay.jetty</groupId>
>> - <artifactId>maven-jetty6-plugin</artifactId>
>> - <version>6.0.0beta10</version>
>> + <artifactId>maven-jetty-plugin</artifactId>
>> + <version>6.0.0rc4</version>
>
> That probably won't work. I have done it once and reverted the change.
> New jetty plugin has some classloader issues (i.e. puts all webapp jar
> on classpath so shielding does not work as it is supposed).
>
> Maybe something changed though...
>
I see. We are using the newer Jetty plugins exclusively as they fix a
bug with reloading jar files from the local repository. Is there a
Jetty bug for the problem you experienced?
Lars
--
Lars Trieloff
visit http://www.mindquarry.com/