-
Sub-task
-
Resolution: Duplicate
-
Critical
-
3.3.0.M5
-
None
See parent jira JBIDE-10336 for steps to reproduce. Full log is here:
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?
- blocks
-
JBIDE-10415 build problems in Beta3
- Closed
- duplicates
-
JBDS-2016 JBDS generates (lots of) DEBUG statements to stdout
- Closed
- is duplicated by
-
JBDS-1956 get m2eclipse logging under control in JBDS
- Closed
- is related to
-
JBDS-1896 add m2e features to JBDS Installer
- Closed