Maven is a project build management software, it means it Let's you define your project dependencies, features, and behaviors. To do this, Maven downloads plugins and dependencies for various online repositories. People who want to share their libraries, develop using Maven and upload the binaries in a repository. In this article, we’ll discuss how to configure and use Maven dependency.
\nPrerequisites:
\nInstall the Maven support for Eclipse (m2e)
\nMost Eclipse downloads include the Maven tooling already. If it is missing in your installation, you can install it via the main update of your release via Help > Install New Software. The following listing contains the update site for the Neon release and an update site maintained by the m2e project.
\nFor the usage of Maven for Java projects, you only need the m2e component. For Java web development you also want the m2e-wtp entry.
\nDownload the Maven index
\nBy default, the Maven tooling does not download the Maven index for the Eclipse IDE. Via the Maven index, you can search for dependencies, select them and add them to your pom file. To download the index, select Windows > Preferences > Maven and enable the Download repository index updates on startup option.
\nAfter changing this setting, restart Eclipse. This triggers the download of the Maven index. You may want to remove this flag after restarting to avoid network traffic at every start of Eclipse.
\nCreate Maven project
\nCreate a new Maven project via File > New > Other… > Maven > Maven Project.
\nOn the first wizard page, you can select if you want to create a simple project.
\nAfter creating the Maven project, a pom.xml is generated. You can find the file in Project Explorer. A Project Object Model or POM is the fundamental unit of work in Maven. It is an XML file that contains information about the project and configuration details used by Maven to build the project. It contains default values for most projects.
\nNow, you can add a dependency in pom.xml. For example, if you want to add LoginRadius for Java library/dependency, you can add as follows:
\n<dependencies>\n <dependency>\n <groupId>com.loginradius.sdk</groupId>\n <artifactId>java-sdk</artifactId>\n <version>11.0.0</version>\n </dependency>\n ......\n</dependencies>You should now be able to quickly import any libraries that you want o use in your project via Maven.
\n","frontmatter":{"date":"July 11, 2017","updated_date":null,"title":"Maven Dependency in Eclipse","tags":["Java","Maven","Eclipse"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/2d5127407846f33b1b7073695bd669d7/ee604/maven.png","srcSet":"/static/2d5127407846f33b1b7073695bd669d7/69585/maven.png 200w,\n/static/2d5127407846f33b1b7073695bd669d7/497c6/maven.png 400w,\n/static/2d5127407846f33b1b7073695bd669d7/ee604/maven.png 800w,\n/static/2d5127407846f33b1b7073695bd669d7/f3583/maven.png 1200w,\n/static/2d5127407846f33b1b7073695bd669d7/e4d72/maven.png 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Giriraj Yadav","github":null,"avatar":null}}}},{"node":{"fields":{"slug":"/engineering/html5-limitation-in-internet-explorer/"},"html":"HTML 5 is the latest and greatest web technology, although it has some issues in some browsers which don’t have native support for the new HTML5 elements. If you want to support some of the older browsers which may still be in use such as IE8 and lower then you are going to have some trouble using HTML5.
\nThe problem with IE8 and lower versioned IE browsers is that they were created many years ago while HTML5 is new technology and HTML5 tags were newly invented so legacy browsers do not support them. Microsoft will not release any updates for these browsers because they have released new versions of the IE browser.
\nAs old IE browsers do not know about these tags then it can’t style them so you will find that in IE8 or lower your websites will be rendered without many styles.
\nIf you want HTML5s new tags to be supported in IE then you need to add some javascript to create the elements:
\nExample:
\n <script>\n document.createElement('header');\n document.createElement('article');\n document.createElement('aside');\n document.createElement('footer');\n </script>This is not a very good way, you would need to remember all the tags that you have set and include them on every page of your website. If you add any new tags then you need to add these tags on every page of the website as well. Thankfully Remy Sharp provided a solution for this, Remy Sharp has created a Javascript file which he hosts with google code that will handle this for you.
\nadd the following at the top of your pages and it will include this code file on your website if the end user is using an IE browser lower than version 9.
\n<!--[if lt IE 9]>\n<script src="https://html5shim.googlecode.com/svn/trunk/html5.js"></script>\n<![endif]-->IE also does not support some of the most useful new HTML5 methods that are supported by modern browsers:Window.postMessage()
\nWindow.postMessage
\nallows for sending data messages between two windows/frames across domains. Normally, scripts on different pages are allowed to access each other if and only if the pages that executed them are at the same locations with the same protocol (usually both http) and matching host names. The HTML5 postMessage function provides a great way to communicate securely and with high performance and reliability even cross-domain. Unfortunately, the HTML5 postMessage function does not work in IE
\nLet’s take a look at how Window.postMessage works:
\nThe below signature is used for postMessage:
\notherWindow.postMessage(message, targetOrigin);
\notherWindow\nA reference to another window; such a reference may be obtained, for example, using the contentWindow property of an iframe element, the object returned by window.open
\nmessage\nThis parameter is required for a message to be sent to the other window. The message is serialized using the structured clone algorithm. This means you can pass a broad variety of data objects safely to the destination window without having to serialize them yourself.
\ntargetOrigin\nWhen the message is dispatched, the current location of the target document is checked. If it does not match the specified URI, then the message will not be dispatched. This parameter can be useful if you want to be sure of the location of the target document before dispatching the message and you can also specify a literal string “*” (indicating no preference) or as a URI
\nbut always provide a specific targetOrigin, not *, if you know where the other window’s document should be located. If you do not set a specific location and use “*” then a malicious site can change the location of the window without your knowledge, and therefore it can intercept the data sent using the postMessage method.
\nExample for postMessage
\nSender
\nThe first part of the process is setting up a “source”. With the source, we will open a new window (or IFrame), send the new window message (in the our example, we’ll do so every 6 seconds, and create an event listener for any response we receive from the destination window.
\n//create popup window\nvar domain = 'https://www.example.com';\nvar myPopup = window.open(domain + '/postmessage.html','myWindow');\n//periodical message sender\nsetInterval(function(){\n var message = 'Hello! The time is: ' + (new Date().getTime());\n myPopup.postMessage(message,domain); //send the message and target URI\n},6000);\n \n//listen to back\n \nwindow.addEventListener('message',function(event) {\n if(event.origin !== 'http://scriptandstyle.com') return;\n console.log('received response: ',event.data);\n},false);I have used window.addEventListener which doesn’t work with Internet Explorer so use window.attachEvent
\nReceiver
\nIn the destination window we should validate the message origin and if it is not valid then we will not send the message to the sender, otherwise we send a response back to the sender:
\nwindow.addEventListener('message',function(event) {\n if(event.origin !== 'https://lrblogs.wpengine.com) return;\n event.source.postMessage('message received: ',event.origin);\n},false);sessionStorage
\nsessionStorage stores data for one session only, this is used in a single transaction it stores the data only for one session and as you close the window the session would be lost and the data is deleted when the browser is closed.
\nHTML5 sessionStorage object are shared in different tabs in the same browser session if you change a sessionStorage attribute’s value in one tab, that change should be reflected within another tab but in IE8 this system will not work properly it does not share sessionStorage objects between frames on a page. This issue has since been fixed in IE11.
\nExample:
\n//save a value\nsessionStorage.setItem("website", "https://www.example.com");\n//retrieve item\nvar website= sessionStorage.getItem("website");\n//remove the key\nsessionStorage.removeItem(“website”);localStorage
\nThe localStorage object stores the data like a persistent cookie, with no expiration date. The data will not be deleted when the browser is closed, and will be available when a user returns to the browser.
\nIE also supports localStorage from IE8 but it does not support localStorage in IE7 and previous versions.
\nlocalStorage Vs Cookies
\nExample
\n//save a value\nlocalStorage.setItem("Domain", "https://www.example.com");\n//retrieve item\nvar website= localStorage.getItem("website");\n//remove the key\nlocalStorage.removeItem(“website”);