"Strict modularity" feedback

[Enrique Rodriguez <en...@gmail.com>]

I hit the "strict modularity" issues updating Apache Directory to Felix 
tonight.  I found the overall issues to be no worse than troubleshooting 
any other OSGi dependency issues.  The error messages were really great 
to have and I think they'll help newbies a lot.

I had to add:

  javax.naming, \
  javax.naming.spi, \
  javax.naming.directory, \
  javax.naming.ldap, \
  javax.security.auth.kerberos

to our config.properties.

Enrique

Re: "Strict modularity" feedback

["Richard S. Hall" <he...@ungoverned.org>]

Sounds good. At least we are building up our experience to get a feel 
for how much we are impacted by strict modularity. Hopefully, it will 
stay positive.

-> richard

Enrique Rodriguez wrote:
> Richard S. Hall wrote:
> ...
>> The question I have is, were you able to determine why you needed 
>> these packages? Were they packages you were using and didn't include 
>> or were they from methods used on parent classes or what?
>
> I think in most of the cases I just needed to include system packages. 
> Maybe 1-2 cases were methods on parent classes.  I know in a couple 
> cases I had to intuit that the issue was missing import statements, 
> based on the missing class and my knowledge of our class hierarchy. 
> Once again, mangen will be a big help here.  Also, all of our package 
> names changed in a big refactoring over the holidays, so this was more 
> than just a move from Oscar to Felix - I had a lot of import/export 
> statements busted.
>
> Enrique
>

Re: "Strict modularity" feedback

[Enrique Rodriguez <en...@gmail.com>]

Richard S. Hall wrote:
...
> The question I have is, were you able to determine why you needed these 
> packages? Were they packages you were using and didn't include or were 
> they from methods used on parent classes or what?

I think in most of the cases I just needed to include system packages. 
Maybe 1-2 cases were methods on parent classes.  I know in a couple 
cases I had to intuit that the issue was missing import statements, 
based on the missing class and my knowledge of our class hierarchy. 
Once again, mangen will be a big help here.  Also, all of our package 
names changed in a big refactoring over the holidays, so this was more 
than just a move from Oscar to Felix - I had a lot of import/export 
statements busted.

Enrique

Re: "Strict modularity" feedback

["Richard S. Hall" <he...@ungoverned.org>]

Excellent feedback Enrique.

I am glad that you were able to get it to work without much difficulty. 
I labored on the precise text of the diagnostic messages for a while, so 
I am happy that they were helpful. :-)

The question I have is, were you able to determine why you needed these 
packages? Were they packages you were using and didn't include or were 
they from methods used on parent classes or what?

-> richard

Enrique Rodriguez wrote:
> I hit the "strict modularity" issues updating Apache Directory to 
> Felix tonight.  I found the overall issues to be no worse than 
> troubleshooting any other OSGi dependency issues.  The error messages 
> were really great to have and I think they'll help newbies a lot.
>
> I had to add:
>
>  javax.naming, \
>  javax.naming.spi, \
>  javax.naming.directory, \
>  javax.naming.ldap, \
>  javax.security.auth.kerberos
>
> to our config.properties.
>
> Enrique
>