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

  • From: Matthias Bläsing < >
  • To:
  • Subject: [nbdev] Re: Upgrade 7.2 -> 7.2.1: Seems modules were changed (implementation version changed) but modules are not updated
  • Date: Mon, 14 Jan 2013 14:34:35 +0100

Hey,

most important think first: I didn't want to insult anyone. If this
seemed different I apologize - it's just frustrating to fight against
unnecessary problems. In turn I'll ignore the parts that I took as such.

Am Donnerstag, den 10.01.2013, 15:14 -0500 schrieb Wade Chandler:
> On 01/10/2013 01:19 PM, Matthias Bläsing wrote:
> > Am Donnerstag, den 10.01.2013, 06:28 +0100 schrieb Benno Markiewicz:
> >>  [Idea: create a plugin only for 7.2.1 or 7.2]
>> [My diagnosis: not an option]
>
> [Reply: - It depends on the perspective what is a solution/workaround
>         - Discussion that I should not use implementation dependencies]
> 

I know that implementation dependencies are and I know I should use them 
with care. In this case I could not work around it:

- Issue Tracker SPI and core classes are only accessible to friends (I 
  checked that I only used exported classes
- JAX-WS dependency: Axis tried to load a class (if I remember correctly 
  it was some mime support) via the system class loader - resulting in an
  error if the class could be loaded from multiple modules (this gets ugly!)
- SwingX I already needed implementation dependencies - so this didn't make
  the situation worse

> 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;

As pointed out above - this is not as easy as it sounds.

> 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.
> 
> [Discussion that to many friend-only APIs in netbeans hinder extension
> development]

Yes to implement an issue tracking plugin (or an api user) you need at
least friend access. And yes - this gets annoying very quickly. I can
understand it in a way (=> the api seems to be in flux - the SPI for 7.3
requires one more feature than the 7.2), but it doesn't make it easier
to create a bugtracker module.

Greetings

Matthias

PS: I'm subscribed to nbdev, so no need to keep me in CC



[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 20140418.2d69abc). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close