-
1. Re: how to deploy weld2 example to jboss as 7?
alesj Dec 25, 2012 3:40 PM (in response to subaochen)1 of 1 people found this helpfulI suggest to check Jozef' blog: http://in.relation.to/Bloggers/Jozef
-
2. Re: how to deploy weld2 example to jboss as 7?
subaochen Dec 26, 2012 1:18 AM (in response to alesj)Thanks Justin, I have checked Jozef's blog, in fact, I have droped a comment on his most recent blog entry but get no feedback(the link: http://in.relation.to/23806.lace#comments ), maybe I asked a silly question:-(
-
3. Re: how to deploy weld2 example to jboss as 7?
subaochen Dec 26, 2012 4:50 AM (in response to subaochen)I have tried mvn jboss-as:deploy within weld2/examples/jsf/login but failed:
[INFO] Scanning for projects...
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml
Downloading: http://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml
Downloaded: http://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (22 KB at 14.1 KB/sec)
Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (9 KB at 5.2 KB/sec)
Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml (11 KB at 5.2 KB/sec)
Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml (24 KB at 2.2 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.895s
[INFO] Finished at: Wed Dec 26 17:46:23 CST 2012
[INFO] Final Memory: 12M/110M
[INFO] ------------------------------------------------------------------------
[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 repositories [local (/home/subaochen/.m2/repository), jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public), central (http://repo.maven.apache.org/maven2)] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[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 read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
I have set up $JBOSS_HOME=/home/subaochen/devel/jboss as a soft link to /home/subaochen/devel/jboss-as-7.1.1.Final.
Please help, thanks in advance!
-
4. Re: how to deploy weld2 example to jboss as 7?
alberto_souza Dec 27, 2012 10:42 PM (in response to subaochen)1 of 1 people found this helpfulThere is a folder called as7-installer/. I followed the instructions and everything worked fine.
-
5. Re: how to deploy weld2 example to jboss as 7?
subaochen Dec 28, 2012 10:28 AM (in response to alberto_souza)hi alberto,
Thanks first!
I have followed the instructions in as7-installer:
mvn clean install -Pupdate-jboss-as
And the above command build successfully.
But when I run
mvn jboss-as:deploy
in weld2/exmaples/jsf/login, the command failed with error message :
subaochen@subaochen-desktop:~/devel/weld/examples/jsf/login$ mvn jboss-as:deploy
[INFO] Scanning for projects...
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0
Downloading: http://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml
Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (9 KB at 6.3 KB/sec)
Downloaded: http://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (22 KB at 12.0 KB/sec)
Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml (11 KB at 5.4 KB/sec)
Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml (24 KB at 9.0 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.088s
[INFO] Finished at: Fri Dec 28 23:15:24 CST 2012
[INFO] Final Memory: 12M/114M
[INFO] ------------------------------------------------------------------------
[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 repositories [local (/home/subaochen/.m2/repository), jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public), central (http://repo.maven.apache.org/maven2)] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[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 read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
I really don't know how to fix this problem, thanks for any help!
-
6. Re: how to deploy weld2 example to jboss as 7?
alberto_souza Dec 28, 2012 5:53 PM (in response to subaochen)why don't you try just deploy the app without maven? Sometimes is better... I installed the weld2 version and everything is working. But i did not use the examples projects.
-
7. Re: how to deploy weld2 example to jboss as 7?
subaochen Dec 28, 2012 8:49 PM (in response to subaochen)I have tried "mvn package" command examples/jsf/login , it just miracualously success! Then go into target and copy weld-login.war to $JBOSS_HOME/standlone/deployments, all works fine now.
I think the documentation of weld2 beta2 is badly organizied or not good for jboss 7, build.xml is targeted to jboss6, ant package, ant deploy will fail. And maven also failed to deploy the examples to jboss7.
-
8. Re: how to deploy weld2 example to jboss as 7?
jharting Jan 2, 2013 9:19 AM (in response to subaochen)(Although late) I posted a reply at https://community.jboss.org/message/785282#785282
Yes, we need to go over the build files and make them up-to-date.