Hi Neil,
thanks for the inputs...
I have been using maven since a long time. too long before I started
with OSGi 3 years ago.
Then it was natural my involvement with the maven-bundle-plugin and
tycho and m2e. Besides the fact that was a kind problematic at the
beginning, currently we have a pretty cool building process with both
maven based tools.
Unfortunately I should say that the Ant way of build was the reason that
we didn't get comfortable with Bndtools when we tried, even though it
has a lot of great features.
In that time it would be need to maintain binary jars for dependencies
into the scm repository instead of getting them from a central
repository and that was determinant to our bosses decision.
best regards,
Cristiano
On 03/10/13 14:38, Neil Bartlett wrote:
Cristiano,
Bndtools can use most build tools, including Ant, Maven and Gradle. We
use the "build model" provided by bnd to abstract away from the
low-level build system, so actually you rarely touch the build.xml
files when working with bnd.
I know that Ant isn't fashionable these days. But neither is assembly
language... nevertheless, everything you write in Java ultimately gets
translated down to assembly. So in Bndtools, we treat Ant's build
files as our "assembly". Gradle also works very well, and is faster
than Ant, so we may be moving our own builds to Gradle soon.
Maven is the most problematic of the three because it's a control
freak. So we have to compromise, i.e. provide less advanced features.
This is why I personally avoid Maven except where I'm working with a
customer that requires it.
Regards,
Neil
On 3 October 2013 at 18:28:55, Cristiano Gavião ([email protected])
wrote:
Just a curiosity...
why Bndtools uses Ant instead Maven ?
Cristiano
On 03/10/13 13:49, Neil Bartlett wrote:
Did you take a look at the book suggestions you received on the
other mailing list? I particularly recommend OSGi in Action (Hall et
al) and Enterprise OSGi in Action (Ward and Cummins).
After that, it's best to try to apply what you have learned to
something real, even if it's only small scale. How about a web
application? A blog engine, for example?
I don't agree with the suggestion to go off and learn technologies
like Blueprint, Karaf etc purely for their own sake. Unfortunately
on this list, everybody has their favourite technology that they
would like you to use. That includes me... I think you should stick
with DS and Bndtools. Hey, at least I'm open about my biases!
Neil
On 3 October 2013 at 17:24:24, Christian Schneider
([email protected]) wrote:
Hi Syed,
joke apart ..
the tutorial is a grea starting point but as a next step you should
pick
some small real world or toy project and try to implement it using
OSGi.
On the way you will learn a lot and for sure come back with some
questions and problems where we can help out.
You might also want to investigate some additional technologies like
blueprint as an alternative for ds and Apache Karaf as a server. I did
some tutorials about blueprint and karaf at
http://www.liquid-reality.de/display/liquid/Karaf+Tutorials . As you
will notice the development model is very different between
bndtools and
plain eclipse + m2eclipse which I use with karaf.
Bndtools probably provides the easier start but karaf + eclipse is
very
maven focused which is a plus in many company environments.
Christian
Am 03.10.2013 11:03, schrieb [email protected]:
> Dear Osgi Members,
>
> I have gone through this below link. What should i do after this.
> Please help me out. I am new to OSGi.
> http://bndtools.org/tutorial.html
>
> Thanks & Regards
> Syed
> 8553043179
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
