Closed GoogleCodeExporter closed 9 years ago
This ClassCastException is not related to dependency resolution. When
dependency
resolution fails it throws a AbstractArtifactResolutionException.
Probably is some maven bug. What version are you using?
VELO
Original comment by velo...@gmail.com
on 25 Aug 2008 at 12:49
I use maven 2.0.9
Original comment by emmanuel...@gmail.com
on 25 Aug 2008 at 1:03
No idea...
I add you at gtalk, when you can ping me there.
VELO
Original comment by velo...@gmail.com
on 25 Aug 2008 at 1:06
fix checked in to r704. Can you test it?
Original comment by RedB...@gmail.com
on 25 Aug 2008 at 2:17
Now I get this:
Downloading:
http://repo1.maven.org/maven2/com/adobe/flex/framework/rpc/3.1.0.2710/rpc-3.1.0.
2710-fr_FR.rb.swc
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: com.adobe.flex.framework
ArtifactId: rpc
Version: 3.1.0.2710
Reason: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.adobe.flex.framework -DartifactId=rpc
-Dversion=3.1.0.2710 -Dclassifier=fr_FR -Dpackaging=rb.swc -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.adobe.flex.framework -DartifactId=rpc
-Dversion=3.1.0.2710 -Dclassifier=fr_FR -Dpackaging=rb.swc -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
com.adobe.flex.framework:rpc:rb.swc:3.1.0.2710
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
maven2-repository.dev.java.net (http://download.java.net/maven/2/),
archiva.accovia.internal (https://svn.ibiza.accovia.com/archiva/repository/internal/),
flex-mojos-repository (http://svn.sonatype.org/flexmojos/repository/),
archiva.accovia.snapshots (https://svn.ibiza.accovia.com/archiva/repository/snapshots/)
It is normal because this artifact doesn't exist, but I don't think it's the
good option.
A resource bundle artifact is optional (at least with 3.0.0.477, it worked), so
I
think it would be better to skip it if it doesn't exist (line 180 in
info.rvin.flexmojos.utilities.MavenUtils)
Original comment by emmanuel...@gmail.com
on 25 Aug 2008 at 3:40
Resource bundles are not optional. Did you do a copylocale on your sdk to get
the
fr_FR resources and then do a install-mojo:install-sdk?
I'm not sure why it worked on 3.0.0.477, unless you forgot that you installed
the
fr_FR resources manually yourself.
Original comment by RedB...@gmail.com
on 25 Aug 2008 at 5:16
Can you look in your local repository and see what was there before for rpc? It
should be in:
<user.home>/.m2/repository/com/adobe/flex/sdk/rpc/3.0.0.477/
Is there a rpc-3.0.0.477-fr_FR.swc?
Original comment by RedB...@gmail.com
on 25 Aug 2008 at 5:19
Before works, but, was a flex-mojos bug.
Prabably it worked at 2.0-alpha3 because flex-mojos inject all RB in all
compilation.
So, your fr_FR was using en_US resource bundles.
May be we should add resource chaining to flex-mojos....
Any thoughts?
Original comment by velo...@gmail.com
on 25 Aug 2008 at 5:41
With something like a warning?
WARNING: resource bundle not found for fr_FR, substituting en_EN in it's place
How would you do the substitution though? modify the dependency? create a tmp
locale in target and point to
it?
Original comment by RedB...@gmail.com
on 25 Aug 2008 at 6:52
I don't have rpc-3.0.0.477-fr_FR.swc in my local repo.
As Velo said, it worked before, but I don't think it was a bug in flex-mojos
but in
sdk 3.0.0.477. It works with FlexBuilder too that use for the moment sdk
3.0.0.477.
I tried to skip it with only a warning but it doesn't work with the following
message:
[ERROR] Inconsistant linkage in C:\Documents and
Settings\evenisse\.m2\repository\com\adobe\flex\framework\rpc\3.1.0.2710\rpc-3.1
.0.2710-en_US.rb.swc$locale/en_US/core.properties
- 'en_US$core_properties' is marked as extern, but 'fr_FR$core_properties' is
not.
About the substitution, I think the following process would work:
- add a warning about the substitution
- extract the en_US bundle in target
- open catalog.xml and replace all en_US strings by fr_FR
- create a new archive file with the modified content and point to it
Original comment by emmanuel...@gmail.com
on 26 Aug 2008 at 9:15
Why is it marked as fixed?
Original comment by emmanuel...@gmail.com
on 26 Aug 2008 at 9:45
Emmanuel: It works with FlexBuilder too that use for the moment sdk 3.0.0.477.
I curious how you are using. It shouldn't be working :D
Well don't try to threat rb.swc as optional. They are required and if not
informed
will got a compilation error. And if bad informed you can get applications half
en_US, half ja_JP or whatever.
To create a new resource bundle use copylocale. Or download it from internet:
http://ttfx.org/Tontons_Flexeurs/BabelFlex.html. But I'm not sure if this
project is
compatible with flex 3.1.
This issue was fixed. The original bug is already fixed and we are talking
about a
new problem.
Original comment by velo...@gmail.com
on 26 Aug 2008 at 11:37
Ok, thank you. I'll look at ttfx.org
Original comment by emmanuel...@gmail.com
on 26 Aug 2008 at 12:06
I had checked in all locales available at BabelFlex.
Enjoy.
Original comment by velo...@gmail.com
on 26 Aug 2008 at 12:06
Original issue reported on code.google.com by
emmanuel...@gmail.com
on 25 Aug 2008 at 11:56