View source

From APIDesign

You do not have permission to do that, for the following reason:

The action you have requested is limited to users in the group Bureaucrats.

You can view and copy the source of this page:

Specification and also an implementation for packaging, managing [[dependencies]], deploying and executing applications composed from pieces/modules. [[Java]] users can choose from [[OSGi]], [[NetBeans Runtime Container]] or possibly [[OSGiAndNetBeans|mix them]] together.

In case one cares more about the build than execution, then have a look at [[Maven]]. In case your primary domain is packaging, then you are probably seeking for [[RPM]] or [[Debian]] solutions.


=== A bit of math ===

[[Module system]] design needs to face some tricky (e.g. [[NP-Complete]]) issues. Especially complex is management of module dependencies as described at [[LibraryReExportIsNPComplete]]. This can have various solutions (like [[LibraryWithoutImplicitExportIsPolynomial]]), but it also shows why good [[API]] design skills are needed and why [[BackwardCompatibility]] is important.

=== The need for Common Ground ===

Do you wonder why certain people think [[Ruby]] is better than [[Java]]? Do you think it is due to [[Talk:Blogs:JaroslavTulach:Theory:LanguagesForEvolution|duck-typing]]? Due to having [[closures]]? Wrong, it is because [[Ruby]] has [[Gems]]. Listen to following screencast to get convinced that [[Java]] needs such [[Module system|common ground]] too. See it with your own eyes [[NetbinoxTutorial|in action]].

{{#ev:bliptv|2790848}}

<comments/>

[[Category:Video]]

Return to Module system.

Retrieved from "http://wiki.apidesign.org/wiki/Module_system"

View source

From APIDesign

Views

Personal tools

blogs & look

Navigation

Search

Toolbox

View source

From APIDesign

Views

Personal tools

blogs & look

Navigation

Search

Toolbox

buy