Hi Thilina, Yeah, this was there for sometime since ws-messenger is running inside Axis2 and we use simpleAxis2 Server as the default server. Ideally what should happen is we should take only the required jars and start simple axis2 server, but required utilities (configuration files and file structure we need to build locally) should be build by ws-messenger. Currenly there is no option of download axis2 distribution during the build time because by putting the distribution as a dependency doesn't pick the distribution from repo properly.
For the time being easiest solution I can see is to keep it in our SVN with everything as it is, but I am +1 to improve this to use download required axis2 jars as dependency and create folder structure and start scripts locally. Lahiru On Thu, Jul 21, 2011 at 2:50 PM, Thilina Gunarathne <[email protected]>wrote: > Hi, > I noticed we have a whole Axis2 distribution and ton of other jar > files in the following directories. Wondering whether they got in by > mistake? > > > http://svn.apache.org/viewvc/incubator/airavata/trunk/ws-messaging/distribution/axis2_releases/axis2-1.6.0/ > > http://svn.apache.org/viewvc/incubator/airavata/trunk/ws-messaging/distribution/resources/nio_lib/ > > thanks, > Thilina > > -- > https://www.cs.indiana.edu/~tgunarat/ > http://www.linkedin.com/in/thilina > http://thilina.gunarathne.org >
