The problem is a known bug (4671171) in 1.4.0, 1.4.1RC JDK in the URL
class, if a relative path to UNC paths is used.
I had deployed maven to a UNC path location for common network access, so I
ran into this strange error.
Thomas Weber
To: "Turbine Maven Users List"
<[EMAIL PROTECTED]>
09/03/2002 cc:
09:42 AM Subject: Re: Entity resolver problem with
j2ee plugin(Document link: Thomas
Weber)
I did not execute a j2ee goal. Just having the j2ee plugin enabled got me
this error.
if I comment out the following in plugin.jelly, the error vanishes. BTW I
use JDK 1.4.0
..
<j:import inherit="true" uri="./appserver/tomcat-4.x.jelly" />
..
It seems to be a Jelly problem.
>Which goal were you executing.
>It appears an entity is being resolved via ftp....
>There are pieces of the j2ee plugin that aren't ready for prime time, but
>ear and validate-war should be fine....
>--
>dIon Gillard, Multitask Consulting
>Work: http://www.multitask.com.au
>Developers: http://adslgateway.multitask.com.au/developers
>[EMAIL PROTECTED] wrote on 03/09/2002 01:06:43 AM:
>>
>> I get the following errors from the j2ee plugin (maven b6 from CVS). It
>> seems that the j2ee plugin tries to download something. Any ideas?
>> cmd line:
>> [ERROR] File......
>> \\delta3\develop\cmr\code\java\maven\plugins\maven-j2ee-plugin-1.
>> 0\plugin.jelly
>> [ERROR] Element... j:import
>> [ERROR] Line...... 19
>> [ERROR] Column.... 65
>> [ERROR] Connection refused: connect
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
