Now I need to figure on the layout. I wish I can just say, "no layout". What do people use for release repos? My release repo is going to have all sorts of stuff in it, .NET code, java (android), Object C, etc.
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: Jordo [mailto:[hidden email]]
> Sent: 12 March 2014 14:31
> To: [hidden email] > Subject: Re: [Artifactory-users] How to .NET in Artifactory?
> Great thank you!
> I was able to get the NuGet stuff to work.
> Now I need to figure on the layout. I wish I can just say, "no layout".
> What do people use for release repos? My release repo is going to have all
> sorts of stuff in it, .NET code, java (android), Object C, etc.
> View this message in context: http://forums.jfrog.org/How-to-NET-in- > Artifactory-tp7579689p7579701.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
> Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the
> definitive new guide to graph databases and their applications. Written by
> three acclaimed leaders in the field, this first edition is now available.
> Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech > _______________________________________________
> 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 ______________________________________________________________________
These features ony only work when artifactory knows the version of an artefact.
Artifactory only knows the version of an artefact if it is able to parse it from the repository path used to deploy the artifact.
If you are not planning to use features that rely on the Module Fields in the link Hugh posted, you can completely ignore the repository layout. An upload will still work (at least directly via the API) if you do not follow the repository layout.
I think I finally understand what the value of repo layouts are, thank you!
This whole time I thought it was how Artifactory automatically stores the artifacts but its not that at all. It is a "map legend" and how artifactory extrapolates useful information from the paths and names of the artifacts them selves.