[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [e4-dev] eScriptMonkey naming
|
Renaming can definitely be done after the
move. I was a bit slow to follow up here because I was trying to find out
what process we need to follow here. I was hoping it would not be necessary
but It turns out we will need a CQ for this code. Here is what to do:
- Take the current contents of
the master branch in your github repository
- Remove all third party libraries
- Zip up the remaining source
code and submit a CQ, or send me the zip file and I can do it for you.
Given the limited history and the fact
that most of it comes from an existing Eclipse project I am hopeful we
can get that sorted out quickly.
John
From:
DAUSSY Arthur <arthur.daussy@xxxxxxxx>
To:
E4 Project developer
mailing list <e4-dev@xxxxxxxxxxx>,
Cc:
"Discussions about
scripting Eclipse." <eclipse-scripting-dev@xxxxxxxxxxx>
Date:
10/02/2013 10:05 AM
Subject:
Re: [e4-dev]
eScriptMonkey naming
Sent by:
e4-dev-bounces@xxxxxxxxxxx
Hi Paul,
I thought that I had to rename
the namespace before moving to E4 but if I don’t, I’m starting to migrate
to E4 this afternoon. (Except Python interpreter).
However I would like to know
if it was possible to have (somewhere into the eclipse Bugzilla) a
place where I can add tickets. Maybe a E4 component or something like that.
This would help me to keep track of what I’m doing and what I have to
do.
Regards.
Arthur Daussy
Atos
arthur.daussy@xxxxxxxx
+33 5 34 36 32 90
De : e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx]
De la part de Paul Webster
Envoyé : mercredi 2 octobre 2013 14:48
À : E4 Project developer mailing list
Cc : Discussions about scripting Eclipse.
Objet : Re: [e4-dev] eScriptMonkey naming
On Wed, Oct 2, 2013 at 4:11 AM,
DAUSSY Arthur <arthur.daussy@xxxxxxxx>
wrote:
Hi All,
Time has come..
Using the vote previously published you have decided that the new Eclipse
Scripting Component would be named "EASE" standing for Eclipse
Advanced Scripting Environment.
Renaming the source is the first step, then we will migrate the source
into E4 repository. (Do you know if the repository is already available?)
The E4 repo is ready for you guys:
http://git.eclipse.org/c/e4/org.eclipse.e4.scripting.git/
org.eclipse.ease.* sounds like
as good a namespace as any.
If you have clearance to bring
the source over, why not push it over in a working state and then do the
rename in the E4 repo so we have a record if things go wrong?
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
Ce message et les pièces jointes sont confidentiels
et réservés à l'usage exclusif de ses destinataires. Il peut également
être protégé par le secret professionnel. Si vous recevez ce message par
erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire.
L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité
du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien
que les meilleurs efforts soient faits pour maintenir cette transmission
exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard
et sa responsabilité ne saurait être engagée pour tout dommage résultant
d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it. As its integrity
cannot be secured on the Internet, the Atos group liability cannot be triggered
for the message content. Although the sender endeavors to maintain a computer
virus-free network, the sender does not warrant that this transmission
is virus-free and will not be liable for any damages resulting from any
virus transmitted._______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev