The bug is back already. I added a couple more Atlassian dependencies and
Artifactory is back to producing garbage again. I simply can't get Artifactory
to work any more.
On Thu, Dec 31, 2015 at 6:31 PM, David Hoffer <[email protected]> wrote:
> Okay this is really weird. I upgraded to 4.3.3 per the suggestion that I
> might have hit on a bug that was fixed but 4.3.3 has the same problem, it
> still creates garbage when it downloads from a perfectly good repo.
>
> Now a little about my upgrade, I have a standalone service so I followed
> the upgrade instructions where I replace the bin, tomcat & artifactory.war
> in the old install with the new files. So after this starts up and I see
> that it does not fix the bug I notice that Artifactory now has a lot of old
> remote repos (Admin | Repositories | Remote) that I had deleted a long time
> ago. (They did not show in the UI with the prior version.)
>
> The reason I had previously deleted some old ones was because of this same
> bug, I was told that newer versions of Artifactory don't support some
> public maven repositories that it used to support (if I recall they were
> maven repos hosted in svn or something like that). Well in any case the
> old repos are back now in the UI in this new version. So I suspect that
> although I had deleted them previously Artifactory was still 'using' them
> and that's why the bug persisted.
>
> So I now have re-deleted the old repos and now I'm not getting garbage
> anymore from the Atlassian repo. But just like last time I suspect the
> bug will come back because apparently Artifactory isn't really deleting
> anything. So I have no confidence the bug won't come back when I add
> another repo (or whatever is triggering this bug).
>
> Very strange behavior...have no confidence in the tool anymore.
>
>
>
>
> On Thu, Dec 31, 2015 at 9:41 AM, dave_p [via Artifactory] <
> [email protected]> wrote:
>
>> You might also want to take a look at this thread:
>>
>> http://forums.jfrog.org/Expected-a-folder-but-found-a-file-td7580656.html
>>
>> And double check all your remote repository URLs. (Assuming the
>> "libs-releases" repository is a virtual repository that includes one or
>> more cached repositories.)
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580686.html
>> To unsubscribe from Artifactory won't proxy artifacts anymore, click here
>> <http://forums.jfrog.org/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7580586&code=ZGhvZmZlcjZAZ21haWwuY29tfDc1ODA1ODZ8LTc0ODU5MzA3NQ==>
>> .
>> NAML
>> <http://forums.jfrog.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
--
View this message in context:
http://forums.jfrog.org/Artifactory-won-t-proxy-artifacts-anymore-tp7580586p7580688.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
