History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: BLZ-71
Type: Task Task
Status: Resolved Resolved
Resolution: Deferred
Priority: D D
Assignee: hsee
Reporter: Sebastien Arbogast
Votes: 22
Watchers: 11
Operations

If you were logged in you would be able to see more operations.
BlazeDS

Put BlazeDS WAR and libraries in a public Maven repository

Created: 03/02/08 09:00 AM   Updated: 05/24/08 03:00 PM
Component/s: Installation
Security Level: Public (All JIRA Users )

Severity: Usability Issue
Found in Version: BlazeDS 3.0.1
Affected OS(s): All OS Platforms
Steps to Reproduce:
It would be great if BlazeDS was available in a public Maven repository, either an official one or an Adobe-specific one.

The WAR would be a minimum to use Maven WAR overlay feature. Individual libraries would be a bonus.

Everything is explained here:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
 
Language Found: English
Bugbase Id: none
QA Owner: hsee
Resolved by: Trevor Baker
Participants: François Le Droff, hsee, Marvin Froeder, Per Olesen, Sebastien Arbogast and Trevor Baker
JDK: Sun JDK 5
Application Server: Apache Tomcat 6.x


 All   Comments      Sort Order:
Trevor Baker - [03/11/08 03:15 PM ]
Deferred for now. Maybe for BlazeDS 4.

François Le Droff - [04/30/08 12:07 PM ]
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.


Marvin Froeder - [04/30/08 12:43 PM ]
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

Sebastien Arbogast - [05/09/08 05:36 PM ]
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.


Per Olesen - [05/24/08 03:00 PM ]
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!