On Wed, May 19, 2010 at 8:51 PM, Josh McDonald <j...@joshmcdonald.info> wrote: > That's been my plan all along, but the powers-that-be have decided > otherwise. Can it not be done?
Like everyone said, you'll want to do it the Maven way, with artifacts in a repo. But if that seems daunting, then perhaps we need to understand more of what seems daunting about it. Our project uses about a dozen third-party swcs. That should take about 20-30 min to upload those into a private maven repo (if the cheque-payers want you to use maven, then they should provide you with a server you can put Nexus or Artifactory or whatever on it). If you have significantly more artifacts than that, then you might have to write a script, or use the bundle-publisher to get all of those artifacts into the maven repo. That should still at most be a one-time cost of a few hours, perhaps most of a day. Now if you are consuming artifacts from other teams that are not using maven, then yes, it might get trickier. If they are using ant, it is fairly straightforward to use the maven ant tasks to deploy their ant artifacts into a maven repo, and they should have a plan to move to Maven too. Or they might have to upload them manually into your Nexus or Artifactory repo on each release. Either way, it shouldn't be that much of a burden, though when you're not used to something it can feel that way. Logan -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to flex-mojos@googlegroups.com To unsubscribe from this group, send email to flex-mojos+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
