Andrew Phillips

Note that for e.g. EC2 [RunningInstance](https://github.com/jclouds/jclouds/blob/master/apis/ec2/src/main/java/org/jclouds/ec2/domain/RunningInstance.java) already has `launchTime` information. Initial questions from me would be: - which clouds specifically do you need this information for? - for these clouds,...

> EC2, OpenStack Nova and CloudStack all have a launch time Seems like the current "big guns", indeed... ;-) Do we do `@Nullable launchTime` or `Optional launchTime` in `NodeMetadata` nowadays?...

Hi Stephen > Just looking for any kind of update. Adrian will certainly be better placed to give a definitive update - just wondering whether you've had a chance to...

> current release of that doesn't work with the newest release of this Ack. Sorry to hear, Stephen. @abayer: I see a patch to [upgrade to 1.5.8](https://issues.apache.org/jira/browse/WHIRR-708). Is there a...

See also https://github.com/jclouds/jclouds/issues/1469. I'm guessing option 2 would help address that too.

> @demobox thoughts? Not done all that much with Java proxying lately so this is not an "expert opinion". But based on the comments it certainly seems like a good...

Hi Giovanni It looks like the wrong parsing method is being called. `iso8601DateParse` is fine with the following input: ``` new SimpleDateFormatDateService().iso8601DateParse("2013-02-14T17:53:20.000+0100"); ``` (note the milliseconds) but does indeed not...

> I've tryed patching OpenNebula to return milliseconds too, and my code works as expected. Glad to hear things work, at least. And given the specification you refer to, the...

@iocanel Any OSGi imports in there that could be simplified with `*` expressions? And could this be included in any automatic generation or would it require hand-tuning?

> All the rest of the existing code is only affected by using annotations. I'm sure we could spend many long hours on fun conversations about current Java usage of...