Hi Deepal, I read the readme but, since the parent pom was on my local repo, it was building for me :(.
I think we should be able to get rid of this parent module. I will try to come up with a solution, if at all possible... Thanks, Ruwan On Tue, Oct 7, 2008 at 5:19 PM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > 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. > > > Nope its not ok. Did you ever read the readme.txt ? > The main reason I added that to build a complete transport jar. If you > know any other way to do that please go ahead and remove that. Please > remember we need to build a complete jar including all the transports. > > 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. > > > If you get the complete jar working I have no problem. Because I came up > with that solution after spending a day (I know my knowledge on maven is > very little). > > -Deepal > > Thanks, > > Ruwan > > > > > > > -- > Thank you! > > > http://blogs.deepal.org > > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
