Hhhhmmmm :( I am sorry, you are correct it was building for me because it is on my local maven repo.
I saw you have reverted the parent module, but I still think we should be able to get rid of this and make the root pom as the parent pom. Any way the current strategy of building the complete jar is not gonna work for the OSGi bundle generation. I will have a look at this and get back. Thanks, Ruwan On Tue, Oct 7, 2008 at 2:06 PM, Andreas Veithen <[EMAIL PROTECTED]>wrote: > As the name implies the parent POM is the parent of all other modules > (except the POM in the root directory), so it's not at all obsolete and you > should not remove it. If you are still able to build the transports after > removing this, it is only because this parent POM is still available from > your local (or some other) repository! Can you please revert this? > > Andreas > > Ruwan Linton wrote: > >> Hi devs, >> >> I had a look at the current maven build of the transports and realized >> that >> the complete axis2-transports.jar is generated from the root pom but there >> is an obsolete module also to do the same but is not doing anything. >> Therefore I removed that. Andreas, I hope this ok from the tests reports >> point of view as well. >> >> At the same time for the moment this complete transports jar is generated >> with out the jar plugin and we will need to change the way we build this >> jar >> in order to produce an OSGi bundle jar (but not just a jar). Hope it is >> OK. >> >> Thanks, >> Ruwan >> >> >> > > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
