Hi,I'm trying to get the snapshot process working as closely to the new release process as possible. From what I can tell, mvn release:prepare is really oriented towards releases, not towards snapshots. Does anyone know of an equivalent snapshot target that we could use?
-Patrick On Jul 16, 2008, at 7:06 AM, Kevin Sutter wrote:
Sounds good, Patrick. So, in the mean time, should I make a temporaryrepository for the "latest" docs? Or, if you think this will get resolvedin the next day or two, then I could just wait. Thanks, KevinOn Tue, Jul 15, 2008 at 6:40 PM, Patrick Linskey <[EMAIL PROTECTED]> wrote:Hi, I think that this is because the machine that builds and uploads thesnapshots was offline for the last couple of months. I got that partially back up and running last week, and hope to get the snapshots uploading againlater this week. -Patrick On Jul 15, 2008, at 5:30 PM, Kevin Sutter wrote: Hi,I just noticed that our links for the "latest" OpenJPA documentation isoutof date (http://cwiki.apache.org/openjpa/documentation.html). I wouldexpect that our "latest" link should point at some version of documentationassociated with trunk. But, it's currently pointing at some version based on the 1.1.0 build. I was going to go ahead and clean this up, but itlooks like I don't have proper authority to the /www/openjpa.apache.org/docs/latest directory. It looks like Patrick is theonly one with enough authority. This "latest" directory is currently linked to this: latest -> ../builds/1.1.0/apache-openjpa-1.1.0/docs/ So, I'm thinking a few things need to be done:o It would be great to post our current nightly drivers and documentation out on people.apache.org from our TC system. (BTW, it looks like our nightly drivers page is still pointing at the 1.1.0 SNAPSHOT builds, so wehave some clean up there as well.) I'm not sure on the status of Patrick'sTC system and whether we are able to get something like this setup or not.o If we can post our nightly drivers and documentation, then we couldchange this "latest" directory link to our upload location for the drivers.o If this type of clean up and setup of nightly drivers is going to take some time, then at a minimum, it would be good to change the permissionsonthis "latest" directory so that we could do some manual (pardon the pun)cleanup.BTW, all of this came about because I had pointed a user at our "latest" manual to find out how to turn on the Query SQL Cache support (knowing it was part of the 1.2.0 trunk release). But, I soon discovered that our"latest" manual is quite out of date... :-) Thanks, Kevin-- Patrick Linskey 202 669 5907
-- Patrick Linskey 202 669 5907
smime.p7s
Description: S/MIME cryptographic signature
