Sorry that I can't answer your question now ... I'm leaving for a short trip and will come back on Monday, so please be patient and I'll help you on Monday. Till then perhaps someone on the list will be able to help you.
Chris -----Ursprüngliche Nachricht----- Von: Maxim Solodovnik [mailto:[email protected]] Gesendet: Mittwoch, 16. Juli 2014 17:21 An: [email protected] Betreff: Re: AW: flexmojos-maven-plugin: building flex project without mavenizing Flex binaries I'm really sorry asking dumb questions but somehow maven ignores org.apache.flex:compiler:pom:4.12.1 in local repository and looking it in https://oss.sonatype.org/content/groups/staging with no luck What am I doing wrong? [ERROR] The project org.apache.openmeetings:openmeetings-flash:3.1.0-SNAPSHOT (/home/solomax/work/openmeetings/trunk/singlewebapp/openmeetings-flash/pom.xml) has 2 errors [ERROR] Unresolveable build extension: Plugin net.flexmojos.oss:flexmojos-maven-plugin:7.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failure to find org.apache.flex:compiler:pom:4.12.1 in https://oss.sonatype.org/content/groups/staging was cached in the local repository, resolution will not be reattempted until the update interval of flex-mojos-plugin-repository has elapsed or updates are forced -> [Help 2] On 16 July 2014 21:47, Christofer Dutz <[email protected]> wrote: > Ups ... my bad, > > I fixed the documentation ... sorry for that. > > Chris > ________________________________________ > Von: Maxim Solodovnik <[email protected]> > Gesendet: Mittwoch, 16. Juli 2014 16:36 > An: [email protected] > Betreff: Re: AW: flexmojos-maven-plugin: building flex project without > mavenizing Flex binaries > > still get > [ERROR] Unresolveable build extension: Plugin > net.flexmojos.oss:flexmojos-maven-plugin:7.1.0-SNAPSHOT or one of its > dependencies could not be resolved: The following artifacts could not > be > resolved: > net.flexmojos.oss:flexmojos-threadlocaltoolkit-wrapper:jar:4.12.1, > org.apache.flex:compiler:pom:4.12.1: Could not find artifact > net.flexmojos.oss:flexmojos-threadlocaltoolkit-wrapper:jar:4.12.1 in > flex-mojos-plugin-repository ( > https://oss.sonatype.org/content/groups/staging) -> [Help 2] > > > https://oss.sonatype.org/content/groups/staging contains > net.flexmojos.oss:flexmojos-threadlocaltoolkit-wrapper:jar starting > from version 5.0-beta/ < > https://oss.sonatype.org/content/groups/staging/net/flexmojos/oss/flex > mojos-threadlocaltoolkit-wrapper/5.0-beta/ > > > > version 4.12.1 is missing :( > > > > On 16 July 2014 20:05, Christofer Dutz <[email protected]> wrote: > > > Dam ... misst part of the URL ... try this one.... > > > > https://oss.sonatype.org/content/groups/staging > > > > Chris > > ________________________________________ > > Von: Maxim Solodovnik <[email protected]> > > Gesendet: Mittwoch, 16. Juli 2014 14:33 > > An: [email protected] > > Betreff: Re: AW: flexmojos-maven-plugin: building flex project > > without mavenizing Flex binaries > > > > I get 404 when trying to access > https://oss.sonatype.org/content/staging/ > > :( > > > > > > On 16 July 2014 19:22, Christofer Dutz <[email protected]> > wrote: > > > > > Hi Maxim, > > > > > > First of all, thank you for testing. > > > > > > To your 0) ... well the "without mavenizing" part will be possible > > > as > > soon > > > as we have released Apache Flex as Maven artifacts and I have > > > finished > > the > > > last Part of Flexmojos that auto-mavenizes everything. Currently > > > you > have > > > to mavenize. > > > > > > To 1) Well you have to add the Sonatype Snapshot repo to your > > > repositories, otherwise you won't be able to access the plugin > > > (Think I should add that to the documentation) I have this setup at " > > > https://oss.sonatype.org/content/staging/"; and it should also work > > > for you. > > > > > > Chris > > > > > > ________________________________________ > > > Von: Maxim Solodovnik <[email protected]> > > > Gesendet: Mittwoch, 16. Juli 2014 13:45 > > > An: [email protected] > > > Betreff: Re: AW: flexmojos-maven-plugin: building flex project > > > without mavenizing Flex binaries > > > > > > Hello Chris, > > > > > > Finally I was able to finish following your guide :) Here are > > > couple of issues I found: > > > > > > 0) somehow "building flex project without mavenizing Flex binaries" > > > requires manual mavenizing :) > > > > > > 1) after trying to build I get: > > > [ERROR] The build could not read 1 project -> [Help 1] [ERROR] > > > [ERROR] The project > > > org.apache.openmeetings:openmeetings-flash:3.1.0-SNAPSHOT > > > > > > > > > (/home/solomax/work/openmeetings/trunk/singlewebapp/openmeetings-flash/pom.xml) > > > has 2 errors > > > [ERROR] Unresolveable build extension: Plugin > > > net.flexmojos.oss:flexmojos-maven-plugin:7.1.0-SNAPSHOT or one of its > > > dependencies could not be resolved: The following artifacts could not > be > > > resolved: net.flexmojos.oss:flexmojos-maven-plugin:jar:7.1.0-SNAPSHOT, > > > net.flexmojos.oss:flexmojos-threadlocaltoolkit-wrapper:jar:4.12.1, > > > org.apache.flex:compiler:pom:4.12.1: Could not find artifact > > > net.flexmojos.oss:flexmojos-maven-plugin:jar:7.1.0-SNAPSHOT -> [Help 2] > > > [ERROR] Unknown packaging: swf @ > > > org.apache.openmeetings:openmeetings-flash:[unknown-version], > > > > > > > > > /home/solomax/work/openmeetings/trunk/singlewebapp/openmeetings-flash/pom.xml, > > > line 28, column 13 > > > > > > 2) I have added > > > <repositories> > > > <repository> > > > <id>flex-mojos-repository</id> > > > <url>http://repository.sonatype.org/content/groups/flexgroup</url> > > > </repository> > > > </repositories> > > > <pluginRepositories> > > > <pluginRepository> > > > <id>flex-mojos-plugin-repository</id> > > > <url>http://repository.sonatype.org/content/groups/flexgroup</url> > > > </pluginRepository> > > > </pluginRepositories> > > > > > > with no luck :( > > > > > > Would appreciate further help on this :) > > > > > > > > > > > > On 14 July 2014 01:58, Maxim Solodovnik <[email protected]> wrote: > > > > > > > Mavenizer seems to be built as expected > > > > will continue after the Football > > > > > > > > Go Germany :)) > > > > > > > > > > > > On 12 July 2014 19:37, Christofer Dutz <[email protected]> > > > wrote: > > > > > > > >> Your whish is my command :) > > > >> > > > >> > > > > > > https://cwiki.apache.org/confluence/display/FLEX/Quick+Start+Guide:+Building+Apache+Flex+applications+using+Maven > > > >> > > > >> I hope I got everything important in there. If you get stuck, feel > > free > > > >> to tell me and I'll make sure to sort out any problems. > > > >> > > > >> Chris > > > >> > > > >> -----Ursprüngliche Nachricht----- > > > >> Von: Maxim Solodovnik [mailto:[email protected]] > > > >> Gesendet: Freitag, 11. Juli 2014 16:55 > > > >> An: [email protected] > > > >> Betreff: Re: AW: flexmojos-maven-plugin: building flex project > without > > > >> mavenizing Flex binaries > > > >> > > > >> I saw this game (starts 3 AM here :) ) it was amazing :) > > > >> > > > >> Maybe you have small how-to and I'll try to test it this weekend > > > >> > > > >> > > > >> On 11 July 2014 21:51, Christofer Dutz <[email protected]> > > > wrote: > > > >> > > > >> > Well I guess if the german football team wouldn't have been that > > > >> > kick-ass recently, I would have had more results :-) > > > >> > > > > >> > But I did upload an updated SNAPSHOT version 1 or 2 weeks ago, > which > > > >> > you can use with the new Mavenizer ... would love people to test > > that > > > >> > combination. > > > >> > (Remember the new mavenizer is in the " > > > >> > > https://github.com/apache/flex-utilities/tree/mavenizer-refactoring > > " > > > >> > branch. > > > >> > > > > >> > Seems my refactorings have even finally fixed some haunted code in > > > >> > Flexmojos which caused the testusuite to fail every 4 or 5 times. > > > >> > > > > >> > As soon as I have a few more people confirming that the new > > mavneizer > > > >> > works, I need to merge that back to develop and do a release of > the > > > >> > mavenizer. > > > >> > Before that is released I can't integrate that into Flexmojos as > > > >> > everyone would have to manually build the Mavenizer :-( > > > >> > > > > >> > Chris > > > >> > > > > >> > > > > >> > ________________________________________ > > > >> > Von: Maxim Solodovnik <[email protected]> > > > >> > Gesendet: Freitag, 11. Juli 2014 16:44 > > > >> > An: [email protected] > > > >> > Betreff: Re: AW: flexmojos-maven-plugin: building flex project > > without > > > >> > mavenizing Flex binaries > > > >> > > > > >> > Hello Chris, > > > >> > > > > >> > Maybe you have anything to test? :) > > > >> > > > > >> > > > > >> > On 24 June 2014 18:46, Maxim Solodovnik <[email protected]> > > wrote: > > > >> > > > > >> > > Great ! > > > >> > > Thanks :) > > > >> > > Will wait this huge release :) > > > >> > > > > > >> > > > > > >> > > On 24 June 2014 18:32, Christofer Dutz < > [email protected] > > > > > > >> > wrote: > > > >> > > > > > >> > >> Yes actually there are updates: > > > >> > >> - Flexmojos now works with the new mavenized fdks > > > >> > >> - I removed a lot of legacy stuff, that made flexmojos depend > on > > > >> > >> flex 2 and flex 3 from Adobe > > > >> > >> - The testsuite is now 100% green and I wanted to commit those > > > >> > >> changes > > > >> > as > > > >> > >> soon as I had the time to review the changes again (will > probably > > > >> > >> be a > > > >> > very > > > >> > >> large commit) > > > >> > >> - As soon as that's out, I would need to somehow release the > > > >> > >> mavenizer > > > >> > so > > > >> > >> I can deploy the libs to Apaches Central Maven Repo (I still > want > > > >> > >> to do > > > >> > one > > > >> > >> change before triggering this release) > > > >> > >> - As soon as the mavenizer is released, we could discuss > > releasing > > > >> > >> an Apache Flex SDK as Maven artifacts, by running the Mavanizer > > > >> > >> against the rellease version and using the Mavenizers deployer > to > > > >> upload everything. > > > >> > >> - After that's done I can use those libs from Flexmojos and > > > >> > >> implement > > > >> > the > > > >> > >> last step needed to auto-download and mavenize Flex and Air > > > >> artifacts. > > > >> > >> > > > >> > >> So I would state that the technical difficulties have been > > solved, > > > >> > >> all I need to do is implement one further module for Flexmojos > > that > > > >> > >> simply integrates a call to the mavenizer from a maven build. > The > > > >> > >> rest is just paperwork ;-) > > > >> > >> > > > >> > >> Chris > > > >> > >> > > > >> > >> > > > >> > >> ________________________________________ > > > >> > >> Von: Maxim Solodovnik <[email protected]> > > > >> > >> Gesendet: Dienstag, 24. Juni 2014 13:14 > > > >> > >> An: [email protected] > > > >> > >> Betreff: Re: AW: flexmojos-maven-plugin: building flex project > > > >> > >> without mavenizing Flex binaries > > > >> > >> > > > >> > >> Hello Chris, > > > >> > >> Any updates on this issue? > > > >> > >> > > > >> > >> > > > >> > >> On 30 May 2014 22:54, Maxim Solodovnik <[email protected]> > > > wrote: > > > >> > >> > > > >> > >> > Thanks for the update :) > > > >> > >> > Also will have a vacation (hopefully) Please let me know if > you > > > >> > >> > need any help with testing :) > > > >> > >> > > > > >> > >> > > > > >> > >> > On Fri, May 30, 2014 at 10:50 PM, Christofer Dutz < > > > >> > >> > [email protected]> wrote: > > > >> > >> > > > > >> > >> >> Well currently I'm a little consumed with other tasks. I did > > do > > > >> > >> >> a > > > >> > >> little > > > >> > >> >> testing in building Flexmojos with the new FDKs and it > seems I > > > >> > >> >> will > > > >> > >> have to > > > >> > >> >> do a little more tweaking of the generated poms (It seems I > > will > > > >> > >> >> have > > > >> > >> to > > > >> > >> >> generate the dependency management stuff into a new pom > > similar > > > >> > >> >> to > > > >> > the > > > >> > >> way > > > >> > >> >> I initially did it). > > > >> > >> >> But I doubt I'll be able to finish this this week and then > I'm > > > >> > >> >> going > > > >> > to > > > >> > >> >> be on vacation ... so stay tuned, but don't expect something > > > >> > >> >> useable > > > >> > >> in the > > > >> > >> >> next 2-3 Weeks. > > > >> > >> >> > > > >> > >> >> Chris > > > >> > >> >> > > > >> > >> >> > > > >> > >> >> -----Ursprüngliche Nachricht----- > > > >> > >> >> Von: Maxim Solodovnik [mailto:[email protected]] > > > >> > >> >> Gesendet: Freitag, 30. Mai 2014 16:55 > > > >> > >> >> An: [email protected] > > > >> > >> >> Betreff: Re: AW: flexmojos-maven-plugin: building flex > project > > > >> > without > > > >> > >> >> mavenizing Flex binaries > > > >> > >> >> > > > >> > >> >> Hello Chris, > > > >> > >> >> > > > >> > >> >> Not sure if it is good idea to ask such often .... > > > >> > >> >> but, what are the news? :) > > > >> > >> >> > > > >> > >> >> > > > >> > >> >> On Fri, May 16, 2014 at 10:11 PM, Maxim Solodovnik < > > > >> > >> [email protected]> > > > >> > >> >> wrote: > > > >> > >> >> > > > >> > >> >> > Thanks for the update Chris :) Looking forward to test it > :) > > > >> > >> >> > > > > >> > >> >> > > > > >> > >> >> > On Fri, May 16, 2014 at 3:54 AM, Christofer Dutz < > > > >> > >> >> > [email protected]> wrote: > > > >> > >> >> > > > > >> > >> >> >> Hi Maxim, > > > >> > >> >> >> > > > >> > >> >> >> Well I re-wrote the Mavenizer to mavenize, Air, Flash and > > > Flex > > > >> > >> >> >> seperately (developer branch). > > > >> > >> >> >> Will have to write some missing glue-code to fetch > > artifacts > > > >> from > > > >> > an > > > >> > >> >> >> url and mavenize that. > > > >> > >> >> >> After that I'll have to make sure Flexmojos runs on those > > > >> slightly > > > >> > >> >> >> different Maven artifacts. > > > >> > >> >> >> After that comes the PrepareMojo ... still a while to go > > ... > > > >> but > > > >> > I'm > > > >> > >> >> >> having some progress. > > > >> > >> >> >> > > > >> > >> >> >> Chris > > > >> > >> >> >> > > > >> > >> >> >> > > > >> > >> >> >> -----Ursprüngliche Nachricht----- > > > >> > >> >> >> Von: Maxim Solodovnik [mailto:[email protected]] > > > >> > >> >> >> Gesendet: Donnerstag, 8. Mai 2014 16:26 > > > >> > >> >> >> An: [email protected] > > > >> > >> >> >> Betreff: Re: AW: flexmojos-maven-plugin: building flex > > > project > > > >> > >> >> >> without mavenizing Flex binaries > > > >> > >> >> >> > > > >> > >> >> >> Hello Christofer! > > > >> > >> >> >> > > > >> > >> >> >> any news on this? :) > > > >> > >> >> >> > > > >> > >> >> >> > > > >> > >> >> >> On Wed, Apr 30, 2014 at 2:30 PM, Christofer Dutz > > > >> > >> >> >> <[email protected]>wrote: > > > >> > >> >> >> > > > >> > >> >> >> > Well actually Alex and I have discussed that I will be > > > >> > >> implementing > > > >> > >> >> >> > the following solution: > > > >> > >> >> >> > > > > >> > >> >> >> > We will be deploying Apache Flex without any AIR or > Flash > > > >> > >> artifacts. > > > >> > >> >> >> > But we will be gerating some dummy artifacts > > > >> > >> >> >> > org.apache.flex.runtime.flash or > > > org.apache.flex.runtime.air > > > >> in > > > >> > >> >> >> > which the user references the desired flash or air > > runtime > > > >> > >> version. > > > >> > >> >> >> > In the Prepare Mojo I will be cheking if for every > > > >> > >> >> >> > org.apache.flex.runtime.flash a matching > com.adobe.flash > > > and > > > >> > >> >> >> > org.apache.flex.runtime.air a matching com.adobe.air > > > >> artifact is > > > >> > >> >> >> > present in the build. If not, it tries to download the > > > >> artifact > > > >> > >> >> >> > from a remote repository. If this is not possible it > > > outputs > > > >> > some > > > >> > >> >> >> > license text and asks the user if he accepts. If he > does, > > > it > > > >> > >> >> >> > downloads the corresponding binary blob (as defined in > > the > > > >> > config > > > >> > >> >> >> > script of our new > > > >> > >> >> >> > installer) and then executes the mavenizer part to > create > > > the > > > >> > >> >> >> > missing artifacts. Then a dynamic reference to these > > > >> artifacts > > > >> > is > > > >> > >> >> >> > added to the build. > > > >> > >> >> >> > > > > >> > >> >> >> > This way any user has to accept the Adobe license > > Agreement > > > >> and > > > >> > >> >> >> > after accepting he can deploy the Adobe artifacts to > his > > > >> > companies > > > >> > >> >> maven repo. > > > >> > >> >> >> > The other team-users (and the ci server) would now be > > able > > > to > > > >> > >> >> >> > automatically download these artifacts from now on > > without > > > >> > having > > > >> > >> >> >> > to ask someone to accept the license. > > > >> > >> >> >> > > > > >> > >> >> >> > All I all I want to create this functionality in a way > > > that I > > > >> > can > > > >> > >> >> >> > easily use that in Flexmojos as well as the new Apache > > Flex > > > >> > Plugin > > > >> > >> >> >> > I started working on a while ago. > > > >> > >> >> >> > > > > >> > >> >> >> > So far what we have planned. > > > >> > >> >> >> > > > > >> > >> >> >> > Chris > > > >> > >> >> >> > > > > >> > >> >> >> > > > > >> > >> >> >> > ________________________________________ > > > >> > >> >> >> > Von: Simon Morvan <[email protected]> > > > >> > >> >> >> > Gesendet: Dienstag, 29. April 2014 21:46 > > > >> > >> >> >> > An: [email protected] > > > >> > >> >> >> > Betreff: Re: AW: flexmojos-maven-plugin: building flex > > > >> project > > > >> > >> >> >> > without mavenizing Flex binaries > > > >> > >> >> >> > > > > >> > >> >> >> > Le 29/04/2014 09:59, Christofer Dutz a écrit : > > > >> > >> >> >> > > - Publish a release of Apache Flex to Apaches Maven > > Repo > > > >> > >> >> >> > > > > > >> > >> >> >> > > And then you'd be able to build Apache Flex projects > > > >> without > > > >> > >> >> >> > > having to > > > >> > >> >> >> > mavenize anything yourself. > > > >> > >> >> >> > Including airglobal, playerglobal and the like ... ? > > > >> > >> >> >> > There would be provided on an adobe repository or the > > would > > > >> > allow > > > >> > >> >> >> > us to host those binary blobs ? > > > >> > >> >> >> > > > > >> > >> >> >> > > > >> > >> >> >> > > > >> > >> >> >> > > > >> > >> >> >> -- > > > >> > >> >> >> WBR > > > >> > >> >> >> Maxim aka solomax > > > >> > >> >> >> > > > >> > >> >> > > > > >> > >> >> > > > > >> > >> >> > > > > >> > >> >> > -- > > > >> > >> >> > WBR > > > >> > >> >> > Maxim aka solomax > > > >> > >> >> > > > > >> > >> >> > > > >> > >> >> > > > >> > >> >> > > > >> > >> >> -- > > > >> > >> >> WBR > > > >> > >> >> Maxim aka solomax > > > >> > >> >> > > > >> > >> > > > > >> > >> > > > > >> > >> > > > > >> > >> > -- > > > >> > >> > WBR > > > >> > >> > Maxim aka solomax > > > >> > >> > > > > >> > >> > > > >> > >> > > > >> > >> > > > >> > >> -- > > > >> > >> WBR > > > >> > >> Maxim aka solomax > > > >> > >> > > > >> > > > > > >> > > > > > >> > > > > > >> > > -- > > > >> > > WBR > > > >> > > Maxim aka solomax > > > >> > > > > > >> > > > > >> > > > > >> > > > > >> > -- > > > >> > WBR > > > >> > Maxim aka solomax > > > >> > > > > >> > > > >> > > > >> > > > >> -- > > > >> WBR > > > >> Maxim aka solomax > > > >> > > > > > > > > > > > > > > > > -- > > > > WBR > > > > Maxim aka solomax > > > > > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
