Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [geclipse-dev] MyProxy packaging

Maybe we should generally remove the VOMS stuff from the gLite plug-ins since VOMS is not only gLite?! VOMS does only depend on bouncycastle but should not depend on any gLite library if I remember correctly.

Cheers, Mathias


-----Ursprüngliche Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx im Auftrag von Ariel Garcia
Gesendet: Do 04.06.2009 12:19
An: geclipse-dev@xxxxxxxxxxx
Betreff: [geclipse-dev] MyProxy packaging
 
Hi Thomas, all,

as you have seen in the previous email the eu.geclipse.myproxy{,.ui} 
plugins are now in the build.

As they depend on e.g.voms i've added them to the glite-feature which is 
IMHO not ideal, because plain Globus would also benefit from it.

On the other hand the plugins are both very small, it doesn't make sense to 
separate them even more in myproxy, myproxy.voms, etc.

My suggestion would be to integrate the MyProxy functionality in the main 
e.g.globus and e.g.voms plugins, where the e.g.globus.myproxy pieces would 
provide an extension point for the  e.g.voms.myproxy to register. 

What do you think, or do you have a better refactoring proposal?

Cheers, Ariel

_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev



Back to the top