Yes, I have only one project / no module. I used to have a root project with 2 modules: one for compiling swf, one for making the assembly, and in this case, this release artifact only contains the tar.gz.
I changed this with a unique project with a profile for activating assembly / tar.gz. It's more simple for flex developers who are used to get their swf next to their sources in Flashbuilder. It's working fine in both case, but what's annoying me is duplication in deliveries. In both case I have swf tied directly in the artifact, and the same swf into the tar.gz. It's not a big disk loss at each snapshot or release, but as these swf are useless, if i can remove them from my Nexus, it's not bad (this project is meant to be deployed to web server, not used as dependency in other one). Another problem is the flex application is loading dynamically swf modules, and it expects unversionned filenames for these swf. I'm using version stripping before building the tar.gz so swf filename into are fine, but not those tied directly to the artifact (i get the artifact version in filename plus classifier as there are several deliveries). -- View this message in context: http://maven.40175.n5.nabble.com/Choose-file-to-install-deploy-tp4271077p4271155.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
