[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [epp-dev] Indigo M6 EPP
|
I see couple of unrelated issues here.
As already discussed in this thread, m2e should not get activated early.
This is a bug we will address for M7 and this will eliminate m2e-related
debug log messages for users who do not use m2e.
For users who do use m2e and launched eclipse with -consoleLog, I think
m2e behaviour is correct according to the description of this command
line option, i.e. "any log output is also sent to Java's System.out
(typically back to the command shell if any)" (source [1]). Obviously,
we are open for discussion here.
[1]
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
--
Regards,
Igor
On 11-03-17 11:30 AM, Markus Knauer wrote:
I started several of the packages (CPP, Java, RCP, ...) with -consoleLog
and found that much log output only in the Java package, mostly
m2eclipse messages. For the final release in June we should try to
eliminate those messages because they do not leave a good impression to
the unexperienced users.
Markus
On 17 March 2011 14:51, Steffen Pingel <steffen.pingel@xxxxxxxxxxx
<mailto:steffen.pingel@xxxxxxxxxxx>> wrote:
When I ran the Java package with a clean workspace on Gtk/x86_64 I
got a lot of debug output on the console. The output was mostly from
m2eclipse but also from other plugins:
340312: Indigo M6 logs lots of output
https://bugs.eclipse.org/bugs/show_bug.cgi?id=340312
Does that happen with other packages as well?
Steffen
On Thu, Mar 17, 2011 at 6:27 AM, Markus Knauer
<mknauer@xxxxxxxxxxxxxxxxx <mailto:mknauer@xxxxxxxxxxxxxxxxx>> wrote:
JEE update: Now all 6 JEE packages could be build including the
Linux 64-bit one. They can be found here:
http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110317-1136/
Regards, Markus
On 17 March 2011 12:40, Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx
<mailto:mknauer@xxxxxxxxxxxxxxxxx>> wrote:
Now that all packages are available (with the exception of
JEE/Linux/64-bit), we can start to test them. They are
available from
http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110317-0706/
If you want to test update scenarios from older Indigo
milestones, you need to add the following two p2
repositories (and you may disable all others). In general
you can find the EPP p2 repository that was used for the
package build at the same download location in the
'repository' sub-directory:
http://download.eclipse.org/releases/staging
http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110317-0706/repository/
Please start testing and send your votes to the mailing list
as usual.
JEE status: I am going to rebuild the JEE packages. I hope
that it was a one-time problem that is gone now because I
could not find any difference to the other packages.
Thanks, Markus
On 17 March 2011 11:12, Markus Knauer
<mknauer@xxxxxxxxxxxxxxxxx
<mailto:mknauer@xxxxxxxxxxxxxxxxx>> wrote:
Early results can be found here:
http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110317-0706/
For some reason ("An error occurred during the
org.eclipse.equinox.internal.p2.engine.phases.CheckTrust
phase.") the JEE package could not be build for Linux
64-bit. As soon as the above build finishes I'll take a
closer look, maybe we need to rebuild the JEE packages.
Regards, Markus