Hi, Currently, automation team is using snapshot dependencies for ongoing automation work. The automation team have build the trunk and using artifacts at local repo. This approach doesn't scale when we are going to deliver the work to QA or Devs. And, our initial plan is to maintain maven based system-test-framework separately from trunk. So we cannot expect others to build trunk or branch in order to use the framework.So snapshot maven repo is required for automation work. Since we are going to run the automation frameworks against each releases, this has to be online repo associated with current trunk or branch.
Our standard snapshot repo at [1] haven't been updated since Feb 2010. AFAIK, trunk is unstable now. So is there any way to deploy at least required artifacts to our repo. How about maintaning staging snapshot repo for on going dev/automation work? Your comments and suggestions are welcome. Thanks, Krishantha. [1]http://dist.wso2.org/snapshots/maven2/
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
