Ow, this sourceFile is really painful =/ but flex compiler demands it and I do my best to find the right one =D FWIW, flexmojos should be looking the files content searching for the unique Application before asking you the file..... Did you had more then one Application?
Anway I will try to improve the console feedback. Can we continue that on flexmojos users list? http://groups.google.com/group/flex-mojos/ <http://groups.google.com/group/flex-mojos/>VELO On Mon, Sep 21, 2009 at 3:27 AM, Wim Deblauwe <wim.debla...@gmail.com>wrote: > Hi, > > We initially had only 1 mxml file in the source folder, so flex-mojos > picked this one up. Later, we added an .as file to that same folder and > suddenly flex-mojos did not compile anymore. I looked through the source > code and found that if there is more then 1 mxml or as file, you only look > for Main.mxml or Index.mxml, but our file was not named like that. > Solving it once I knew what the problem was, was easy. I just had to add > <sourceFile> to my configuration. > > Maybe you can document this some more in the docs of <sourceFile/>. Now, it > just states that this is optional, but it would be good to elaborate on it. > > Maybe it would also be good to fail the build with a nice exception, saying > you cannot find a single mxml or as file and the user needs to specify it > using <sourceFile/>. It would have saved me some hours of research. > > regards, > > Wim > PS: Thanks for the great plugin! > > 2009/9/19 Marvin Froeder <velo...@gmail.com> > > Now I got curious.... >> What is up with flexmojos? >> >> >> VELO >> >> On Wed, Sep 16, 2009 at 6:31 AM, Wim Deblauwe <wim.debla...@gmail.com >> >wrote: >> >> > It seems the problem was not related to assembly, but to flex mojos. >> Thank >> > you for your help. >> > >> > regards, >> > >> > Wim >> > >> > 2009/9/16 Aleksey Didik <di...@magenta-technology.ru> >> > >> > > Hi, >> > > because you use _aseembly:single_ instead of _assembly:assembly_. >> > > >> > > Documentation of maven-assembly-plugin, goal single : >> > > >> > > Assemble an application bundle or distribution from an assembly >> > >>> descriptor. This goal is suitable either for binding to the >> lifecycle >> > or >> > >>> calling directly from the command line (provided all >> required >> files >> > are >> > >>> available before the build starts, or are produced by another goal >> > specified >> > >>> before this one on the command line). >> > >>> >> > >> >> > > >> > > Change _<goal>single</goal>_ to _<goal>assembly</goal>_ and try >> again. >> > > >> > > >> > > >> > > Best regards, >> > > >> > > Aleksey Didik >> > > >> > > >> > > >> > > >> > > Wim Deblauwe ?????: >> > > >> > > Hi, >> > >> >> > >> I have a maven project with 'swf' packaging. I also have the assembly >> > >> plugin >> > >> configured as follows: >> > >> >> > >> <plugin> >> > >> <groupId>org.apache.maven.plugins</groupId> >> > >> <artifactId>maven-assembly-plugin</artifactId> >> > >> <executions> >> > >> <execution> >> > >> <id>assembly</id> >> > >> <goals> >> > >> <goal>single</goal> >> > >> </goals> >> > >> <phase>package</phase> >> > >> <configuration> >> > >> <descriptors> >> > >> >> > >> <descriptor>src/main/assembly/descriptor.xml</descriptor> >> > >> </descriptors> >> > >> </configuration> >> > >> </execution> >> > >> </executions> >> > >> </plugin> >> > >> >> > >> When I do a 'mvn clean install', the swf is not generated and I see >> the >> > >> following info message: >> > >> >> > >> [INFO] [install:install {execution: default-install}] >> > >> [INFO] No primary artifact to install, installing attached artifacts >> > >> instead. >> > >> >> > >> Why is my swf no longer being installed? >> > >> >> > >> regards, >> > >> >> > >> Wim >> > >> >> > >> >> > >> >> > > >> > >> > >
