la misura centrale, il «contributo di solidarietà» sui redditi superiori a 90 mila euro, è profondamente ingiusta. Essa infatti colpisce una minoranza di cittadini (poco più dell’1%) che ha due sole colpe: guadagnare più di 4000 euro netti al mese, e pagare le tasse.
Il rischio di sacrifici inutili – LASTAMPA.it
Published August 14, 2011 Uncategorized Leave a CommentThis 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. http://twitter.com/#!/ildella/status/71189575145496576
@njbartlett answered me: "It can happen with classes produced by the Eclipse compiler that still have compile errors in them. "
http://twitter.com/#!/njbartlett/status/71192822333718528 Really? Really?
"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.
2. how do I change the layout of "osgi:list" and "obr:list" to display symbolicName instead of the (useless) bundle name?
3. how do I instruct maven-bundle-plugin to create a war without the dependencies jars in the WEB-INF/lib folder?
4. how do I configure Export-Package to export ALL the packages in the bundle BUT the packages that the bundles already imports from some other bundle?
5. why there are so few tutorial kind of documentation about OSGI?
Zap Mama – Iko Iko (Suca Mama) HQ | Listen to Free Music Online | delladj – Blip.fm
Published April 8, 2011 Uncategorized Leave a Commentbeen released. It’s a serious upgrade and here is a list of the most
significative improvment I see: XML schema for features descriptor
https://issues.apache.org/jira/browse/KARAF-53
Pax Web 1.0 https://issues.apache.org/jira/browse/KARAF-338
Allow the use of version ranges on dependant features
https://issues.apache.org/jira/browse/KARAF-251
encryption with Jasypt 1.7 https://issues.apache.org/jira/browse/KARAF-266
Pax Logging 1.6 with SLF4J 1.6 support
https://issues.apache.org/jira/browse/KARAF-396
Command to manage users, password and roles
https://issues.apache.org/jira/browse/KARAF-188
‘extract’ deployment option, with automatic detection of feature
repositories https://issues.apache.org/jira/browse/KARAF-151 Also we have some minor upgrade to Aries, Spring, Jetty, Pax and so on
and something like 50 bug fixes, here’s the complete release notes,
find out what’s relevant for you.
http://karaf.apache.org/index/community/download/karaf-2.2.0-release.html
You just need to install elementary and then choose the theme in System | Preferences | Appeareance.
There are two ways to install the theme:@
The easy way:
From a terminal:
sudo add-apt-repository ppa:elementaryart/ppa sudo apt-get update sudo apt-get install elementary-icon-theme elementary-theme elementary-wallpapers
To get the terminal, press CTRL+ALT+T or launch it from the Application menu, Accessories.
The hard way:
From Applications menu, choos Software Sources.
Now fro the menu, Edit | Software Sources
Now choose the Other Software tab, press add and finally insert:
ppa:elementaryart/ppa
Now after reloading the sources, elementary theme, icons and wallpapers will be available.
In the end
Just choose the theme from the System | Preferences | Appeareance
it's our own damn fault
That's the way to roll, and Micheal got the point totally.
Rocknroll.better and better on a single activity or practice is like the 100
meters runner that trains himself not to beat his previous best time
but to improve the appearance of his legs muscles.
I got satisfaction (architectural solutions and cool technologies)
Published July 6, 2010 Uncategorized Leave a CommentI got over both of them in less than two weeks, doing other tasks in the meantime.
Now I have a running Felix and I am able to produce a bundle that got activated once installed and started. This without changing my build tool chain, a simple "mvn install" is enough to produce the bundle, I just miss the way to deploy directly to the felix install.
And on the ActiveMQ side I can connect producer as well as subscribers to my queues or topics and my subscribers are able to reconnect and recover messages they lost when they were offline. This solve all the first wave of technical challenges and put the basis for a nice infrastructure. So I am satisfied and I deserve a present, let's go looking for that Android phone…
Maven Eclipse Plugin and the POM packaging project
Published June 14, 2010 Uncategorized Leave a CommentSo I hacked into and "fixed" it. That was simple. What is not is to understand reason behind the choice and provide a better alternative. Let's dig into it
When it comes to multi-project maven configuration, there is always a little confusion. There has been a discussion about it on the jug Milano mailing list a few months ago and what put confusion in my opinion is that "pom" packaging type is misleading cause it is used for multi-modules project as well for POM inheritance. So, "pom" is a bad keyword for a packaging type. First, is the name of the file itself, second isn't related in any way to the to the objective of the packaging type. We should have two different keyword, something like "multi-module" and "abstract", the second behing for pom inheritance while the first one is obvious. Back to the maven-eclipse-plugin, I expect it to generate a default Eclipse project, not a Java Project, for those two kind of projects. And the multi-module of course should not include the childs project in its Eclipse project structure: a project with just the pom.xml in it should be more than enough. What do you think about?

Recent Comments