Difference between revisions of "GCube Maven BOMs"

From Gcube Wiki
Jump to: navigation, search
(Created page with '== What is a BOM == When dealing with large projects like in the case of gCube, it's fondamental to introduce mechanism in order to mitigate the ''anarchy'' of developers in usi…')
 
(What is a BOM)
Line 5: Line 5:
 
As described in the maven documentation [[http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]] there is a standard way to define the base artifacts of a project by implementing a '''BOM''' ( BIll of Materials)  
 
As described in the maven documentation [[http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]] there is a standard way to define the base artifacts of a project by implementing a '''BOM''' ( BIll of Materials)  
  
The Maven BOM is a pom only component which fixed the dependencies and base versions of a component which import it.
+
The Maven BOM is a pom only component which fixed the dependencies and base versions of a component which import it.  
 +
 
 +
== the GHN Maven BOM ==
 +
 
 +
In the case of gCube,  the gCube services are deployed in an ''old fashioned'' container based on globus WS-Core 4.0, which unfortunately does not implement child classloaders for each deployed component as for the latest web service containers ( like OGSA or tomcat) .
 +
 
 +
Given that we have to deal with a flat classloader schema which leads to very

Revision as of 12:39, 31 January 2013

What is a BOM

When dealing with large projects like in the case of gCube, it's fondamental to introduce mechanism in order to mitigate the anarchy of developers in using thrid party dependencies or even other developers artifacts versions.

As described in the maven documentation [[1]] there is a standard way to define the base artifacts of a project by implementing a BOM ( BIll of Materials)

The Maven BOM is a pom only component which fixed the dependencies and base versions of a component which import it.

the GHN Maven BOM

In the case of gCube, the gCube services are deployed in an old fashioned container based on globus WS-Core 4.0, which unfortunately does not implement child classloaders for each deployed component as for the latest web service containers ( like OGSA or tomcat) .

Given that we have to deal with a flat classloader schema which leads to very