[Stuart Schmukler]

I have a complex legency project with multiple C and java targets.

I set my java build source path to include “java/” and exclude “c/“.
This generates messages about incorrect package paths and causes problems with refactoring.
Meaning: “The declared package does not match the expected package java.src.com….”. (Full package tree edited for the client’s protection. 😥 )

To get rid of the messages about incorrect I switched the java build source path to “java/src/” .
Which causes the “java/src” tree to disappear int the package explorer.

Stuart

System Setup ——————————-
Operating System and version: Linux Redhat AS3.0
Eclipse version: 3.1.2
Eclipse build id: M200060118-1600
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: none.
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8 including org.eclipse.pde
MyEclipse version: 4.1.1
Eclipse JDK version: SUN 1.5.0
Application Server JDK version: SUN 1.5.0
Are there any exceptions in the Eclipse log file? Yes :

!ENTRY org.eclipse.core.resources 4 368 2006-06-06 19:17:29.256
!MESSAGE Resource /ua/java/_build.xml does not exist.

!ENTRY org.eclipse.update.configurator 2006-06-06 19:26:36.800
!MESSAGE Can’t find bundle for base name feature, locale en_US

If this is a DB related question please answer the following: Not a DBMS problem.

RDBMS vendor and version:
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:

– Message Body ——————————-

[Stuart Schmukler]

Sorry folks,

The patterns I tried were “java/”, “java/src/*”, “java/src/**”, “java/src/**/*.java” all had problems.

Fixed the problem by using the include “java/src” !!!

Stuart

[Author]

Posts