Joke of the day
What happened to me today. The OSGi Manifest file generator tool suddenly started inserting a dot in the import package. A dot? A dot. Does not make sense, who tells him to do that?
This way the bundle won't start on the OSGi container. Why does this happen? All other 4 projects with the very exact same configuration work fine. Two hours investigating the problem. In the end, I hacked the maven-bundle-plugin, discovered that is the underline tool, Bnd, that insert the dots, and hacked the maven-bundle-plugin to remove the dots. In the meantime, I asked the question on twitter.
@njbartlett answered me: "It can happen with classes produced by the Eclipse compiler that still have compile errors in them. "
"It's because you drank a capuccino too late this morning".
"Hey, have you called your mom today? That's why it does not work"
"Look out, there's too much sun, so Bnd insert the dot". These explanations to me make sense exacly like the one that has been provided by @njbartlett
The only difference is that he is right, that is exactly the problem that was affecting me. But why? Why in the world this happen? And why specifically with Eclipse?
You can say it's easy, you just make the build compile. Yes, but it continue not to make sense.
And I still lost two precious hours dealing with some completely insane behavior. That's bad.
This way the bundle won't start on the OSGi container. Why does this happen? All other 4 projects with the very exact same configuration work fine. Two hours investigating the problem. In the end, I hacked the maven-bundle-plugin, discovered that is the underline tool, Bnd, that insert the dots, and hacked the maven-bundle-plugin to remove the dots. In the meantime, I asked the question on twitter.
Why #bnd would ever put a dot in the beginning of the Import-Package? #osgi #maven
— Daniele Dellafiore (@ildella) May 19, 2011
@njbartlett answered me: "It can happen with classes produced by the Eclipse compiler that still have compile errors in them. "
Really? Really?@ildella It can happen with classes produced by the Eclipse compiler that still have compile errors in them.
— Neil Bartlett (@njbartlett) May 19, 2011
"It's because you drank a capuccino too late this morning".
"Hey, have you called your mom today? That's why it does not work"
"Look out, there's too much sun, so Bnd insert the dot". These explanations to me make sense exacly like the one that has been provided by @njbartlett
The only difference is that he is right, that is exactly the problem that was affecting me. But why? Why in the world this happen? And why specifically with Eclipse?
You can say it's easy, you just make the build compile. Yes, but it continue not to make sense.
And I still lost two precious hours dealing with some completely insane behavior. That's bad.
