NetBeans Forums
| View previous topic :: View next topic |
| Author |
Message |
Jesse Glick
Posted via mailing list.
|
 Posted: Thu Dec 15, 2011 8:27 pm Post subject: Re: Transitivity of incompatible change was: Range terminology is not suitable for versioning |
 |
|
On 12/15/2011 02:46 PM, Jaroslav Tulach wrote:
| Quote: | It depends on whether the libs.javacimpl is re-exported or not. If not, then
this restriction is not necessary.
|
But what about the case that types from a dependency B appear in public signatures of A, yet the incompatible change in B has no impact on users of A unless they were
independently using that part of B?
For example, it would be nice to get rid of FileObject.getPackageName [1] which probably no one still uses. To do so properly would mean pushing org.openide.filesystems
to 8.0. org.netbeans.modules.projectapi depends on this module and refers to this class, e.g. in Project.getProjectDirectory. But there is no incompatible change in
projectapi per se, so we do not want to have to push it to 2.0.
Again I would like to know why we are concerned about a problem that can only affect systems which do something that NetBeans does not do - search for an earlier version
of a module that might satisfy constraints better than the newest version. The module system could not do this even if we wanted it to, since a config/Modules/*.xml
refers to one and only one JAR; we would have to invent a new storage layer (a repository) to do otherwise. The Ant harness refers to whatever version of a dependency is
in your target platform or suite; the Maven plugin refers to whatever version you specified in your POM. Plugin Manager could in principle try to select a subset of
modules to update that would result in a consistent state, but this would contradict the purpose of #Handling_possibly_broken_dependencies - assuming all dependencies are
either satisfied or only violated on the high end of a range, you want to download all updates and then just check for actual problems on next startup. (If some are
violated on the low end, simply refuse the update - this would normally mean you are using the wrong update center.)
[1] http://wiki.netbeans.org/ThingsToDeprecateAndPlanToDelete#Filesystems |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
