Amazing; I just started a conversation on this exact topic on #jboss-dev about 15 minutes ago! I'm experimenting with the /pom.xml file right now to see if I can make this go away. On 10/23/2009 10:09 AM, Kabir Khan wrote: > AS trunk seems to have moved to using the m2eclipse plugin, and after > a few unsuccessful attempt it now works for me. However, the maven > console output show it to spend about 5 minutes trying to resolve the > org.codehaus.mojo:jboss-packaging-maven-plugin plugin? > > 10/23/09 3:38:22 PM BST: Updating index http://repo1.maven.org/maven2/ > 10/23/09 3:38:23 PM BST: Downloading central : nexus-maven-repository- > index.gz > 10/23/09 3:39:51 PM BST: Refreshing [/build/pom.xml, /component-matrix/ > pom.xml, /jboss-as-aspects/pom.xml, /jboss-as-cluster/pom.xml, /jboss- > as-connector/pom.xml, /jboss-as-console/pom.xml, /jboss-as-deployment/ > pom.xml, /jboss-as-ejb3/pom.xml, /jboss-as-hibernate-int/pom.xml, / > jboss-as-iiop/pom.xml, /jboss-as-jbossas-jmx-remoting/pom.xml, /jboss- > as-jbossas-remoting/pom.xml, /jboss-as-jmx-remoting/pom.xml, /jboss-as- > main/pom.xml, /jboss-as-management/pom.xml, /jboss-as-messaging/ > pom.xml, /jboss-as-profileservice/pom.xml, /jboss-as-security/ > pom.xml, /jboss-as-server/pom.xml, /jboss-as-system/pom.xml, /jboss-as- > system-jmx/pom.xml, /jboss-as-tomcat/pom.xml, /jboss-as-varia/ > pom.xml, /jboss-as-webservices/pom.xml, /testsuite/pom.xml, /tools/ > pom.xml] > 10/23/09 3:40:36 PM BST: Refreshing [/jboss-as-tomcat/pom.xml, /jboss- > as-varia/pom.xml, /jboss-as-webservices/pom.xml, /testsuite/pom.xml, / > tools/pom.xml] > 10/23/09 3:40:37 PM BST: [INFO] Attempting to resolve a version for > plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta- > version: LATEST > 10/23/09 3:40:37 PM BST: [INFO] Using version: 2.1 of plugin: > org.codehaus.mojo:jboss-packaging-maven-plugin > 10/23/09 3:40:43 PM BST: [INFO] Attempting to resolve a version for > plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta- > version: LATEST > 10/23/09 3:40:43 PM BST: [INFO] Using version: 2.1 of plugin: > org.codehaus.mojo:jboss-packaging-maven-plugin > <SNIP/> > 10/23/09 3:45:01 PM BST: [INFO] Attempting to resolve a version for > plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta- > version: LATEST > 10/23/09 3:45:01 PM BST: [INFO] Using version: 2.1 of plugin: > org.codehaus.mojo:jboss-packaging-maven-plugin > 10/23/09 3:45:02 PM BST: [INFO] Attempting to resolve a version for > plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta- > version: LATEST > 10/23/09 3:45:02 PM BST: [INFO] Using version: 2.1 of plugin: > org.codehaus.mojo:jboss-packaging-maven-plugin > 10/23/09 3:45:03 PM BST: [INFO] Attempting to resolve a version for > plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta- > version: LATEST > 10/23/09 3:45:03 PM BST: [INFO] Using version: 2.1 of plugin: > org.codehaus.mojo:jboss-packaging-maven-plugin > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development

On 23-10-2009 18:23, Brian Stansberry wrote: > FYI, for those not on #jboss-dev: > > I made the logging go away, but not the time the eclipse build is > spending when it logged those messages. That is, looks like the > logging > was noise during a time-consuming process that still exists. > > Adding<version/> tags to the<plugins/> section of /pom.xml made the > logging go away. Those shouldn't have been necessary, as the versions > were already declared in<pluginManagement/> section. But, well, > this is > all voodoo so I slaughtered a chicken. > > did you report a jira on this against m2eclipse for us to track ? If not, please do and let me know the link.

/max _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development