[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epp-dev] Indigo RC1 packages
|
M2E writes maven index cache to ~/.m2/repository/.cache/m2e. You can
delete this directory safely.
When M2E is used for real work, i.e. you actually have Maven projects in
your workspace, it will also write to Maven local repository, which is
~/.m2/repository by default.
M2E is not expected to write to any other location outside of workspace.
--
Regards,
Igor
On 11-05-20 11:21 AM, Eric Rizzo wrote:
On 5/20/11 11:15 AM, Igor Fedorenko wrote:
No, Maven index update is not expected unless the workspace has Maven
projects or m2e is activated by explicit UI actions (check m2e
preferences, wizards, etc).
As I mentioned, I am not able to reproduce the problem locally so can't
tell what triggers m2e activation in your environment. Please provide
steps we can use to reproduce the problem and we'll have a look asap.
Igor,
Is there some way for me to "wipe the slate clean" for m2e. That is,
remove any trace that m2e was ever used on my machine? Like I said,
after it finished the first time, it doesn't do it again; so I'm trying
to get back to the state I was in this morning before I installed Indigo
RC1.
Eric
--
Regards,
Igor
On 11-05-20 10:29 AM, Eric Rizzo wrote:
I let it finish the Updating Indexes task and then shut down. Restarted
with -console, and saw your expected results (only the usagedata bundle
was ACTIVE). Tried again with a brand new workspace and then another
workspace with old Java projects. Same result. So it appears that the
first time Indigo is started, m2e does the Updating Indexes thing; as
long as you let it finish, it doesn't activate eagerly any more.
Is that expected?
Eric
On 5/20/11 10:12 AM, Igor Fedorenko wrote:
Apparently yes, m2e got activated for some reason. To know for sure,
you
can start Eclipse with OSGi console (i.e. -console parameter), then
type
"ss m2e" in the console.
org.eclipse.m2e.usagedata and org.eclipse.m2e.discovery will most
likely
be ACTIVE, but this is expected and should not cause any logging or any
other noticeable overhead. org.eclipse.m2e.discovery is actually
expected to be <<LAZY>> after first restart.
If any other m2e bundle shows as ACTIVE, then please open a bugreport
and provide steps to reproduce the problem.
--
Regards,
Igor
On 11-05-20 09:55 AM, Eric Rizzo wrote:
On 5/19/11 8:53 PM, Igor Fedorenko wrote:
m2e contribution towards Indigo/RC2 will be properly signed using
Eclipse certificate. We track this as Bug 339970.
I've opened Bug 346563 to track wrong bundle and provider names in
org.eclipse.m2e.usagedata and we'll address it for RC2.
As for logging, this requires some explanation.
When m2e is dormant, it obviously does not log anything and I
double-checked that at least on linux x86_64 m2e is not eagerly
activated. We fixed two problems with eager activation since M6
(342232
and 340328, to be specific), but if you still see m2e activated
eagerly
and unnecessary, please submit new bugreport in m2e bugzilla and
we'll
try out best to address it before RC2.
When m2e is activated it does use slf4j for logging purposes.
However,
as we explained on this list last time this topic has been brought
up,
something else, i.e. not m2e, pulls in ch.qos.logback.slf4j
bundles and
configures it to print debug log messages to console (see [1]).
There is
nothing we can do about it from m2e end to stop this. We offered to
implement proper slf4j support at framework level [2], but this
proposal
did not receive any support from any Eclipse core committers. The
only
other solution I can think of is to block ch.qos.logback.slf4j from
getting included in java epp distro, but I am not sure how to
implement
this, if at all possible.
[1] http://dev.eclipse.org/mhonarc/lists/epp-dev/msg01378.html
[2]
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg05659.html
I'm using the 64-bit OS X Java package. I started it pointed at an
existing workspace with some Java projects (never used m2e before).
Haven't seen any Console logging during initialization (including an
apparent full workspace rebuild), but I do have m2e Updating Indexes
task in the Progress view. Doesn't this mean that m23 is being
activated
without user action?
Eric
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
