[
https://issues.jboss.org/browse/JBIDE-10628?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-10628 at 1/24/12 10:51 AM:
---------------------------------------------------------------
On a fresh Indigo SR1 installation (Windows 7 64bits), I installed JBoss Central, Maven
Examples and the JBoss AS features from the update site. During installation, I checked
m2e-wtp, m2e and the mavenarchiver features were also installed.
Clicking on the kitchensink quickstart in central, the project was created without errors
(no missing connectors).
Window->Preferences->Maven->Discover->Open catalogs works.
Importing the m2e-wtp projects, m2e discovers and offers me to install the m2e-tycho
configurator.
Jochen, if you didn't change anything to the stock kitchensink pom.xml and get
"Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (execution: default-compile,
phase: compile)" that would mean the m2e JDT integration is not installed or started
correctly. Is there anything noteworthy your workspace logs
(<workspaceroot>/.metadata/.log)
Also, you can try diff'ing your eclipse installations when you install m2e directly or
from JBT, see if some plugins/features are missing.
was (Author: fbricon):
On a fresh Indigo SR2 installation (Windows 7 64bits), I installed JBoss Central,
Maven Examples and the JBoss AS features from the update site. During installation, I
checked m2e-wtp, m2e and the mavenarchiver features were also installed.
Clicking on the kitchensink quickstart in central, the project was created without errors
(no missing connectors).
Window->Preferences->Maven->Discover->Open catalogs works.
Importing the m2e-wtp projects, m2e discovers and offers me to install the m2e-tycho
configurator.
Jochen, if you didn't change anything to the stock kitchensink pom.xml and get
"Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (execution: default-compile,
phase: compile)" that would mean the m2e JDT integration is not installed or started
correctly. Is there anything noteworthy your workspace logs
(<workspaceroot>/.metadata/.log)
Also, you can try diff'ing your eclipse installations when you install m2e directly or
from JBT, see if some plugins/features are missing.
Discover new m2e connectors fails
---------------------------------
Key: JBIDE-10628
URL:
https://issues.jboss.org/browse/JBIDE-10628
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.3.0.M5
Environment: Linux 3.1.6-gentoo #1 SMP x86_64 Intel(R) Core(TM) i7-2720QM CPU @
2.20GHz GenuineIntel GNU/Linux
IcedTea JDK 6.1.10.4
eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz
Reporter: Jochen Buchholz
Assignee: Fred Bricon
Labels: connectors, discovery, m2e, maven
I followed the guide on
https://community.jboss.org/community/tools/blog/2011/12/23/jboss-tools-m...
I installed eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz and update JBoss Tools from
http://download.jboss.org/jbosstools/updates/development/indigo/ . I started with the
Kitchensink example on the "Jboss Central". I opened the pom.xml and put the
pointer over the plugin tag of the maven-compiler-plugin. An Error/Quickfix pop's up
(snip snap):
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (execution: default-compile,
phase: compile)
2 Quickfixes avaiulable:
-Permanently mark goal bla bla bla
-Discover new m2e connectors
CoreException: Could not calculate build plan ....
I choose "Discover new m2e connectors" and got an error:
"Discovery completed without finding any extensions. Please check your network
connection and try again."
Very confusing Message, because my network connection is ok. It is impossible to discover
m2e connectors under Preferences->maven-> Discovery->Open Catalog. The Catalog
URL is
http://download.eclipse.org/technology/m2e/discovery/directory.xml
When I install m2e without Jbosstools Help->install new software, m2e is able to
discover connectors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira