We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Ability to use path map variable or classpath of the project with the Java visualization.
UML models (*.emx-files) and class diagrams (*.dnx-files) should be independent from the project in which they were created. Using Path map variable or the classpath of the current project to resolve Java types could help to achieve this.
1. Different project names for the same project in different versions
One project can exist with different names in an Eclipse workspace,
because there are different versions of the project.
2. Models are stored in a shared directory in order to be available for
Projects save their models in a directory, that is visible for every
other project. They make their Java classes available for other
projects by jar files.
If a member of project B wants to inform himself about project A by
looking at models of project A, the Java classes of project A are not
displayed correctly, if project A is not opened in his workspace.
If the RSD would search for the Java classes in the classpath of
project B, the RSD would find the classes, since the classes exist in
the project_A.jar in project B.
3. Projects export their *.dnx class diagrams and their Java classes in
jar files and make them available for other projects
Unfortunately the result is the same as above. A developer of project
B with project_A.jar opens the class diagram in the project_A.jar and
the Java classes are not displayed correctly. This is even less
understandable, since the Java classes are located in the same jar as
the class diagram. Unfortunately the RSD looks for the Java classes,
that are referenced in the class diagram, with the project name and
finds them only if incidentally project B is opened in the same
workspace as project A.
These three examples show that searching for Java classes in models via
the project name, in which the model was created, doesn´t take us further.
The problems described above could be avoided, if the Java classes, referenced in a model, were not only searched in the project, where they were created, but as well in the class path of the current project.
Do not place IBM confidential, company confidential, or personal information into any field.