From: Jarek C. <jar...@po...> - 2012-02-29 19:46:09
|
W dniu 02/29/2012 07:17 PM, Matthieu Casanova pisze: > > <url name="jedit-plugins-lib"> > <artifact > pattern="jar:http://${mirror}.dl.sourceforge.net/sourceforge/jedit-plugins/[artifact]-[revision]-bin.zip!/[branch].jar > <http://dl.sourceforge.net/sourceforge/jedit-plugins/[artifact]-[revision]-bin.zip%21/[branch].jar>" > /> > </url> > This is not what I intended. Thanks for trying, but what I suggested seems to be better. Have a look at this: ivy settings: <url name="jedit-plugins-zip-resolver"> <artifact pattern="http://${mirror}.dl.sourceforge.net/sourceforge/jedit-plugins/[artifact]-[revision]-bin.zip" /> </url> ivy file: <dependency name="ErrorList" org="jedit-plugins-zip" rev="1.9"/> <dependency name="SideKick" org="jedit-plugins-zip" rev="1.2"/> <dependency name="RhinoPlugin" org="jedit-plugins-zip" rev="1.7R3"/> I get whole zips, although I don't know why they have "jar" extensions. In these zips (jars) I have all the jars that are needed. For the first 2 plugins these are the single jars as before. But in RhinoPlugin.jar(zip) I have 2 jars that I was missing. Only to unzip them and that's it. Notice that using this method there's no need to download rhino.jar from other sources, like mozilla. Everything comes from jedit server. And we are sure, that we use the same rhino.jar for building and for running. What is this all for? To automatically get all the jars needed for both building and testing a plugin. Testing with exact versions of plugins that were specified in props file. Jarek |