Tim,

I just had a chance to look at the repository link you included, and it
appears that all of the old API versions are indeed gone.  I doubt there
will be much chance of recreating them.



On Sun, Feb 24, 2013 at 4:05 PM, Jim Gomes <e.se...@gmail.com> wrote:

> Excellent. Thanks, Tim. I'll follow up with Hiram to see if we can get
> this squared away.
> On Feb 24, 2013 3:32 PM, "Timothy Bish" <tabish...@gmail.com> wrote:
>
>> On 02/24/2013 05:56 PM, Jim Gomes wrote:
>>
>>> Hi pwalter
>>>
>>> Thanks for your inquiry. I have not had a opportunity to solve this
>>> problem
>>> yet. If you are in immediate need of reference documentation, it is
>>> possible to generate them from the source code yourself.  It appears that
>>> the files were moved or deleted from the server. If they were deleted, it
>>> may take quite a while to regenerate all of the old versions, and I
>>> doubt I
>>> would put my time into doing all the old versions.
>>>
>>> Best,
>>> Jim
>>> On Feb 24, 2013 2:05 PM, "pwalter" <patrick.wal...@nasa.gov> wrote:
>>>
>>
>> It looks like the content isn't lost, at least I think its all there in
>> svn now:
>> https://svn.apache.org/repos/**asf/activemq/site/nms/ndoc<https://svn.apache.org/repos/asf/activemq/site/nms/ndoc>
>>
>> I'd guess that when Hiram migrated the site to svn pub style that
>> something didn't quite go right in the NMS part of the site publishing.
>>  Maybe bug Hiram and see if its an easy fix.
>>
>>  ANY IDEA WHY THE NMS LINKS ARE STILL NOT AVAILABLE??
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://activemq.2283324.n4.**nabble.com/ActiveMQ-NMS-API-**
>>>> Location-tp4663581p4663989.**html<http://activemq.2283324.n4.nabble.com/ActiveMQ-NMS-API-Location-tp4663581p4663989.html>
>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
>>>>
>>
>> --
>> Tim Bish
>> Sr Software Engineer | RedHat Inc.
>> tim.b...@redhat.com | www.fusesource.com | www.redhat.com
>> skype: tabish121 | twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>>

Reply via email to