Also check for error messages on the Tomcat server side, in the Tomcat logs.
Wayne
On Oct 8, 2015 6:49 PM, "ke...@na7kr.us" wrote:
> I tried tomcat plugin and it starts to upload and stops no error.
>
>
> On October 8, 2015 2:13:18 PM tras...@stratuscom.com wrote:
>
> Check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Keven,
The Tomcat plugin should work. Make sure you have tomcat-users.xml set
up with a script user and the proper role. The file is located in
$CATALINA_HOME/conf. If you need help with that, the Tomcat mailing
list is the place to go.
We stuff
I agree with Wayne. My suggestion would be to create a new Vaadin project
via Maven, then move your custom stuff over as needed. It'll probably save
you much trouble.
I do see this:
[09/Oct/2015:19:14:49 +] "PUT
/manager/deploy?path=%2FYT-100_ATU_Controller HTTP/1.1" 403 3196
On Fri, Oct 9, 2015 at 9:39 AM, Wayne Fay wrote:
> Also check for error messages on the Tomcat server side, in the Tomcat
> logs.
>
> Wayne
> On Oct 8, 2015
403 error means “Forbidden”.
The good news is - Maven deployer is obviously connecting to the Tomcat Manager
app before it gets turned away for being unauthorized. So you’re 95% of the
way there! The remote does a “HTTP PUT” request that contains the application
that you’re trying to