Hi,

I am currently working on different "OSGi on Scala" projects, e.g.  
ScalaModules, Lift (OSGi-fying Lift) and BindForge. I do not know how  
well OSGi is known in the Scala space, but it will be a very serious  
thing for Java and in my opinion also very useful for Scala. To keep  
things simple: It is a dynamic module system which allows to develop  
and deploy modular Java/Scala systems. Basically there is some  
metadata specified in a JAR's manifest declaring things like module ID  
and version, public API, dependencies, etc. Hence all that is needed  
to OSGi-fy an existing library is adding the necessary manifest headers.

For the above mentioned projects me and my mates have created OSGi- 
fied versions of the Scala libraries (scala-lang and scala-compiler so  
far). But that is redundant work! We would like to create these OSGi- 
fied Scala libraries in ONE common project and publish these to ONE  
central Maven repository. So far I have been talking to David Pollak  
and we decided to go for:

"org.scala-lang" as group id and "scala-library-osgi", "scala-compiler- 
osgi", etc. as artifact ids.

This naming resembles the "original" Scala libraries and makes clear  
that you will find OSGi inside.
What do you think? Any other ideas?

Heiko



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to