AW: [rap-dev] Cyclical Dependency in Upload Widget and Demo

["Stefan Roeck" <Stefan.Roeck@xxxxxx>]

Hi Elias,

you're right, this cyclic dependency is awful. Your proposal is possible. However, the current two projects have the advantage that someone just has to download them and can test the upload widget without caring about which other bundles are needed (in which versions, etc). Additionally, the demo project will probably never be used in production environment, so it's up to the developer to have a clean dependency graph within its application.

What do you think?
Regards,
Stefan.

-----Ursprüngliche Nachricht-----
Von: rap-dev-bounces@xxxxxxxxxxx [mailto:rap-dev-bounces@xxxxxxxxxxx] Im Auftrag von Volanakis, Elias
Gesendet: Donnerstag, 19. Juni 2008 21:16
An: RAP project development-related communication
Betreff: [rap-dev] Cyclical Dependency in Upload Widget and Demo

Hi,

I've been experimenting with the Upload Widget and Demo in the sandbox.
Thanks for making these available.

However there is a cyclical dependency between the upload widget project
(consuming apache.commons.{fileupload,io}) and the upload widget demo
(providing apache.commons.{fileupload,io}; requiring the upload widget).

I propose to fix this by using the plugins from orbit instead
(org.apache.commons.fileupload v1_2 and org.apache.commons.io v_1_3_2)
and delete the libs from the widget demo project. 

Let know if there is any reason not to do that. I noticed that the io
library provided was v1_4; however the widget seems to work with v1_3_2
as well.

Thanks,
Elias.

PS: I know we are in a ramp down phase, but AFAIK the sandbox is not
part of the release.
_______________________________________________
rap-dev mailing list
rap-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rap-dev