[#BLZ-169] Prepare OSGi-ready versions of BlazeDS libraries to be deployed to SpringSource Enterprise Repository

BlazeDS

Prepare OSGi-ready versions of BlazeDS libraries to be deployed to SpringSource Enterprise Repository

Created: 05/09/08 05:38 PM Updated: 05/14/08 02:37 PM

Component/s:

Installation

Security Level:

Public (All JIRA Users )

Severity:	Usability Issue
Reproducibility:	Every Time
Discoverability:	Medium
Found in Version:	BlazeDS 3.0.2
Affected OS(s):	All OS Platforms
Steps to Reproduce:	« Hide It would be really great if BlazeDS libraries could be repackaged as OSGi-ready bundles and deployed to http://www.springsource.com/repository/app/ You can even use the same libraries to deploy them in central Maven repository (see http://bugs.adobe.com/jira/browse/BLZ-71) Show » It would be really great if BlazeDS libraries could be repackaged as OSGi-ready bundles and deployed to http://www.springsource.com/repository/app/ You can even use the same libraries to deploy them in central Maven repository (see http://bugs.adobe.com/jira/browse/BLZ-71)
Language Found:	English
Bugbase Id:	none
QA Owner:	hsee
Resolved by:	Trevor Baker
Participants:	hsee, Jack Rudnick, Sebastien Arbogast and Trevor Baker
Browser:	Firefox 2.x
JDK:	Sun JDK 5
Application Server:	Apache Tomcat 6.x

All

Comments

Sort Order:

[ Permlink | « Hide ]

Trevor Baker - [05/13/08 03:07 PM ]

deferred for now

[ Permlink | « Hide ]

Jack Rudnick - [05/14/08 02:37 PM ]

Why is this deferred? It seems like an important task that should at least be explained for why it would be deferred. Also, it looks like even if we wanted to put together our own "BlazeDS" bundle, we'd be hand-tied because of the use of Class.forName(type) (i.e. in places like FactorySettings.java).