Introducing Spring Actionscript in our project revealed two problems with the Maven dependency management, that are pretty hard to tackle down. The problems are not restricted to neither Spring Actionscript nor Flex, but can arise with any new dependency that you introduce to you Maven build.
-
Denial-of-service Attacks Are on the Rise, Anti-DDoS Vendors Report
-
Apple intern's thesis leaks secret project to port Mac OS X to ARM processors
-
video - Getting started with OpenShift, the first Java EE 6 PaaS from JBoss
-
A little bit of qUnit
-
Performance - Using .Net and COM
-
Got REST? Build HTML5 Mobile App
Comments
Adam Leggett replied ago:
Good blog post. Just a couple of points - the distributionManagement has been around for a while and although you are using a custom repo it does relate to a known issue with Maven (http://jira.codehaus.org/browse/MEV-643). In the past to resolveproblems like this I have built an 'internal version' of a library from source and modified the pom appropriately before releasing/deploying it, but its an ugly fix really.
CarstenSchlipf replied ago:
Thank you this info. Glad to hear that there is a Bug report. I would wish that external dependency resolution via distributionManagement could be disabled by a setting in .m2/settings.xml or at least through a switch for the mvn command. But I haven't found anything yet.
Also I still do not know, why the external repo was not contacted with 2.0.9, but suddenly is with 2.2.1.
Voters For This Link (13)
Voters Against This Link (0)