our M7 contribution is coming late due to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466361
I just pushed our M7 contribution to Gerrit for validation
https://git.eclipse.org/r/#/c/47166/
-Matthias
___
cross-project-issues-dev mailing list
Many of the entries on the unsigned report [1] are features.
Features must also be signed.
Please check if your features are on the list. Note that the report
doesn't include a path or make any particular distinction for features.
I chased a plug-in for a solid hour yesterday before I noticed
BTW, the new launch bar feature isn’t signed yet. I’ll work on that today.
Doug.
From: Wayne Beaton wa...@eclipse.orgmailto:wa...@eclipse.org
Organization: The Eclipse Foundation
Reply-To: Cross project issues
cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org
Date:
I just opened a bug for you :-)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466466
Wayne
On 05/05/15 11:57 AM, Doug Schaefer wrote:
BTW, the new launch bar feature isn’t signed yet. I’ll work on that today.
Doug.
From: Wayne Beaton wa...@eclipse.org mailto:wa...@eclipse.org
Organization:
I don't think I've sent this out before ... apologies if I am repeating
myself.
I'm sure everyone is familiar with
https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build
but I recently added a section:
For years, I've had a working setup that allowed me to update Sapphire's
simrel contribution. With changes to use Gerrit, I am no longer able to
contribute. I've spent hours reading various wikis and I still cannot figure
out what keys I need to have and where I am supposed to shove them. Maybe
For years, I've had a working setup that allowed me to update Sapphire's
simrel contribution. With changes to use Gerrit, I am no longer able to
contribute. I've spent hours reading various wikis and I still cannot figure
out what keys I need to have and where I am supposed to shove them. Maybe
On 05/05/2015 03:50 PM, Konstantin Komissarchik wrote:
Thanks, Carl. Regarding step 1, how do I generate and store the ssh key
so that Eclipse will use it when communicating with Gerrit? I am on Windows.
This may help:
I wish it did. Unfortunately, this is one of those content-free doc pages. I
can see those preference pages well enough on my own. Doesn't help in
knowing what I am supposed to do with them.
So I go to SSH2 - Key Management - Generate RSA Key
Yay! So far so good. Apply, close dialog, re-open,
On 05/05/2015 10:21 PM, Konstantin Komissarchik wrote:
Thanks, Doug! The “save private key” button was the magic step that I
was missing.
Now I am able to fetch the repo and push my change, but I am not done
yet, am I? I need to go somewhere to monitor and approve it now?
Nope. it's in:
Yep. Just figured out that it went directly in. Oy!
So what should I have done if I wanted to exercise the new verifier feature?
- Konstantin
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Mickael
Istria
Sent:
Yeah, that caught me for a while the first time too.
If you push directly to the master branch, it goes straight in without going
through the Gerrit review part. In that case Gerrit is just an over-engineered
git server.
You only see it in Gerrit if you push to gerrit, I.e. refs/for/master, in
I've gone through the list and have opened bugs for most of the unsigned
JARs.
I can't sort out how org.eclipse.gemini.jpa_1.2.0.M1.jar is being
included in the composite repo.
It's in the plug-ins directory, but I don't see any references to it in
any feature or any aggregator file.
I've not looked, so don't know if this is the issue, but the VALIDATE,
BUILD, and CLEAN_BUILD jobs meant to run one after the other with
VALIDATE being based on Git change and the other two being based on
successful previous step. BUILD and CLEAN_BUILD take as their input,
what was used in the
If you have your keys generated with openssh, they are put in the regular
~/.ssh folder, which Eclipse and EGit will use. So just generating the keys
should be enough.
I am on Windows and don't have any SSH tools installed, as far as I know.
Did you try to use HTTPS instead ?
Thanks, Doug! The save private key button was the magic step that I was
missing.
Now I am able to fetch the repo and push my change, but I am not done yet,
am I? I need to go somewhere to monitor and approve it now?
- Konstantin
From: cross-project-issues-dev-boun...@eclipse.org
On 05/05/2015 10:26 PM, Konstantin Komissarchik wrote:
So what should I have done if I wanted to exercise the new verifier
feature?
To create a Gerrit review instead of pushing directly, push to branch
refs/for/master instead of master. This creates the review and the
validation job starts
Personally, I always add the remote review url as described in [1], so I
just have to 'git push review' my changes.
[1] https://wiki.eclipse.org/Gerrit#Adding_a_dedicated_remote
On Tue, May 5, 2015 at 4:28 PM, Mickael Istria mist...@redhat.com wrote:
On 05/05/2015 10:26 PM, Konstantin
On 05/05/2015 09:48 PM, Konstantin Komissarchik wrote:
Have you uploaded your SSH key to Gerrit ?
https://wiki.eclipse.org/Gerrit#SSH_Keys
It would require having such a key in the first place. I understand
the theory of it and I’ve seen tools to gen key pairs, but I don’t
know where I am
On 05/05/2015 10:06 PM, Konstantin Komissarchik wrote:
git clone
https://kkomissarc...@git.eclipse.org/r/simrel/org.eclipse.simrel.build
Does your remote sets correctly your HTTPS password ( visible at
https://git.eclipse.org/r/#/settings/http-password ) in EGit?
Use the Gerrit workflow. The Hudson job watches Gerrit for change requests and
fires off a job when it sees one.
From: Konstantin Komissarchik
konstantin.komissarc...@oracle.commailto:konstantin.komissarc...@oracle.com
Reply-To: Cross project issues
Wayne,
If you already opened a bug for the javax.persistence, can you
duplicate it against https://bugs.eclipse.org/bugs/show_bug.cgi?id=460094 ?
If you did not open a bug, that's fine- we already have one.
FWIW,
- Carl Anderson
WTP Build guy
From: Wayne Beaton wa...@eclipse.org
ICYMI, Java 9 is now releasing September 2016.
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223
Original Message
From: mark.reinh...@oracle.com
Sent: Tuesday, May 5, 2015 12:22 PM
To: jdk9-...@openjdk.java.net
Subject: Proposed schedule for JDK 9
Here is a proposed schedule
23 matches
Mail list logo
