We intend using Artifactory for organizing mainly C++ .libs and .exes.
We do not want to switch to NuGet right away since this would be a major change to our build processes.
Is there any best practice how to organize a repository in such a situation?
We are thinking of creating zip files as package replacement and uploading them to Artifactory.
At the moment we are using the standard maven2 layout.
not official advice in any way (neither on behalf of JFrog or of my own employer), but you might want to have a look at these Gradle plugins: https://bitbucket.org/nm2501/holy-gradle-plugins. In particular, the intrepid plugin handles downloading ZIPs, unzipping them into (a custom subfolder of) your GRADLE_USER_HOME, and creating a symlink in your Gradle project workspace. They're not perfect, and not commercially supported, though.
Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
http://www.tmvse.com / mailto:[hidden email]
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.
> -----Original Message-----
> From: pscheir [mailto:[hidden email]]
> Sent: 11 September 2013 07:09
> To: [hidden email] > Subject: [Artifactory-users] Best repository layout for c++
> We intend using Artifactory for organizing mainly C++ .libs and .exes.
> We do not want to switch to NuGet right away since this would be a major
> change to our build processes.
> Is there any best practice how to organize a repository in such a situation?
> We are thinking of creating zip files as package replacement and uploading
> them to Artifactory.
> At the moment we are using the standard maven2 layout.
> Thank you, Peter
> View this message in context: http://forums.jfrog.org/Best-repository- > layout-for-c-tp7579089.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT 2.
> Standardize and globalize service processes across IT 3. Implement zero-
> touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk > _______________________________________________
> Artifactory-users mailing list
> [hidden email] > https://lists.sourceforge.net/lists/listinfo/artifactory-users >
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com > ______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________