Hi,
To build successfully 6.X branch i had to install flexunit manually in
local repo
mvn install:install-file -DartifactId=flexunit -DgroupId=org.flexunit
-Dversion=4.1.0 -Dpackaging=swc -Dclassifier=flex4
-Dfile=flexunit-4.1.0-8-flex_
4.1.0.16076.swc
mvn install:install-file
ok, I'll post it there,
thank you
ciao
pigiuz
On Tuesday, January 15, 2013 6:55:29 PM UTC+1, Christofer Dutz wrote:
Thanks for that input. As the mavenizer is an Apache flex tool, I would
suggest to post this to the Apache flex mailinglist. In general I created
the tool to generate to an
I couldn't get further with flexmojos 6.x, I didn't find any example pom so
I gave up for now and sticking my builds on flexmojos 4.2.
as far as I know mavenizer tool should solve your problem but I couldn't
get any pom working.
so the solution I see in the short term is sticking to your current
There is conflict between the Apache Flex SDK Mavenizer and Flexmojos6.()
While the Mavenizer isn't adding a classifier when mavenizing the theme
swc, FlexMojos6 is expecting the classifier theme.
I solved the problem by changing the net.flexmojos.oss.plugin.compiler.
AbstractFlexCompilerMojo
FlexUnit 4 isn't available as maven artifact. You have to download it and
install in your maven repository.
Patrick
Am Sonntag, 20. Januar 2013 18:55:34 UTC+1 schrieb Sylvain Lecoy:
Now I need to resolve org.flexunit:flexunit:swc:flex4:4.1.0. :-)
Any pointers ?
Le vendredi 18 janvier
@Piergiorgio Niero
Thank you man! Are you compiling with AIR? If yes, any chance you could
share an example pom.xml or zipped project example?
Kind regards, adq
On Monday, January 14, 2013 10:05:46 AM UTC-5, Piergiorgio Niero wrote:
Ok, I created a skinny recap of my experience so far with
to resolve spark theme artifact :
dependency
groupId${flex.groupId}.framework.themes/groupId
artifactIdspark/artifactId
version${flex.version}/version
typeswc/type
scopetheme/scope
/dependency
and for flexunit :
dependency
groupIdorg.flexunit/groupId
artifactIdflexunit/artifactId
Hi Sylvain,
Yes, I renamed spark theme as you to pass this step.
And I took flexunit from here:
https://www.escidoc.org/artifactory/repo/org/flexunit/flexunit/4.1.0/
Plus I removed some Integration Tests, I mean AIR and some previous
versions of flex.
So I've succeeded with 4.6.0.23201 version,
Hello guys,
Let me introduce myself quickly: I am working with Flex since 3 years and
Flexmojos since 2 years. I have been successfully compiling, testing and
running project on jenkins/hudson from Flex framework 3.5 to 4.6. What I
always found really annoying was the really bad integration of
Oh ... just saw that you allready did ... the binaries are available at:
https://oss.sonatype.org/content/groups/staging/org/flexunit/flexunit/4.1.0/
I think they should also find their way to the repo1.maven.org, but don't
know how long this will take.
Chris
2013/1/21 Christofer Dutz
I deployed the flexunit binaries in 3 flavours. flex4, flex3 and as3 so you
need a classifier pulling in the flex4 version.
Chris
2013/1/20 Sylvain sylvain.le...@gmail.com
Now I need to resolve org.flexunit:flexunit:swc:flex4:4.1.0. :-)
Any pointers ?
Le vendredi 18 janvier 2013 16:17:11
Ok, this one was actually easy: just navigate to http://flexunit.org,
download the 4.1.0-SDK in the Download section.
Open the archive and move the flexunit-4.1.0-8-flex_4.1.0.16076.swc file to
.m2/repository/org/flexunit/4.1.0/flexunit-4.1.0.swc
Le dimanche 20 janvier 2013 18:55:34 UTC+1,
Hi Sylvain,
Current'y, I'm also working on a new m2e connector for FlashBuilder and
FlexMojos and hope to release the connector this weekend.
My m2e connector supports the synchronization of the settings of the pom.xml
with the Flash Builder settings (Flash Builder 4, 4.5, 4.6, 4.7),
The problem is that usually the Air Version is tightly coupled with the
flex version. So as far as I know it's usually not possible to build Air
applications with other versions than the one shipped with the FDK. The
mavenizer now did a first step to decouple this. Unfortunately I never
built any
Cool stuff :-) Thanks for your work :-)
Thing is that probably most people tend to leave the Eclipse path when it
comes to big Maven projects. A short statement that put's says everything
with only few words: Life's too short to use Eclipse ;-) But I think good
support for Eclipse would certainly
@Patrick ... yes ... creating a pull request would be the best way to go.
@Patrick ... Flexunit 4.1 is available ... I deployed the lib to sonatype
myself.
2013/1/21 Sylvain sylvain.le...@gmail.com
Ok, this one was actually easy: just navigate to http://flexunit.org,
download the 4.1.0-SDK in
+1 !
On Monday, January 21, 2013 10:40:42 AM UTC+1, Sylvain Lecoy wrote:
Hello guys,
Let me introduce myself quickly: I am working with Flex since 3 years and
Flexmojos since 2 years. I have been successfully compiling, testing and
running project on jenkins/hudson from Flex framework
No I'm not thinking about it ... I'm actually working on it.
Unfortunately I haven't got much further than setting up a rudimentary
project and linking in dummy mojos into the build lifecycle as I'm
currently swamped with other work. But as soon as this swamp is dried out,
I will concentrate on
Why don't you move flexmojos there and just add falcon?
There is a ton of work on FM code...
On Jan 23, 3:02 pm, Christofer Dutz christofer.d...@gmail.com wrote:
No I'm not thinking about it ... I'm actually working on it.
Unfortunately I haven't got much further than setting up a rudimentary
2013/1/23 Marvin Froeder velo...@gmail.com
Why don't you move flexmojos there and just add falcon?
Well because it's a pretty messy thing to support both groupIds
(com.adobe.flex and org.apache.flex) ... I doubt there could be a clean
solution for supporting both ... hence there would be a
Well, you can remove whatever you don't wanna, so apache FM has not
support for com.adobe stuff and if it gives me no headaches, where
do I sign?
On Jan 23, 3:33 pm, Christofer Dutz christofer.d...@gmail.com wrote:
2013/1/23 Marvin Froeder velo...@gmail.com
Why don't you move flexmojos
Just contact the guys from the Flex dev list. I think donating so much code
might require more than the usual stuff ... and I don't know if it is that
easy to donate FM as there seem to be several classes that were written by
others and I don't know if you can donate their stuff (Just judging from
Factually, I'm not certain of this:
The problem is that usually the Air Version is tightly coupled with the
flex version.
...as we could customize the Flex sdk by overwriting the AIR files
distributed within the Flex framework with the AIR sdk of your choice, etc.
Moreover, Adobe has
23 matches
Mail list logo
