|
|
|
[
Permlink
| « Hide
]
Trevor Baker - [03/11/08 03:15 PM ]
Deferred for now. Maybe for BlazeDS 4.
To help you and me out regarding this issue.
Here are a few ant scripts I developed yesterday to automatize and ease the creation of local and remote repository from a set of libraries. It comes with a blazeDS repository creation sample : http://www.jroller.com/francoisledroff/entry/create_your_maven_repository_from Note that this does not address the dependency configurations. A good start is Adobe create Coping guide, like what maven project did for sun jars:
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html VELO I really don't understand how such an issue can be deferred. It's obviously a quick win, since you know what libraries you depend on, you can easily write custom POMs for transitive dependencies and follow the standard procedure to upload those to the central repository.
And once that is done, it will be much easier for all Java developers using Maven to integrate BlazeDS in their developments! Until then, we're forced to tinker with local repositories. Until the flex engineering team deliver that, you may try out the repository created for my blazeds maven archetype project, see
* http://www.jroller.com/francoisledroff/entry/a_blazeds_xdoclet_spring_hibernate * http://blogs.adobe.com/francoisledroff/2008/05/my_blazeds_xdoclet_spring_hibe.html * http://code.google.com/p/fna/wiki/blazedsXdocletSpringHibernateMvnArchetype Sebastian is right. Do not defer this. Just do it. It should not be a big task at all. And it will help the adoption greatly!
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||