Ok, my maven profile was not setup correctly and now I am able to deploy the helloservlet but I can't access it through browser. My console log seems to be saying that the app has been deployed : 01:07:02,306 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) HornetQ Server version 2.1.2.Final (Colmeia, 120) started 01:07:02,382 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta3 "Salyut" started in 11503ms - Started 100 of 147 services (47 services are passi ve or on-demand) 01:48:14,531 INFO [org.jboss.as.server.deployment] (ManagementCommunication-thr eads - 3) Content added at location C:\Apps\jboss-7.0.0.Beta3\standalone\data\co ntent\c9\426f0f7f253294c648717632e6314dacd52347\content 01:48:14,565 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Sta rting deployment of "jboss-as-helloworld.war" 01:48:14,574 WARN [org.jboss.vfs] (MSC service thread 1-13) VFS was unable to s et the URLStreamHandlerFactory. This will have unpredictable results 01:48:14,873 INFO [org.jboss.weld] (MSC service thread 1-12) Processing CDI dep loyment: jboss-as-helloworld.war 01:48:15,539 INFO [org.jboss.weld] (MSC service thread 1-2) Starting Services f or CDI deployment: jboss-as-helloworld.war 01:48:15,584 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.1 (Final) 01:48:15,662 INFO [org.jboss.weld] (MSC service thread 1-8) Starting weld servi ce 01:48:16,222 INFO [org.jboss.web] (MSC service thread 1-11) registering web con text: /jboss-as-helloworld When I try accessing it I get 404. Moreover, to undeploy the app, when I use mvn jboss-as:undeploy Maven complains : [ERROR] No plugin found for prefix 'jboss-as' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the r epositories [local (C:\vkk\maven_repository), jboss-public-repository-group (htt ps://repository.jboss.org/nexus/content/groups/public-jboss/), central (http://r epo1.maven.org/maven2)] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundF Can somebody please help. Thx Vimal On 15/06/2011 1:23 AM, Vimal Kansal wrote: > Hi, > > I am going through the quickstarts guide and have installed eclipse > indigo with JBoss tools as described in the doc. When I import maven > projects, eclipse hangs and closes suddenly. > > Trying to deploy through commandline, I am getting the following error : > > C:\vkk\downloads\software\jboss\JBossAS\quickstarts\helloworld>mvn > install -U > [INFO] Scanning for projects... > [INFO] > [INFO] > ------------------------------------------------------------------------ > [INFO] Building JBoss AS Quickstarts: Helloworld 7.0.0-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > Downloading: > > http://repo1.maven.org/maven2/org/jboss/as/plugins/jboss-as-deploy > - > plugin/7.0.0.Beta3/jboss-as-deploy-plugin-7.0.0.Beta3.pom > [WARNING] The POM for > org.jboss.as.plugins:jboss-as-deploy-plugin:jar:7.0.0.Beta > 3 is missing, no dependency information available > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 0.760s > [INFO] Finished at: Wed Jun 15 01:14:03 EST 2011 > [INFO] Final Memory: 2M/15M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Plugin org.jboss.as.plugins:jboss-as-deploy-plugin:7.0.0.Beta3 > or one of > its dependencies could not be resolved: Failed to read artifact > descriptor for > org.jboss.as.plugins:jboss-as-deploy-plugin:jar:7.0.0.Beta3: Could not > find arti > fact org.jboss.as.plugins:jboss-as-deploy-plugin:pom:7.0.0.Beta3 in > central (htt > p://repo1.maven.org/maven2) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e swit > ch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please rea > d the following articles: > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/PluginResoluti > > onException > > Can somebody please help. > > Thx > > Vimal > > _______________________________________________ > jboss-as7-dev mailing list > > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Hi Pete, When I do mvn install in one of the quickstarts I get another error (with the latest master of AS7): [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2.174s [INFO] Finished at: Thu Jun 16 20:26:26 IST 2011 [INFO] Final Memory: 6M/81M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-deploy-plugin:7.0.0.Beta3:deploy (default) on project jboss-as-helloworld: Could not deploy jboss-as-helloworld.war. Reason: java.lang.Exception: {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "Parameter content may not be null "}} In the server window is an exception with a similar message. BTW I'm not sure I like the fact that a 'mvn install' also does a deploy to as7, I would leave that out of the default install lifecycle and make that a separate step that only happens when running 'mvn jboss-as:deploy'... I think that other maven-based tools that do deployment also typically do this separately... Cheers, David On 15/06/2011 18:03, Pete Muir wrote: > Vimal, please cc me when you are looking at quickstarts, I don't read this list regularly. > > I'll fix both these problems + ping you when done if you can check. You shouldn't need to adjust your settings.xml at all for the quickstarts to work, so when you test, if you could wipe you local ~/.m2 directory away that would be great! > > On 14 Jun 2011, at 17:10, Vimal Kansal wrote: > >> Ok, my maven profile was not setup correctly and now I am able to deploy the helloservlet but I can't access it through browser. My console log seems to be saying that the app has been deployed : >> >> 01:07:02,306 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service >> thread 1-6) HornetQ Server version 2.1.2.Final (Colmeia, 120) started >> 01:07:02,382 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta3 >> "Salyut" started in 11503ms - Started 100 of 147 services (47 services are passi >> ve or on-demand) >> 01:48:14,531 INFO [org.jboss.as.server.deployment] (ManagementCommunication-thr >> eads - 3) Content added at location C:\Apps\jboss-7.0.0.Beta3\standalone\data\co >> ntent\c9\426f0f7f253294c648717632e6314dacd52347\content >> 01:48:14,565 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Sta >> rting deployment of "jboss-as-helloworld.war" >> 01:48:14,574 WARN [org.jboss.vfs] (MSC service thread 1-13) VFS was unable to s >> et the URLStreamHandlerFactory. This will have unpredictable results >> 01:48:14,873 INFO [org.jboss.weld] (MSC service thread 1-12) Processing CDI dep >> loyment: jboss-as-helloworld.war >> 01:48:15,539 INFO [org.jboss.weld] (MSC service thread 1-2) Starting Services f >> or CDI deployment: jboss-as-helloworld.war >> 01:48:15,584 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 >> 1.1.1 (Final) >> 01:48:15,662 INFO [org.jboss.weld] (MSC service thread 1-8) Starting weld servi >> ce >> 01:48:16,222 INFO [org.jboss.web] (MSC service thread 1-11) registering web con >> text: /jboss-as-helloworld >> >> When I try accessing it I get 404. >> >> Moreover, to undeploy the app, when I use >> >> mvn jboss-as:undeploy >> >> Maven complains : >> >> [ERROR] No plugin found for prefix 'jboss-as' in the current project and in the >> plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the r >> epositories [local (C:\vkk\maven_repository), jboss-public-repository-group (htt >> ps://repository.jboss.org/nexus/content/groups/public-jboss/), central (http://r >> epo1.maven.org/maven2)] -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit >> ch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, please rea >> d the following articles: >> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundF >> >> Can somebody please help. >> >> Thx >> >> Vimal >> >> >> On 15/06/2011 1:23 AM, Vimal Kansal wrote: >>> Hi, >>> >>> I am going through the quickstarts guide and have installed eclipse >>> indigo with JBoss tools as described in the doc. When I import maven >>> projects, eclipse hangs and closes suddenly. >>> >>> Trying to deploy through commandline, I am getting the following error : >>> >>> C:\vkk\downloads\software\jboss\JBossAS\quickstarts\helloworld>mvn >>> install -U >>> [INFO] Scanning for projects... >>> [INFO] >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building JBoss AS Quickstarts: Helloworld 7.0.0-SNAPSHOT >>> [INFO] >>> ------------------------------------------------------------------------ >>> Downloading: >>> >>> http://repo1.maven.org/maven2/org/jboss/as/plugins/jboss-as-deploy >>> - >>> plugin/7.0.0.Beta3/jboss-as-deploy-plugin-7.0.0.Beta3.pom >>> [WARNING] The POM for >>> org.jboss.as.plugins:jboss-as-deploy-plugin:jar:7.0.0.Beta >>> 3 is missing, no dependency information available >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 0.760s >>> [INFO] Finished at: Wed Jun 15 01:14:03 EST 2011 >>> [INFO] Final Memory: 2M/15M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Plugin org.jboss.as.plugins:jboss-as-deploy-plugin:7.0.0.Beta3 >>> or one of >>> its dependencies could not be resolved: Failed to read artifact >>> descriptor for >>> org.jboss.as.plugins:jboss-as-deploy-plugin:jar:7.0.0.Beta3: Could not >>> find arti >>> fact org.jboss.as.plugins:jboss-as-deploy-plugin:pom:7.0.0.Beta3 in >>> central (htt >>> p://repo1.maven.org/maven2) -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e swit >>> ch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please rea >>> d the following articles: >>> [ERROR] [Help 1] >>> >>> http://cwiki.apache.org/confluence/display/MAVEN/PluginResoluti >>> >>> onException >>> >>> Can somebody please help. >>> >>> Thx >>> >>> Vimal >>> >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Hi Pete, When I do mvn install in one of the quickstarts I get another error (with the latest master of AS7): [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2.174s [INFO] Finished at: Thu Jun 16 20:26:26 IST 2011 [INFO] Final Memory: 6M/81M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-deploy-plugin:7.0.0.Beta3:deploy (default) on project jboss-as-helloworld: Could not deploy jboss-as-helloworld.war. Reason: java.lang.Exception: {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "Parameter content may not be null "}} In the server window is an exception with a similar message.

I believe the issue is on the maven plugin side. Not sure, James just told me he would handle it :-) On 17 Jun 2011, at 12:45, Shelly McGowan wrote: > > > Pete, > > IS there a tracking JIRA for the issue is that James is "going to fix". I've encountered similar regressions in deployment > with the BV TCK. > > Shelly > > > On 16 Jun 2011, at 20:34, David Bosschaert wrote: > > James is going to fix this for us, something changed in the AS APIs.