Compilation errors not displaying in Message Log after compiling DB packages ...

This link has some details http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r2/prod/appdev/sqldev/plsql_debug/plsql_debug_otn.htm#t…

I was thinking that you might find something like this.

http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r2/prod/appdev/sqldev/plsql_debug/images/crproc09a.gif

It seems that 4.1.5 (for the rest of us) yields the following for such a test case...

1. In the Messages tab: Compiled (with errors)

2. In the Compiler tab: something similar to the gif shown by the other poster's link above

In situations where SQL Developer does not do what it is supposed to in a specific environment, you can test if any of the following help:

1. Window > Reset Windows To Factory Settings

2. Tools > Features... > Clear Cache

3. Finally, if neither of those work, delete (or rename) the system_cache folder. You can find that under

C:\Users\<youruser>\AppData\Roaming\SQL Developer\system4.1.5.21.78

I hope one of those works for you.

What happen if you go to view > log?

Ouch...  I was hoping it was just the system_cache.  Sometimes it gets out of synch with user settings, whether exposed to the user via preferences or just other internally maintained things. 

In that case, two other recommendations...

1. If you want to debug a bit...

    a) In your sqldeveloper.conf file, remove "non" from IncludeConfFile  sqldeveloper-nondebug.conf

    b) Run sqldeveloper.exe from a console window opened on ...\sqldeveloper\sqldeveloper\bin

   c) See if any messages appear in the console, or in any of the Log tabs.

2. Otherwise I imagine that deleting or renaming the system4.1.5.21.78 folder will do the trick.

Just remember to export your connections first if you delete it.

are you in a sql worksheet or a code (plsql) editor?

if in a sql worksheet, you have to add a Show Errors to your script and 'compile' via F5

I'm not sure exactly how you are compiling your code

just making sure you're not running into this

http://www.thatjeffsmith.com/archive/2012/01/viewing-plsql-compilation-errors-in-oracle-sql-developer/

In your first post, you said,

When I open my package files from the file system and compile them in the DB

which is consistent with the setting

Tools > Preferences > Code Editor > Link Stored Procedures to Files

This all works for me for *.pks and *.pkb files opened from the file system on Windows 7, SQL Developer 4.1.5.21.78 (and all the other releases 4x production releases, too) with jdk1.8.0_102.  You never said you were not using Windows, so I assume yours is a WIndows environment.

Anyway, after having followed my advice to address all the "usual" suspects in the user settings, if this still does not work, then the final suggesion is to begin again with a completely clean install:

1. Download 4.1.5 again

2. Remove the system4.1.5.21.78 folder

3. Follow the instructions to unzip into an empty directory

4. When ask whether to migrate setting from any prior SQL Developer install, skip the migration.

I just created a brand new package, and followed the instructions from Jeff Smith in the above referenced link about creating packages as File, New, Database Objects, Packages, and I still can't get the compiler log to show up when I create files for these packages and re-open the files to code and compile.

SHOW US:

1. WHAT you do

2. HOW you do it

3. WHAT results you get

I'm already on my second install of this version of SQL Developer. 

OK, but you never said if you skipped the user settings migration on the second install.  Did you?

If this problem only occurs for 4.1.5 in your environment with other versions working fine, and other users have no issues with 4.1.5 in this area, then corruption of user settings is really the only suspect.

I think I'm going to re-install the old version I had (Version 3.xx) which was working just fine.

You never had to de-install it. Multiple installations on the same machine are supported. So reverting is a reasonable plan if you can eliminate user settings corruption as the cause.  You also never said if you tried my debugging advice -- error messages, if any, appearing in that scenario could be of help in knowing what has gone wrong in your environment.