Greetings cross-projects,
for the error reporting I’d like to give committers/reporters the ability to
store personal preferences and get access to the errors they sent in the past,
current status of these problems etc. For that I need to authenticate users by
email address. One (half-baked)
Konstantin,
I dug a bit deeper into Sapphire error reports. My conclusion: Adding more open
source namespaces wont help much in your (and Nebula’s) case.
Most reports mentioning Sapphire are from the namespaces
oracle.eclipse.tools.* and com.liferay.* Some reports show that Sapphire
clients
Am 24.07.2015 um 17:36 schrieb Gunnar Wagenknecht gun...@wagenknecht.org:
Am 24.07.2015 um 08:27 schrieb Marcel Bruch marcel.br...@codetrails.com:
Most reports mentioning Sapphire are from the namespaces
oracle.eclipse.tools.* and com.liferay.* Some reports show that Sapphire
clients
Am 24.07.2015 um 08:27 schrieb Marcel Bruch marcel.br...@codetrails.com:
Most reports mentioning Sapphire are from the namespaces
oracle.eclipse.tools.* and com.liferay.* Some reports show that Sapphire
clients even do not follow the bundle name to package name conventions.
Neither
Hi Pascal
Thanks for thinking about Buildship.
Interestingly, right this morning, I had a 1-hour chat with Markus re:
inclusion of Buildship in SR1. We got a lot of valuable information from him
and we (Donat and i) will start tackling it beginning of next week. I think we
are in good shape
On 24 Jul 2015, at 17:27, Marcel Bruch wrote:
I think those clients (which currently make ~28% of the error reports)
should actually sign-up and subscribe to their error reports
How do I subscribe to error reports that are filtered ?
- or set up their own error collection to review and fix
Do you happen to know where the team is at wrt producing a build for
consumption in the aggregator?
I'm just asking because RC1 [1] is coming quickly (August 14th) and so
it may be better to work out the problems sooner rather than later.
Otherwise I can imagine the project being put at risk
I am pretty sure we are not allowed to collect usage data. Wayne still
can't decide the policy around this [1]. I have some opensource code for
out-of-eclipse usage collection which I use with my m2e extensions, if
you are interested.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=413169
--
Hey,
IIRC back in April / May, it was decided that Buildship (Gradle
integration in Eclipse) would be added to Mars SR1.
Is this still the plan?
Pascal
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your
Yep, that's the plan if I may answer this question.
Regards,
Markus
On 24 July 2015 at 18:43, Pascal Rapicault pas...@rapicorp.com wrote:
Hey,
IIRC back in April / May, it was decided that Buildship (Gradle
integration in Eclipse) would be added to Mars SR1.
Is this still the plan?
Hi,
My apologies for not paying attention, but is there anything of the
Usage data collection work that could be used within an RCP app? (As
opposed to Eclipse)
If so, is there any experiences and/or documentation that could be shared?
Thanksinadvance,
Scott
On 24 Jul 2015, at 19:34, Scott Lewis wrote:
Hi,
My apologies for not paying attention, but is there anything of the
Usage data collection work that could be used within an RCP app? (As
opposed to Eclipse)
If so, is there any experiences and/or documentation that could be
shared?
if you
Wayne is on holidays until Aug. 3.
If you can't manage to delete it and create a new one, please drop a
line to webmas...@eclipse.org. We probably can, otherwise we can edit
the SQL backend.
Denis
On 24/07/15 03:16 PM, Scott Lewis wrote:
Wayne appears to be inaccessible so I'll ask this
I think those clients (which currently make ~28% of the error reports)
should actually sign-up and subscribe to their error reports
Liferay would love to sign up, just point the way.
On Fri, Jul 24, 2015 at 1:09 PM, Konstantin Komissarchik
konstantin.komissarc...@oracle.com wrote:
I dug
Wayne appears to be inaccessible so I'll ask this list:
Is it possible to edit/change (e.g. move up) a scheduled release in the
meta-data editor? If so, how?
Alternatively, I could delete the existing release and create a new one
with the correct date, but I can't see a way to delete a
Hi,
after you login, you go to your project page and select the release you want to
change.
The press the Edit button on the left of the black toolbar.
Then open the The Basics section and change the date in Release Date.
Marc
From:
Oh and to delete a release, you also got to Edit and at the bottom
there is a red Delete button.
From: cross-project-issues-dev-boun...@eclipse.org
[cross-project-issues-dev-boun...@eclipse.org] on behalf of Marc Khouzam
[marc.khou...@ericsson.com]
Sent:
I dug a bit deeper into Sapphire error reports. My conclusion: Adding more
open source namespaces wont help much in your (and Nebula’s) case.
Most reports mentioning Sapphire are from the namespaces
oracle.eclipse.tools.*
and com.liferay.* Some reports show that Sapphire clients even
Hi Etienne,
Good to hear. Good luck!
Pascal
On 07/24/2015 07:30 PM, Etienne Studer wrote:
Hi Pascal
Thanks for thinking about Buildship.
Interestingly, right this morning, I had a 1-hour chat with Markus re:
inclusion of Buildship in SR1. We got a lot of valuable information
from him and
On Fri, Jul 24, 2015 at 10:34 AM, Marcel Bruch marcel.br...@codetrails.com
wrote:
Greetings cross-projects,
for the error reporting I’d like to give committers/reporters the ability
to store personal preferences and get access to the errors they sent in the
past, current status of these
20 matches
Mail list logo
