As far as this goes, there is definitely something strange going on, and I think it points to the SSL self signed cert. Can someone verify that the tomcat7 maven plugin works with self signed SSL?
I have setup another TC7 server on a remote BSD VM with the absolute basic configuration. Since the first server has the manager application running on a self signed SSL certificate (not sure if I mentioned that before), I decided NOT to set it [SSL] up on the new machine, and it works as expected and can be reproduced on demand. I notice that when I script the command using curl, I have to pass it the -k option to get it to work. I am wondering if that might be the problem that I am seeing, just masked by the 401 error. I'm looking in the tomcat logs and I'm not seeing anything out of the ordinary though. Maybe that error is only returned by maven. Anyone? On Thu, Dec 13, 2012 at 9:48 AM, Josh Gooding <josh.good...@gmail.com>wrote: > > > On Thu, Dec 13, 2012 at 9:36 AM, Olivier Lamy <ol...@apache.org> wrote: > >> 2012/12/13 Josh Gooding <josh.good...@gmail.com>: >> > On Wed, Dec 12, 2012 at 6:05 PM, Olivier Lamy <ol...@apache.org> wrote: >> > >> >> Good detailed description :-). >> >> >> > >> > Hey even I get it right once in a while... ;) >> > >> > >> >> I just wonder about the cli you are using ? >> >> >> > >> > cli as in command line interface? - Win 7, CentOS, and Ubuntu >> terminals, >> > and yes I get my fair share of flack for not letting Eclipse "just do >> it". >> > Of course I'm a control freak when it comes to my code... >> :-) >> >> I mean mvn tomcat7:deploy or something else ? >> or you bind deploy to a lifecycle phase ? >> >> > Oh I gotcha. tomcat7:deploy I didn't bind the deploy to the life-cycle > phase yet. I want to get it working first. > So let me form possibly some better questions here: 1 - Where does the plug in > > >> > >> >> >> >> 2012/12/12 Josh Gooding <josh.good...@gmail.com>: >> >> > I didn't want to come here to ask as I always hate to bother anyone, >> but >> >> > maybe I should have come here first. I'm coming up short on answers >> and >> >> > ideas. I'm having an issue with using maven and the tomcat7 plugin. >> >> > >> >> > Maven version -3.0.4 >> >> > Tomcat version - 7.0.29 >> >> > .jdk version - 1.6 >> >> > tomcat7-maven-plugin version - 2.0 >> >> > >> >> > Hey group, I am having an issue here with using the >> tomcat7-maven-plugin >> >> > in conjunction with the tomcat 7 manager. here's what I have so far. >> >> > >> >> > tomcat-users.xml - >> >> > >> >> > <tomcat-users> >> >> > <role rolename="manager-gui"/> >> >> > <role rolename="manager-script"/> >> >> > <role rolename="admin"/> >> >> > <user username="localTomcatAdmin" password="password" >> >> > roles="manager-gui,manager-script,admin"/> >> >> > </tomcat-users> >> >> > >> >> > in my M2_HOME/conf/settings.xml: (note not in my .m2/ directory) >> >> > (I'll get to this definition in a minute) >> >> > <pluginGroups> >> >> > <pluginGroup>org.apache.tomcat.maven</pluginGroup> >> >> > </pluginGroups> >> >> > >> >> > <servers> >> >> > <server> >> >> > <id>LocalTomcatServer</id> >> >> > <username>localTomcatAdmin</username> >> >> > <password>password</password> >> >> > </server> >> >> > </servers> >> >> > >> >> > now for the last piece, in my pom-deploy.xml (parent) I have this: >> >> > >> >> > <plugin> >> >> > <groupId>org.apache.tomcat.maven</groupId> >> >> > <artifactId>tomcat7-maven-plugin</artifactId> >> >> > <version>2.0</version> >> >> > <configuration> >> >> > <server>LocalTomcatServer</server> >> >> > <path>/TripTixRX</path> >> >> > <port>8080</port> >> >> > </configuration> >> >> > </plugin> >> >> > >> >> > I have verified that the manager works with the applied credentials, >> I >> >> can >> >> > login and supply the credentials to my local /manager/html. >> >> > >> >> > The problem is that when I deploy through maven as mvn >> tomcat7:deploy and >> >> > returns me the dreaded 401 - Unauthorized page with the same >> credentials. >> >> > It's almost like maven is not parsing the configuration for the >> plugin >> >> > maybe? >> >> > >> >> > At this point I don't know what to do. I've turned on verbose >> output in >> >> > maven and it shows what appears that the plugin is attempting to >> upload >> >> the >> >> > war file twice and returns the 401 page. >> >> > >> >> > >> >> > I also have a question as to getting this to work initially. I >> added the >> >> > <pluginGroup>org.apache.tomcat.maven</pluginGroup> to my >> >> conf/settings.xml >> >> > to get the tomcat7 plugin to download and work, is this normal or >> should >> >> I >> >> > not have to define it here? I mean having to change and version >> maven >> >> > settings.xml files seems a bit counter intuitive for preserving >> maximum >> >> > portability right, or am I looking at this from the wrong angle? >> >> > >> >> > Any information anyone can provide as to where to look or what could >> be >> >> > causing this issue, I would be greatly appreciated. >> >> > >> >> > Warmest regards, >> >> > >> >> > - Josh >> >> >> >> >> >> >> >> -- >> >> Olivier Lamy >> >> Talend: http://coders.talend.com >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> >> >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >
