Hi John
if you remove this, the plugin will require maven 2.0.1 in order to
generate correct system dependencies. What about leaving it as is for
backward compatibility?

fabrizio


On 12/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: jdcasey
> Date: Wed Dec  7 09:39:54 2005
> New Revision: 354811
>
> URL: http://svn.apache.org/viewcvs?rev=354811&view=rev
> Log:
> PR: MNG-1379
>
> Commented out the line in EclipsePlugin.java that reconfigures the artifact 
> file based on dependency systemPath, and reran the tests...it seems to pass 
> just fine, so I assume the problem has been fixed as a side effect of another 
> issue's resolution. I'm leaving the code in there (but commenting out the 
> method call), just in case this proves to be incorrect.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to