Your Liferay console output shows your plugin deploying. It looks like this:
INFO: Deploying web application directory [liferay version]\[tomcat version]\webapps\sample-portlet
INFO [pool-2-thread-2][HotDeployImpl:178] Deploying sample-portlet from queue
INFO [pool-2-thread-2][PluginPackageUtil:1033] Reading plugin package for sample-portlet
Note: If you get the following error after executing mvn liferay:deploy, make sure you’re executing the command from your plugin’s directory (e.g., sample-portlet).
[ERROR] No plugin found for prefix 'liferay' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\cdhoag\.m2\repository), central (http://repo.maven .apache.org/maven2)] -> [Help 1]
If you’re deploying the plugin to a release or snapshot repository, specify the repository by adding a distribution management section to your plugin’s pom.xml.
Here’s an example distribution management section for a snapshot repository:
The proper contents for your <distributionManagement> element can be found in the Summary tab for each of your repositories.
Since you created the plugin as a snapshot, you’ll have to deploy it to a snapshot repository. You can deploy a plugin as a release, but the plugin’s POM must specify a valid release version (e.g., <version>1.0</version>), not a snapshot version (e.g., <version>1.0-SNAPSHOT</version>).
Deploy your plugin into your specified Nexus repository:
Note: There are three build phases you’ll use when developing plugins with Maven:
In Maven’s compile phase, explicit dependencies are downloaded to your local repository (i.e., .m2/repository/com/liferay/portal).
In Maven’s package phase, the plugin’s inferred dependencies are downloaded to your local repository (i.e., .m2/repository).
In Maven’s install phase, your plugin is installed to your local repository.
Now that you’ve deployed a plugin using Maven, let’s consider the types of Liferay plugins you can develop with Liferay Maven archetypes.