Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 545 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 440 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
reference a project in a different workspace?

618893
Member Posts: 138
Is it possible to reference a project in a different workspace (aka application)?
Or are you restricted only to the projects in the same workspace?
Or are you restricted only to the projects in the same workspace?
Tagged:
Answers
-
I'm not quite sure what you mean by "reference." If it's just a matter of coding against the classes you've developed in another workspace, you certainly can--even if you don't want to deploy the project as a library. Just set your current project's "additional classpath" to include the "classes" directory of the project you want to use.
Even if, say, you want to use business components from the other project, you can "import" the other project's business components (select the business component package XML file to import them).
If you want to do something fancy, like actually ensure the other project gets rebuilt every time one of your projects gets rebuilt, then I think the only way to go is to add the project to the current workspace. (A project can be in more than one workspace; just "add to workspace" and browse to the other project's jpr file.) I'm not terribly sure I recommend this except in extremis, though--if a project is open in two workspaces, dealing with, e.g., whose job it is to actually change files in it can be difficult.
This discussion has been closed.