In a decently administered Linux environment you strictly separate users. For example user oracle
for the servers (database, application server and so on). All
developers should work on their own accounts (eg. my account would be olaf).
Under
the same assumptions I install all other software like JDeveloper, SQL
Developer, and so on in a central directory and all users can use it
(or leave it...).
Just installed the latest JDeveloper Studio 10.1.3.1.0 on a Linux system.
To my amazement some developers seem to read my blog. All the shell files I've mentioned in my last entry now have the execute permission (they are located in $JDEV/jdev/bin and the filenames are jdev, ojc, startoc4j, stopoc4j, and ojaudit).
« Using JDeveloper on Linux | Main | Migrating to OC4J: Leveraging the APP-INF directory »
Using JDeveloper on Linux, Part II
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on November 23, 2006 9:55 AM.
The previous post in this blog was Using JDeveloper on Linux.
The next post in this blog is Migrating to OC4J: Leveraging the APP-INF directory.
Many more can be found on the main index page or by looking through the archives.
Comments (2)
Many devs (including myself) on the jdev team are now using Linux for development instead of Windows... The linux install / run experience is getting a whole lot more attention than it used to as a result. Now if only we could put together an rpm... ;)
Posted by Brian Duff | November 26, 2006 9:23 PM
Posted on November 26, 2006 21:23
That's why. RPMs are fine, but for some reason I'd like to create my own directory structure.
Posted by Olaf Heimburger | November 27, 2006 3:17 AM
Posted on November 27, 2006 03:17