[sip-comm-dev] Suggestion for using Maven


#1

Hi

I am Kasun Herath, a 3rd year undergraduate student from Sri Lanka. I am
much intersted in SIP Communicator project and I am hoping to participate in
GSOC 2009 from this project. While researching about SIP Communicator and
going through the code I learned that it is based on OSGI framework and uses
ant. I have worked previously on another open source project which is also
based on OSGI and it uses maven as the build tool. From the brief experience
I have got it is my humble opinion that using maven to manage a project that
is based on OSGI, is much more easier because of the maven bundle plugin. Is
there any specific reason that SIP Communicator uses ant or would you be
moving to maven in the future?

Following is a good article which I used to gain knowledge of the plugin.

http://wso2.org/library/tutorials/develop-osgi-bundles-using-maven-bundle-plugin
<http://wso2.org/library/tutorials/develop-osgi-bundles-using-maven-bundle-plugin>

regards
Kasun Herath


#2

Hey Kasun,

kasun herath wrote:

Hi

I am Kasun Herath, a 3rd year undergraduate student from Sri Lanka. I am
much intersted in SIP Communicator project and I am hoping to
participate in GSOC 2009 from this project.

Excellent! Wish you good luck then! :slight_smile:

While researching about SIP
Communicator and going through the code I learned that it is based on
OSGI framework and uses ant. I have worked previously on another open
source project which is also based on OSGI and it uses maven as the
build tool. From the brief experience I have got it is my humble opinion
that using maven to manage a project that is based on OSGI, is much more
easier because of the maven bundle plugin. Is there any specific reason
that SIP Communicator uses ant or would you be moving to maven in the
future?

We picked ant from the start mainly because back then maven didn't exist
yet. I don't think we've ever seriously considered switching to maven. I
am afraid however that unless there's an extremely compelling advantage
to do this now, we will probably have to leave it for another time. Over
the years our build.xml has grown to include a lot of stuff (nearly
2KLOC now). Cruise control and all our package building systems are also
using it. Switching to maven would therefore probably imply a
considerable effort.

Following is a good article which I used to gain knowledge of the plugin.

http://wso2.org/library/tutorials/develop-osgi-bundles-using-maven-bundle-plugin
<http://wso2.org/library/tutorials/develop-osgi-bundles-using-maven-bundle-plugin>

Thanks for the ref!

Cheers
Emil

ยทยทยท

regards
Kasun Herath

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net