jvanzyl 2004/05/12 10:37:48
Modified: xdocs Tag: MAVEN-1_0-BRANCH repository-upload.xml
Log:
o adding a bit of an explanation as to why we want the POMs and lics.
Revision Changes Path
No revision
No revision
1.7.4.7 +25 -2 maven/xdocs/repository-upload.xml
Index: repository-upload.xml
===================================================================
RCS file: /home/cvs/maven/xdocs/repository-upload.xml,v
retrieving revision 1.7.4.6
retrieving revision 1.7.4.7
diff -u -r1.7.4.6 -r1.7.4.7
--- repository-upload.xml 10 May 2004 22:17:44 -0000 1.7.4.6
+++ repository-upload.xml 12 May 2004 17:37:48 -0000 1.7.4.7
@@ -21,6 +21,7 @@
<properties>
<author email="[EMAIL PROTECTED]">Ben Walding</author>
+ <author email="[EMAIL PROTECTED]">Jason van Zyl</author>
<title>Uploading to ibiblio</title>
</properties>
@@ -68,7 +69,7 @@
<p>
Post your request to <a
href="http://jira.codehaus.org/secure/CreateIssue.jspa?pid=10367&issuetype=3";>JIRA</a>.
The first line of the description should be the URL of the upload bundle,
then leave a blank line and place
- any addition comments you wish in the following paragraph. So the
+ any additional comments you wish in the following paragraph. So the
description field might look like:
</p>
@@ -79,6 +80,28 @@
clipping of nose hairs. Please upload! DO IT NOW!
</source>
- </section>
+ </section>
+
+ <section name="Explanation">
+ <p>
+ Some folks have asked why do we require the POM and license each
+ time an artifact is deployed so here's a small explanation. The POM
+ being deployed with the artifact is part of the process to make
+ transitive dependencies a reality in Maven. The logic for getting
+ transitive dependencies working is really not that hard, the problem
+ is getting the data. So we have changed the process of uploading
+ artifacts to include the POM in an attempt to get transitive
+ dependencies working as quickly as possible. The other applications
+ that may be possible having all the POMs available for artifacts
+ are vast, so by placing them into the repository as part of the
+ process we open up the doors to new ideas that involve unified
+ access to project POMs. We also ask for a license now because it is
+ possible that your project's license may change in the course of
+ its life time and we are trying create tools to help normal people
+ sort out licensing issues. For example, knowing all the licenses
+ for a particular graph of artifacts we could have some strategies
+ that would identify potential licensing problems.
+ </p>
+ </section>
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
