[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

  • From: Wade Chandler < >
  • To:
  • Cc: Matthias Bläsing < >
  • Subject: [nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated
  • Date: Thu, 10 Jan 2013 15:14:22 -0500

On 01/10/2013 01:19 PM, Matthias Bläsing wrote:
Hey,

Am Donnerstag, den 10.01.2013, 06:28 +0100 schrieb Benno Markiewicz:
You could upload the versions as separate plugins with different
names. But I think you should only support  7.2.1, because it is a
recommended bugfix release to 7.2.
are you serious? At the end I will create a new version for each update
version of netbeans ... Sorry but that is not even a work around.

Don't take me wrong, the idea is creative, but not a solution (and this
would only clutter the plugin portal).
Hmmm...whether something is *even a workaround* or a *solution* or not depends on the reason and reasoning and what you can and can't do.

You are the one who coded your code based on impl deps. Do you need them? If not, then why are you using impl deps instead of spec deps? If you require impl deps, then of course this is a solution, and probably the only one you have.

If you don't require impl deps, and spec deps will work for you, then you should be using those. You should also use the spec version from 7.2 and tell the module system you want it greater than or equal to some spec version and module version:
http://bits.netbeans.org/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/api.html

If the SwingX and JAX-WS modules require impl access, then I would think you would need to have your own copies of those libraries in your module not exported as public APIs versus trying to reuse the ones in the IDE; if that is in fact what you are doing and is the problem you were trying to overcome. If Issue Tracking requires friend access or an impl dep, then to me the question is why? And that is something you could indeed ask the NB devs, and to me would be perfectly reasonable to ask; if that is indeed the case.

This is the problem with too many friend only lists for things to not have an impl deps. Impl deps and friend lists make NB more closed if you ask me. Essentially the NB team can get their work done, others can't *really* extend the IDE to support new technologies, not without first getting some patches into the codebase etc, and it generally can make life harder for those trying to use the NB platform or IDE to extend it or build something with it. So, in that lies one issue.

Either way, this is entirely different than whether or not you specifically require impl deps for your module? Is this in fact true or not?

At least for swingx the implementation version did not need to be bumped
(exposes the same version of swingx...) and I suspect this is the case
also for the other modules. Big question: Why aren't they just pushed
out to the users, than there would be no problem ... (maybe even by
bumping the specification version - not sure what enforces an update)

Are you writing for the netbeans developer team?

Not sure your question is for the NB team is it? Were you specifically requesting someone specific answer your question? Seems someone was trying to answer your question, but you don't understand enough about module dependencies to understand the answer, or you were not offering them the same kind of courtesy they were affording you by spending their time and life giving you some truthful advice, and did not give enough prior information related to your use of impl deps.

If you want a general place to ask questions about APIs, extending the IDE, or using the RCP platform, then is the place to ask. nbdev is mainly for NB development communication (actually developing the IDE or the platform), or if you really have an issue with an NB API or some NetBeans code or why perhaps some module can only truly be used to add functionality to the IDE by way of impl deps or being on some closed friend list (can be quite irritating); but in the case of most issues, one should really file an issue in BugZilla.

Wade

--

=================
Wade Chandler

Software Engineer and Consultant
NetBeans Contributor
NetBeans Dream Team Member

wadechandler.com
netbeans.org



[nbdev] Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Matthias Bläsing 01/09/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Benno Markiewicz 01/10/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Matthias Bläsing 01/10/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Benno Markiewicz 01/10/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Ernie Rael 01/10/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Wade Chandler 01/10/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Wade Chandler 01/10/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Matthias Bläsing 01/14/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Matthias Bläsing 01/14/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Geertjan Wielenga 01/21/2013

[nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated

Matthias Bläsing 01/21/2013

Project Features

About this Project

www was started in November 2009, is owned by jpirek, and has 21 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20131025.e7cbc9d). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close