Hi, Christofer! What i meant by point 1, was that your mavenizer tool uses two dependencies. When running the maven generated jar (the mavenizer) - i get some class not found exceptions, because the dependencies in the pom are not available in the mavenizer jar.
The shade plugin assures, that the dependencies are packaged in the mavenizer jar. Regards ;) Den mandag den 26. november 2012 21.49.02 UTC+1 skrev Christofer Dutz: > > @netphreak > > I will give the code a review as soon as I setup my write access to the > apache repo. But I think this is a good point ;-) > After searching the entire code, I found that the compiler stuff is indeed > created using "\" instead of the java platform neutral "/". > I'll change that as soon as possible. > > Have to admit that I didn't quite get your point 1 ... I know that it > would be good to model out the dependencies of a jar in the compiler part, > unfortunately I don't have exact information on what jar file references > which other jar. Adobe did a lot of patching and hacking so this > information would have to be written manually. The only way I can do this > at the moment is to assume that if all jars of the compiler directory are > available at runtime, no CNFE should occur. I agree that this could cause > problems if one of the artifacts used in the Flex compiler are also used in > another plugin in the build. Then the classpath could get cluttered with > different versions of the same classes. The only real solution I currently > see would be a truely mavenized Flex compiler buid, but that's not going to > happen too soon. > > > 2012/11/26 netphreak <[email protected] <javascript:>> > >> Hi, Christofer! >> >> Thanks for your hard work - it's much appreciated!! >> >> I've checked out your mavenizer project - and have identified a few >> problems. >> >> 1. >> It think, that you need to package the pom jar dependencies into your jar >> file, it can be done using the maven shade plugin, to avoid class not found >> exceptions: >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-shade-plugin</artifactId> >> <executions> >> <execution> >> <phase>package</phase> >> <goals> >> <goal>shade</goal> >> </goals> >> </execution> >> </executions> >> <configuration> >> <finalName>${artifactId}-${version}</finalName> >> </configuration> >> </plugin> >> >> 2. I noticed, on OSX some folders are created in the FDKTarget: >> com\adobe\flex\compiler\rideau\4.6.0.23201 >> com\adobe\flex\compiler\saxon9\4.6.0.23201... >> >> I suppose it should have been a set of nested folders? >> - I suggest you use the System.getProperty("file.separator"), to ensure >> you use a compatible directory separator, to be system agnostic.. >> >> >> The SDKDeployer fails, i suppose, based on the folder structure error >> described in point 2? >> >> >> Regards. >> >> >> >> Den fredag den 9. november 2012 11.15.54 UTC+1 skrev Christofer Dutz: >> >>> Hi guys, >>> >>> sorry for me being a little overloaded in the last weeks, but I have >>> been working hard on my Flex SDK Mavenizer and the Flexmojos 6.x branch. >>> After more than one month of full time work (if a add all up) we are ready >>> to go. I just contributed the code for the Generator to Apache Flex and >>> it's available for download at: https://svn.apache.org/** >>> repos/asf/incubator/flex/**utilities/trunk/mavenizer/<https://svn.apache.org/repos/asf/incubator/flex/utilities/trunk/mavenizer/> >>> In a few hours I think that will have an updated README.txt explaining >>> how to use it. >>> >>> Flexmojos 6.x is currently available in my Github Repo at >>> https://github.com/**chrisdutz/flexmojos<https://github.com/chrisdutz/flexmojos> >>> but >>> I will push those changes back to velos repo soon. Just if you want to >>> start testing, give it a go :-) Really hoping on some feedback. >>> >>> Additionally you might be interested that rP and I were really busy on >>> the new Confluence at https://flexmojos.**atlassian.net/wiki/display/** >>> FLEXMOJOS/Home<https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Home> >>> Now most of the content of the old sonatype wiki is available at the new >>> destination and I merged in all of my finished documents from my companies >>> Wiki. Currently we are workin on updating those pages, but a lot has been >>> done. So give it a try and give us some feedback at what you think and >>> where things have to be corrected. Reall looking forward to turning off all >>> of the old sites so the web is not polluted with outdated information, so >>> if your're looking for information, you'll be guided to the most recent >>> source. >>> >>> So much for now, >>> Chris >>> >>> >>> >>> >>> >>> -- >> 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]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> 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/
