I would suggest this setup: Introduce some central Company Maven Repo (Artifactory, Nexus, whatsoever). Additionally have a Continuous Integration server that automatically builds upon SVN updates. This CI server automatically deploys the built artifacts to your central Company Maven Repo. All clients have their Maven builds configured to reference the central Company Maven Repo. This way the builds can use the latest versions of modules that weren't compiled on the current machine.
As soon as you have finished a version, simply use the maven release Plugin to make a real version from the SNAPSHOT versions (1.2.3-SNAPSHOT then becomes 1.2.3). Chris Well I would suggest to use SNAPSHOTs during the development process. 2011/4/28 Van <[email protected]>: > Perhaps I'm just stating the same problem in another way here, but the > main thing preventing me from replacing our ant scripts with flexmojos > is the fact that if one of the developers upgrades one of the swc's in > the libraries folder and checks it in, both flashbuilder and ant will > build the project with whatever version of the libraries are checked > into the project. And that's the behavior we want because developers > always get the latest version of libraries without doing anything. > That's the behavior we want. > > But with flexmojos it looks like we'd have to be aware of that library > upgrade and install that new version of the swc into our maven > repository. Furthermore, we'd love to install the maven environment > on multiple testservers and on development machines that don't always > have network access to each other. So whe I can see the benefit of a > centralized repository for our libraries, it seems that with flexmojos > it's a requirement, not an option. We'd have to teach our developers > how to upgrade a maven dependency in their local repository, notify > them each time a library changes, and depend on them manually > upgrading it. > > - Van > > On Apr 27, 11:43 pm, "Hessick, Michael" <[email protected]> > wrote: >> My flex artifacts are packaged as zips and stored in Nexus. >> >> Because I need to package my swf and swc files with a text file containing a >> version and build number for each. >> >> I want to propagate this information down the dependency chain. >> >> Is there another customary way of accomplishing this? It's easy with the jar >> / war plugin, just specify a manifest property. >> >> I need a way of tracing back to source without viewing the SWF via a browser >> or decompiling it. I cannot include source in the promoted packages. >> >> Labeling the artifact only results in lost information about the build >> number of what went into it. >> >> Maybe I'm missing something, I'm new to promoting flex packages. >> >> It seems that I'll need to use antrun to call the flex compiler so I can >> pass it the library paths after I unpack them. >> >> Reading the files with build numbers is done via a batch script, then I >> create another master text file with all the values and package the zip >> containing the SWF with the assembly plugin. >> >> I'm hoping there's an easier way that I'm not aware of, considering my >> requirements. >> >> Mike >> >> ________________________________ >> From: [email protected] <[email protected]> >> To: [email protected] <[email protected]> >> Sent: Wed Apr 27 20:37:51 2011 >> Subject: Re: [flex-mojos] specify the '-library-path' command line option >> >> The library path is created by FlexMojos based on the dependencies of the >> module. There is no direct support for mutating it that I'm aware of. If you >> need something in the path, add a dependency on it. Note that, because many >> Flex projects are not Mavenized, you may need to setup your own Maven >> repository (Sonatype's Nexus [http://nexus.sonatype.org] is an excellent >> choice, and free) where you can publish artifacts that are not otherwise >> available in a repository. >> >> Hope this helps, >> Bryan Turner >> >> On Wed, Apr 27, 2011 at 4:02 PM, Hessick, Michael >> <[email protected]<mailto:[email protected]>> wrote: >> I'm using flex-mojos 3.6.1 >> >> Is there a way to specify 'library-path' to either the compile-swf (mxmlc) >> or compile-swc (compc) goals using your plugin (or any other version of it?) >> >> I need to be able to specify library path and it appears there is no support. >> >> Thanks, >> >> -Mike >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Flex Mojos" group. >> To post to this group, send email to >> [email protected]<mailto:[email protected]> >> To unsubscribe from this group, send email to >> [email protected]<mailto:flex-mojos%2Bunsubscribe@goo >> glegroups.com> >> For more options, visit this group >> athttp://groups.google.com/group/flex-mojos >> >> http://flexmojos.sonatype.org/ >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Flex Mojos" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group >> athttp://groups.google.com/group/flex-mojos >> >> http://flexmojos.sonatype.org/ > > -- > You received this message because you are subscribed to the Google > Groups "Flex Mojos" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/ > -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
