Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 61751 - [Module Properties] removed dependency after change Platform
[Module Properties] removed dependency after change Platform
Status: NEW
Product: apisupport
Classification: Unclassified
Component: Project
All All
: P3 (vote)
Assigned To: Martin Kozeny
: UI
Depends on:
  Show dependency treegraph
Reported: 2005-08-03 13:34 UTC by pzajac
Modified: 2013-02-14 13:17 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description pzajac 2005-08-03 13:34:31 UTC
There are installed Platform1 and Platform2 in NB platform manager. 
The Platform1 contains module A. The Platform2 doesn't contain module B. 

1)Show project's properties for standalon module
2)Change the platform to Platform1
3)Add module A to classpath
4)Change the platform to Platfrom2 (in platforms combobox)

The module A is removed from classpath. There is better to show dialog that the
Platform2 doesn't contain module A and ask user if he really want to change
Comment 1 Martin Krauskopf 2005-09-08 14:29:13 UTC
Agree, would be nice to have. Probably not for 5.0. We should show at least
information dialog. BTW user can always press Cancel.
Comment 2 Jesse Glick 2005-09-08 18:29:45 UTC
User will also get an error message when he next tries to build, so the problem
won't go unnoticed for long.
Comment 3 Martin Krauskopf 2006-02-01 09:37:00 UTC
I feel that this one somehow clashes with issue 70917. So any temporary solution
to this issue would just bring confusion dependeing on that issue. So I'll
eventually implement this one after 70917 is fixed. Feel free to comment.
Comment 4 Jesse Glick 2006-02-01 15:03:49 UTC
I don't think this has anything to do with issue #70917. That issue is simply
about picking the right specification (and perhaps major) version for an
existing dependency.

This issue is about whether a module exists or not. Independently of #70917,
this looks like a UI bug to me; changing the platform by itself should not
result in changes to the list of module deps. However it is one of those things
that would be best solved with a general problem notification & resolution UI.
Comment 5 Martin Krauskopf 2006-02-01 15:42:25 UTC
> This issue is about whether a module exists or not.

Umm, yes. I though about different scenario, sorry.
Comment 6 Martin Krauskopf 2008-02-07 17:49:05 UTC
I'm not working on APISupport anymore. Reassigning to owner of the component, so
the issue is not 'forgotten' forever.

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo