mirror of https://github.com/apache/ant-ivy
extract site to a separate component, move doc/doc up one level (in doc) and make it self contained (IVY-558)
git-svn-id: https://svn.apache.org/repos/asf/incubator/ivy/core/trunk@553243 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Xavier Hanin
parent
a7a917cdb2
commit
f088aae5eb
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -1,41 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Each distribution of ivy contains samples. The documentation is packaged separately due to its size. It corresponds to a snapshot of the online documentation at the time of the release. Prefer the site itself if you want to have an updated and commented version of the documentation.
|
||||
With each version of ivy, you can find:
|
||||
<h2>binary distribution</h2>
|
||||
Containing ivy jars, dependencies and samples.
|
||||
This is the recommended version if you just want to use ivy. It requires at least a jre 1.4+ to run, and it is recommended to use it from ant (1.5.1+, 1.6.2+ recommended).
|
||||
<h2>sources</h2>
|
||||
Ready to be build with ant 1.6.0 or greater and ... ivy 1.4-RC1+. Yes, ivy eats its own dog food, and needs a binary version of itself to be build. Note that you will also need to have an internet access during build in order to ivy to download dependencies from ibiblio.
|
||||
This is the recommended version if you want to build ivy yourself and see it in action at the same time.
|
||||
<i>Note:</i> version 1.6.0 of ant is required here because the build file use its namespace feature to import ivy tasks.
|
||||
<h2>documentation</h2>
|
||||
Full ivy documentation easily browsable offline, packaged as a zip.</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 3};</script>
|
||||
<script type="text/javascript" src="../../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 3};</script>
|
||||
<script type="text/javascript" src="../../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 3};</script>
|
||||
<script type="text/javascript" src="../../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 3};</script>
|
||||
<script type="text/javascript" src="../../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 3};</script>
|
||||
<script type="text/javascript" src="../../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
The Ivy demo is not available yet. Come back later or contribute a new demo!</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -1,76 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Welcome to the official Ivy documentation.
|
||||
|
||||
<h1>What is Ivy?</h1>
|
||||
Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies. It is characterized by the following:
|
||||
<ol>
|
||||
<li>flexibility and configurability - Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes.</li>
|
||||
|
||||
<li>tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication.</li>
|
||||
</ol>
|
||||
Ivy is open source and released under a very permissive <a href="license.html">license</a>.
|
||||
Ivy has a lot of powerful [[features]], the most popular and useful being its flexibily, integration with ant, and its strong transitive dependencies management engine.
|
||||
The transitive dependencies management is a feature which let you get dependencies of your dependencies, transitively. In order to address this problematic ivy needs to find metadata about your modules, usually in an <a href="doc/ivyfile.html">ivy file</a>. To find these metadata and your dependencies artifacts (usually jars), Ivy can be configured to use a lot of different <a href="doc/configuration/resolvers.html">repositories</a>.
|
||||
|
||||
<h1>About this doc</h1>
|
||||
This documentation has been migrated from the old Ivy web site hosted by Jayasoft, feel free to report any problem on the [[mailing-lists]].
|
||||
|
||||
If you browse this documentation from your installation of ivy, you can also check the <a href="http://incubator.apache.org/ivy/doc.html">online version</a> for latest updates.
|
||||
|
||||
You can also browse this documentation offline either by downloading the documentation distribution, or by checking out the doc directory from svn. This documentation uses <a href="http://xooki.sourceforge.net/">xooki</a> as documentation engine, so you can very easily [[get-involved edit it and submit patches]] when you browse it from source.
|
||||
|
||||
The online version of this documentation is updated periodically, especially when new features are added during development. So if you find something documented here not available in your version of ivy, it may be because it is available only with the latest <a href="download.html">download</a>.
|
||||
|
||||
If you want to view the whole documentation in a single printer-friendly page, please use the <a href="doc.html?action=print">printer-friendly link</a> at the bottom of any documentation page in the online documentation, and you will get a printer friendly version of the current page and all its sub pages.
|
||||
|
||||
<h1>Other places to go</h1>
|
||||
Check Ivy <a href="features.html">features</a>.
|
||||
Read our <a href="faq.html">FAQ</a>.
|
||||
Ask for help on our <a href="mailing-lists.html">mailing lists</a>.
|
||||
Report bug or feature request in our <a href="issues.html">issue tracking system</a>.
|
||||
Check <a href="links.html">external tools and resources</a>.
|
||||
|
||||
<h1>Overview</h1>
|
||||
This documentation is decomposed in 3 main parts:
|
||||
<ul>
|
||||
<li><a href="doc/tutorial.html">Tutorials</a></li>
|
||||
The tutorials is the best way to begin to play with ivy. You will easily and quickly learn the basics of Ivy.
|
||||
<li><a href="doc/reference.html">Reference</a></li>
|
||||
The reference documentation gives you all the details of Ivy.
|
||||
The introduction part is particularly useful: it defines some vocabulary, explains main concepts such as dependency resolvers and patterns, and give an overview on how ivy works internally.
|
||||
It's also in the reference doc that you will find all you always dreamed to know about ivy configuration, ivy files, and ivy use (especially with ant).
|
||||
<li><a href="doc/appendix.html">Appendix</a></li>
|
||||
The appendix section contains a bunch of Ivy related information which is not part of Ivy reference doc.
|
||||
</ul>
|
||||
|
||||
You will also find here interesting pages like [[doc/bestpractices]], the [[faq]] or the [[links]] pages.
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,113 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h2>Disclaimer</h2>
|
||||
<code>
|
||||
Apache Ivy is an effort undergoing incubation at The Apache Software
|
||||
Foundation (ASF). Incubation is required of all newly accepted projects
|
||||
until a further review indicates that the infrastructure, communications,
|
||||
and decision making process have stabilized in a manner consistent with
|
||||
other successful ASF projects. While incubation status is not necessarily
|
||||
a reflection of the completeness or stability of the code, it does
|
||||
indicate that the project has yet to be fully endorsed by the ASF.
|
||||
</code>
|
||||
|
||||
<h2>Download</h2>
|
||||
<div style="float:right;margin:10px;"><a href="http://people.apache.org/dist/incubator/ivy/2.0.0-alpha-1-incubating/"><img src="images/ivy-dl-2.0.0-alpha-1.png" style="border: none;"/></a></div>
|
||||
The first release of Ivy within the Apache Incubator, <b>2.0.0-alpha-1</b>, is now available! Check the [[history/2.0.0-alpha-1 release notes]].
|
||||
|
||||
Use the links below to download a distribution of Ivy from our repository. It is good practice to <a href="#VerifyReleases">verify the integrity</a> of the distribution files, especially if you are using one of our mirror sites. In order to do this you must use the signatures from our <a href="http://people.apache.org/dist/incubator/ivy/">main distribution directory</a>.
|
||||
|
||||
Ivy is distributed as zip and tar.gz archives - the contents are the same. Please note that the tar.gz archives contain file names longer than 100 characters and have been created using GNU tar extensions. Thus they must be untarred with a GNU compatible version of tar.
|
||||
|
||||
You can download Ivy binary and source distribution here:
|
||||
<code>
|
||||
http://people.apache.org/dist/incubator/ivy/
|
||||
</code>
|
||||
|
||||
<h2>Building from source</h2>
|
||||
What you can get here at the ASF is the latest sources from the Subversion repository:
|
||||
<code>
|
||||
svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
|
||||
</code>
|
||||
Then to build Ivy from source, assuming you have ant 1.6.2+ and a jdk 1.4+ installed, then you only need to run the following command:
|
||||
<code>
|
||||
ant jar
|
||||
</code>
|
||||
Then you will find ivy.jar in <b>build/artifact</b>.
|
||||
|
||||
<h2>Snapshot build</h2>
|
||||
We drop snapshot builds from time to time to help people give early testing, without going into the full release process. These snapshot builds are usually built from the trunk with no other testing than our unit tests suite. Here is where they can be found:
|
||||
http://incubator.apache.org/ivy/downloads/latest/
|
||||
|
||||
<h2><a name="VerifyReleases">Verify Releases</a></h2>
|
||||
It is essential that you verify the integrity of the downloaded files using the PGP signature or the SHA1 or MD5 checksums. The checksums are not as strong indicators as the PGP signature.
|
||||
|
||||
The PGP signatures can be verified using PGP or GPG. First download the <a href="http://people.apache.org/dist/incubator/ivy/KEYS">KEYS</a> as well as the asc signature file for the particular distribution. Make sure you get these files from the <a href="http://people.apache.org/dist/incubator/ivy/">main distribution directory</a>, rather than from a mirror. Then verify the signatures using
|
||||
|
||||
<code>
|
||||
% pgpk -a KEYS
|
||||
% pgpv apache-ivy-2.0.0-alpha-1-incubating-bin.tar.gz.asc
|
||||
</code>
|
||||
<em>or</em>
|
||||
<code>
|
||||
% pgp -ka KEYS
|
||||
% pgp apache-ivy-2.0.0-alpha-1-incubating-bin.tar.gz.asc
|
||||
</code>
|
||||
<em>or</em>
|
||||
<code>
|
||||
% gpg --import KEYS
|
||||
% gpg --verify apache-ivy-2.0.0-alpha-1-incubating-bin.tar.gz.asc
|
||||
</code>
|
||||
|
||||
Alternatively, you can verify the checksums on the files. Unix programs called md5/sha1 or md5sum/sha1sum are included in many unix distributions. *sum is also available as part of <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/">here</a>. <a href="http://www.slavasoft.com/fsum/">fsum</a> supports MD5 and SHA1.
|
||||
|
||||
We highly recommend to verify the PGP signature, though.
|
||||
|
||||
<h2>Latest stable version (not Apache)</h2>
|
||||
The latest stable version of Ivy is <a href="doc/releasenotes/1.4.1.html">1.4.1</a>, and is not an Apache incubating release, but a release done while Ivy was still hosted by jayasoft:
|
||||
<ul>
|
||||
<li><a href="http://www.jaya.free.fr/downloads/ivy/1.4.1/ivy-1.4.1-bin.zip">binaries</a></li>
|
||||
<li><a href="http://www.jaya.free.fr/downloads/ivy/1.4.1/ivy-1.4.1-src.zip">sources</a></li>
|
||||
<li><a href="http://www.jaya.free.fr/downloads/ivy/1.4.1/ivy-1.4.1-doc.zip">documentation</a></li>
|
||||
</ul>
|
||||
|
||||
To have a quick overview of some of the changes in this version, check the <a href="doc/releasenotes/1.4.html">1.4.1 release notes</a> page.
|
||||
|
||||
You can also download ivy jar and ivy.xml alone directly from the jayasoft site (useful especially for easy ant setup) using the following pattern:
|
||||
http://www.jayasoft.org/downloads/ivy/[revision]/[artifact]-[revision].[ext]
|
||||
|
||||
This is used to auto install Ivy from internet, in the <a href="doc/tutorial.html">first tutorial</a>. Take a look at these examples if you want such an auto install feature in your own builds.
|
||||
The xsd for ivy files of the version is also available online at:
|
||||
http://www.jayasoft.org/downloads/ivy/[revision]/ivy.xsd
|
||||
|
||||
To have info about the different kind of distributions, see <a href="choose-distrib.html">that page</a>.
|
||||
For previous version information and download, see the <a href="doc/releasenotes.html">release notes page</a> in the documentation.
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
119
doc/faq.html
119
doc/faq.html
|
|
@ -1,119 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>What and Why</h1>
|
||||
<h2><a name="what-is-ivy"></a>What is Ivy ?</h2>
|
||||
<p>Ivy is a powerful dependencies manager with transitive dependencies support and much more <a href="features.html">features</a>.</p>
|
||||
<p>With Ivy you define the dependencies of your module in an xml file, called an ivy file. Then you usually ask ivy to retrieve your dependencies to a local lib dir, and it does it for you by locating the artifacts of your dependencies in repositories, such as ibiblio.</p>
|
||||
<h2><a name="why-should-i-use-a-dependencies-manager"></a>Why should I use a dependencies manager ?</h2>
|
||||
<p>Without a dependencies manager, two solutions are often used to store the dependencies of a project: a project lib dir or direct access to a shared repository.<br />
|
||||
The major drawback of the project lib dir is that the same dependencies are stored in multiple location if you have several projects using the same dependencies. Moreover, we often see project where dependencies revisions are not documented, which can cause problems for maintenance.<br />
|
||||
With the shared repository the problem is often to maintain the list of dependencies of the project. This list is often lost within the build file, which does not help maintenance. Moreover, this solution often requires a download of the whole repository, unless home made dependencies management solution has been used.</p>
|
||||
<p>Finally, the major drawback of these solutions is that they do not use transitive dependencies. Transitive dependencies are the dependencies of your dependencies. Managing transitive dependencies let you declare dependencies only on what you really need, and not what the module you use themselves need. This not only eases your dependencies declaration, but it also improves a lot the maintenability of your project, especially in multi-project environment. Imagine you develop a component used in several other projects. Then each time your component needs a new dependency, without transitive dependencies, you have to update all the projects using your component ! And this could really take a lot of time !</p>
|
||||
<h2><a name="why-should-i-use-ivy"></a>Why should I use Ivy ?</h2>
|
||||
<p>If you are convinced of using a dependencies manager, you may wonder why using Ivy and not another tool. We are not able to answer this question without being biased, but have a look at Ivy <a href="features.html">features</a> and the [[m2comparison product comparison]] we provide, and you will certainly see that Ivy is one of the best dependencies manager currently available ;-)</p>
|
||||
<h2><a name="how-does-ivy-differ-from-maven-2"></a>How does Ivy differ from Maven2 ?</h2>
|
||||
<p>The answer to this question is too long, so it deserves its own page <a href="doc/m2comparison.html">here</a>.</p>
|
||||
<h1>Ivy in use</h1>
|
||||
<h2><a name="i-dont-understand-whats-happening"></a>I don't understand what's happening...</h2>
|
||||
<p>The first thing to do when you don't understand what's going wrong is to try to change the message level. If you use ant, you can use the -debug or -verbose options to get more detailed messages and better understand what's happening.</p>
|
||||
<h2><a name="ivy-seems-to-fail-connecting"></a>Ivy seems to fail connecting to ibiblio...</h2>
|
||||
<p>First, check if the ibiblio site is ok with your favorite browser. If the site is ok, maybe it's a problem of proxy configuration. Set your ANT_OPTS environment variable<br />
|
||||
to configure your proxy if you have one.<br />
|
||||
For instance:<br />
|
||||
<code>set ANT_OPTS=-Dhttp.proxyHost=myproxy -Dhttp.proxyPort=3128</code></p>
|
||||
<p>If it still doesn't work, maybe it's your dependency file which is not ok. Check<br />
|
||||
if the module name you depend on is actually a name of directory under<br />
|
||||
<a href="http://www.ibiblio.org/maven/" title="www.ibiblio.org/maven/">www.ibiblio.org/maven/</a>. If this is the case, check if the jar with a name like<br />
|
||||
[module]-[revision].jar is present under the jars directory of this module on ibiblio.<br />
|
||||
For instance: <a href="http://www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.jar" title="www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.jar">www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.jar</a></p>
|
||||
<p>If this is the case, check your ivy configuration to see if you actually use the ibiblio<br />
|
||||
or ivyrep resolver.</p>
|
||||
<p>Finally, you can check if the files were not downloaded but corrupted<br />
|
||||
(Ivy has no md5 checking for the moment) by checking your lib directory and opening<br />
|
||||
the jars if any with an unzip program.</p>
|
||||
<p>If you still have problems post on the <a href="forum/core.html">forum</a><br />
|
||||
mentioning your OS, your version of ant, your version of ivy, your configuration file<br />
|
||||
and your ivy file.</p>
|
||||
<h2><a name="ivy-fails-to-get-an-artifact"></a>Ivy fails to get an artifact / ivy file on my http server. What's wrong?</h2>
|
||||
<p>The first thing to do is to ensure the setting is correct. Ivy should log the url it tried, copy this url and paste it in your favorite browser, and verify you get no error.</p>
|
||||
<p>If this is ok, check if you don't need any proxy setting nor authentication. For proxy setting, you can use for instance this:<br />
|
||||
<code>set ANT_OPTS=-Dhttp.proxyHost=myproxy -Dhttp.proxyPort=3128</code><br />
|
||||
For authentication, fill in the appropriate data at <a href="doc/use/configure.html">configuration</a> time.</p>
|
||||
<p>If you still have no idea of what is wrong, then I suggest to use commons-httpclient if it isn't already the case (you should just put commons-httpclient in you classpath), and then <a href="http://jakarta.apache.org/commons/httpclient/logging.html">turn on the debug logging</a>.</p>
|
||||
<p>You will then have very detailed information on how your url is handled. If you still have problem, ask for help on the <a href="forum/core.html">forum</a>.</p>
|
||||
<h2><a name="getting-rid-of-lib-directory"></a>What if I do not want to put my library files in the lib directory ? </h2>
|
||||
<p>No problem, you just have to set an ant property:</p>
|
||||
<code><property name="ivy.lib.dir" value="pathtomylibdir"/></code>
|
||||
<h2><a name="getting-rid-of-revision"></a>What if I do not want the revision of the files I retrieve to appear in the file name ?</h2>
|
||||
<p>A typical question for people using an IDE like eclipse and often changing<br />
|
||||
dependency revision: it's a bit boring to change your IDE project just to tell<br />
|
||||
him to use comp-build2596.jar instead of comp-build2595.jar, when you have<br />
|
||||
already changed your ivy file (and even if you haven't changed it, if you use<br />
|
||||
the continuous integration feature !). No problem, you have a total control on<br />
|
||||
the files retrieved using the pattern attribute in the retrieve task:</p>
|
||||
<p>Here is the default pattern:</p>
|
||||
<code><ivy:retrieve pattern="${ivy.lib.dir}/[artifact]-[revision].[ext]"/></code>
|
||||
<p>And here is one which do not suffix file name with dependency revision:</p>
|
||||
<code><ivy:retrieve pattern="${ivy.lib.dir}/[artifact].[ext]"/></code>
|
||||
<p>And one which makes your lib directory have the same layout as the ibiblio repository:</p>
|
||||
<code><ivy:retrieve pattern="${ivy.lib.dir}/[module]/[type]s/[artifact]-[revision].[ext]"/></code>
|
||||
<p>Not too difficult, and really flexible, isn't it ? And check the retrieve task<br />
|
||||
reference documentation to learn more about it...</p>
|
||||
<h2><a name="why-two-xml-files"></a>Why two xml files ?</h2>
|
||||
<p>Ivy uses two types of xml files: configuration files and ivy files.</p>
|
||||
<p>In fact, Ivy distinguishes two different steps to describe and get your<br />
|
||||
dependencies:<br />
|
||||
You write ivy files to describe the dependencies of your module, independently of how you retrieve them.<br />
|
||||
Then you configure ivy to indicate where it can find your dependencies. Thus you can easily share your ivy files, even if you have internal dependencies which are not resolved the same way in your environment as in the target development environment. You just need to write two configuration files, one in your default development environment, and one in the target development environment with the <b>same ivy files</b>. </p>
|
||||
<h2><a name="how-do-i-separate-dependencies"></a>How do I separate the dependencies I need at xxx time and the one I need at yyy time ?</h2>
|
||||
<p>Ivy uses a concept called <i>configurations</i> to handle this, and many more. As explained in the <a href="doc/terminology.html">terminology page</a>, a <i>configuration</i> of your module can be thought as a way to use your module (<i>note: this has nothing to do with the configuration of ivy itself, through the use of configuration file</i>). You can describe what dependencies are needed in each configuration. </p>
|
||||
<p>Moreover, because the dependencies are modules too, they can also have configurations. What is extremely powerful with ivy is that you can define configurations mapping, i.e. which conf of the dependency is needed in which conf of your module. Thus what is needed at 'runtime' of a dependency can be needed for 'test' of your module.</p>
|
||||
<p>Finally, the configurations are unlimited, defined in each module, and can extend each other. This contributes a lot to ivy flexibility.</p>
|
||||
<h2><a name="no-artifact"></a>Can I write an ivy file for a module with no artifact at all ?</h2>
|
||||
<p>Yes, this is what is called a 'virtual' module.</p>
|
||||
<p>Having a module which has no publication and only dependencies can be useful in many cases. </p>
|
||||
<p>In particular, you can in this way define a set of dependencies used in several projects. Once defined, you can simply add a dependency on this virtual module to get all its dependencies, thanks to transitive dependencies management.</p>
|
||||
<p>It can also be useful if you want to define a flexible framework. In your framework, you will certainly have several modules, each having its own dependencies. But for the users of your framework, it can be interesting to provide a virtual module, representing the framework as a whole, and using configurations to let the user choose what he really wants to use in your framework, in a very flexible and effective way.</p>
|
||||
<p>But the problem is that ivy considers by default that a module publishes one artifact, with the same name as the module itself. So the way to define a virtual module is to add to its ivy file a publications section with no publication inside:</p>
|
||||
<code><publications/></code>
|
||||
<h2><a name="ibiblio-module-missing"></a>I do not manage to get xxx module on ibiblio. What's wrong ?</h2>
|
||||
<p>The problem can come from several places... usually it comes from the fact that some modules on ibiblio do not respect a clean structure.</p>
|
||||
<p>For instance, opensymphony projects are all in an opensymphony directory, which does not respect the [module]/[artifact]-[revision].[ext] pattern. In this case the only way to go with this is to configure another resolver with the appropriate pattern, and configure ivy to use this resolver for opensymphony only.</p>
|
||||
<p>Another similar problem is to have several modules in one directory, such xerces and xmlapis in the xerces directory. The problem is that if you consider the two as one module, you will be tempted to declare a dependency on two revisions of this module. This is not the right approach, because this does not match ivy definition of a module. A better approach is similar to the preceding one with a special configuration for this only.</p>
|
||||
<p>Another solution is to setup a local repository for those modules that are not cleanly deployed on ibiblio. Using this local repository first and the ibiblio repository after is a good way to turn around the problems of ibiblio and still benefit from the huge number of artifacts that can be found.</p>
|
||||
<h2><a name="module-update"></a>When I update an ivy file in my repository ivy do not take the change into account. Is this normal ?</h2>
|
||||
<p>This the default behaviour of ivy, which relies on the revision and on its cache to avoid too many downloads. However, this can be changed on each resolver using the <em>checkmodified</em> attribute, or globally by setting <em>ivy.resolver.default.check.modified</em> variable to true.</p>
|
||||
<h1>Misc</h1>
|
||||
<h2><a name="release-notes"></a>Where are the release notes ?</h2>
|
||||
<p>Release notes can be found in the [[doc/index documentation]].</p>
|
||||
<h2><a name="more-information"></a>Where can I get more information?</h2>
|
||||
<p>If you need more information about Ivy than the one found in the documentation, you can see the <a href="links.html">links</a> page, use the <a href="forum/core.html">forum</a> to ask your question to the community, or use your favorite search engine.<br />
|
||||
For search engine search, we advise to use ivy + ant or java as base keywords, since ivy alone is a very common word.</p></textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,83 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<p>Ivy is a very powerful dependency manager oriented toward Java dependency management, even though it could be used to manage dependencies of any kind.</p>
|
||||
<p>If you don't see why you should use a dependency manager at all, or have any question concerning Ivy in general, have a look at the <a href="faq.html">FAQ</a> and at the [[mailing-lists]].</p>
|
||||
<h1>Integrated with Ant</h1>
|
||||
<p>Of course, Ivy is integrated with the most popular build management system for Java projects. But the integration goes way beyond common Ant integration. Indeed Ivy has been designed with Ant integration and design principles in mind. If you have Ant skills, you already have Ivy skills! The plugin mechanism in Ivy follows the same design as Ant, you will find macrodef and files import in Ivy configuration, many things with which Ant users are already familiar with.<br/>
|
||||
And since Ivy is now an Apache project, we are getting even closer to Ant development.</p>
|
||||
<h1>Simple to use</h1>
|
||||
<p>For simple cases, Ivy is easy to use. Declare your dependencies, and that's all. See the <a href="doc/tutorial/start.html">quick start tutorial</a> to check yourself, it should take less than 5 minutes!</p>
|
||||
<p>Ivy can therefore be used to bring the dependency management feature of maven to Ant build files, for those of you who already use Ant and who do not want to setup a maven project. But Ivy does not stop there, it provides many more great features!</p>
|
||||
<h1>Clean dependency reports</h1>
|
||||
<p>Ivy is able to produce mainly two kind of reports: HTML reports and graph reports. HTML reports gives you a good understanding of what Ivy did, and which dependencies your project depends upon. The graph reports let you have a good overview of the transitive dependencies (see below) and conflicts in your project.</p>
|
||||
<p>Here are some samples of what Ivy generates for you:<br />
|
||||
<center><br />
|
||||
<a href="samples/ivy-sample-xslt.xml"><img src="images/ivyfile-small.png" title="browsable ivy file through simple xslt"/></a> <a href="images/hibgraph.png" alt="ivyfile"><img src="images/hibgraph-small.png" title="full dependency graph"/></a> <a href="samples/jayasoft-ivyrep-example-default.html" alt="graph"><img src="images/report-small.png" title="detailed dependency report" alt="report"/></a><br />
|
||||
</center></p>
|
||||
<h1>Non intrusive</h1>
|
||||
<p>Ivy most common use is to resolve dependencies and copy them in the lib dir of your project. Once copied, your build does not depend on Ivy any more. Thus you can easily migrate existing builds using the lib dir pattern to store dependencies. Moreover, you can easily deliver your project with its dependencies so that the build file does not depend on Ivy.</p>
|
||||
<h1>Extremely flexible</h1>
|
||||
<p>With Ivy, you usually do not have to adapt your project to Ivy structure, Ivy will conform to your environment.</p>
|
||||
<p>Even though Ivy comes with a lots of default values to work out of the box, you can change many things in Ivy. Of course, the dependencies repositories possibilities covers a lot of uses (file system, URL based, repository chaining, ...). But that's not all. You can change the way Ivy finds latest versions of your dependencies, you can change of conflict manager, you can choose if you want Ivy to copy dependencies in your project libs or use them directly from Ivy cache, ...</p>
|
||||
<h1>Easily extensible</h1>
|
||||
<p>When Ivy does not do what you want out of the box, you can often extend it to solve your problem. For instance, you can plug your own repository (like Scott Haug did for a svn repository now available in Ivy tools). But you can also define your own latest strategy and your own conflict manager. See <a href="doc/extend.html">how to extend Ivy</a> in the reference doc. </p>
|
||||
<p>Since Ivy 1.4 you can even define very easily your own metadata on your modules, with <a href="doc/concept.html#extra">extra attributes</a>.</p>
|
||||
<h1>High performances</h1>
|
||||
<p>In Ivy, performances have been taken in consideration from the beginning. It uses a cache to avoid downloading twice a dependency, its strong conflict management system has been thought to avoid downloading a dependency if not necessary, all configuration and Ivy file parsing are done using SAX for maximum performance, and so on...</p>
|
||||
<h1>Transitive dependencies</h1>
|
||||
<p>Imagine you have a component that you often reuse in your software development. Imagine that this component has dependencies as well. Then with classical dependency management, each time you use this component in your software you have to declare it as a dependency, but also all its dependencies.</p>
|
||||
<p>With Ivy it's different: you simply write a dependency file once for the component, declaring its own dependencies, then anytime you want to use this component you simply have to declare a dependency on it.</p>
|
||||
<p>And this is even more powerful if the component your software depends on changes of dependencies during its own development. Then, without Ivy, you have to maintain all your components dependencies declaration each time the dependencies of this component change. With Ivy, you update the Ivy file of the component and that's it !</p>
|
||||
<p><i>If you want to quickly start using this feature or simply see it in action with real world examples, check the official repository: <a href="ivyrep.html">ivyrep</a></i></p>
|
||||
<h1>Strong conflict management</h1>
|
||||
<p>The problem with transitive dependencies is that it's sometimes difficult to know exactly which version of a dependency you get, because several modules are depending on it in different versions. Ivy provides a strong and flexible conflict management engine, which let you easily choose which version should be evicted or kept if its default behaviour does not fit your needs. </p>
|
||||
<p>It is also fully integrated with transitive dependencies management, which means that conflicts are solved for each dependency before being solved for your whole module. This ensures that problematic conflicts will only need to solved in the dependency they are encountered.</p>
|
||||
<h1>Out of the box ibiblio repository support</h1>
|
||||
<p>Maven users all know this repository, where you can find a lot of Java projects artifacts. With Ivy, you benefit from this repository out of the box. But you even benefit from more, since Ivy also uses its <a href="http://ivyrep.jayasoft.org/">own repository</a> for dependencies metadata, leveraging the power of transitive dependencies.</p>
|
||||
<h1>Continuous Integration Ready</h1>
|
||||
<p>Are you working in a continuous integration environment? No? You should ;-)</p>
|
||||
<p>If you are working in a continuous integration environment, and if you have many projects that depend one on each other, then you are maybe experiencing the dependency management nightmare... Fortunately, Ivy is there to help !</p>
|
||||
<p>With Ivy you can declare that a component depends on the latest version of another component. Knowing that, Ivy will search for the latest version of the dependency whenever you ask it to do so. This latest version is computed by Ivy either by checking the date of the dependency versions or by comparing versions as text (either lexicographically or with an algorithm close to the one used in php version_compare function).</p>
|
||||
<h1>Publication handling</h1>
|
||||
<p>Ivy handles for you the publication of your projects to your repository, as defined in Ivy. This simplifies a lot the management of multi-project environment.</p>
|
||||
<h1>Pluggable module descriptor parsers</h1>
|
||||
<p>Ivy is able to use Ivy files as module descriptors, but also maven2 POMs, or even your own module descriptors! This can help you move softly from an existing repository of modules to an Ivy managed one.</p>
|
||||
<h1>Unique enterprise features</h1>
|
||||
<p>Ivy is the only dependency management tool to support powerful features such as repository namespace and building through the install task. A <a href="doc/tutorial/build-repository.html">tutorial</a> is dedicated to this feature, and show you how you can build your own repository importing data from public one, and converting heterogeneous repositories into a stable and homogeneous one.</p>
|
||||
<h1>Heavily tested</h1>
|
||||
<p>Ivy benefits from a lot of unit tests checked at each code modification. It is also under heavy testing by the community itself, and bugs reported by the community are often fixed in only a few days.</p>
|
||||
<h1>Supported by several tools</h1>
|
||||
<p>A growing number of tools support Ivy, see the <a href="links.html">links</a> page for details.</p>
|
||||
<h1>Free and open source</h1>
|
||||
<p>Ivy is an incubating Apache project, which means that it's fully open sourced, with a business friendly Apache license.</p>
|
||||
<p>Being open source, you can even modify it for your own needs, and let the community benefit from your enhancements if you like.</p>
|
||||
<h1>Extensively documented</h1>
|
||||
<p>With Ivy, not only the tool is free and open source, but you also have access to a documentation of about 120 pages in its printer friendly version for free!</p></textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,48 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
As an Apache Incubator project, Ivy is very open to external contributions.
|
||||
|
||||
There are many ways to contribute to Ivy.
|
||||
|
||||
First, [[download]] and use it, subscribe to the [[mailing-lists]], and answer to other user questions. You can also browse [[issues jira issues]], vote for the one you are most interested in, add your comments and feedback. You can also very easily contribute to the [[wiki]].
|
||||
|
||||
When you browse the documentation, whenever you see something that could be improved, feel free to edit it and provide a documentation patch. It's very easy if you browse the documentation offline (in the doc directory if you check out Ivy from svn), you will see a small toolbar at the upper left of the page, which allows you to edit the page. Then all you have to do is attach your modification as a patch to a new issue in JIRA.
|
||||
<i>If you are interested in contributing documentation, read [[write-doc this page]].</i>
|
||||
|
||||
You can also provide brand new documentation pages, tutorials, demo, or even links to a tutorial on your own blog.
|
||||
|
||||
Another useful way to contribute is to spread the word: if you like Ivy, say it! On your blog, on other blog comments, on popular java related sites, wherever. The more Ivy is popular, the more it will get external contributions, and the better it will be, for the benefit of the whole community.
|
||||
|
||||
When you get more confident with Ivy, you can check it out from svn, and begin to see if there are issues you could fix or implement, and provide patches to make the whole community benefit from your work.
|
||||
|
||||
When you provide a patch, to increase the chance to get integrated, do not forget to provide a junit test, and a patch to the documentation if it changes anything in Ivy behaviour.
|
||||
|
||||
And if you often provide patches and answers on the mailing lists, you may get the chance to become a commiter, with write access to the svn repository!</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-01-16)</h1>
|
||||
- Bug fix: NPE in publish task.
|
||||
- Documentation update.
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.5.1-bin.zip">ivy-0.5.1-bin.zip</a> (742 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.5.1-src.zip">ivy-0.5.1-src.zip</a> (511 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.5.1-src-withdep.zip">ivy-0.5.1-src-withdep.zip</a> (774 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Ivy 0.5 is the first public version of Ivy, plublished on 2005-01-12.
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.5-bin.zip">ivy-0.5-bin.zip</a> (731 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.5-src.zip">ivy-0.5-src.zip</a> (501 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.5-src-withdep.zip">ivy-0.5-src-withdep.zip</a> (764 kB)
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,41 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-02-11)</h1>
|
||||
+ bugs fix
|
||||
- conf 'extends' problem with publications
|
||||
- typedef badly handled in ivyconf.xml
|
||||
- default properties loading in ivy configure loaded using task classloader
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.6.1-bin.zip">ivy-0.6.1-bin.zip</a> (947 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.6.1-src.zip">ivy-0.6.1-src.zip</a> (739 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.6.1-src-withdep.zip">ivy-0.6.1-src-withdep.zip</a> (1002 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,54 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-02-03)</h1>
|
||||
+ functional
|
||||
- added haltonfailure attribute on resolve and retrieve task, so that build can be halt when resolve or retrieve fails
|
||||
- added dependency artifacts filtering feature, enabling to work better with ibiblio
|
||||
- ibiblio resolver can now be configured to use any maven like repository, with root and pattern attributes
|
||||
- added download progression info on resolve
|
||||
- default cache is now in user home (.ivy-cache in user home), so that cache is shared by default for all projects of the same user
|
||||
- added public access to method getDependencies(...) in Ivy, which resolve dependencies without downloading artifacts
|
||||
- added DualResolver, which allows to have ivy files in one place and artifacts in another one
|
||||
|
||||
+ non functional
|
||||
- added some unit tests
|
||||
- deep review of ivy file reference documentation
|
||||
|
||||
+ bugs and refactoring
|
||||
- bug fix: SimpleURLResolver not handling the case when there is no ivy file
|
||||
- refactoring: URLResolver renamed to AbstractURLResolver
|
||||
- refactoring: SimpleURLResolver renamed to URLResolver
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.6-bin.zip">ivy-0.6-bin.zip</a> (935 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.6-src.zip">ivy-0.6-src.zip</a> (723 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.6-src-withdep.zip">ivy-0.6-src-withdep.zip</a> (986 kB)
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-03-11)</h1>
|
||||
- added latest sub revision feature: you can now select the latest sub revision of a module using a +. For instance, "1.0+" selects the latest revision starting with 1.0. (thanks to jonas for the idea)
|
||||
- haltonfailure now defaults to true (as suggested by Jeroen)
|
||||
- shorter info lines to better view important info (as suggested by Jeroen)
|
||||
- retrieve now checks if files are up to date before copying them from cache. This feature can be disabled using the checkUpToDate attribute in ivy configuration file.
|
||||
- do not download dependencies when not necessary during publication (as suggested by Daniele)
|
||||
- bug fix: better handling of publish without recursive delivery
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.7-bin.zip">ivy-0.7-bin.zip</a> (951 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.7-src.zip">ivy-0.7-src.zip</a> (745 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.7-src-withdep.zip">ivy-0.7-src-withdep.zip</a> (1008 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,56 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-03-30)</h1>
|
||||
<i>Note: this version is a major update compared to version 0.7, and contains several API breaks. Ivy files and configuration are compatible, but this is not the case of Ivy Java API. Some defaults changes also, especially default resolver which is no longer ibiblio but ivyrep (but ivyrep is compatible with ibiblio, so it should no break your builds).</i>
|
||||
|
||||
- url resolver now handles latest with file urls and http ones (tested only with apache server, many thanks to Glen Marchesani for its contribution)
|
||||
- added publish artifacts feature, which enable to publish declared artifacts of a module to a repository described by a dependency resolver. It currently works only with filesystem resolver.
|
||||
- added conflict management at resolve time: during resolve, modules in conflict can be evicted and thus not downloaded
|
||||
- added ivyrep resolver, using ivyrep to find ivy files, and ibiblio for artifacts
|
||||
- use ivyrep instead of ibiblio as default resolver
|
||||
- added more info in ivy files (description, homepage, ivy authors, license, public repository, ...)
|
||||
- added validate attribute on resolve, retrieve and publish, which allows to disable ivy file validation against ivy.xsd (useful to parse future compatible ivy files)
|
||||
- ant properties are now available in ivysettings file
|
||||
- unified default properties in ivysettings, with better independance from url or file
|
||||
- added ext on artifacts: this enable to distinguish artifact extension from artifact type, util in cases where it differs (example: 'src' type with 'zip' extension, 'ivy' type with 'xml' extension, ...)
|
||||
- added latest strategy concept: the way to determine which artifact is the latest is now configurable on resolvers handling latest.
|
||||
- added parameter on chain resolver to say if it should return first found or try to find the latest among all if asked
|
||||
- a module can now publish no artifact, useful for virtual modules consisting only of integration of other modules
|
||||
- now cache layout is configurable, using cacheIvyPattern and cacheArtifactPattern attributes on conf element in ivysettings.xml
|
||||
- changed default cache layout: artifacts are separated by type
|
||||
- added cachepath task, which enables to build an ant path of artifacts in cache required for a conf
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.8-bin.zip">ivy-0.8-bin.zip</a> (946 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.8-src.zip">ivy-0.8-src.zip</a> (761 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.8-src-withdep.zip">ivy-0.8-src-withdep.zip</a> (1024 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,59 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-04-06)</h1>
|
||||
<i>Note: this version is not compatible with preceding ones.
|
||||
The way to indicate patterns (in configuration as well as in some tasks) has changed: brackets are used for tokens instead of ant notation, which is kept for variables.
|
||||
Thus a pattern previously noted:
|
||||
${repository.dir}/${organisation}/${module}/${artifact}-${revision}.${ext}
|
||||
will now be:
|
||||
${repository.dir}/[organisation]/[module]/[artifact]-[revision].[ext]
|
||||
|
||||
This has been done to prevent collision and make a better separation between variables and tokens.
|
||||
Moreover migration costs should not be too high, ivy files not being concerned by the change.
|
||||
</i>
|
||||
- ChainResolver are now able to publish (delegating the call to the first resolver in the chain)
|
||||
- DualResolver sub resolvers are now registered in Ivy
|
||||
- more precise message on eviction
|
||||
- add validate attribute on most resolvers
|
||||
- ivy files validation handling review
|
||||
- use ivy variables in ant tasks to get default values for attributes
|
||||
- documentation update for configuring ivy
|
||||
- FIX: dependencies order not taken into account during resolve
|
||||
- FIX: evicting modules also evict confs
|
||||
- FIX: NPE during resolve when a dependency ivy file has no publication date
|
||||
- FIX: check nullity of artifact download reports
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.9-bin.zip">ivy-0.9-bin.zip</a> (958 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.9-src.zip">ivy-0.9-src.zip</a> (776 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-0.9-src-withdep.zip">ivy-0.9-src-withdep.zip</a> (1039 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,46 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-04-12)</h1>
|
||||
- add report task, which enables to generates reports of dependencies, including a graph ready to be layed out by yEd
|
||||
- add exclude feature in dependency
|
||||
- include exclude feature now handles regexps
|
||||
- new latest strategy: latest revision now uses a "php version_compare" like algorithm, whereas lexicographic comparison is now available in latest lexicographic
|
||||
- enhance xml resolve report details
|
||||
- FIX: better separation between root configurations
|
||||
- FIX: XmlModuleDescriptorUpdater now preserves xml header
|
||||
- FIX: modules figures in report (displayed at the end of resolve)
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc1-bin.zip">ivy-1.0-rc1-bin.zip</a> (1161 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc1-src.zip">ivy-1.0-rc1-src.zip</a> (984 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc1-src-withdep.zip">ivy-1.0-rc1-src-withdep.zip</a> (1247 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,45 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-04-18)</h1>
|
||||
- IMPROVE: improved messages: more debug, more verbose, and more details on failures
|
||||
- FIX: bug with '\' in path patterns
|
||||
- FIX: bug with relative paths patterns
|
||||
- FIX: configure task tries ivy.conf.file as relative to base dir and to current dir
|
||||
- FIX: file system resolver publishes ivy files with ivy pattern
|
||||
- FIX: 0 content length considered as non existing (behaviour of jre 5.0 on linux)
|
||||
=> empty ressources are now considered as non existing
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc2-bin.zip">ivy-1.0-rc2-bin.zip</a> (1164 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc2-src.zip">ivy-1.0-rc2-src.zip</a> (987 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc2-src-withdep.zip">ivy-1.0-rc2-src-withdep.zip</a> (1250 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,45 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-04-21)</h1>
|
||||
<i>A few bugs have been discovered in the 1.0-rc2, so here is the reason for this rc3, which should fix these bugs.
|
||||
If no bug is discovered, 1.0-rc3 should be promoted to 1.0 on <b>2005-04-26</b></i>
|
||||
- IMPROVE: added debug messages on variables setting
|
||||
- FIX: ivysettings now able to load a properties file given as url
|
||||
- FIX: deliver pub date now actually defaults to 'now'
|
||||
- FIX: all tasks attributes now substitute ivy variables
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc3-bin.zip">ivy-1.0-rc3-bin.zip</a> (1168 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc3-src.zip">ivy-1.0-rc3-src.zip</a> (993 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-rc3-src-withdep.zip">ivy-1.0-rc3-src-withdep.zip</a> (1256 kB)
|
||||
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,46 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
1.0-rc3 has been promoted to 1.0 on 2005-04-26
|
||||
|
||||
See child pages for details about changes introduced by each release candidate
|
||||
|
||||
<i>Known bugs and limitations:</i>
|
||||
- cyclic dependencies result in StackOverflowError
|
||||
- infinite loop in rare cases when a conflict occur between a latest subversion and a fully resolved revision
|
||||
- url connections not closed properly when not using commons-httpclient
|
||||
- latest does not work with http urls in some cases, when the name of the link is truncated in the web page
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-bin.zip">ivy-1.0-bin.zip</a> (1166 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-src.zip">ivy-1.0-src.zip</a> (904 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.0-src-withdep.zip">ivy-1.0-src-withdep.zip</a> (1167 kB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,69 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-06-13)</h1>
|
||||
- remote configuration (if available) of ivyrep and ibiblio patterns and roots
|
||||
- new detailed messages when ivy fails to reach an url (thanks to Nicolas)
|
||||
- new artifactproperty task, which enables to set a property for each dependency artifacts resolved by ivy
|
||||
- new defaultconf attribute in ivy file dependencies, to change the default conf to use in the file when no conf is specified for a dependency
|
||||
- add the ability to change the xsl file and report name pattern used by report task
|
||||
- http listing now compatible with tomcat listing (tested with 5.0.28)
|
||||
- pub revision in deliver task now defaults to timestamp if not provided by any other way
|
||||
- debug messages improvements, with configuration dump among others
|
||||
- new var task, enables to set ivy variables from ant
|
||||
- now defaults for ivyrep and ibiblio resolver are configurable by variables
|
||||
- refactoring: introduce the notion of BasicResolver, Repository, Resource, RepositoryResolver, making much easier the task of writing basic resolvers
|
||||
- added checkmodified attribute on all basic resolvers, which defaults to ${ivy.resolver.default.check.modified}
|
||||
This makes ivy check last modified date of ivy files to see it its cache is up to date
|
||||
- artifacts download are now first made to a temp file, which is renamed only at the end of the download.
|
||||
This prevent interrupted downloads to be considered as finished
|
||||
- FIX: handle proxy configuration with http-client (thanks to Nicolas)
|
||||
- FIX: remove dependency on ant outside of ant integration classes
|
||||
- FIX: resolve problem when conflicts on latest revisions
|
||||
- FIX: allow use of any kind of URL in IvyRepResolver (both ivyroot and artroot) and IBibiblioResolver
|
||||
- FIX: chain resolver can now be used for artifacts part of dual resolver
|
||||
- FIX: now detects and warn about circular dependencies
|
||||
- FIX: cachepath task now takes pathid as parameter instead of id, to prevent
|
||||
special handling from ant
|
||||
- FIX: ivy.xsd: set artifact minOccurs to 0 in publications
|
||||
|
||||
Thanks to John Shields from Robert Half International, Inc.:
|
||||
- FIX: no more infinite loop when a conflict occurs between a latest subversion and a fully resolved revision
|
||||
- FIX: BasicURLHandler now closes its connections
|
||||
- FIX: ApacheURLLister now works with capital letter in revisions and truncated names
|
||||
- now use of ivy variables is allowed in ivy files
|
||||
- added a null check in pattern helper substitute
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.1-bin.zip">ivy-1.1-bin.zip</a> (999 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.1-src.zip">ivy-1.1-src.zip</a> (738 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.1-src-withdep.zip">ivy-1.1-src-withdep.zip</a> (1001 kB)
|
||||
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,68 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2005-09-16)</h1>
|
||||
<i>Note: due to a bad delivery operation, version 1.2 found on this site from 2005-09-14 to 2005-09-16 was not the intended 1.2 version. Please use 1.2a instead</i>
|
||||
|
||||
- new ivy.deps.changed property set if there are changes since last resolve (IVY-71)
|
||||
- new buildlist task: calculate order of dependencies of subprojects for easy multi-projects builds (IVY-69)
|
||||
- accept organization as token (IVY-55)
|
||||
- added type filtering mechanism on resolve task (IVY-45)
|
||||
- detect and warn about resolver using ivy cache as repository (IVY-53)
|
||||
- new transitive attribute on dependency, which enable to disable transitive dependency management on a particular dependency (thanks to Ingo Adler) (IVY-20)
|
||||
- new '@' in dependency configuration mapping declaration, used to indicate that a configuration maps to itself useful with *, '*->@' meaning that all configurations of the module maps to their equivalent (same name) in the dependency (IVY-52)
|
||||
- new changing attribute on dependencies indicate that the dependency artifacts may change even without revision change, but with only a new ivy file with new publication date
|
||||
- new useRemoteConfig on conf tag in ivyconf.xml, tells to use remote configuration file for repository config
|
||||
- new type filtering in cachepath task
|
||||
- new cachefileset task: builds an ant fileset of artifacts in cache
|
||||
- publish task now uses srcivypattern for ivy files finding and for delivery
|
||||
- better debug and error messages (IVY-60 IVY-61)
|
||||
- added a javadoc target in ant build (thanks to joshua nichols)
|
||||
|
||||
- FIX: module descriptors sort was failing in some case cases (fix by Karl Baum)
|
||||
- FIX: Ivy complains about schema directive (IVY-64)
|
||||
- FIX: 'null' status attribute in module descriptor (IVY-62)
|
||||
- FIX: report header contains incorrect link after resolve for multiple, comma-separated configurations (IVY-57)
|
||||
- FIX: error retrieving dependencies with a '+' in their revision if the ivy file doesn't exist - fixed by maarten coene (IVY-59)
|
||||
- FIX: trying to resolve latest with no revision in pattern caused a StackOverflowError (IVY-56)
|
||||
- FIX: now handle transitive eviction (IVY-51)
|
||||
- FIX: resolve now store resolved file id in ivy variables, so that multiple resolve calls can be followed by multiple retrieve, each retrieve will use the last resolve info (IVY-49)
|
||||
- FIX: IllegalStateException on retrieve done from command line
|
||||
- FIX: checks ivy files data consistency with asked info (org, module name and revision)
|
||||
- FIX: use AUTH configuration for configuration file
|
||||
- IMPROVE: added publish handling from command line (IVY-48)
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.2a-bin.zip">ivy-1.2a-bin.zip</a> (1028 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.2a-src.zip">ivy-1.2a-src.zip</a> (776 kB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.2a-src-withdep.zip">ivy-1.2a-src-withdep.zip</a> (1040 kB)
|
||||
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2006-01-25)</h1>
|
||||
<em>compatiblity with previous version:
|
||||
- the default place for the cache has changed, it is now in {USER_HOME}/.ivy/cache, instead of {USER_HOME}/.ivy-cache
|
||||
please move this directory if you want to avoid unnecessary downloads
|
||||
- modules are now logged as they are found, set ivy.log.module.when.found variable to false to avoid this</em>
|
||||
|
||||
- NEW: namespace system: a resolver can be declared to belong to a namespace, which itself specify the transformation to apply to convert it from and to system namespace (IVY-147)
|
||||
- NEW: pluggable module descriptor parsers let define new kind of module descriptor (IVY-146) (thanks to Maarten Coene)
|
||||
- NEW: a new install task let add modules found in a repository in another one, even transitively (IVY-141)
|
||||
- NEW: maven2 pom compatibility: most resolvers are now able to handle m2 pom as project metadata and there is a new convertpom task able to convert a pom file to an ivy file (IVY-140)
|
||||
- NEW: include configurations from external file (IVY-88)
|
||||
- NEW: a new default resolver which let override ivy files and artifacts found on public repository (ivyrep / ibiblio) and let publish modules in a local repository (IVY-132)
|
||||
- NEW: ivyconf file inclusion in ivyconf files (IVY-99)
|
||||
- NEW: macrodef feature in ivyconf for defining macro resolvers with parameters (IVY-98)
|
||||
- NEW: conf fallback mechanism (IVY-145)
|
||||
- NEW: exclusion now let exclude whole modules (IVY-144)
|
||||
- NEW: ability to use a dependency instead of an ivy file in standalone mode (IVY-96)
|
||||
- NEW: ability to output a path of dependencies in cache from the standalone mode (IVY-92)
|
||||
- NEW: it is now possible to reference existing resolver in resolver containers (IVY-35)
|
||||
- NEW: overwrite attribute in the publish task now let force overwrite of read only files (IVY-83)
|
||||
- NEW: add a conflict manager ("strict") making build fail when a diamond conflict is found (thanks to Christer Jonsson) (IVY-118)
|
||||
|
||||
- IMPROVE: generate xml report using ivy:report task (IVY-143)
|
||||
- IMPROVE: possibility to configure ivy so that special revisions are not queried as fixed one at all (IVY-139)
|
||||
- IMPROVE: better url querying management (IVY-138) (thanks to Bernard Niset)
|
||||
- IMPROVE: do not add resolver info in ivy files in cache so that they can be safely used as usual ivy files in a repository (IVY-137)
|
||||
- IMPROVE: review default conf mapping management (IVY-134)
|
||||
- IMPROVE: add possibility for a chain to behave like a dual chain (IVY-131)
|
||||
- IMPROVE: add possibility to avoid overwrite of an ivy variable when setting them in ivyconf.xml (IVY-127)
|
||||
- IMPROVE: ability to exclude the root project from the buildlist (thanks to Constantine Vetoshev) (IVY-124)
|
||||
- IMPROVE: exclusion of artifacts now works on transitive artifacts, and exclusion can specify organisation and/or module (IVY-116)
|
||||
- IMPROVE: now dynamic revisions replacement by deliver task can be turned off (IVY-120)
|
||||
- IMPROVE: better performance with deep transitive dependencies
|
||||
- IMPROVE: allow optional parts in the patterns (IVY-102) (thanks to Maarten Coene)
|
||||
- IMPROVE: ability to define variable directly in ivyconf.xml (IVY-100)
|
||||
- IMPROVE: ability to use no revision in pattern with latest.integration dependency, artifacts being updated according to revision change in ivy file (if checkmodified is set to true) (IVY-95)
|
||||
- IMPROVE: ability to specify a root module in buildlist to filter out unnecessary build files (IVY-93) (thanks to Kristian Cibulskis)
|
||||
- IMPROVE: import system properties as ivy variables in standalone mode
|
||||
- IMPROVE: string identifying a module is now clearly different from a path
|
||||
- IMPROVE: better error message when publish fails due to readonly destination (IVY-83)
|
||||
- IMPROVE: some javadoc improvements (IVY-136 IVY-129) (thanks to Stephen Nesbitt)
|
||||
|
||||
- FIX: problem resolving dependencies when 2 module versions have different configurations (IVY-151)
|
||||
- FIX: problem with inheritance between public and private conf (IVY-149)
|
||||
- FIX: no variable replacement during the deliver step (IVY-133)
|
||||
- FIX: conflict badly solved in some complex cases (IVY-130)
|
||||
- FIX: mapping on conf * now only takes public configurations (IVY-126)
|
||||
- FIX: bad dependency ivy files now causes failure (IVY-112)
|
||||
- FIX: stack overflow error in contradictory conflict cases (IVY-117)
|
||||
- FIX: publish now doesn't call deliver when not necessary (IVY-119)
|
||||
- FIX: cachefileset was returning all artifacts for empty configuration (IVY-108)
|
||||
- FIX: transitive and changing attribute were not copied in ivy files in cache (IVY-94)
|
||||
- FIX: chain resolver now support latest strategy configuration (IVY-90)
|
||||
- FIX: raise a clean error when a cyclic variable definition is found (IVY-75)
|
||||
- FIX: clean ant project reference at the end of the build to improve usability in ide launching multiple builds in the same vm (like netbeans) (IVY-87 - IVY-115)
|
||||
- FIX: ivy is now able to use simple ivy files in cache (doesn't need resolver info, use default one if no resolver is given) (IVY-86)
|
||||
- FIX: private conf not accessible from other modules (IVY-76)
|
||||
- FIX: root module configurations isolation bug fixed (IVY-84)
|
||||
- FIX: changed the place where ivy stores master ivy files in cache to not overlap with dependencies one (IVY-85)
|
||||
- FIX: bug in ResourceHelper didn't let override resource easily (IVY-80)
|
||||
- FIX: throws a circular dependency exception when a circular dependency is found instead of failing silently (IVY-79)
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.3-RC1-bin.zip">ivy-1.3-RC1-bin.zip</a> (1.41 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.3-RC1-src.zip">ivy-1.3-RC1-src.zip</a> (1.15 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.3-RC1-src-withdep.zip">ivy-1.3-RC1-src-withdep.zip</a> (1.48 MB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,51 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2006-02-15)</h1>
|
||||
- IMPROVE: ivy now supports ${pom.version} in poms (IVY-174)
|
||||
- IMPROVE: adds the possibility to disable concistency check (IVY-163)
|
||||
- IMPROVE: add possibility to choose matcher on include exclude and conflict manager rules in ivy files, and on resolver per module in ivyconf (IVY-161)
|
||||
- IMPROVE: add regexp management in the install ant task (IVY-154)
|
||||
|
||||
- FIX: httclient is not registered for https urls (IVY-171)
|
||||
- FIX: post resolve tasks like retrieve or cachepath should be able to run from cache information (IVY-169)
|
||||
- FIX: resolve fails without appropriate message when cache is empty and a module in the repository has no revision (IVY-165)
|
||||
- FIX: resolve problem with configuration inheritance (IVY-164)
|
||||
- FIX: some files in cache detected by not used by Ivy for subsequent retrieves (IVY-159)
|
||||
- FIX: HTML report shouldn't display the dependencies of evicted modules (IVY-158) (thanks to Maarten Coene)
|
||||
- FIX: bug when an organisation or module or revision contains a space (IVY-157)
|
||||
- FIX: cos-nonambig warnings (IVY-156)
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.3-RC2-bin.zip">ivy-1.3-RC2-bin.zip</a> (1.53 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.3-RC2-src.zip">ivy-1.3-RC2-src.zip</a> (1.22 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/ivy-1.3-RC2-src-withdep.zip">ivy-1.3-RC2-src-withdep.zip</a> (1.60 MB)
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,49 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2006-03-06)</h1>
|
||||
- IMPROVE: Retrieve task now also optionally do ivy file downloads (IVY-167) (with the contribution of Costin Leau)
|
||||
|
||||
- FIX: ivy variable substitution in ivy files (IVY-186)
|
||||
- FIX: force attribute is not treated as it should in some cases (IVY-182)
|
||||
- FIX: problem reading 'invalid' POMs (IVY-153)
|
||||
- FIX: cryptic NPE due to spelling error in ivy.xml (IVY-177)
|
||||
- FIX: conflicts with dynamic revisions not resolved properly (IVY-181)
|
||||
- FIX: incorrect configuration definition gives misleading NullPointerException (IVY-175)
|
||||
- FIX: throw an error when using a non-existing conflict manager as default (IVY-179) (thanks to Maarten Coene)
|
||||
- FIX: eviction problem with different conflicts in multiple confs (IVY-173)
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3-RC3/ivy-1.3-RC3-bin.zip">ivy-1.3-RC3-bin.zip</a> (1.56 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3-RC3/ivy-1.3-RC3-src.zip">ivy-1.3-RC3-src.zip</a> (1.26 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3-RC3/ivy-1.3-RC3-src-withdep.zip">ivy-1.3-RC3-src-withdep.zip</a> (1.64 MB)
|
||||
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,52 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log (2006-03-30)</h1>
|
||||
This version is bugfix release, upgrade from 1.3 is strongly recommended.
|
||||
- FIX: retrieval of multiple artifacts in different configurations does not work as expected (IVY-188)
|
||||
- FIX: configuration http url include doesn't work with commons http client (IVY-203)
|
||||
- FIX: problem with conflict resolution in transitive dependencies (IVY-199)
|
||||
- FIX: pb with force when it comes after a conflict which has already been solved (IVY-193)
|
||||
- FIX: POM files that reference to the parent artifact download fails (IVY-195) (thanks to Tat Leung)
|
||||
- FIX: M2 compatibility does not take into account the . replacement for publishing artifacts (IVY-191) (thanks to Peter Hayes)
|
||||
- FIX: artifactproperty does not set the [conf] token in the pattern to the correct value. It is always set to 'default'. (IVY-123) (thanks to Peter Oxenham)
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3.1/ivy-1.3.1-bin.zip">ivy-1.3.1-bin.zip</a> (1.57 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3.1/ivy-1.3.1-src.zip">ivy-1.3.1-src.zip</a> (1.27 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3.1/ivy-1.3.1-src-withdep.zip">ivy-1.3.1-src-withdep.zip</a> (1.65 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3.1/ivy-doc-1.3.1.zip">ivy-doc-1.3.1.zip</a> (1.6MB) (New! Easily browsable offline)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3.1/ivy-1.3.1.jar">ivy-1.3.1.jar</a>
|
||||
|
||||
<em>Note: the zips distributed here before 2006-04-14 didn't include ivy.xml for ivy itself. This is now fixed, for those who want to get it you can find it here:
|
||||
<a href="./downloads/ivy/1.3.1/ivy-1.3.1.xml">ivy-1.3.1.xml</a>
|
||||
</em>
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,44 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log</h1>
|
||||
Ivy 1.3-RC3 has been promoted to 1.3 on 2006-03-17.
|
||||
|
||||
For known bugs and limitations please see http://jira.jayasoft.org/
|
||||
|
||||
For detailed list of changes since 1.2a, please see changes of the three release candidates below.
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3/ivy-1.3-bin.zip">ivy-1.3-bin.zip</a> (1.52 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3/ivy-1.3-src.zip">ivy-1.3-src.zip</a> (1.21 MB)
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.3/ivy-1.3-src-withdep.zip">ivy-1.3-src-withdep.zip</a> (1.59 MB)
|
||||
|
||||
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,168 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Here are the release notes of version 1.4-RC1.
|
||||
A new and noteworthy section is available on <a href="../../doc/releasenotes/1.4.html">version 1.4 page</a>.
|
||||
|
||||
You can download it here:
|
||||
<ul><li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC1/ivy-1.4-RC1-bin.zip">binaries</a></li>
|
||||
<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC1/ivy-1.4-RC1-src.zip">sources</a></li>
|
||||
<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC1/ivy-1.4-RC1-doc.zip">documentation</a></li>
|
||||
</ul>
|
||||
|
||||
It includes 30 new features, 33 improvements and even more bug fixes since Ivy 1.3.1.
|
||||
<code>
|
||||
version 1.4-RC1 - 2006-09-17
|
||||
=================================
|
||||
Incompatibility with previous versions:
|
||||
---------------------------------------
|
||||
* usage:
|
||||
- no known major incompatiblity
|
||||
- build list task now requires a configured ivy instance (configure will automatically be called if you don't call it explicitly)
|
||||
- publish now requires the published ivy file to have the published revision (automatic if you use deliver)
|
||||
|
||||
* API:
|
||||
- Numerous API changes especially in the BasicResolver class and subclasses due to the introduction of VersionMatcher,
|
||||
this may break some custom dependency resolvers or other tools or plugins depending directly on Ivy API
|
||||
|
||||
Changes:
|
||||
--------
|
||||
* thanks to Jayasoft:
|
||||
- NEW: ivy report generate full graph from automated build (IVY-155)
|
||||
- NEW: support for build number calculation (IVY-276)
|
||||
- NEW: find modules in repository (IVY-275)
|
||||
- NEW: explicitly specify artifact download URL (IVY-271)
|
||||
- NEW: introduce branch management (IVY-269)
|
||||
- NEW: resolve dependencies directly without using an ivy file (IVY-268)
|
||||
- NEW: ability to invoke any build scripts for dependencies (IVY-68)
|
||||
- NEW: support sftp repository (IVY-267)
|
||||
- NEW: pluggable version matcher (IVY-219)
|
||||
- NEW: support for version ranges (IVY-295)
|
||||
- NEW: dependency based on dependency status (IVY-47)
|
||||
- NEW: add possibility to define extra attributes in ivy files (IVY-217)
|
||||
- NEW: option to omit specific confs and allow the rest (IVY-66)
|
||||
- NEW: use custom classloader for plugins (IVY-220)
|
||||
- NEW: adding to SPECIAL_MEANINGS in LatestRevisionStrategy (IVY-121)
|
||||
- NEW: Allow use of system properties in ivyconf.xml (IVY-228)
|
||||
|
||||
- IMPROVE: allow to use file-system repository directly without cache (IVY-211)
|
||||
- IMPROVE: deliver task use a default value for revision (IVY-252)
|
||||
- IMPROVE: better documentation distribution (IVY-274) - in progress
|
||||
- IMPROVE: define conflict manager per organisation/module in ivyconf (IVY-270)
|
||||
- IMPROVE: transitive parameter in resolve (IVY-21)
|
||||
- IMPROVE: add syncing feature in retrieve (IVY-33)
|
||||
- IMPROVE: use of md5 and/or sha1 files to check downloads (IVY-27)
|
||||
- IMPROVE: possible to use m2compatible without automatically using POMs as well (IVY-263)
|
||||
- IMPROVE: support for circular dependencies (IVY-202)
|
||||
- IMPROVE: make status list configurable (IVY-242)
|
||||
- IMPROVE: use only ivy patterns for listing revisions when module desciptor is required (allownomd = false) (IVY-166)
|
||||
- IMPROVE: implement strict haltonfailure if ivy.xml is not found (IVY-110)
|
||||
- IMPROVE: artifact's "name" attribute could be omitted (IVY-231)
|
||||
- IMPROVE: ivy standalone now return error status (IVY-152)
|
||||
- IMPROVE: log messages do not display most specfic resolver name (IVY-170)
|
||||
- IMPROVE: prints URL before downloading in verbose mode (IVY-257)
|
||||
- IMPROVE: incorrect value in status attribute causes silent failure (IVY-259)
|
||||
- IMPROVE: suport empty dependencies tag in an ivy file (IVY-281)
|
||||
- IMPROVE: isolate dependency resolution from artifact downloading (IVY-254)
|
||||
- IMPROVE: Pass artifact to repository when calling "put" (IVY-192)
|
||||
- IMPROVE: Do not publish ivy file with bad revision, and allow to force the deliver when calling publish task (IVY-245)
|
||||
|
||||
- FIX: Problem with multiple artifact includes in transitive dependencies (IVY-283)
|
||||
- FIX: Endless recursion in report (IVY-284)
|
||||
- FIX: http url lister doesn't work when link text has spaces (IVY-282)
|
||||
- FIX: Incorrect ant log level (IVY-279)
|
||||
- FIX: Wrong resolution of dependencies if artifacts specified explicitly (IVY-261)
|
||||
- FIX: Multiple versions of dependencies appearing in retrieve (IVY-264)
|
||||
- FIX: Too many false CircularDependencyException errors thrown (IVY-230)
|
||||
- FIX: CircularDependencyException not always thrown (IVY-184)
|
||||
- FIX: NullPointer in BasicResolver (IVY-258)
|
||||
- FIX: Bad diagnostics message when no space left (IVY-250)
|
||||
- FIX: Maven2 POM support can find groupId from "parent" element (IVY-262)
|
||||
- FIX: Parent version is expected to be equal to the module version in POM (IVY-241)
|
||||
- FIX: problem with cache and returnFirst (IVY-207)
|
||||
- FIX: modules splitted across a chain are not handled correctly (IVY-206)
|
||||
- FIX: problem with conf extension and latest revisions (IVY-240)
|
||||
- FIX: The clean-cache target in /src/example/hello-ivy/build.xml file refers to ${user.home}/.ivy-cache instead of ${user.home}/.ivy/cache/ (IVY-265)
|
||||
|
||||
* thanks to Ivy Community:
|
||||
- NEW: SSH Resolver added and aligned with SFTP resolver (IVY-273) (thanks to Andreas Sahlbach)
|
||||
- NEW: ability to turn off transitivity at configuration level (IVY-103) (thanks to Karl Baum and Maarten Coene)
|
||||
- NEW: a conflict manager that is able to allow implementation changes but not api changes (1.2.x - OK), (1.x.x - Not OK) (IVY-223) (thanks to Anders Janmyr)
|
||||
- NEW: enhance standalone mode to execute java program by creating classloader of dependant jars from cache (IVY-210) (thanks to Peter Hayes)
|
||||
- NEW: addition of Vfs Resolver which uses Commons-Vfs to resolve files (IVY-128) (thanks to Glen Marchesani, Matt Inger and Stephen Nesbitt)
|
||||
|
||||
- IMPROVE: use global properties in the recursive delivery (IVY-222) (with the contribution of Roshan Punnoose)
|
||||
- IMPROVE: better handling of authentication (thanks to Christian Riege)
|
||||
|
||||
- FIX: Ant log messsages not embedded in task log (IVY-280) (thanks to Gilles Scokart)
|
||||
- FIX: Ivy fails when downloading from a server that supports NTLM authentication (IVY-213) (thanks to Damon Rand)
|
||||
- FIX: Delivered Ivy files with incomplete last line. (IVY-125) (thanks to Matthias Kilian)
|
||||
- FIX: the vfs resolver should not log passwords (IVY-292) (thanks to Antoine Levy-Lambert)
|
||||
|
||||
* thanks to Maarten Coene:
|
||||
- NEW: add failureproperty parameter to the resolve task (IVY-285)
|
||||
- NEW: Add type filtering to retrieve task (IVY-260)
|
||||
- NEW: Add selectors to the configuration mapping (IVY-253)
|
||||
- NEW: Add Ant task to retrieve information from an Ivy file without doing a resolve (IVY-255)
|
||||
- NEW: add option to cachepath task to create a path with local artifact paths (IVY-221)
|
||||
- NEW: allow extending configurations to override the mapping of their super configurations (IVY-218)
|
||||
|
||||
- IMPROVE: Retain artifact filenames along the publish/resolve/retrieve process (IVY-54)
|
||||
- IMPROVE: report Ant-task doesn't process the reports in batch (IVY-247)
|
||||
- IMPROVE: make ReportOutputter pluggable and customizable (IVY-205)
|
||||
- IMPROVE: add wildcard support for extending configurations (IVY-235)
|
||||
- IMPROVE: add support for xslt parameters in the report task (IVY-227)
|
||||
- IMPROVE: comments now aren't lost when delivering ivy files (IVY-226)
|
||||
- IMPROVE: add sort of 'fallback'-mapping to the defaultconfmapping attribute (IVY-215)
|
||||
- IMPROVE: artifact origin is not included in the default report (IVY-251)
|
||||
|
||||
- FIX: VFS Resolve fails when trying to resolve a + version (IVY-237)
|
||||
- FIX: report Ant-task doesn't use outputpattern for generating graphml reports (IVY-246)
|
||||
- FIX: report Ant-task doesn't call init() on the internal XSLTProcess (IVY-248)
|
||||
- FIX: value of confmappingoverride from imported configurations is lost when writing Ivy file (IVY-239)
|
||||
- FIX: including configurations doesn't import the confmappingoverride setting (IVY-238)
|
||||
- FIX: NullPointerException when the creation of Ivy file in cache fails (IVY-234)
|
||||
- FIX: Ivy file containing 2 different versions of the same module is not deliverd correctly (IVY-229)
|
||||
- FIX: ModuleRevisionId encode/decode doesn't work if revision is empty (IVY-233)
|
||||
- FIX: cachepath task should preserve the order of the dependencies (IVY-225)
|
||||
- FIX: specifying a defaultconfmapping adds dependencies of each unlisted configuration (IVY-214)
|
||||
|
||||
* thanks to Johan Stuyts:
|
||||
- NEW: always update artifacts when revision matches a regex pattern (IVY-189)
|
||||
- NEW: provide Ant task for generating report about artifacts depended upon (IVY-194)
|
||||
|
||||
- IMPROVE: change default cache artifact pattern to handle missing extension (IVY-196)
|
||||
|
||||
* thanks to Karl Baum:
|
||||
- NEW: "this" symbol for configuration mappings (IVY-183)
|
||||
|
||||
- IMPROVE: performances improved (IVY-187)
|
||||
</code>
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,50 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Here are the release notes of version 1.4-RC2.
|
||||
A new and noteworthy section is available on <a href="../../doc/releasenotes/1.4.html">version 1.4 page</a>.
|
||||
|
||||
You can download it here:
|
||||
<ul><li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-bin.zip">binaries</a></li>
|
||||
<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-src.zip">sources</a></li>
|
||||
<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-doc.zip">documentation</a></li>
|
||||
</ul>
|
||||
|
||||
It includes only bug fixes since 1.4-RC1.
|
||||
<code>
|
||||
version 1.4-RC2 - 2006-09-27
|
||||
=====================================
|
||||
- FIX: m2compatible flag is ignored for display of failed artifact searches (IVY-303)
|
||||
- FIX: AntCallTriggerTest and AntBuildTriggerTest fail when run from ivy build.xml (IVY-310)
|
||||
- FIX: Classloader problem with ant (IVY-311)
|
||||
- FIX: Make resolve overview more compact (IVY-299)
|
||||
- FIX: Could not write to "tmp:///webdav_tmp.c1" because it is read-only (IVY-312)
|
||||
</code>
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,57 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Ivy 1.4.1 is mainly a bug fix version, upgrade from 1.4 is strongly recommended.
|
||||
|
||||
It has been released on 2006-11-09.
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-bin.zip">ivy-1.4.1-bin.zip</a>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-src.zip">ivy-1.4.1-src.zip</a>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-doc.zip">ivy-1.4.1-doc.zip</a>
|
||||
|
||||
<h1>Changes log</h1>
|
||||
<pre>
|
||||
- IMPROVE: ability to rebuild all dependent projects from a leaf (IVY-101)
|
||||
- IMPROVE: Artifact pattern list attribute for the ivy:publish (IVY-113)
|
||||
- IMPROVE: Measure code coverage (IVY-323)
|
||||
- IMPROVE: add release target to build file (IVY-339)
|
||||
- IMPROVE: Add a 'conf' parameter to the ivy 'publish' ant task (IVY-322) (thanks to Emmanuel Pellereau)
|
||||
|
||||
- FIX: retrieve fails when resolve is done with useOrigin set to true (IVY-304)
|
||||
- FIX: IVY complains about non-existent reports in the cache directory (IVY-315)
|
||||
- FIX: Typo in failureproperty attribute of Ant resolve task (IVY-327) (thanks to Jean-Baptiste Quenot)
|
||||
- FIX: ivy:resolve useOrigin fails to behave correctly (IVY-332)
|
||||
- FIX: ChainVersionMatcher doesn't handle IvyAware children version matchers (IVY-331)
|
||||
- FIX: latest.<status> does not work properly when no matching revision exist (IVY-318)
|
||||
- FIX: attribute name in macrodef is not handled as expected (IVY-319)
|
||||
- FIX: confmappingoverride doesn't work for configurations extending from "*(public)" (IVY-326)
|
||||
</pre>
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,339 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Changes log</h1>
|
||||
Ivy 1.4-RC2 has been promoted to 1.4 on 2006-10-09
|
||||
|
||||
Known bugs and limitations:
|
||||
- references in resolvers are not resolved 'in-time' with macrodef (IVY-319)
|
||||
- latest.<status> does not work properly when no matching revision exist (IVY-318)
|
||||
- IVY complains about non-existent reports in the cache directory (IVY-315)
|
||||
- retrieve fails when resolve is done with useOrigin set to true (IVY-304)
|
||||
|
||||
For detailed list of changes since 1.3.1, please see changes of the two release candidates detailed in child pages.
|
||||
For an overview of what's new and noteworthy in this release since 1.3 see the new and noteworthy section below.
|
||||
|
||||
<h1>Downloads</h1>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-bin.zip">ivy-1.4-bin.zip</a>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-src.zip">ivy-1.4-src.zip</a>
|
||||
<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-doc.zip">ivy-1.4-doc.zip</a>
|
||||
|
||||
<div class="newandnoteworthy">
|
||||
<h1><center><big>New and noteworthy</big></center></h1>
|
||||
<h1>Documentation</h1>
|
||||
<h2>A new introduction tutorial as simple as 1-2-3</h2>
|
||||
It has never been so easy to try Ivy! You don't even need to install it yourself! Follow this simple steps and you're done:
|
||||
<ol>
|
||||
<li>make sure you have <a href="http://ant.apache.org/">ant</a> 1.6.2 or greater and a <a href="http://java.sun.com">jdk</a> properly installed</li>
|
||||
<li>copy [[svn:src/example/go-ivy/build.xml this build file]] in an empty directory on your local filesystem (and make sure you name it build.xml)</li>
|
||||
<li>open a console in this directory and run "ant". That's it!</li>
|
||||
</ol>
|
||||
If you have any trouble, check the <a href="../../faq.html">FAQ</a>, it may be related to your internet connection (proxy anyone?).
|
||||
Want to try more tutorials? Check the <a href="../../doc/tutorial.html">tutorials</a> page in the documentation.
|
||||
<h2>Offline documentation greatly improved</h2>
|
||||
The offline documentation has been greatly improved, and is now a real copy of the online documentation, with all the navigation between pages as on the online version. Continue to use the online version when you can to have the latest updated version with user comments.
|
||||
<h2>Documentation update</h2>
|
||||
As usual, the documentation has been extensively updated with to reflect the new features. Some are still missing, but we will finish the update before the 1.4 release.
|
||||
|
||||
Moreover, more examples have been added, more links between the pages, and some very useful pages have been added like the <a href="../../doc/bestpractices.html">best practices</a> one.
|
||||
<h1>Core features</h1>
|
||||
<h2><a href="../../doc/concept.html#extra">Extra attributes</a></h2>
|
||||
Several tags in ivy xml files are now extensible with extra attributes.
|
||||
|
||||
The idea is very simple: if you need some more information to define your modules, you can add the attribute you want and you will then be able to access it as any other attribute in your patterns for example.
|
||||
|
||||
Example:
|
||||
Here is an ivy file with the attribute 'color' set to blue:
|
||||
<code type="xml">
|
||||
<ivy-module version="1.4">
|
||||
<info organisation="jayasoft"
|
||||
module="foo"
|
||||
color="blue"
|
||||
status="integration"
|
||||
revision="1.59"
|
||||
/>
|
||||
</ivy-module>
|
||||
</code>
|
||||
Then you can use the extra attribute when you declare a dependency on foo:
|
||||
<code>
|
||||
<dependency org="jayasoft" name="foo" color="blue" rev="1.5+" />
|
||||
</code>
|
||||
And you can define your repository pattern as:
|
||||
<code>
|
||||
${repository.dir}/[organisation]/[module]/[color]/[revision]/[artifact].[ext]
|
||||
</code>
|
||||
|
||||
Note that in order to use extra attributes, you will need to disable ivy file validation, since your files won't fulffill anymore the official ivy xsd. See the <a href="../../doc/configuration/conf.html">configuration doc page</a> to see how to disable validation.
|
||||
|
||||
<h2><a href="../../doc/ivyfile/dependency.html">Version matchers</a></h2>
|
||||
Ivy now rely on a new concept to specify which version of a dependency should be used: pluggable version matchers.
|
||||
This means that you can define your own way to match a dependency version.
|
||||
|
||||
Both latest.integration and latest sub version (1.3+ for instance) have been ported to this mechanism.
|
||||
|
||||
With this new feature Ivy also comes with two new built-in version matchers:
|
||||
<ul>
|
||||
<li>latest.[any status]</li>selects the latest revision of the dependency module with at least the specified status.
|
||||
<li>version ranges</li>You can now express your version contraint as a mathematical range.
|
||||
</ul>
|
||||
|
||||
Examples:
|
||||
<code type="xml">
|
||||
<dependency org="foo" name="bar" rev="latest.milestone" />
|
||||
</code>
|
||||
Will find the latest version of bar which is in milestone or release status.
|
||||
<code type="xml">
|
||||
<dependency org="foo" name="bar" rev="[1.0,2.0]" />
|
||||
</code>
|
||||
Matches any revision greater than 1.0 and lower than 2.0, inclusive.
|
||||
|
||||
<h2><a href="../../doc/ivyfile/dependency-artifact.html">URL attribute on artifact to improve ease of use</a></h2>
|
||||
The artifact tag used when declaring a dependency now supports an url attribute. Even if this should be used only in very special cases (because it derrogates to the standard repository management), it can be useful, well, in very special cases :-)
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<dependency org="foo" name="bar" rev="1.0">
|
||||
<artifact name="baz" type="jar" url="http://www.acme.com/repository/bar/baz-1.0-acme.jar"/>
|
||||
</dependency>
|
||||
</code>
|
||||
|
||||
<h2><a href="../../doc/ivyfile/conf.html">Module configurations enhancements</a></h2>
|
||||
Several improvements have been made on the module configurations:
|
||||
<ul><li>It is now possible to disable transitivity for a whole configuration.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<conf name="compile" extends="core" transitive="false" visibility="private" />
|
||||
</code></li>
|
||||
<li>You can use <code>*</code>, <code>*(public)</code> or <code>*(private)</code> as wildcards to extend a set of configurations.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<conf name="all" extends="*" />
|
||||
</code></li>
|
||||
<li>You can use <code>*, !A, !B</code> in configurations mapping to mean all configurations but A and B.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<dependency name="commons-lang" rev="1.0" conf="*, !deploy->default" />
|
||||
</code></li>
|
||||
</ul>
|
||||
|
||||
<h2><a href="../../doc/concept.html#event">Events and triggers</a></h2>
|
||||
Ivy now fires events all along the dependency resolution process, which can be listened and which can trigger events.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<triggers>
|
||||
<ant-build antfile="${ivy.settings.dir}/[module]/build.xml" target="publish"
|
||||
event="pre-resolve-dependency" filter="revision=latest.integration"/>
|
||||
</triggers>
|
||||
</code>
|
||||
Triggers an ant build just before resolving a dependency with a latest.integration revision.
|
||||
|
||||
<h1>New Resolvers</h1>
|
||||
<h2><a href="../../doc/resolver/vfs.html">vfs</a></h2>
|
||||
The new vfs resolver leverages the work from <a href="http://jakarta.apache.org/commons/vfs/">apache commons vfs</a> to give a uniform access to a set of different file systems including ftp, sftp, webdav, zip, ...
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<vfs name="remote">
|
||||
<ivy pattern="webdav://username:password@host:8080/[organisation]/[module]/[revision]/ivy.xml" />
|
||||
<artifact pattern="webdav://username:password@host:8080/[organisation]/[module]/[revision]/[artifact].[ext]" />
|
||||
</vfs>
|
||||
</code>
|
||||
|
||||
<h2><a href="../../doc/resolver/ssh.html">ssh</a> and <a href="../../doc/resolver/sftp.html">sftp</a></h2>
|
||||
The new ssh and sftp resolvers allow, as their name suggest, to access a repository using ssh or sftp. The secured nature of ssh and its wide spread implementation on most *nix servers makes these resolvers very good candidate in an enterprise environment.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<sftp name="secured" keyFile="path/to/key/file" keyFilePassword="${password}">
|
||||
<ivy pattern="sftp://user:xavier@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
|
||||
<artifact pattern="sftp://user:xavier@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
|
||||
</sftp>
|
||||
</code>
|
||||
|
||||
<h1>Configuration files</h1>
|
||||
<h2><a href="../../doc/configuration/statuses.html">Configurable statuses</a></h2>
|
||||
The list of statuses available in module files is now configurable.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<statuses default="bronze">
|
||||
<status name="gold" integration="false"/>
|
||||
<status name="silver" integration="false"/>
|
||||
<status name="bronze" integration="true"/>
|
||||
</statuses>
|
||||
</code>
|
||||
<h2><a href="../../doc/configuration/module.html">Per module settings</a></h2>
|
||||
It is now possible possible to configure conflict-manager per module set.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<modules>
|
||||
<module organisation="jayasoft" name="ivy*" matcher="glob" conflict-manager="latest-time"/>
|
||||
</modules>
|
||||
</code>
|
||||
<h2><a href="../../doc/concept#checksum.html">Checksums</a></h2>
|
||||
Ivy now allow to use checksums to verify the correctness of a downloaded file.
|
||||
|
||||
For the moment Ivy supports md5 and sha1 algorithm.
|
||||
|
||||
The configuration of using md5 and/or sha1 can be done globally or by dependency resolver.
|
||||
Globally, use the ivy.checksums variable to list the check to be done (only md5 and sha1 are supported).
|
||||
On each resolver you can use the checksums attribute to override the global setting.
|
||||
|
||||
The setting is a comma separated list of checksum algorithm to use.
|
||||
During checking (at download time), the first checksum found is checked, and that's all. This means that if you have a "sha1, md5" setting, then if ivy finds a sha1 file, it will compare the downloaded file sha1 against this sha1, and if the comparison is ok, it will assume the file is ok. If no sha1 file is found, it will look for a md5 file. If none is found no checking is done.
|
||||
During publish, all listed checksum algorithms are computed and uploaded.
|
||||
|
||||
By default checksum algorithms are "sha1, md5".
|
||||
<h2><a href="../../doc/configuration/resolvers#common.html">Fail when no module descriptor is found</a></h2>
|
||||
By default when ivy doesn't find a module descriptor for a module, it lloks for an artifact, and if it finds one it assumes a default module descriptor.
|
||||
It is now possible to configure this behaviour per resolver, by setting the allownomd attribute to false you can force the use of a module descriptor, and fail if none is found. This is also useful to improve performances on a resolver for which you know you will always have module descriptors.
|
||||
<h2>System properties</h2>
|
||||
All java system properties are now available as ivy variables in your configuration files.
|
||||
Thus you can now easily define the default cache relative to user home (using ${user.home}), or access any specific property set via the standard java system property mechanism.
|
||||
|
||||
<h2><a href="../../doc/configuration/resolvers#common.html">Changing pattern</a></h2>
|
||||
You can now define a changingPattern and a changingMatcher to configure a set of revisions which should always be considered as changing one (artifacts are checked to see if they are up to date).
|
||||
|
||||
The pattern and the matcher name are attributes available on all built-in resolvers.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<filesystem name="local" changingPattern="*-SNAPSHOT" changingMatcher="glob">
|
||||
</code>
|
||||
will consider all modules with a revision ending by SNAPSHOT to be changing revisions.
|
||||
|
||||
<h2><a href="../../doc/configuration/classpath.html">Customisable classpath</a></h2>
|
||||
You can now add jars to use to load plugins directly in ivy configuration, so that you can easily use your plugins in several execution environment (ant, standalone, IDE plugin, ...).
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<ivyconf>
|
||||
<classpath file="${ivy.settings.dir}/custom-resolver.jar"/>
|
||||
<typedef name="custom" classname="fr.jayasoft.ivy.resolver.CustomResolver"/>
|
||||
<resolvers>
|
||||
<custom name="custom"/>
|
||||
</resolvers>
|
||||
</ivyconf>
|
||||
</code>
|
||||
|
||||
<h1>Ant tasks</h1>
|
||||
<h2><a href="../../doc/use/repreport.html">repreport</a></h2>
|
||||
A new repreport task allows to generate reports directly from your repository. The graph generation is the most interesting one, it can gives you a good overview of the dependencies between of all your modules available in your repository, or restrict this graph to just the modules from this organisation, and so on.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<ivy:repreport organisation="myorg" xml="false" graph="true" />
|
||||
will generate a graphml of dependencies with all modules in the organisation "myorg"
|
||||
</code>
|
||||
|
||||
<h2><a href="../../doc/use/artifactreport.html">artifactreport</a></h2>
|
||||
A new artifactreport task has been introduced to easily generate an xml report with artifacts resolved, with useful information such as their original location. This report is particularly well suited for generating IDE classpaths (see also the <a href="../../links.html">links</a> page for higher IDE integration via plugins).
|
||||
|
||||
The generated report looks like this:
|
||||
<code type="xml">
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<modules>
|
||||
<module organisation="hippo" name="sant-classes" rev="1.01.00b04-dev" status="integration">
|
||||
<artifact name="sant-classes-src" ext="zip" type="zip">
|
||||
<origin-location is-local="true">
|
||||
C:/home/jstuyts/data/ivy/local/hippo/sant-classes/1.01.00b04-dev/sant-classes-src-1.01.00b04-dev.zip</origin-location>
|
||||
<cache-location>
|
||||
C:/home/jstuyts/data/ivy/cache/hippo/sant-classes/zips/sant-classes-src-1.01.00b04-dev.zip</cache-location>
|
||||
<retrieve-location>lib/test/sant-classes-src-1.01.00b04-dev.zip</retrieve-location>
|
||||
</artifact>
|
||||
</module>
|
||||
<module organisation="testng" name="testng" rev="4.6.1-jdk15" status="release">
|
||||
<artifact name="testng" ext="jar" type="jar">
|
||||
<origin-location is-local="false">
|
||||
http://repository.hippocms.org/maven/testng/jars/testng-4.6.1-jdk15.jar</origin-location>
|
||||
<cache-location>C:/home/jstuyts/data/ivy/cache/testng/testng/jars/testng-4.6.1-jdk15.jar</cache-location>
|
||||
<retrieve-location>lib/test/testng-4.6.1-jdk15.jar</retrieve-location>
|
||||
</artifact>
|
||||
</module>
|
||||
</code>
|
||||
|
||||
<h2><a href="../../doc/use/info.html">info</a></h2>
|
||||
The new info task eases the access to some essential data contained in an ivy file without performing a dependency resolution.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<ivy:info file="${basedir}/path/to/ivy.xml" />
|
||||
</code>
|
||||
|
||||
<h2><a href="../../doc/use/listmodules.html">listmodules</a></h2>
|
||||
The new listmodules task let you list modules available in the repository and set ant properties accordingly.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<ivy:listmodules organisation="jayasoft" module="ivy" revision="*" property="ivy.[revision]" value=="found"/>
|
||||
</code>
|
||||
|
||||
<h2><a href="../../doc/use/findrevision.html">findrevision</a></h2>
|
||||
This new task sets an ant property with the latest revision found for a given module matching a given revision constraint.
|
||||
|
||||
<code type="xml">
|
||||
<ivy:findrevision organisation="jayasoft" module="ivy" revision="1.0+"/>
|
||||
</code>
|
||||
|
||||
<h2><a href="../../doc/use/resolve.html">useOrigin</a></h2>
|
||||
The resolve, cachepath, and retrieve tasks now supports a new useOrigin attribute, which allow to use the original location of local artifacts instead of their location in ivy cache. Used directly on a resolve or when no resolve has been done, it will avoid the copy of the artifact to the cache, and use directly the artifact from its original location.
|
||||
|
||||
<code type="xml">
|
||||
<cachepath pathid="default.classpath" conf="default" useOrigin="true" />
|
||||
</code>
|
||||
<h2><a href="../../doc/use/resolve.html">Disable transitive dependencies on resolve</a></h2>
|
||||
You can now disable transitive dependencies on resolve.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<ivy:resolve file="path/to/ivy.xml" transitive="false" />
|
||||
</code>
|
||||
<h2><a href="../../doc/use/retrieve.html">Synchronization feature in retrieve</a></h2>
|
||||
The retrieve task can now performs a real synchronization of the destination directory, instead of a simple copy.
|
||||
|
||||
Example:
|
||||
<code type="xml">
|
||||
<ivy:retrieve pattern="${lib.dir}/[conf]/[artifact].[ext]" sync="true" />
|
||||
</code>
|
||||
|
||||
<h1>Standalone mode</h1>
|
||||
<h2>Application launcher</h2>
|
||||
Ivy can now be used as an application launcher:
|
||||
<code>
|
||||
java fr.jayasoft.ivy.Main -conf path/to/myivyconf.xml -dependency bar foo 2.0 -main org.bar.foo.FooMain
|
||||
</code>
|
||||
calls ivy with given ivyconf file and resolve bar foo 2.0, and then run org.foo.FooMain class with the resolved artifacts (foo 2.0 and its dependencies) as classpath
|
||||
</div>
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,230 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h2>Disclaimer</h2>
|
||||
<code>
|
||||
Apache Ivy is an effort undergoing incubation at The Apache Software
|
||||
Foundation (ASF). Incubation is required of all newly accepted projects
|
||||
until a further review indicates that the infrastructure, communications,
|
||||
and decision making process have stabilized in a manner consistent with
|
||||
other successful ASF projects. While incubation status is not necessarily
|
||||
a reflection of the completeness or stability of the code, it does
|
||||
indicate that the project has yet to be fully endorsed by the ASF.
|
||||
</code>
|
||||
<h2>Announcement</h2>
|
||||
<code>
|
||||
April 26 2007 - The Ivy incubator project is please to announce its
|
||||
2.0.0 alpha 1 release, exactly two years after Ivy 1.0!
|
||||
|
||||
Ivy is a tool for managing (recording, tracking, resolving and
|
||||
reporting) project dependencies, characterized by flexibility,
|
||||
configurability, and tight integration with Apache Ant.
|
||||
|
||||
This is the first release of Ivy in the Apache incubator, and as an
|
||||
alpha version we do not guarantee any stability, that API and features
|
||||
are still likely to change until final 2.0.0 version. Still we encourage
|
||||
the use of this version for early testing.
|
||||
|
||||
This version focus was to refactor the code to get better readability,
|
||||
rename packages to org.apache.ivy, improve maven 2 compatibility along
|
||||
with some other bug fixes and improvement.
|
||||
|
||||
Download the 2.0.0 alpha 1 release files at:
|
||||
http://incubator.apache.org/ivy/download.html
|
||||
|
||||
More information can be found on the Ivy website -
|
||||
http://incubator.apache.org/ivy/
|
||||
|
||||
regards,
|
||||
Xavier Hanin (2.0.0-alpha-1 release mgr)
|
||||
</code>
|
||||
<h2>Release Notes</h2>
|
||||
CONTENTS
|
||||
1. What is Apache Ivy?
|
||||
2. Status of this release
|
||||
3. Major Changes in this Release
|
||||
4. Migrating from Jayasoft Ivy to Apache Ivy
|
||||
5. How to Get Involved
|
||||
6. How to Report Issues
|
||||
7. Committers and Contributors for this release
|
||||
8. List of Changes in this Release
|
||||
|
||||
|
||||
<h3>1. What is Apache Ivy?</h3>
|
||||
|
||||
Apache Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies.
|
||||
It is characterized by the following:
|
||||
|
||||
1. flexibility and configurability
|
||||
Apache Ivy is essentially process agnostic and is not tied to any methodology or structure.
|
||||
Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes.
|
||||
|
||||
2. tight integration with Apache Ant
|
||||
while available as a standalone tool, Apache Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication.
|
||||
|
||||
<h3>2. Status of this release </h3>
|
||||
|
||||
This release of Apache Ivy is the first release within the Apache Incubator, and is labelled and should be considered as an alpha version.
|
||||
|
||||
This means that we do not guarantee any stability, that API and features are still likely to change until final 2.0.0 version. Still we encourage
|
||||
the use of this version for early testing.
|
||||
|
||||
The current production quality version is still 1.4.1, which has not been produced within the Apache Software Foundation.
|
||||
|
||||
<h3>3. Major Changes in this Release</h3>
|
||||
|
||||
This section describes what has changed between version 1.4.1 and this version of Apache Ivy.
|
||||
|
||||
This new version of Apache Ivy is fully compatible with previous versions as long as you do not use custom plugins: Ivy API has changed, but not its behavior:
|
||||
|
||||
Some tasks and configuration elements have been renamed, but the old versions
|
||||
are still available, they are only deprecated (you will see deprecated warnings).
|
||||
|
||||
<h4>3.1. Java Package Name Changes</h4>
|
||||
|
||||
All of the Ivy Java package names have changed in Apache Ivy. They now start
|
||||
with org.apache rather than fr.jayasoft. There have been other changes as well.
|
||||
Important refactorings have done on the source code to ease the understanding
|
||||
of Ivy internal architecture by new developers.
|
||||
|
||||
A class named org.apache.ivy.Ivy14 is provided with an API compatible with the
|
||||
fr.jayasoft.Ivy class of Ivy 1.4.1, to ease migration to this new version.
|
||||
|
||||
<h4>3.2. Configuration replaced by Settings</h4>
|
||||
|
||||
Configuration used to have two meanings in prior Ivy versions, causing some confusion with new users.
|
||||
To avoid this confusion, Apache Ivy calls settings instead of configuration the files used to customize Ivy. Configuration is still used for module configurations.
|
||||
|
||||
Besides the changes in the documentation, this renaming also imply a modification in settings files, which now use ivysettings as root element instead of ivyconf, and settings instead of conf element to define top level defaults (such as defaultCache, ...).
|
||||
Previous names have been deprecated, so previous settings files can still be used, but you will see a deprecation warning.
|
||||
|
||||
<h4>3.3. public resolver in default settings is now ibiblio in m2 compatible mode</h4>
|
||||
|
||||
In previous versions Ivy used to use the ivyrep resolver as default public resolver, but ivyrep is no longer maintained, while maven 2 repository on ibiblio is growing rapidly.
|
||||
|
||||
Since Ivy is compatible with maven 2 repository, defaulting to the ibiblio maven 2 repository makes more sense.
|
||||
|
||||
If you have any issue of backward compatibility with these new settings, you can simply set the following ant property before calling configure (implicitly or explicitly):
|
||||
<code>
|
||||
ivy.14.compatible=true
|
||||
</code>
|
||||
|
||||
<h3>4. Migrating from Jayasoft Ivy to Apache Ivy</h3>
|
||||
|
||||
Apache Ivy is fully compatible with Jayasoft Ivy as long as you do not use
|
||||
custom plugins.
|
||||
This means that you can use Apache Ivy as a drop in replacement of Jayasoft Ivy.
|
||||
|
||||
However due to the the renaming of configuration files to settings files, we
|
||||
strongly suggest to update your configuration files:
|
||||
- rename the files called ivyconf*.xml in ivysettings*.xml
|
||||
- rename 'ivyconf' element in 'ivysettings'
|
||||
- rename 'conf' element of those settings file in 'settings'
|
||||
|
||||
Migrating custom plugins can be done by using the org.apache.ivy.Ivy14 class instead of fr.jayasoft.ivy.Ivy, and reorganizing your imports to reflect the changes in the package names.
|
||||
|
||||
<h3>5. How to Get Involved</h3>
|
||||
|
||||
The Apache Ivy project really needs and appreciates any contributions, including documentation help, source code and feedback. If you are interested in contributing, please visit http://incubator.apache.org/ivy/get-involved.html.
|
||||
|
||||
<h3>6. How to Report Issues</h3>
|
||||
|
||||
The Apache Ivy project uses JIRA for issue tracking. Please report any issues you find at http://issues.apache.org/jira/browse/IVY
|
||||
|
||||
<h3>7. Committers and Contributors for this Release</h3>
|
||||
|
||||
Here is the list of people who have contributed source code and documentation to this release. Many thanks to all of them, and also to the whole Ivy community contributing ideas and feedback, and promoting the use of Ivy. The list would be too long, but Ivy couldn't be what it is without you!
|
||||
|
||||
<h4>Committers</h4>
|
||||
Maarten Coene
|
||||
Xavier Hanin
|
||||
|
||||
<h4>Contributors</h4>
|
||||
Stephane Baillez
|
||||
Pierre Hägnestrand
|
||||
Matt Inger
|
||||
Costin Leau
|
||||
William Lyvers
|
||||
Gilles Scokart
|
||||
John Williams
|
||||
|
||||
<h3>8. List of Changes in this Release</h3>
|
||||
|
||||
For a full release history of Ivy see the file <a href="http://svn.apache.org/repos/asf/incubator/ivy/core/branches/2.0.0-alpha-1/CHANGES.txt">CHANGES.txt</a>
|
||||
|
||||
For details about the following changes, check our JIRA install at http://issues.apache.org/jira/browse/ivy
|
||||
|
||||
- TASK: refactor Ivy source code to improve readibility (IVY-434)
|
||||
|
||||
- NEW: define artifacts not declared by the dependency module descriptor (IVY-419)
|
||||
- NEW: Module wide exclude (IVY-431)
|
||||
- NEW: The default public resolver used is now ibiblio with m2 compatible mode (IVY-463)
|
||||
|
||||
- IMPROVE: OSGIfy ivy artifacts (IVY-464) (thanks to Costin Leau)
|
||||
- IMPROVE: Let user specify Ivy file when using a post-resolve task (IVY-455)
|
||||
- IMPROVE: IvyArtifactProperty and IvyArtifactReport tasks should be a post resolve task (IVY-452)
|
||||
- IMPROVE: Rename ivy configuration in settings to remove ambiguity on configuration meaning (IVY-438)
|
||||
- IMPROVE: Please typedef CacheResolver as "cache" for us (IVY-359)
|
||||
- IMPROVE: ivy:retrieve should be able to create symlinks (IVY-353) (thanks to John Williams)
|
||||
- IMPROVE: Ability to have multiple roots in the <ivy:buildfilelist> task (IVY-340) (thanks to Matt Inger)
|
||||
- IMPROVE: Refactoring / documentation / test of matcher package (IVY-375) (thanks to Stephane Baillez)
|
||||
- IMPROVE: Add a unit test to verify that latest.integration accepts released modules (IVY-394) (thanks to Gilles Scokart)
|
||||
- IMPROVE: New "modules in use" section in console report at the end of resolve (IVY-373) (thanks to John Wiliams)
|
||||
- IMPROVE: Generated XML reports now contains more information about the resolved module (IVY-446)
|
||||
|
||||
- FIX: ivy-retrieve failure when explicit absolute 'ivy.dep.file' path specified (IVY-396)
|
||||
- FIX: IvyPostResolve Task doesn't reuse Ivy file of previous resolve (IVY-458)
|
||||
- FIX: Ivy standalone is passing null args to main method when invoking with no args (IVY-457)
|
||||
- FIX: Invalid error report with m2compatible resolver (IVY-456)
|
||||
- FIX: IvyPostResolve Task doesn't use specified cache for the resolve (IVY-453)
|
||||
- FIX: XmlModuleDescriptorWriterTest not working with Java 6 (IVY-374)
|
||||
- FIX: Conflict managers ignored, when assigned to modules in Ivy configuration (setting, ivyconf.xml) (IVY-448)
|
||||
- FIX: Ivy should fail if ';' has been used in publications/artifact/@conf of ivy.xml (IVY-441)
|
||||
- FIX: Ivy should fail where dependency uses undefined configuration (IVY-442)
|
||||
- FIX: Dynamic revision not calculated properly when using multiple directories (IVY-427)
|
||||
- FIX: LatestRevisionStrategy.sort() doesn't sort as specified (IVY-435)
|
||||
- FIX: setting m2compatible on ibiblio resolver overwrite root and pattern settings (IVY-437)
|
||||
- FIX: ivy.revision property not set correctly for second resolve (IVY-429)
|
||||
- FIX: NPE when no organisation or no name is provided in module element of ivyconf (IVY-422)
|
||||
- FIX: FileUtil#copy(File src, File dest, CopyProgressListener l, boolean overwrite) (IVY-420)
|
||||
- FIX: Invalid pom parsing when version is only declared in parent (IVY-436)
|
||||
- FIX: ${project.groupId} and ${project.version} not processed correctly in poms (IVY-425)
|
||||
- FIX: Incorrect pom parsing with profile (IVY-423)
|
||||
- FIX: Ivy doesn't recognize maven2 classifiers (IVY-418)
|
||||
- FIX: PomModuleDescriptorParser fails with nested profile dependency (IVY-392) (thanks to William Lyvers)
|
||||
- FIX: Static revision replacement is not working when delivering an artifact with a dependency having extra attributes (IVY-415)
|
||||
- FIX: Static revision replacement is not working when delivering an artifact with a dependency on a branch (IVY-404)
|
||||
- FIX: latest-time conflict manager not working properly (IVY-407)
|
||||
- FIX: LatestRevisionStrategy do not consider all dynamic revisions properly (IVY-383) (thanks to John Williams for the unit test)
|
||||
- FIX: IOException during publish causes NullPointerException (IVY-371)
|
||||
- FIX: Comments in ivy.xml duplicated (IVY-336) (thanks to Gilles Scokart)
|
||||
- FIX: Ivy failure when the ivy.xml file contains non US-ASCII characters (IVY-346) (thanks to Gilles Scokart)
|
||||
- FIX: Urlresolver is not possible to use dynamic revisions on nonstandard repository structure (IVY-350) (thanks to Pierre Hägnestrand)
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,35 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
The 2.0 version will be the first stable version released at Apache.
|
||||
|
||||
Most of the efforts of the development team is concentrated on this version, and a [[history/2.0.0-alpha-1 first alpha]] version is available for early preview.
|
||||
|
||||
Despite the version name, the 2.0 version will be mostly backward compatible with prior 1.x versions. Indeed we choose to use a major version number change to reflect the change in the Ivy API which has been deeply revisited, and our migration to the Apache Software Foundation. But from a user point of view, Ivy 2.0 will be mostly a drop in replacement of the previous 1.x versions.</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,83 +0,0 @@
|
|||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<title>${title} | Ivy</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<link rel="stylesheet" type="text/css" href="style/style.css" />
|
||||
|
||||
<script src="js/jquery.pack.js" type="text/javascript"></script>
|
||||
<script src="js/jquery.treeview.js" type="text/javascript"></script>
|
||||
<script type="text/javascript">
|
||||
$(document).ready(function(){$("#treemenu").Treeview({speed: "fast",store: true});});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="body">
|
||||
<table border="0" cellpadding="0" cellspacing="0" width="100%">
|
||||
<tr>
|
||||
<td id="sidebar-left">
|
||||
<div class="block block-book" id="block-book-0">
|
||||
<a href="http://incubator.apache.org/"
|
||||
title="Home"><img src="images/apache-incubator-logo.png" alt="Apache Incubator"
|
||||
border="0" /></a>
|
||||
<br/><br/>
|
||||
<h2>Ivy</h2>
|
||||
|
||||
<div class="content">${menu}</div>
|
||||
|
||||
</div>
|
||||
|
||||
</td>
|
||||
|
||||
<td valign="top">
|
||||
<div id="main">
|
||||
${body}
|
||||
</div><!-- main -->
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<table id="footer-menu" summary="Navigation elements." border="0"
|
||||
cellpadding="0" cellspacing="0" width="100%">
|
||||
<tr>
|
||||
<td align="center" valign="middle">
|
||||
<div class="primary-links">::
|
||||
<a href="index.html">Home</a> ::
|
||||
<a href="download.html">Download</a> ::
|
||||
<a href="doc.html">Documentation</a> ::
|
||||
<a href="doc/tutorial.html">Tutorials</a> ::
|
||||
<a href="get-involved.html">Get Involved</a> ::
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
<div id="footer-message"></div>
|
||||
|
||||
|
||||
</div><!-- body -->
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -20,26 +20,57 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0, path: {template: "homeTemplate.html"}};</script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<table border="0" class="home">
|
||||
<tr><td colspan="4"><img src="images/ivy-lierre.png"/></td></tr>
|
||||
<tr style="font-size:xx-large;"><td colspan="4"><span style="font-size:xx-large;">The agile dependency manager</span></td></tr>
|
||||
<tr><td colspan="4" style="font-size:large; padding: 1cm 0 0.7cm 0;">Ivy is a popular dependency manager focusing on flexibility and simplicity.<br/>
|
||||
Find out more about its unique <a href="features.html">enterprise features</a>, what <a href="testimonials.html">people say about it</a>,<br/>
|
||||
and <a href="doc.html">how it can improve your build system!</a></td></tr>
|
||||
<tr class="homeitems"><td><a href="download.html"><img src="images/ivy-dl-2.0.0-alpha-1.png"/></a></td><td><a href="doc.html"><img src="images/ivy-book.png"/></a></td><td><a href="demo.html"><img src="images/ivy-demo.png"/></a></td><td><a href="mailing-lists.html"><img src="images/ivy-forum.png"/></a></td></tr>
|
||||
<tr class="homeitems"><td><a href="download.html">download</a></td><td><a href="doc.html">documentation<br/>& tutorials</a></td><td><a href="demo.html">demo</a></td><td><a href="mailing-lists.html">share your experience</a></td></tr>
|
||||
</table>
|
||||
<hr/><a href="">Latest News</a><table border="0" cellpadding="5">
|
||||
<tr><td>05/03/2007</td><td><a href="presentations/apache-con-2007/">slides</a> from ApacheCon EU 2007 are available!</td></tr>
|
||||
<tr><td>04/26/2007</td><td>[[history/2.0.0-alpha-1]] version available</td></tr>
|
||||
<tr><td>03/28/2007</td><td> <a href="http://www.jetbrains.com/teamcity/features/newfeatures.html#TeamCity_Administration_Interface_Enhancements">TeamCity</a> integrates Ivy for dependent build management</td></tr>
|
||||
<tr><td>03/01/2007</td><td> New site menu and new look for the home page.<br/> [[mailing-lists Tell us]] what you think about it!</td></tr>
|
||||
</table></textarea>
|
||||
Welcome to the official Ivy documentation.
|
||||
|
||||
<h1>What is Ivy?</h1>
|
||||
Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies. It is characterized by the following:
|
||||
<ol>
|
||||
<li>flexibility and configurability - Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes.</li>
|
||||
|
||||
<li>tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication.</li>
|
||||
</ol>
|
||||
Ivy is open source and released under a very permissive <a href="license.html">license</a>.
|
||||
Ivy has a lot of powerful [[features]], the most popular and useful being its flexibily, integration with ant, and its strong transitive dependencies management engine.
|
||||
The transitive dependencies management is a feature which let you get dependencies of your dependencies, transitively. In order to address this problematic ivy needs to find metadata about your modules, usually in an <a href="doc/ivyfile.html">ivy file</a>. To find these metadata and your dependencies artifacts (usually jars), Ivy can be configured to use a lot of different <a href="doc/configuration/resolvers.html">repositories</a>.
|
||||
|
||||
<h1>About this doc</h1>
|
||||
This documentation has been migrated from the old Ivy web site hosted by Jayasoft, feel free to report any problem on the [[mailing-lists]].
|
||||
|
||||
If you browse this documentation from your installation of ivy, you can also check the <a href="http://incubator.apache.org/ivy/doc.html">online version</a> for latest updates.
|
||||
|
||||
You can also browse this documentation offline either by downloading the documentation distribution, or by checking out the doc directory from svn. This documentation uses <a href="http://xooki.sourceforge.net/">xooki</a> as documentation engine, so you can very easily [[get-involved edit it and submit patches]] when you browse it from source.
|
||||
|
||||
The online version of this documentation is updated periodically, especially when new features are added during development. So if you find something documented here not available in your version of ivy, it may be because it is available only with the latest <a href="download.html">download</a>.
|
||||
|
||||
If you want to view the whole documentation in a single printer-friendly page, please use the <a href="doc.html?action=print">printer-friendly link</a> at the bottom of any documentation page in the online documentation, and you will get a printer friendly version of the current page and all its sub pages.
|
||||
|
||||
<h1>Other places to go</h1>
|
||||
Check Ivy <a href="features.html">features</a>.
|
||||
Read our <a href="faq.html">FAQ</a>.
|
||||
Ask for help on our <a href="mailing-lists.html">mailing lists</a>.
|
||||
Report bug or feature request in our <a href="issues.html">issue tracking system</a>.
|
||||
Check <a href="links.html">external tools and resources</a>.
|
||||
|
||||
<h1>Overview</h1>
|
||||
This documentation is decomposed in 3 main parts:
|
||||
<ul>
|
||||
<li><a href="doc/tutorial.html">Tutorials</a></li>
|
||||
The tutorials is the best way to begin to play with ivy. You will easily and quickly learn the basics of Ivy.
|
||||
<li><a href="doc/reference.html">Reference</a></li>
|
||||
The reference documentation gives you all the details of Ivy.
|
||||
The introduction part is particularly useful: it defines some vocabulary, explains main concepts such as dependency resolvers and patterns, and give an overview on how ivy works internally.
|
||||
It's also in the reference doc that you will find all you always dreamed to know about ivy configuration, ivy files, and ivy use (especially with ant).
|
||||
<li><a href="doc/appendix.html">Appendix</a></li>
|
||||
The appendix section contains a bunch of Ivy related information which is not part of Ivy reference doc.
|
||||
</ul>
|
||||
|
||||
You will also find here interesting pages like [[doc/bestpractices]], the [[faq]] or the [[links]] pages.
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Issues are tracked using JIRA hosted at Apache:
|
||||
http://issues.apache.org/jira/browse/IVY
|
||||
|
||||
Feel free to browse what are the bugs already reported for each version, what are the features planned for next versions, and contribute your own feedback by submitting bug reports or feature requests, patches, comments, or simply by voting for your favorite issues.</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 2};</script>
|
||||
<script type="text/javascript" src="../../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
237
doc/license.html
237
doc/license.html
|
|
@ -1,237 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Apache Ivy is an Apache Incubator project, available under an <a href="http://www.apache.org/licenses/LICENSE-2.0.txt">Apache v2.0 license</a>.
|
||||
|
||||
<code>
|
||||
/*
|
||||
* Apache License
|
||||
* Version 2.0, January 2004
|
||||
* http://www.apache.org/licenses/
|
||||
*
|
||||
* TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
||||
*
|
||||
* 1. Definitions.
|
||||
*
|
||||
* "License" shall mean the terms and conditions for use, reproduction,
|
||||
* and distribution as defined by Sections 1 through 9 of this document.
|
||||
*
|
||||
* "Licensor" shall mean the copyright owner or entity authorized by
|
||||
* the copyright owner that is granting the License.
|
||||
*
|
||||
* "Legal Entity" shall mean the union of the acting entity and all
|
||||
* other entities that control, are controlled by, or are under common
|
||||
* control with that entity. For the purposes of this definition,
|
||||
* "control" means (i) the power, direct or indirect, to cause the
|
||||
* direction or management of such entity, whether by contract or
|
||||
* otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
||||
* outstanding shares, or (iii) beneficial ownership of such entity.
|
||||
*
|
||||
* "You" (or "Your") shall mean an individual or Legal Entity
|
||||
* exercising permissions granted by this License.
|
||||
*
|
||||
* "Source" form shall mean the preferred form for making modifications,
|
||||
* including but not limited to software source code, documentation
|
||||
* source, and configuration files.
|
||||
*
|
||||
* "Object" form shall mean any form resulting from mechanical
|
||||
* transformation or translation of a Source form, including but
|
||||
* not limited to compiled object code, generated documentation,
|
||||
* and conversions to other media types.
|
||||
*
|
||||
* "Work" shall mean the work of authorship, whether in Source or
|
||||
* Object form, made available under the License, as indicated by a
|
||||
* copyright notice that is included in or attached to the work
|
||||
* (an example is provided in the Appendix below).
|
||||
*
|
||||
* "Derivative Works" shall mean any work, whether in Source or Object
|
||||
* form, that is based on (or derived from) the Work and for which the
|
||||
* editorial revisions, annotations, elaborations, or other modifications
|
||||
* represent, as a whole, an original work of authorship. For the purposes
|
||||
* of this License, Derivative Works shall not include works that remain
|
||||
* separable from, or merely link (or bind by name) to the interfaces of,
|
||||
* the Work and Derivative Works thereof.
|
||||
*
|
||||
* "Contribution" shall mean any work of authorship, including
|
||||
* the original version of the Work and any modifications or additions
|
||||
* to that Work or Derivative Works thereof, that is intentionally
|
||||
* submitted to Licensor for inclusion in the Work by the copyright owner
|
||||
* or by an individual or Legal Entity authorized to submit on behalf of
|
||||
* the copyright owner. For the purposes of this definition, "submitted"
|
||||
* means any form of electronic, verbal, or written communication sent
|
||||
* to the Licensor or its representatives, including but not limited to
|
||||
* communication on electronic mailing lists, source code control systems,
|
||||
* and issue tracking systems that are managed by, or on behalf of, the
|
||||
* Licensor for the purpose of discussing and improving the Work, but
|
||||
* excluding communication that is conspicuously marked or otherwise
|
||||
* designated in writing by the copyright owner as "Not a Contribution."
|
||||
*
|
||||
* "Contributor" shall mean Licensor and any individual or Legal Entity
|
||||
* on behalf of whom a Contribution has been received by Licensor and
|
||||
* subsequently incorporated within the Work.
|
||||
*
|
||||
* 2. Grant of Copyright License. Subject to the terms and conditions of
|
||||
* this License, each Contributor hereby grants to You a perpetual,
|
||||
* worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
* copyright license to reproduce, prepare Derivative Works of,
|
||||
* publicly display, publicly perform, sublicense, and distribute the
|
||||
* Work and such Derivative Works in Source or Object form.
|
||||
*
|
||||
* 3. Grant of Patent License. Subject to the terms and conditions of
|
||||
* this License, each Contributor hereby grants to You a perpetual,
|
||||
* worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
* (except as stated in this section) patent license to make, have made,
|
||||
* use, offer to sell, sell, import, and otherwise transfer the Work,
|
||||
* where such license applies only to those patent claims licensable
|
||||
* by such Contributor that are necessarily infringed by their
|
||||
* Contribution(s) alone or by combination of their Contribution(s)
|
||||
* with the Work to which such Contribution(s) was submitted. If You
|
||||
* institute patent litigation against any entity (including a
|
||||
* cross-claim or counterclaim in a lawsuit) alleging that the Work
|
||||
* or a Contribution incorporated within the Work constitutes direct
|
||||
* or contributory patent infringement, then any patent licenses
|
||||
* granted to You under this License for that Work shall terminate
|
||||
* as of the date such litigation is filed.
|
||||
*
|
||||
* 4. Redistribution. You may reproduce and distribute copies of the
|
||||
* Work or Derivative Works thereof in any medium, with or without
|
||||
* modifications, and in Source or Object form, provided that You
|
||||
* meet the following conditions:
|
||||
*
|
||||
* (a) You must give any other recipients of the Work or
|
||||
* Derivative Works a copy of this License; and
|
||||
*
|
||||
* (b) You must cause any modified files to carry prominent notices
|
||||
* stating that You changed the files; and
|
||||
*
|
||||
* (c) You must retain, in the Source form of any Derivative Works
|
||||
* that You distribute, all copyright, patent, trademark, and
|
||||
* attribution notices from the Source form of the Work,
|
||||
* excluding those notices that do not pertain to any part of
|
||||
* the Derivative Works; and
|
||||
*
|
||||
* (d) If the Work includes a "NOTICE" text file as part of its
|
||||
* distribution, then any Derivative Works that You distribute must
|
||||
* include a readable copy of the attribution notices contained
|
||||
* within such NOTICE file, excluding those notices that do not
|
||||
* pertain to any part of the Derivative Works, in at least one
|
||||
* of the following places: within a NOTICE text file distributed
|
||||
* as part of the Derivative Works; within the Source form or
|
||||
* documentation, if provided along with the Derivative Works; or,
|
||||
* within a display generated by the Derivative Works, if and
|
||||
* wherever such third-party notices normally appear. The contents
|
||||
* of the NOTICE file are for informational purposes only and
|
||||
* do not modify the License. You may add Your own attribution
|
||||
* notices within Derivative Works that You distribute, alongside
|
||||
* or as an addendum to the NOTICE text from the Work, provided
|
||||
* that such additional attribution notices cannot be construed
|
||||
* as modifying the License.
|
||||
*
|
||||
* You may add Your own copyright statement to Your modifications and
|
||||
* may provide additional or different license terms and conditions
|
||||
* for use, reproduction, or distribution of Your modifications, or
|
||||
* for any such Derivative Works as a whole, provided Your use,
|
||||
* reproduction, and distribution of the Work otherwise complies with
|
||||
* the conditions stated in this License.
|
||||
*
|
||||
* 5. Submission of Contributions. Unless You explicitly state otherwise,
|
||||
* any Contribution intentionally submitted for inclusion in the Work
|
||||
* by You to the Licensor shall be under the terms and conditions of
|
||||
* this License, without any additional terms or conditions.
|
||||
* Notwithstanding the above, nothing herein shall supersede or modify
|
||||
* the terms of any separate license agreement you may have executed
|
||||
* with Licensor regarding such Contributions.
|
||||
*
|
||||
* 6. Trademarks. This License does not grant permission to use the trade
|
||||
* names, trademarks, service marks, or product names of the Licensor,
|
||||
* except as required for reasonable and customary use in describing the
|
||||
* origin of the Work and reproducing the content of the NOTICE file.
|
||||
*
|
||||
* 7. Disclaimer of Warranty. Unless required by applicable law or
|
||||
* agreed to in writing, Licensor provides the Work (and each
|
||||
* Contributor provides its Contributions) on an "AS IS" BASIS,
|
||||
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
||||
* implied, including, without limitation, any warranties or conditions
|
||||
* of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
||||
* PARTICULAR PURPOSE. You are solely responsible for determining the
|
||||
* appropriateness of using or redistributing the Work and assume any
|
||||
* risks associated with Your exercise of permissions under this License.
|
||||
*
|
||||
* 8. Limitation of Liability. In no event and under no legal theory,
|
||||
* whether in tort (including negligence), contract, or otherwise,
|
||||
* unless required by applicable law (such as deliberate and grossly
|
||||
* negligent acts) or agreed to in writing, shall any Contributor be
|
||||
* liable to You for damages, including any direct, indirect, special,
|
||||
* incidental, or consequential damages of any character arising as a
|
||||
* result of this License or out of the use or inability to use the
|
||||
* Work (including but not limited to damages for loss of goodwill,
|
||||
* work stoppage, computer failure or malfunction, or any and all
|
||||
* other commercial damages or losses), even if such Contributor
|
||||
* has been advised of the possibility of such damages.
|
||||
*
|
||||
* 9. Accepting Warranty or Additional Liability. While redistributing
|
||||
* the Work or Derivative Works thereof, You may choose to offer,
|
||||
* and charge a fee for, acceptance of support, warranty, indemnity,
|
||||
* or other liability obligations and/or rights consistent with this
|
||||
* License. However, in accepting such obligations, You may act only
|
||||
* on Your own behalf and on Your sole responsibility, not on behalf
|
||||
* of any other Contributor, and only if You agree to indemnify,
|
||||
* defend, and hold each Contributor harmless for any liability
|
||||
* incurred by, or claims asserted against, such Contributor by reason
|
||||
* of your accepting any such warranty or additional liability.
|
||||
*
|
||||
* END OF TERMS AND CONDITIONS
|
||||
*
|
||||
* APPENDIX: How to apply the Apache License to your work.
|
||||
*
|
||||
* To apply the Apache License to your work, attach the following
|
||||
* boilerplate notice, with the fields enclosed by brackets "[]"
|
||||
* replaced with your own identifying information. (Don't include
|
||||
* the brackets!) The text should be enclosed in the appropriate
|
||||
* comment syntax for the file format. We also recommend that a
|
||||
* file or class name and description of purpose be included on the
|
||||
* same "printed page" as the copyright notice for easier
|
||||
* identification within third-party archives.
|
||||
*
|
||||
* Copyright [yyyy] [name of copyright owner]
|
||||
*
|
||||
* Licensed under the Apache License, Version 2.0 (the "License");
|
||||
* you may not use this file except in compliance with the License.
|
||||
* You may obtain a copy of the License at
|
||||
*
|
||||
* http://www.apache.org/licenses/LICENSE-2.0
|
||||
*
|
||||
* Unless required by applicable law or agreed to in writing, software
|
||||
* distributed under the License is distributed on an "AS IS" BASIS,
|
||||
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
* See the License for the specific language governing permissions and
|
||||
* limitations under the License.
|
||||
*/
|
||||
</code></textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,96 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
<h1>Repositories</h1>
|
||||
<ul>
|
||||
<li><a href="http://ivyrep.jayasoft.org/">IvyRep</a></li>
|
||||
<p> The main repository of ivy files used by Ivy.</p>
|
||||
<li><a href="https://opensvn.csie.org/ivyrepsandbox/">IvyRep Sandbox</a></li>
|
||||
<p> This subversion repository is used to share ivy files before promoting them to ivyrep.</p>
|
||||
<li><a href="http://www.ibiblio.org/maven/">IBiblio maven repository</a></li>
|
||||
<p> The official repository of maven hosts a great number of jars. It can be used by ivy to find the jars of your depedencies.</p>
|
||||
<li><a href="http://www.opensymphony.com/webwork/wikidocs/Dependencies.html">Webwork ivy repository</a></li>
|
||||
<p> Open symphony has created an ivy repository you can use as a model or directly.</p>
|
||||
<li><a href="http://blog.tryphon.org/tryphon/archives/2006/09/02/kolaka-ivy-repository/">Kokala repository</a></li>
|
||||
<p> Folks from FreeCast have created an ivy repository for building FreeCast. You will find many interesting ivy files over here.</p>
|
||||
<li><a href="https://maven-repository.dev.java.net/">Java.net Maven repository</a></li>
|
||||
<p>Java.net has a maven repository with interesting stuff that can't be found on ibiblio</p>
|
||||
<li><a href="http://mvnrepository.com/">mvnrepository</a></li>
|
||||
<p> Search Maven Ibiblio repository
|
||||
</ul>
|
||||
<h1>Tools and plugins</h1>
|
||||
<p>Here is a list of the ivy related tools and plugins we are aware of that can be found over the net.</p>
|
||||
<p>Feel free to post on the forum to ask for your tool to be added here.</p>
|
||||
<ul>
|
||||
<li><a href="http://www.ivytools.org/">ivytools.org</a></li>
|
||||
<p> This sourceforge project aims to gather community contributed tools and plugins for ivy.</p>
|
||||
<li><a href="http://incubator.apache.org/ivy/ivyde/">IvyDE</a></li>
|
||||
<p> A plugin for eclipse which helps writing ivy files by bringing powerful code completion and wizards, and also let you add a classpath container keeping your eclipse project classpath in sync with the dependencies ivy resolves.</p>
|
||||
<li><a href="http://ivycruise.jayasoft.org/">IvyCruise</a></li>
|
||||
<p> This set of plugins for cruise control let you integrate ivy with this famous continuous integration server.</p>
|
||||
<li><a href="http://plugins.intellij.net/plugin/?id=141">IvyDependencyImportor</a></li>
|
||||
<p> is a plugin for intellij IDEA, which let you import all the libs described in the ivy.xml to the current module library.</p>
|
||||
<li><a href="http://plugins.intellij.net/plugin/?id=140">IVY for IDEA</a></li>
|
||||
<p> is another plugin for intellij IDEA, which reads IDEA module settings such as classpath and source directories from IVY setup.</p>
|
||||
<li><a href="http://www.ivytools.org/ivy+svn.html">Ivy+SVN</a></li>
|
||||
<p> This is a subversion dependency resolver for ivy.</p>
|
||||
<li><a href="http://wiki.hippo.nl/display/OS/SAnt+build+system">SAnt</a></li>
|
||||
<p> SAnt (Shared Ant) is an experimental build system based on Ant and Ivy, primarily developpedd as part of the hippo project.</p>
|
||||
<li><a href="http://dehora.net/code/antant/readme.html">AntAnt</a></li>
|
||||
<p> AntAnt is an ant project generator (generates an ant project skeleton), which uses ivy for dependency management.</p>
|
||||
<li><a href="http://www.fnogol.de/archives/2006/08/21/generate-applicationxml-from-ivyxml-for-packaging-an-ear/">Generate application.xml from ivy.xml for packaging an ear</a></li>
|
||||
<p> is an entry on Philipp Meier's weblog which explain how he used ivy and xslt to generate his application.xml files.</p>
|
||||
<li><a href="http://www.ribomation.com/riboutils/eartask/">EAR ant task</a></li>
|
||||
<p> this is not directly related to ivy, but more to the link above. You have also the possibility to use this task to generate your ear, which does not depend on Ivy, but which can be very easily integrated with.</p>
|
||||
</ul>
|
||||
<h1>Doc, tutorials, articles</h1>
|
||||
<ul>
|
||||
<li><a href="presentations/apache-con-2007/">ApacheCon EU 2007 slides</a></li>
|
||||
<p>slides and demo sources from Xavier's ApacheCon EU 2007 talk</p>
|
||||
<li><a href="http://wiki.java.net/bin/view/Netbeans/FaqIvy">Netbeans FAQ</a></li>
|
||||
<p>The Netbeans FAQ has an entry explaining how to use Ivy in their open source IDE.</p>
|
||||
<li><a href="http://chris-engn.blogspot.com/2005/07/naven-dotnet-continous-integration.html">Using Ivy in a dotnet project</a></li>
|
||||
<p>Chris gives a good idea of how to use ivy, cruise control and nant in a dotnet project environment</p>
|
||||
<li><a href="http://weblogs.java.net/blog/dcengija/archive/2006/04/configuring_ivy.html">Integrating Ivy and luntbuild</a></li>
|
||||
<p>Davor Cengija on his blog explain how he integrates Ivy in luntbuild, an open source continuous integration server</p>
|
||||
<li><a href="doc/articles/ease-multi-module.html">Easing multi module development</a></li>
|
||||
<p>Johan stuyts, the author of SAnt, also contributed a nice article on his view of how to use Ivy on a multi module environment.</p>
|
||||
<li><a href="http://www-128.ibm.com/developerworks/java/library/j-ap10106/index.html?ca=dgr-jw01SmellyScripts">Remove the smell from your build scripts</a></li>
|
||||
<p>This article is not related to Ivy, but to build script in general, but we thought it may be worth for Ivy users to read it.
|
||||
</ul>
|
||||
<h1>Others</h1>
|
||||
<ul>
|
||||
<li><a href="http://ant.apache.org/">ant</a></li>
|
||||
<p>Ant is the popular build tool with which ivy is integrated.</p>
|
||||
<li><a href="http://ant-contrib.sourceforge.net/">AntContrib</a></li>
|
||||
<p>AntContrib is a project offering a set of useful tasks for ant.</p>
|
||||
<li><a href="http://www.javalobby.org/">Javalobby</a></li>
|
||||
<p>Javalobby is a Java community site with interesting forums and tutorials</p>
|
||||
</ul></textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,77 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
We are frequently asked how ivy compares to maven2, so we have decided togives some insight about our opinion on the subject.
|
||||
|
||||
Obviously this comparison is biased (hey, you are on official Ivy site :-)), but we'll try to keep it as fair as possible. Do not hesitate to add comment if you feel something is missing or false on this page. You can also have a look at <a href="http://docs.codehaus.org/display/MAVEN/Feature+Comparisons">Maven2 feature comparison page on codehaus</a>, which itself offers another point of view.
|
||||
|
||||
There have been also severa discussions on the subject, among which the one triggered by <a href="http://www.jayasoft.org/node/806.html">spring contemplating about switching to maven</a> is may be the more interesting.
|
||||
|
||||
But here is the points we think mainly differentiate maven2 and Ivy.
|
||||
|
||||
<h1>Comparing plants and apples</h1>
|
||||
First, the most important difference between maven2 and ivy is that they aren't at all the same kind of tools. Maven2 is a software project management and comprehension tool, whereas Ivy is only a dependency management tool, highly integrated with ant, the popular build management tool. Maven2 offers dependency management facility, and that's why many ask how ivy compares to maven2. That's why we'll focus only on dependency management features of maven2 in this comparison.
|
||||
So if you look for an out of the box software project management tool, you may skip the rest of this comparison and check what maven2 has to offer.
|
||||
|
||||
<h1>Different concepts</h1>
|
||||
Ivy heavily relies on a unique concept called configuration. In ivy, a module configuration is a way to use or to see the module. For instance, you can have a test and runtime configuration in your module. But you can also have a mysql and an oracle configuration. Or an hibernate and a jdbc configuration. In each configuration you can declare what artifacts (jar, war, ...) are required. And in each configuration, you can declare your dependencies on other modules, and describe which configuration of the dependency you need. This is called configuration mapping, and it is a very flexible way to answer to a lot of problems we face very often in software development.
|
||||
|
||||
Maven2 on its side has something called the scope. You can declare a dependency as being part of the test scope, or the buildtime scope. Then depending on this scope you will get the dependency artifact (only one artifact per module in maven2) with its dependencies depending on their scope. Scopes are predefined in maven2 and you can't change that. No way to create an oracle scope. No way to indicate you need what as been declared to be needed in the runtime scope of your dependency in your compile one. Everything here is written in the marble.
|
||||
|
||||
And this leads to some kind of troubles... as Matt Raible stated in his <a href="http://raibledesigns.com/page/rd?anchor=maven_2_s_transitive_dependencies">blog</a> talking about maven2 dependencies:
|
||||
[quote]
|
||||
There are a *lot* of unnecessary dependencies downloaded for many libraries. For example, Hibernate downloads a bunch of JBoss JARs and the Display Tag downloads all the various web framework JARs. I found myself excluding almost as many dependencies as I added.
|
||||
[/quote]
|
||||
The problem is that hibernate can be used with several cache implementations, several connection pool implementation, ... And this can't be managed with scopes, wheres Ivy configurations offers an elegant solution to this kind of problem. For instance, in ivy, assuming hibernate as an ivy file like <a href="http://ivyrep.jayasoft.org/hibernate/hibernate/ivy-2.1.8.xml">this one</a>, then you can declare a dependency like that:
|
||||
<code type="xml">
|
||||
<dependency org="hibernate" name="hibernate" rev="2.1.8" conf="default->proxool,oscache"/>
|
||||
</code>
|
||||
to get hibernate with its proxool and oscache implemetations, and like that:
|
||||
<code type="xml">
|
||||
<dependency org="hibernate" name="hibernate" rev="2.1.8" conf="default->dbcp,swarmcache"/>
|
||||
</code>
|
||||
to get hibernate with dbcp and swarmcache.
|
||||
|
||||
<h1>Documentation</h1>
|
||||
An important thing to be able to use a tool is its amount of documentation. With Ivy, even if they are written in broken english (would you have prefered well written french :-)), the printer friendly version of the documentation is now about 120 pages.
|
||||
With maven2, it's a bit difficult to clearly know what can be considered as dependency management documentation, but we didn't managed to find much: some small introductory guides, short entries in the pom reference guide, and not really much more. Even in the maven book you can get for free on <a href="http://www.mergere.com/">mergere website</a>, the insight about dependency management is still light in our point of view.
|
||||
|
||||
<h1>Conflict management</h1>
|
||||
Conflict management are an important part of dependency management, cause when dealing with transitive dependencies you often have to face conflicts. In this area, Ivy let you do whatever you want: use one conflict manager in one module, another one elsewhere, decide which revision you will get, ... You can even plug your own conflict manager if you need to.
|
||||
|
||||
With maven2, conflict management is quite simple: the principle is to get the nearest definition. So if your module depends on foo 1.0, none of your dependencies will ever manage to get foo 1.1 without a change in your own dependency declaration. It may be ok in some cases, it may not in others...
|
||||
|
||||
<h1>Flexibility</h1>
|
||||
In ivy many things can be <a href="../doc/configuration.html">configured</a>, and many others can be <a href="../doc/extend.html">plugged in</a>: dependency resolvers, conflict manager, module descriptor parser, latest revision strategy, ... Maven2 also offers repository pluggability, but not much more as far as we know. Moreover, repository configuration seems to be less flexible than with ivy.
|
||||
|
||||
<h1>Public Repositories</h1>
|
||||
Maven2 comes out of the box configured to use ibiblio maven2 repository, which contains <strong>a lot</strong> of modules (both artifacts and module descriptors). The only problem some may face is that module descriptors are not always checked, so some are not really well written.
|
||||
Ivy, on its side, is used out of the box with ivyrep, ivy official repository, which contains only a few modules, and is not updated frequently. But it is also compatible with maven1 ibiblio repository (for artifacts only, no module descriptors), can also be used with maven2 repository (with pom compatibility, but you will here face some naming problems - that can be addressed using the namespace feature-, you won't benefit from ivy configurations with the module descriptors found there, and, let's face it, the maven2 compatibility of Ivy is far from maven's one :-)), and also has an ivyrep sandbox in which much more module descriptors can be found (not checked, as with ibiblio repository).
|
||||
</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,108 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
|
||||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
Before posting to mailing lists, make sure you don't have the answer to your question in the [[faq]] or more generally in the [[doc/index]].
|
||||
|
||||
<hr/>
|
||||
<h2>Users mailing list</h2>
|
||||
Used to discuss any issue encountered when using Ivy
|
||||
<table cellpadding="10">
|
||||
<tr><td>
|
||||
<a href="mailto:ivy-user@incubator.apache.org">ivy-user@incubator.apache.org</a>
|
||||
</td><td>
|
||||
<a href="mailto:ivy-user-subscribe@incubator.apache.org">Subscribe</a>
|
||||
</td><td>
|
||||
<a href="mailto:ivy-user-unsubscribe@incubator.apache.org">Unsubscribe</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
<table cellpadding="10">
|
||||
<tr><td>
|
||||
<a href="http://mail-archives.apache.org/mod_mbox/incubator-ivy-user/">Apache Archive</a>
|
||||
</td><td>
|
||||
<a href="http://mail-archive.com/ivy-user%40incubator.apache.org/">mail-archive.com</a>
|
||||
</td><td>
|
||||
<a href="http://www.nabble.com/ivy-user-f18383.html">Nabble</a>
|
||||
</td><td>
|
||||
<a href="http://marc.info/?l=ivy-user">MARC</a>
|
||||
</td><td>
|
||||
</td></tr>
|
||||
</table>
|
||||
<hr/>
|
||||
<h2>Dev mailing list</h2>
|
||||
Used to discuss Ivy development
|
||||
<table cellpadding="10">
|
||||
<tr><td>
|
||||
<a href="mailto:ivy-dev@incubator.apache.org">ivy-dev@incubator.apache.org</a>
|
||||
</td><td>
|
||||
<a href="mailto:ivy-dev-subscribe@incubator.apache.org">Subscribe</a>
|
||||
</td><td>
|
||||
<a href="mailto:ivy-dev-unsubscribe@incubator.apache.org">Unsubscribe</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
<table cellpadding="10">
|
||||
<tr><td>
|
||||
<a href="http://mail-archives.apache.org/mod_mbox/incubator-ivy-dev/">Apache Archive</a>
|
||||
</td><td>
|
||||
<a href="http://mail-archive.com/ivy-dev%40incubator.apache.org/">mail-archive.com</a>
|
||||
</td><td>
|
||||
<a href="http://www.nabble.com/ivy-dev-f18384.html">Nabble</a>
|
||||
</td><td>
|
||||
<a href="http://marc.info/?l=ivy-dev">MARC</a>
|
||||
</td><td>
|
||||
</td></tr>
|
||||
</table>
|
||||
<hr/>
|
||||
<h2>Commit mailing list</h2>
|
||||
Read only mailing list where subversion commit messages are posted
|
||||
<table cellpadding="10">
|
||||
<tr><td>
|
||||
<a href="mailto:ivy-commit@incubator.apache.org">ivy-commit@incubator.apache.org</a>
|
||||
</td><td>
|
||||
<a href="mailto:ivy-commit-subscribe@incubator.apache.org">Subscribe</a>
|
||||
</td><td>
|
||||
<a href="mailto:ivy-commit-unsubscribe@incubator.apache.org">Unsubscribe</a>
|
||||
</td></tr>
|
||||
</table>
|
||||
<table cellpadding="10">
|
||||
<tr><td>
|
||||
<a href="http://mail-archives.apache.org/mod_mbox/incubator-ivy-commit/">Apache Archive</a>
|
||||
</td><td>
|
||||
<a href="http://mail-archive.com/ivy-commit%40incubator.apache.org/">mail-archive.com</a>
|
||||
</td><td>
|
||||
<a href="http://marc.info/?l=ivy-commit">MARC</a>
|
||||
</td><td>
|
||||
</td></tr>
|
||||
</table>
|
||||
<hr/>
|
||||
<br/><br/>
|
||||
The previous way of communication around Ivy was the Jayasoft forum, for which a backup is still available here:
|
||||
http://www.jaya.free.fr/ivy/forum.html
|
||||
|
||||
Feel free to use your favorite search engine to find answers to your questions in over there.</textarea>
|
||||
<script type="text/javascript">xooki.postProcess();</script>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -20,8 +20,8 @@
|
|||
<html>
|
||||
<head>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
|
||||
<script type="text/javascript">var xookiConfig = {level: 1};</script>
|
||||
<script type="text/javascript" src="../xooki/xooki.js"></script>
|
||||
<script type="text/javascript">var xookiConfig = {level: 0};</script>
|
||||
<script type="text/javascript" src="xooki/xooki.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<textarea id="xooki-source">
|
||||
|
|
@ -1,53 +0,0 @@
|
|||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<project name="demo1" default="retrieve-deps" xmlns:ivy="antlib:org.apache.ivy.ant">
|
||||
<condition property="ivy.home" value="${env.IVY_HOME}">
|
||||
<isset property="env.IVY_HOME" />
|
||||
</condition>
|
||||
<property name="ivy.home" value="${user.home}/.ivy" />
|
||||
<property name="ivy.jar.dir" value="${ivy.home}/jars" />
|
||||
<property name="ivy.jar.file" value="${ivy.jar.dir}/ivy.jar" />
|
||||
|
||||
<target name="init-ivy">
|
||||
<mkdir dir="${ivy.jar.dir}"/>
|
||||
<!-- download Ivy from web site so that it can be used even without any special installation -->
|
||||
<!-- use a non standard location during migration to apache -->
|
||||
<get src="http://people.apache.org/~xavier/ivy/2.0.0-alpha-1-incubating/ivy.jar"
|
||||
dest="${ivy.jar.file}" usetimestamp="true"/>
|
||||
<!-- try to load ivy here from local ivy dir, in case the user has not already dropped
|
||||
it into ant's lib dir (note that the latter copy will always take precedence).
|
||||
We will not fail as long as local lib dir exists (it may be empty) and
|
||||
ivy is in at least one of ant's lib dir or the local lib dir. -->
|
||||
<path id="ivy.lib.path">
|
||||
<fileset dir="${ivy.jar.dir}" includes="*.jar"/>
|
||||
</path>
|
||||
<taskdef resource="org/apache/ivy/ant/antlib.xml"
|
||||
uri="antlib:org.apache.ivy.ant" classpathref="ivy.lib.path"/>
|
||||
</target>
|
||||
|
||||
<target name="retrieve-deps" depends="init-ivy">
|
||||
<!-- we do nothing special for the settings, by default Ivy will look into the current directory
|
||||
and check if an ivysettings.xml is available. If none is present, default settings will be used -->
|
||||
<ivy:retrieve organisation="org.apache.struts"
|
||||
module="struts2-core"
|
||||
revision="2.0.5"
|
||||
conf="default"
|
||||
inline="true"/>
|
||||
</target>
|
||||
</project>
|
||||
|
|
@ -1,25 +0,0 @@
|
|||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<ivysettings>
|
||||
<!-- we define our own cache to make the demo independent from default cache location -->
|
||||
<settings defaultCache="../cache" />
|
||||
<!-- include default settings which are ok for the demo -->
|
||||
<include url="${ivy.default.settings.dir}/ivysettings.xml"/>
|
||||
</ivysettings>
|
||||
|
||||
|
|
@ -1,50 +0,0 @@
|
|||
<!--
|
||||
Licensed to the Apache Software Foundation (ASF) under one
|
||||
or more contributor license agreements. See the NOTICE file
|
||||
distributed with this work for additional information
|
||||
regarding copyright ownership. The ASF licenses this file
|
||||
to you under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in compliance
|
||||
with the License. You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing,
|
||||
software distributed under the License is distributed on an
|
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
||||
KIND, either express or implied. See the License for the
|
||||
specific language governing permissions and limitations
|
||||
under the License.
|
||||
-->
|
||||
<project name="demo2" default="retrieve-deps" xmlns:ivy="antlib:org.apache.ivy.ant">
|
||||
<condition property="ivy.home" value="${env.IVY_HOME}">
|
||||
<isset property="env.IVY_HOME" />
|
||||
</condition>
|
||||
<property name="ivy.home" value="${user.home}/.ivy" />
|
||||
<property name="ivy.jar.dir" value="${ivy.home}/jars" />
|
||||
<property name="ivy.jar.file" value="${ivy.jar.dir}/ivy.jar" />
|
||||
|
||||
<target name="init-ivy">
|
||||
<mkdir dir="${ivy.jar.dir}"/>
|
||||
<!-- download Ivy from web site so that it can be used even without any special installation -->
|
||||
<!-- use a non standard location during migration to apache -->
|
||||
<get src="http://people.apache.org/~xavier/ivy/2.0.0-alpha-1-incubating/ivy.jar"
|
||||
dest="${ivy.jar.file}" usetimestamp="true"/>
|
||||
<!-- try to load ivy here from local ivy dir, in case the user has not already dropped
|
||||
it into ant's lib dir (note that the latter copy will always take precedence).
|
||||
We will not fail as long as local lib dir exists (it may be empty) and
|
||||
ivy is in at least one of ant's lib dir or the local lib dir. -->
|
||||
<path id="ivy.lib.path">
|
||||
<fileset dir="${ivy.jar.dir}" includes="*.jar"/>
|
||||
</path>
|
||||
<taskdef resource="org/apache/ivy/ant/antlib.xml"
|
||||
uri="antlib:org.apache.ivy.ant" classpathref="ivy.lib.path"/>
|
||||
</target>
|
||||
|
||||
<target name="retrieve-deps" depends="init-ivy">
|
||||
<!-- here we don't need to specify which ivy file to use, because the default (ivy.xml) is ok -->
|
||||
<ivy:retrieve
|
||||
pattern="lib/[conf]/[artifact]-[revision].[ext]"/>
|
||||
<ivy:report todir="report"/>
|
||||
</target>
|
||||
</project>
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue