/jaxme/jars/jaxme-<build-date>.jar
and
/jaxme/jars/jaxme-<version-no>.jar
It is important to have your artifactId's match across all versions of an artifact, otherwise they aren't the same "artifact", so
/jaxme/jars/jaxme-incubator-x.x.jar
does not share the same artifact id as
/jaxme/jars/jaxme-SNAPSHOT.jar
to have them match it would have to be
/jaxme/jars/jaxme-incubator-SNAPSHOT.jar
So, if your going to be distributing a "build release" I recommend the naming strategy where all artifactID's match. If the jaxme project is planning to leave the incubator anytime in the future, I would highly recommend you not use the word "incubator" in the artifact id. My personal opinion added to this is that its the same way we don't use "jakarta" in in projects like the Jakarta Commons, because some aspects Jakarta is a Foundry. Incubator is also a Foundry.
My future planned strategy to support "build-releases" is to have build releases (daily, weekly builds etc) not be present on:
/www/www.apache.org/dist/java-repository
but to actually be present on:
/www/cvs.apache.org/builds/java-repository
Then, to actually use this approach with Maven you'd have to add the cvs.apache.org repository to your Maven client, this makes project dependencies hairy in the Current release of Maven because the contents wouldn't be present at ibiblio. We still have much to decide to do and infrastructure to setup to have this build location.
My current strategy in this case is to have the build-releases in the same project directory as the version releases, then they are all rsynced with ibiblio properly. This is simply because build releases already existed in the repository when we moved the apache contents of ibiblio back to Apache.
What is the status of jaxme in the incubator? When do they anticipate an official release?
Maybe this is a reason enough to push forward the development of the daily/weekly/... build repository. Allowing any more build-releasing in the dist/java-repository is a sensitive issue when it comes to mirroring. It would be wise for us to stop doing this asap. This is probably a good location where I could use assistance from repository folks in working out these details.
-Mark
robert burrell donkin wrote:
hi mark
the release in question was made whilst jaxme was in the incubator. AIUI it's an important requirement that it's clear that these are not official ASF releases but incubation releases. the most direct way to do this seemed (to me) to be continue to use the naming convention used by incubation releases.
- robert
On 11 Mar 2004, at 00:18, Mark R. Diggory wrote:
Robert, the jars are there, we should probably do a little renaming. My fault for not looking yesterday.
http://www.ibiblio.org/maven/apache-jaxme/jars/ !!!!!!!!!! http://www.ibiblio.org/maven/apache-jaxme/jars/jaxme-incubation-0.2.jar
we should probably have it more simply be
http://www.ibiblio.org/maven/jaxme/jars/jaxme-0.2.jar http://www.ibiblio.org/maven/jaxme/jars/jaxme-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-0.2.jar http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-0.2.jar http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-0.2.jar http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-0.2.jar http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-0.2.jar http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-SNAPSHOT.jar
-Mark
robert burrell donkin wrote:
hi mark
i can see the jaxme jars on apache but not in the maven repository on ibiblio. is there anything else i need to do to push the content over there?
(or have i just make some mistake in the upload...)
- robert
On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
robert burrell donkin wrote:
hi mark
i've given it a go myself but i have a few questions and i'd appreciate it if you'd check my work so far.
On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
You need to establish what your groups id will be. The current naming trend for Apache "xml" projects has been a bit haphazard.
xercies xml-security xml-resolver xalan
Some standardization here would be good. But that will not effect maven.
i've had a chat on IRC and gone for apache-jaxme
There is currently a problem with Maven publishing to a BSD system and md5 signature generation, if you do not want to use maven to do the publishing then these are the tasks you need to complete:
1.) The easiest way right now is for you to place the jars into
java-repository/xml-jaxme/jars/...
gone (but apache-jaxme rather than xml-jaxme)
2.) Generate an md5 signature for each one in the same directory. For instance as an examples
"md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
done
3.) Generate the following symlinks the above files from
java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
done
4.) and create a file
java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the contents "1.0"
these releases are versioned 0.2: should this file contain 0.2 (since it refers to the version of the jars) or 1.0 (since it's a mavenesque version number)
It would be wise, so yes, apache-jaxme-0.2.jar
5.) use the following "POM" in the
java-repository/xml-jaxme/poms/project/pom <project> <pomVersion>3</pomVersion> <id>xml-jaxme</id> <name>xml-jaxme</name> <currentVersion>1.0</currentVersion> <organization> <name>Apache Software Foundation</name> <url>www.apache.org</url> </organization> <licenses> <license> <name>ASL 2.0</name> <url>???????</url> <comments>???????</comments> </license> </licenses> </project>
there are a number of jar in the release. i'd been working on the theory that each needs a separate artifact id. what should the contents of the file be in this case?
- robert
Yes, it should look like:
/java-repository/apache-jaxme/jars/<artifact>-<version>.jar
/java-repository/apache-jaxme/poms/project/pom
<project> <pomVersion>3</pomVersion> <groupId>apache-jaxme</groupId> <name>Apache Jaxme</name> <currentVersion>0.2</currentVersion> <organization> <name>Apache Software Foundation</name> <url>www.apache.org</url> </organization> <licenses> <license> <name>ASL 2.0</name> <url>http://www.apache.org/licenses/LICENSE-2.0</url> </license> </licenses> </project>
sound good, I'll take a look in the directory and verify all looks well.
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
