Hi guys,
To resolve the build failure caused by Bad Request, verify that the
configuration of your hosted repository allow artifacts redeploy.
Regards,
Morgan.
--
--
You received this message because you are subscribed to the Google
Groups Flex Mojos group.
To post to this group, send email to
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
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
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,
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,
@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
Now I need to resolve org.flexunit:flexunit:swc:flex4:4.1.0. :-)
Any pointers ?
Le vendredi 18 janvier 2013 16:17:11 UTC+1, Sylvain a écrit :
I can confirm that I got the same exception as Anton.
Did not find the string classifiertheme/classifier among all POMs.
Le vendredi 11 janvier 2013
Hi there,
Here is my early feedback on the mavenizer :)
1 - I successfully generated sdk 4.6.0, and 4.9.0 with the SDKGenerator
class. I created an eclipse command Executes a Java Application, with a
jdk1.7.0 as JRE. The command line arguments was: sdkhome sdktarget.
Here is the content of my
Le vendredi 11 janvier 2013 12:03:53 UTC+1, Christofer Dutz a écrit :
Try removing the classifiertheme/classifier
Chris
2013/1/11 Anton Eryemenko eldes...@gmail.com javascript:
spark-4.6.0.23201.swc
--
You received this message because you are subscribed to the Google
Groups Flex
I can confirm that I got the same exception as Anton.
Did not find the string classifiertheme/classifier among all POMs.
Le vendredi 11 janvier 2013 11:45:02 UTC+1, Anton Eryemenko a écrit :
Hi Chris, Many thanks for your work.
I'm trying to relocate from FlashBuilder to IntelJ IDEA and
Try removing the classifiertheme/classifier
Chris
2013/1/11 Anton Eryemenko eldest@gmail.com
spark-4.6.0.23201.swc
--
You received this message because you are subscribed to the Google
Groups Flex Mojos group.
To post to this group, send email to flex-mojos@googlegroups.com
To
Le vendredi 9 novembre 2012 11:15:54 UTC+1, Christofer Dutz a écrit :
Hi guys,
[...]
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
The error i get is the following:
java.lang.NoClassDefFoundError:
org/apache/commons/compress/compressors/gzip/GzipCompressorInputStream
So it seems the GzipCompressorInputStream is not available in the
mavenizer.jar.
Den tirsdag den 27. november 2012 12.09.57 UTC+1 skrev Christofer Dutz:
Regarding the other two errors ... do you have any more output? I sort of
can't see the problem as the commandline seemt to be valid. Are you only
generating one FDK? or are these the only ones causing problems? Are you
eventually using a 64bit Java 7 VM? I had to install a 32bit VM just in
oder
Hi, Chris!
My first error is:
Exception in thread main java.lang.NoClassDefFoundError:
org/apache/commons/compress/compressors/gzip/GzipCompressorInputStream
at air.AirRuntimeGenerator.processFlashRuntime(AirRuntimeGenerator.java:139)
at
I think I know the problem. The lib is built using Maven and therefore
would require Maven to provide the dependencies. In your case
GzipCompressInputStream is missing and therefore you are getting that
error. What I really found a little strange is that I have no problem at
all running the thing,
The error i get is the following:
Exception in thread main java.lang.NoClassDefFoundError:
org/apache/commons/compress/compressors/gzip/GzipCompressorInputStream
at air.AirRuntimeGenerator.processFlashRuntime(AirRuntimeGenerator.java:139)
at
Hi Christofer!
Checking out your latest changes (fixing the directory path problem) and
including my fix for the above mentioned class not found exception (using
the shade maven plugin), i'm able to generate almost the entire framework
(paths are generated correctly now for the compiler part
Well the plugin is built using maven and I currently get the 3 dependencies
from default repos. So as soon as the build ran, there should not be any
CNFEs. What classes is ist complaining about? I don't want to bundle third
party artifacts if this is not needed. And Apache explicitly prohibits
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
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
Ok ... so I just setup my SVN access and fixed the path problem for the
compiler artifacts on non-windows machines. @netphreak ... could you please
give this a try? ... When updating the empty zip code I got 0-byte zips
instead of 22byte zips. The 22byte ones are actually real zip files, the
0byte
26 matches
Mail list logo
