[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [geclipse-dev] AWS Refactorings
|
Hi Moritz,
> What once was a monolithic implementation is now a
> flourishing basar of possibilites (metaphorically speaken). What we
ehy, what's wrong with you? too much coding until late? hahaha
> actually did was to take the static eu.geclipse.aws.ec2 implementation
> and extracted the generic aws portions (Vo concept, access credentials
> etc) and moved them into a base plugin eu.geclipse.aws. This foundation
great
> What does that mean for you? The best approach is to remove the existing
> projects eu.geclipse.aws.ec2* plugins from your workspace and check out
> the new implementation:
>
> - eu.geclipse.aws
> - eu.geclipse.aws.ui
> - eu.geclipse.aws.test
> - eu.geclipse.aws.ec2
> - eu.geclipse.aws.ec2.ui
> - eu.geclipse.aws.ec2.test
>
> Make sure that you have removed the old eu.geclipse.aws plugins (hosted
please mention which ones have to be checked out from SVN, which ones from
CVS, and tell me or Markus to move away (in CVS/SVN) the ones which are
not used anymore.
Please notice that there is no need to delete/re-checkout plugins which
keep the name and stay in the same version control system (like and .ec2?)
> in svn) which contain the s3 implementation. The s3 have been renamed to
> eu.geclipse.aws.s3 (as pointed out in last weeks mails). Migration of
> the s3 implementation to the new architecture has not started yet but is
> high on our list.
is that part (ie, S3) still functioning correctly after the latest changes?
i hope... :) otherwise it would be baaaaad release-wise
Cheers, Ariel