[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mdt-papyrus.dev] Re: Copyrights possible problems
|
Title: RE: [mdt-papyrus.dev] Re: Copyrights possible problems
Hi Guys,
Of course it's similar because we use together the same tutorial on web
as an exemple of creating a navigator !
And of course, there isn't 100 differents ways to implement features on
the top of an Eclipse architecture.
But if you want your copyright inside this file, no problem. I don't
really care.
Copyrith is an important thing, of course. But to be clear, for us,
having a stable tool is more important than having our copyright inside
source code.
I hope these problems doesn't offend you. If you have problem and don't
have a 100% trust of what we and Jerome do, please call me.
There were already these kind of suspicions with the EEF feature, and
there were unfounded.
Francisco Javier Cano a écrit :
Hello Jerome,
I have also found that in the Papyrus navigator some of the code is
extremely similar to the MOSKitt model navigator code.
I guess some of the MOSKitt code was used to create the Papyrus
navigator.
If that is the case, would mind stating that in the relevant Papyrus
headers?
Regards,
Javi
----
Francisco Javier Cano Muñoz
Programador senior
Prodevelop
www.prodevelop.es
-----Original Message-----
From: mdt-papyrus.dev-bounces@xxxxxxxxxxx on behalf of Jérôme BENOIS
Sent: Wed 6/24/2009 14:16
To: GERARD Sebastien 166342
Cc: Papyrus Project list
Subject: [mdt-papyrus.dev] Re: Copyrights possible problems
Hi,
I added the missing headers in revision 352.
Regards,
Jérôme.
GERARD Sebastien 166342 wrote:
> Both headers and copytright section have to be changed
accordingly. Initial contributor has to be kept as in the original
class. In this case, it should not have been new classes but updated
classes.
> Could you please Jerome correct all these errors?
>
> Thanks,
> Sébastien.
>
> -----Message d'origine-----
> De : Jérôme BENOIS [mailto:jerome.benois@xxxxxxx]
> Envoyé : mardi 23 juin 2009 17:23
> À : GERARD Sebastien 166342
> Cc : Etienne Juliot; Papyrus Project list; Cedric Dumoulin
> Objet : Re: Copyrights possible problems
>
> Hi Cedric, Sebastien and All,
>
>> So, two points:
>> 1 - I would like to know what happened?
>>
>>
> It seems the class CreateGmfClassDiagramCommandHandler and
> CreateClassDiagramCommand are not quite similar. It is three
differences :
> - the class name
> - the javadoc class header
> - the class inheritance three (extends)
> But, indeed the rest of the content is quite similar.
>
> I think, when we refactored the source code to add wizards UI with
the
> dedicated extension point. We created a new class
> CreateXXXDiagramCommand for each diagrams. It seems We kept the two
> creation class to preserve compatibility with toolbar, and removed
the
> CreateGmfXXXXDiagramCommandHandler in a second step.
> I think we have the same case for the 4 diagrams creation classes
call
> by the generic wizard.
>
>
>> 2 - I suspect this is not an isolate case, so how do we
process to
>> correct that ?
>>
>>
> I think it is a isolate case, but don't hesitate to signal another
> doubt. So to solve this, you can add your name is the header of the
> CreateXXXDiagramCommand classes.
>
> Regards,
> Jérôme.
>
>
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
begin:vcard
fn:Etienne Juliot
n:Juliot;Etienne
org:Obeo
adr;quoted-printable:;;2 rue Robert Schuman;Rez=C3=A9;;44400;France
email;internet:etienne.juliot@xxxxxxx
tel;work:+332 51 13 55 94
tel;cell:+336 86 78 14 82
url:http://www.obeo.fr
version:2.1
end:vcard