Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle ADF Enterprise Application Development Made Simple: Second Edition

You're reading from   Oracle ADF Enterprise Application Development Made Simple: Second Edition

Arrow left icon
Product type Paperback
Published in Feb 2014
Publisher
ISBN-13 9781782176800
Length 432 pages
Edition Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Sten E Vesterli Sten E Vesterli
Author Profile Icon Sten E Vesterli
Sten E Vesterli
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Oracle ADF Enterprise Application Development – Made Simple Second Edition
Credits
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
1. The ADF Proof of Concept 2. Estimating the Effort FREE CHAPTER 3. Getting Organized 4. Productive Teamwork 5. Preparing to Build 6. Building the Enterprise Application 7. Testing Your Application 8. Changing the Appearance 9. Customizing Functionality 10. Securing Your ADF Application 11. Packaging and Delivery Internationalization Index

Avoiding conflicts


It takes time to resolve conflicts, so you should make an effort to avoid them. There are both soft and hard methods that you can use for this. The soft methods are procedural (ways in which you agree to work in your team), and the hard methods are technical; they are implemented using the capabilities of your version control tool.

The first soft method is to take the approach recommended in the previous chapter and split your application into a number of separate workspaces connected via ADF Libraries. If you do this, you have already reduced the risk of version conflicts significantly.

The second soft method you can use is to assign owners to the files that are often the source of version conflicts. If you decide that only Bob, the lead programmer, is allowed to commit changes to the two files that the whole team keeps fighting over, he can keep the purpose and entire structure clear in his mind. If anybody else needs to make a change, they can tell Bob and let him make...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime