So you want a resource uploaded to ibiblio?!
- +- To save time for everybody, here is how you go about it. + To save time for everybody, here is how you go about it.
- +Use the repository plugin provided with the standard Maven distribution to create an upload bundle:
- +The bundle will be created in your "target" directory of the form: ${pom.artifactId}-${pom.currentVersion}-bundle.jar
- +If you are not using maven as your build system but want something uploaded to Ibiblio then you just need to make a JAR with the following format:
- +Post your request to JIRA. - The first line of the description should be the URL of the upload bundle, then leave a blank line and place + The first line of the description should be the URL of the upload bundle, then leave a blank line and place any additional comments you wish in the following paragraph. So the description field might look like: -
+Some folks have asked why do we require the POM and license each Index: xdocs/misc/glossary.xml =================================================================== RCS file: /home/cvspublic/maven/xdocs/misc/glossary.xml,v retrieving revision 1.3 diff -u -r1.3 glossary.xml --- xdocs/misc/glossary.xml 22 Jul 2004 16:28:27 -0000 1.3 +++ xdocs/misc/glossary.xml 2 Aug 2004 23:23:46 -0000 @@ -88,7 +88,7 @@ A repository is an structured storage of project artifacts. Those artifacts are organized under the following structure:
- $MAVEN_REPO/project id/artifact type/project-version.extension
+ $MAVEN_REPO/groupId/artifact type/artifactId-version.extension
For instance, a Maven JAR artifact will be stored in a repository Index: xdocs/reference/project-descriptor.xml =================================================================== RCS file: /home/cvspublic/maven/xdocs/reference/project-descriptor.xml,v retrieving revision 1.35 diff -u -r1.35 project-descriptor.xml --- xdocs/reference/project-descriptor.xml 23 Jul 2004 04:40:08 -0000 1.35 +++ xdocs/reference/project-descriptor.xml 2 Aug 2004 23:26:11 -0000 @@ -41,7 +41,7 @@ href="http://maven.apache.org/xsd/maven-project-3.0.0.xsd">http://maven.apache.org/xsd/maven-project-3.0.0.xsd. In addition, a sample project descriptor is presented in the Integration - document. For those wondering, yes, Maven's build system is built + document. For those wondering, yes, Maven's build system is built by Maven (we believe in eating our own dog food :)
The <project> element specifies various
@@ -231,14 +232,25 @@
+ Note: The use of the id element is + deprecated. Please use artifactId + instead. +
+
If this isn't defined, the central repository is used instead as
- determined by maven.repo.central and
+ determined by maven.repo.central and
maven.repo.central.directory
:) in it.
@@ -534,15 +546,15 @@
scm:cvs:local:ignored:/cvs/root:module-name
- For StarTeam access:
+ For StarTeam access:
scm:starteam:username:password@host:port/project/view/folder
The delimiter is determined by the character after "scm". eg.
- scm|cvs|pserver|user@host|/cvs/root|module-name
+ scm|cvs|pserver|user@host|/cvs/root|module-name
is equivalent to that listed above. This can be useful for Windows users
who have : in their cvsroot parameter (eg. D:\cvsroot).
- The filename that Maven downloads from the repository is
+ The filename that Maven downloads from the repository is
artifactId-version.jar where artifactId corresponds to the artifactId
element and version corresponds to the
version element.
@@ -884,7 +896,7 @@
<artifactId>-<version>.jar pattern.jar.
- Other known and recognised dependency types are:
+ Other known and recognised dependency types are:
ejb and plugin.
mark dependencies with properties. For example the
- war plugin looks for a
+ Properties about the dependency. Various plugins allow you to
+ mark dependencies with properties. For example the
+ war plugin looks for a
war.bundle property, and if found will include the dependency
in WEB-INF/lib. For example syntax, check the war plugin docs.
sourceModification element, which is then described by
- additional elements (described below). These modifications are used
+ additional elements (described below). These modifications are used
to exclude or include various source depending on the environment
the build is running in.
@@ -1038,8 +1050,8 @@
| Element | Description | |
|---|---|---|
| include | - This element specifies an + This element specifies an Ant pattern of files to include in a list. | @@ -1158,7 +1170,7 @@|
| exclude | - This element specifies an + This element specifies an Ant pattern of files to exclude from a list. | Index: xdocs/reference/user-guide.xml =================================================================== RCS file: /home/cvspublic/maven/xdocs/reference/user-guide.xml,v retrieving revision 1.71 diff -u -r1.71 user-guide.xml --- xdocs/reference/user-guide.xml 24 Jul 2004 17:03:48 -0000 1.71 +++ xdocs/reference/user-guide.xml 2 Aug 2004 23:28:45 -0000 @@ -200,7 +200,7 @@|
| maven.repo.central.directory | +maven.repo.central.directory |
This is the directory that Maven will copy the
distribution to during a dist:deploy.
@@ -1217,7 +1217,7 @@
maven.mode.online=true is the combination to use if one needs a working
"-link" option for the javadoc plugin plus no download of snapshot/any jars.
-
+
If you wish to use the default reports but remove one or add one, the + If you wish to use the default reports but remove one or add one, the preferred method is to use a postGoal for xdoc:register-reports like this: - - + +@@ -1807,7 +1805,7 @@ well as links to the numerous Maven-generated reports. |