Comments on: Company Super POM – A Maven Practice http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice ... what's going on in the world of the brothers Moser boys (and their girls and kids) Sat, 14 Jan 2012 13:33:18 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Admin of the System http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice/comment-page-1#comment-1116 Admin of the System Mon, 26 Jul 2010 15:46:53 +0000 http://www.mosabuam.com/?p=1655#comment-1116 You could do that but it sort of mixes responsibilities. The company super pom as I suggest it here does not contain project specific stuff. Only Maven specific settings. The project specific ones would go in a project parent or project super pom.. You could do that but it sort of mixes responsibilities. The company super pom as I suggest it here does not contain project specific stuff. Only Maven specific settings. The project specific ones would go in a project parent or project super pom..

]]> By: Bram http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice/comment-page-1#comment-1112 Bram Tue, 13 Jul 2010 13:55:54 +0000 http://www.mosabuam.com/?p=1655#comment-1112 Please fix my post by adding code-tags to layout the hudson-bit Please fix my post by adding code-tags to layout the hudson-bit

]]> By: Bram http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice/comment-page-1#comment-1111 Bram Tue, 13 Jul 2010 13:54:46 +0000 http://www.mosabuam.com/?p=1655#comment-1111 If you have structured SCM and CI paths based on each projects artifact-id, you could even configure all SCM and CI settings in the super-pom using constructions like these: hudson http://:8080/hudson/job/${artifactId}/ If you have structured SCM and CI paths based on each projects artifact-id, you could even configure all SCM and CI settings in the super-pom using constructions like these:

hudson
http://:8080/hudson/job/${artifactId}/

]]> By: Manfred Moser http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice/comment-page-1#comment-693 Manfred Moser Fri, 30 Oct 2009 16:04:28 +0000 http://www.mosabuam.com/?p=1655#comment-693 I am contemplating putting my full mosabuam super pom on a nexus instance on the mosabuam/vijug vps. Not sure if there is demand but it would also make it easier for me. Stay tuned. I am contemplating putting my full mosabuam super pom on a nexus instance on the mosabuam/vijug vps. Not sure if there is demand but it would also make it easier for me. Stay tuned.

]]> By: Kelly Robinson http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice/comment-page-1#comment-689 Kelly Robinson Fri, 30 Oct 2009 00:34:50 +0000 http://www.mosabuam.com/?p=1655#comment-689 Great post Manfred! This actually applies just as much for individuals using maven as it does companies. Just so long as the use of the pom doesn't impose behaviour on the inheritors, it's great to have a way to keep your entire maven tool stack in sync. As far as the release strategy goes, it seems pretty limited to internal usage, unless of course a company is prepared to release a company pom publicly along with any maven modules they release publicly. Great post Manfred!
This actually applies just as much for individuals using maven as it does companies. Just so long as the use of the pom doesn’t impose behaviour on the inheritors, it’s great to have a way to keep your entire maven tool stack in sync.
As far as the release strategy goes, it seems pretty limited to internal usage, unless of course a company is prepared to release a company pom publicly along with any maven modules they release publicly.

]]>