It's absolutely a good idea to set up source control as well as Artifactory. The modules you store in Artifactory have to be built from some kind of source code, and Git/Hg/SVN provide storage, history, and collaboration for the source code. Artifactory is only intended for storing the output of the compile/test process (JARs, WARs, etc.). If you don't version-control your source code, you'll have a chaotic development process and never-ending bug-fixes. Artifactory isn't intended or suitable for storing source code, except maybe as a dump of source for debugging by people who for some reason can't access your original source code server.
If you're not sure what to do, the best idea is to find someone who *has* set up and managed a source control server before!
It's also a good idea, I think, to include something in your JARs etc. which points back to the exact version of source code from which it was built, e.g., as an entry in the MANIFEST.MF, but that's another story.
Hope that helps,
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: Re-Calcitrant [mailto:[hidden email]]
> Sent: 13 February 2014 12:17
> To: [hidden email] > Subject: [Artifactory-users] Source Control - Confused
> Can anyone advise a Novice attempting to set up a development environment
> for the development of Java EAP Projects as to whether it is necessary,
> advantageous, or required to also use a Source Control System such as GIT or
> SVN in addition to the Artifactory Reposity (OSS) I have setup. I am
> utterly confused. Background - I have setup Amazon ECE2 instances comprised
> of an RHEL6.4 / Apache Reverse (HTTPS) Proxy and a separate instance
> (Bitnami Image) of Artifactory. I have all of the Redhat Java EAP Enterprise
> Artifacts required for development of Redhat supported EAP Projects. Im in
> the process of configuring Jenkins Integration via the CloudBees Platform.
> Production release software will likely run on RedHat's OpenShift platform.
> Would also appreciate any comments on the strategy that anyone may have,
> View this message in context: http://forums.jfrog.org/Source-Control- > Confused-tp7579612.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience. Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&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 ______________________________________________________________________