Discussions
Categories
- 385.5K All Categories
- 4.9K Data
- 2.5K Big Data Appliance
- 2.4K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 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
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 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.