#java package

I demonstrated in my Packages Part 1 Tutorial that we could access a class from another package using its fully qualified name. However, it would get really old really fast if we had to type in the fully qualified name every time we used a class or its members from another package. The import statement comes to rescue! The import statement must reside after the package statement and before the class declaration. You can use the import statement in a couple of different ways. The structure for the statement looks like this: (import) (package.ClassName) (;) (import) (package.*) (;) // wildcard * imports all available classes

This month we are revealing a new marketing site, Java package view, and AWS Beanstalk support. First, we're proud to unveil a brand new design for our website. Besides delighting you with shiny colors, it better articulates the advantages behind a cloud IDE. Check it out and let us know what you think. Second, we've added a package view for Java projects. You'll can browse your files and see referenced libraries simply and beautifully. To try out the package view, go to Window > Show View > Package Explorer. Third, we've added Amazon Elastic Beanstalk as a deployment target. Enter your AWS credentials, choose your environment details, and boom! Deployed. We support the AWS SDKs so that you can do color syntax highlighting, auto complete, and debugging of those calls within Exo IDE (try stepping into an SDK API call - it works!). As always, you can run and debug the app in our development VM before deployment.  Last but not least, we've added management consoles for Amazon S3 buckets and EC2 instances allowing you to restart your instances or upload files to your buckets.  Try it out, tell your friends and join the conversation on our Facebook page, where you can share your feedback and feature requests - or drop us an email at [email protected]. Have fun coding in the cloud! Mark Downey Product Manager at Codenvy