[
https://issues.jboss.org/browse/JBIDE-10339?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10339 at 12/19/11 12:19 PM:
---------------------------------------------------------------
Yes, it happens pretty regularly.
And it happens w/ JBDS ootb, too - JBDS-1956. See attached log for installation then first
start of JBDS (from
jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201112070617N-H851-Beta1.jar):
https://issues.jboss.org/secure/attachment/12349678/install-jbds-get-an-a...
was (Author: nickboldt):
Yes, it happens pretty regularly.
And it happens w/ JBDS ootb, too. See attached log for installation then first start of
JBDS (from jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201112070617N-H851-Beta1.jar):
https://issues.jboss.org/secure/attachment/12349678/install-jbds-get-an-a...
after installing JBT Abridged category (including m2e connectors)
lots of console errors logged
-----------------------------------------------------------------------------------------------
Key: JBIDE-10339
URL:
https://issues.jboss.org/browse/JBIDE-10339
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: maven, updatesite, UpStream
Affects Versions: 3.3.0.M5
Reporter: Nick Boldt
Assignee: Fred Bricon
Fix For: 3.3.0.Beta1
Attachments: install-jbds-get-an-assload-of-maven-crap-in-log.txt
See parent jira JBIDE-10336 for steps to reproduce. Full log is here:
https://issues.jboss.org/secure/attachment/12349551/eclipse.log.Sun_Dec4_...
This could be an upstream issue, but I wanted to make sure you were aware of it in case
it was because of something we're doing w/ m2e on first startup of JBT after install.
Or perhaps because of a missing dependency?
--
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