It should like: <groupId>... <artifactId> <version> <classifier> yes, this is REALLY necessary <type>
Anything completely different from that is incorrect. On Jan 20, 10:50 pm, Logan Allred <[email protected]> wrote: > On Wed, Jan 20, 2010 at 4:34 PM, Justin <[email protected]> wrote: > > I was able to compile both a SWF and a SWC from my module projects by > > packaging the module as a SWF, then adding the additional "test-swc" > > goal. This goal compiles both the module SWF and a SWC with the test > > code; both are installed to my .m2 repository. > > > However, in my test-runner project, I am unable to load the test SWC > > as a dependency, since there is no POM generated for the test-SWC when > > it is installed. Any ideas? > > You shouldn't need a dedicated pom for the test swc. We have some > projects that build both a normal swc and a test-swc, and we reference > the test-swc just fine in our other projects. > > How did you add the dependency to the test-swc? > > Logan
-- 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?hl=en?hl=en http://blog.flex-mojos.info/
