End of an era (for me): Oracle SCM State of Direction

Lucas Jellema 2
0 0
Read Time:1 Minute, 0 Second

It does not come as a great surprise, yet I feel sad. Oracle’s Statement of Direction on Oracle SCM declares the product ‘dead as a dodo’. Well, not quite. No new features will be added, yet the tool will be supported for a long time to come, along with Designer 10g (that depends on Oracle SCM). So if you do Designer development, Oracle SCM is still your (only viable) option for doing version control. However, do not plan on setting up full blown Software Configuration Management for your source files based on Oracle SCM. Instead, go to CVS.

I spent almost 3 years on Oracle SCM and its predecessors, including the infamous Oracle Echo (pka Echo/2000) toolset. I sort of said goodbye to it some three years ago, but it was an interesting time and the contacts will the developers at Oracle’s Thames Valley Park development center rank among the highlights of my time at Oracle. However, having said all that, it is probably a good thing that Oracle provides clarity. There have been so many plans (hosted SCM, web based Oracle Designer – remember Prodigy?? – etc.) that all came to nothing. Now we know where we stand on Oracle SCM.

About Post Author

Lucas Jellema

Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director and Oracle Developer Champion. Solution architect and developer on diverse areas including SQL, JavaScript, Kubernetes & Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press book Oracle SOA Suite 12c Handbook. Frequent presenter on user groups and community events and conferences such as JavaOne, Oracle Code, CodeOne, NLJUG JFall and Oracle OpenWorld.
Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %

Average Rating

5 Star
0%
4 Star
0%
3 Star
0%
2 Star
0%
1 Star
0%

2 thoughts on “End of an era (for me): Oracle SCM State of Direction

  1. Maybe we should think on a way to migrate files controlled in Oracle SCM away to Subversion (or CVS), while maintaining meta-data such as version labels, check in dates and notes and release labels. I am not sure how many people would be interested, but those who need to make the move will be very grateful I’d say.

Comments are closed.

Next Post

Logging quickstart: Log4j and Jakarta Commons logging

Jakarta Commons logging is a wrapper around Log4j (Log4jLogger), the Java native logging system(Jdk14Logger) and the built-in fall-back logger SimpleLog. Depending on which one is on the classpath, that logging system is addressed transparently via the easy-to-learn commons logging API. Recipe: Related posts: Enabling Role-based security management in Oracle Designer […]
%d bloggers like this: