topic Re: Activiti Maven repo moved in Alfresco Archive

Activiti Maven repo moved

trademak — Wed, 16 May 2012 12:32:36 GMT

Hi all,The Activiti Maven repo has changed to:maven.alfresco.com/nexus/content/groups/publicLet us know if you run into problems.Thanks,

Re: Activiti Maven repo moved

rogerofyan — Thu, 17 May 2012 08:11:15 GMT

Thanks for the remind, but I suggest update the page content of http://activiti.org/community.html so that it's easier for others to find this information.

Re: Activiti Maven repo moved

trademak — Thu, 17 May 2012 13:56:19 GMT

I did change the community page, but doesn't seem to get pushed to our web server.
I'll see if I can fix this somehow.

Thanks,

Re: Activiti Maven repo moved

heymjo — Thu, 14 Jun 2012 06:00:31 GMT

FYI there is still a reference to the old repo in engine/pom.xml (which BTW still seems to work)


  <repositories>
    <repository>
      <id>activiti</id>
      <name>Activiti</name>
      <url>http://maven.alfresco.com/nexus/content/repositories/activiti/</url>
    </repository>
  </repositories>

Re: Activiti Maven repo moved

anshumanpurohit — Fri, 21 Sep 2012 23:42:32 GMT

I am not able to proxy to this repository via my internal nexus. Do you require a client certificate? If yes, will a self signed client certificate be sufficient?

Thanks,
Anshuman

Re: Activiti Maven repo moved

ronald_van_kuij — Sat, 22 Sep 2012 11:11:55 GMT

We proxy to this from our internal nexus. No certificate or whatever needed…

Re: Activiti Maven repo moved

anshumanpurohit — Thu, 08 Nov 2012 20:07:29 GMT

I am using http://maven.alfresco.com/nexus/content/groups/public/ as the Remote Storage Location. Nexus repository status stays as "Remote Automatically Blocked and Unavailable". I have expired cache, and Repaired Index but with no avail.

BTW, this url gets redirected to https counter part. I have tried with https in the Remote Storage Location as well.

Please help!

Re: Activiti Maven repo moved

heshamsaleh — Wed, 24 Apr 2013 14:19:30 GMT

We also faced similar "Remote Automatically Blocked and Unavailable" trouble, yet using https instead got us working again (of course, don't forget to right click -> Allow Proxy) on the repository.