[gatein-dev] Some portal build fixes

I’ve done some fixes on the portal build … I’ve added parent.relativePath to many modules to fix ‘chicken or egg’ problem that caused failures when building from scratch with empty repository, without additional settings.xml. Might be that I just patched up the ‘bugs’, not really fixed them, as the modules involved might have wrong parents set in the first place. But it clean builds now when before it didn’t (using maven3). Also, in jboss packaging we have a dependency on org.exoplatform.portal:exo.portal.server.jboss.plugin Looking at the contents of this artifact it’s obvious that it has no effect at all. It contains one conf/portal/configuration.xml file whose content is completely commented out. This is the only artifact for jboss-as5 and jboss-as6 packaging that depends on exo maven repository - it’s not available in jboss repo. So I commented it out for both jboss-as5 and jboss-as6 packaging, and it now builds OOTB without having to create settings.xml with repositories definitions. Also I’d prefer if we mandate maven3 for build. It’s double work to test build for maven2, as well as for maven3, and there’s constant dilemma if someone claims build doesn’t work - what version of maven they used. I see no good reason to maintain compatibility with maven2, when build works perfectly fine with maven3. There’s the issue of packaging/profiles.xml which has no effect when building with maven3, so currently you have to specify extra settings via CLI. That can be fixed by moving properties into packaging/pom.xml. - marko