Hi Larry, you are right. Really strange... Seems like something was going wrong when deploy the jar's. I will make sure it will not happen again for M3. In the meantime you could use M3-SNAPSHOT (M3 should be out soon).
https://repository.apache.org/content/groups/snapshots/org/apache/james/james-server-container-spring/3.0-M3-SNAPSHOT/ Thanks again, Norman 2011/1/19 Larry Ruiz <[email protected]>: > I have a requirement of assembling a customized version of apache james, for > that I am taking as example container-spring module. > The solution was to copy most of plugins for assembling the distribution and > adding a dependency to container-spring > > The problem that I am facing is that the artifact > james-server-container-spring-3.0-M2.jar (deployed in maven central > repositories) seems to be a war file of ~25MB, > When I built it from the source code > (http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2) the > artifact looks to be ok ( a jar file of ~38KB) and everything runs fine and > I able to generate a custom distribution. > so I wondering if the container-spring artifact was wrong deployed, looking > at version M1 of the same artifact looks as normal jar file for the module. > http://repo2.maven.org/maven2/org/apache/james/james-server-container-spring/3.0-M1/ > http://repo2.maven.org/maven2/org/apache/james/james-server-container-spring/3.0-M2/ > Plz take a look a the attachement. > regards, > Larry Ruiz > p.s. I renamed *.bat scripts > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
