 |
History
| Log In
|
|
|
|
[
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!
What's the hold up here? This will only help to further the quality of Flex/AIR + Blaze + [insert framework/platform here] applications/development and bring some much needed credibility to the Adobe Technology Platform.
Another vote for this for the same reasons mentioned above. This likely wouldn't take someone more than a day to do but would make the life of so many developers a lot easier.
Resolved, yet Deferred? The priority isn't LOW -- look at the votes!
There are still jar files missing from the central repository.
The two missing artifacts are messaging-opt and messaging-proxy. Will these be placed in the public repository? Best Regards, Richard L. Burton III Still annoying that you cannot fix this simple issue. In the enterprise world it is not always so simple to advocate using other repositories or even getting custom libraries installed. It would be very helpful to have the libraries available in an official repository, which would inerently make it easier for me to convince the deciders that it's usable in the overly enterprisy solutions we develop on.
C'mon guys! This would provide a huge boost for the project and its supporters. As others have mentioned - this is a quick win and requires very minimal effort. I think you'd be surprised by the number of developers using Maven with their projects.
Also, how is the issue resolved if has been deferred? Perhaps I don't understand your issue management workflow process/steps - is there a guide posted somewhere? I think that's not more to say... I don't understand how it's deffered yet...
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Resolved
D
Put BlazeDS WAR and libraries in a public Maven repository