[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [dsdp-mtj-dev] Going from mdl to source code
|
Kevin, I'm tired to explain the same thing
repeatedly.
You must read the EMF generation web-pages, there the model
generation is explained enough deeply.
There is no sense for me to write the same in a new
document.
(as from a legal perspective, I cannot send you a
document thats content is from an IBM tech. web-article as my own
writing)
The proper headers you have to set with configuring the EMF
with the proper header information.
Kevin, if you go through the pointed documentation, you see
that everyting is fully public information and there is no
hidden secrets here. The only thing is that you have to
know that what you are doing.
I'm hoping that you can find the time to read the related
documents, do some tests and conclude your goal to generate the src from the
model.
After reading these mails, their attitude and hearing
the discussion from the last telco, I feel really sad about the situation
now.
I would feel much more better if here would
be discussion about how to do the missing tasks and reach the projects
milestones, than discuss
about e.g. protectionism.
-Arto
Arto,
Just provide the instructions. As it turns out,
your recent changes reinstated the use of the fields that were ignored, so
changes are not necessary. However, the documentation is. Get over
your protectionist attitude and provide the information. If you have
others who are able to do it, have them provide the information. I don't
care who documents it, as long as the entire set of steps from set-up to
completion are provided. You state in your mail that you have do make
changes to get the license information in. Steps like that need to be
documented.
kevin
-----------------------------------------------------------------
Kevin
Horowitz
khorowit@xxxxxxxxxx
Expeditor Tools Development
Workplace
Portal and Collaboration Software
IBM - Boca Raton,
+1-561-862-2113
<Arto.Laurila@xxxxxxxxx>
Sent by: dsdp-mtj-dev-bounces@xxxxxxxxxxx
05/31/2007 02:23 AM
|
Please respond
to
Mobile Tools for The Java Platform mailing list
<dsdp-mtj-dev@xxxxxxxxxxx> |
|
|
To
| <dsdp-mtj-dev@xxxxxxxxxxx>
|
|
cc
| <dsdp-mtj-dev-bounces@xxxxxxxxxxx>
|
|
Subject
| RE: [dsdp-mtj-dev] Going from mdl
to source code |
|
Kevin,
What is going over here?
The information is
totally public for everybody and now YOU should calm down.
Certainly the
model driven development do have one "risk" and that is the model management.
As now our Rose UML has been in the CVS for public access and
it certainly would be nice if you would like to
take action to make improvements to manage the mode, even propose design
changes through that.
As you
state that you may have some improvements to the model, where is the design? A
UML or word document would help all others to understand your goals
and the design in your side.
As we do have agreed on earlier that the model should not be changed
and generated in many places, cause of the risk that the new model would cause
some
malfunction or bugs. You
self have agreed and said that it should not be done parallel in many
places.
As you have not been willing to expose the design behind of your
changes, it would certainly be very nice to everybody to know that what the
design change is and
is it
supporting the active, high priority tasks and our release plan.
My worry is that some persons would like to change the model for some
external products needs without having discussion with the project members,
do not actually focus to the
agreed tasks and the release plan.
As it seems that you have send a lot of
mail to many places, it would be nice that you explain a bit more about your
goals and what you are doing?
By going through the CVS and seeing that what has
been done by each person and comparing that to the agreed task list, it feels
a bit sad that you have not been able to
proceed in the main agreed tasks. As you state in your
private mail that you have had holiday
It seems that the Usersupplied plug-in has been your main task (is that
somehow supporting the IBM internal tooling?, not anyway any external
usage).
Why you cannot discuss
more open on this and expose your needs and we could all agree about the
design around that.
There is not secret or hidden issues around the
EMF usage. Thus, it does have an issue that there are a lot of dependencies,
so any changes must be discussed in advance
with the project members. I wish that you could also agree
on that.
The EMF generation is
fully normal EMF usage, take the Rose model and generate it to EMF model, then
generate the src from that.
Please see these URLs for example:
http://dev.eclipse.org/viewcvs/indextools.cgi/org.eclipse.emf/doc/org.eclipse.emf.doc/references/overview/EMF.html
http://dev.eclipse.org/viewcvs/indextools.cgi/org.eclipse.emf/doc/org.eclipse.emf.doc/tutorials/clibmod/clibmod.html
The
normal generation does not ask, nor figure out the license header, so you have
to modify the generator to apply the proper header file.
The model can be generated by who ever, the only
wish is that the person should know what he is doing.
With totally
unrelated to this, I have done some studies around the EMF with other
developers and they could independently generate needed EMF model and source
code from an Rose UML. So, I do
not feel it as a show stopper if I have not written any other documentation
about the model management, cause it is following
exactly the public and known web-based information.
Certainly there is a burden to learn it.
I do have a proposal that we should
concentrate against the high priority tasks and not bundle here some other
issues.
My first priority is
the MTJ related work around the agreed top priority tasks and all other
support for other products is coming in second priority.
A question to you
Kevin, in what agreed tasks are you working now and how these are helping the
project to achieve the release?
I did try to call
you yesterday (16:30 GMT+3), but was it too early for you?
ps. I'm surprised and glad on your care to my health, thanks.
-Arto
From: dsdp-mtj-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of ext Kevin
M Horowitz
Sent: 30 May, 2007 17:00
To: Mobile Tools for
The Java Platform mailing list
Cc: dsdp-mtj-dev@xxxxxxxxxxx;
dsdp-mtj-dev-bounces@xxxxxxxxxxx
Subject: RE: [dsdp-mtj-dev] Going
from mdl to source code
Arto,
Provide the details so that there is not a single
person who controls the information What happens if you get hit by a bus
on the way home tonight?
kevin
-----------------------------------------------------------------
Kevin
Horowitz
khorowit@xxxxxxxxxx
Expeditor Tools Development
Workplace
Portal and Collaboration Software
IBM - Boca Raton,
+1-561-862-2113
<Arto.Laurila@xxxxxxxxx>
Sent by:
dsdp-mtj-dev-bounces@xxxxxxxxxxx
05/30/2007 09:32 AM
|
Please respond
to
Mobile Tools for The Java Platform mailing list
<dsdp-mtj-dev@xxxxxxxxxxx> |
|
|
To
| <dsdp-mtj-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [dsdp-mtj-dev] Going from mdl
to source code |
|
First, why do you
want to generate the EMF code again, what changes are you doing
there?
I
have copied again the related src to the cvs, have you checked the
cvs?
Can you send your rose model that we could see the
changes?
-Arto
From: dsdp-mtj-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of
ext Kevin M Horowitz
Sent: 30 May, 2007
16:28
To: Mobile Tools for The Java Platform mailing
list
Subject: RE: [dsdp-mtj-dev] Going from mdl to source
code
Arto,
I see how EMF works. The problem is that you promised to
provide the steps that you use to go from Rose Model to EMF code so that when
the code is generated the code matches the existing code. Just
generating code from a model does not match the existing code, and we don't
want to regression test the differences. You stated, during the last
conference call, that you figured out the steps that you took to make the code
match, and promised documentation about those steps on May 21st. It as
also a recurring theme during the previous development cycle that was not
provided. I do not want to just generate the code using the defaults,
and have multiple changes that break our use since some of the supporting
structures are different when the code is generated.
Please send the information, and
we can stop wasting cycles repeating ourselves.
kevin
-----------------------------------------------------------------
Kevin
Horowitz
khorowit@xxxxxxxxxx
Expeditor Tools Development
Workplace
Portal and Collaboration Software
IBM - Boca Raton,
+1-561-862-2113
<Arto.Laurila@xxxxxxxxx>
Sent by:
dsdp-mtj-dev-bounces@xxxxxxxxxxx
05/30/2007 09:15 AM
|
Please respond
to
Mobile Tools for The Java Platform mailing list
<dsdp-mtj-dev@xxxxxxxxxxx> |
|
|
To
| <dsdp-mtj-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [dsdp-mtj-dev] Going from mdl
to source code |
|
Kevin,
On how
EMF works, please see:
http://www.eclipse.org/modeling/emf/
The changes that we are
doing in the codebase, are agreed in earlier (also by you).
If there are some new
bugs, we have to fix those when that is needed.
Instead of having so much
mail writing, there could be some real coding with in the project.
-Arto
From: dsdp-mtj-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of
ext Kevin M Horowitz
Sent: 30 May, 2007
16:10
To: Mobile Tools for The Java Platform mailing
list
Cc: dsdp-mtj-dev@xxxxxxxxxxx;
dsdp-mtj-dev-bounces@xxxxxxxxxxx
Subject: RE: [dsdp-mtj-dev]
Going from mdl to source code
Arto--
Send the promised data, or fix the code that you broke, and
send the promised data so that we don't have this problem in the
future.
kevin
-----------------------------------------------------------------
Kevin
Horowitz
khorowit@xxxxxxxxxx
Expeditor Tools Development
Workplace
Portal and Collaboration Software
IBM - Boca Raton,
+1-561-862-2113
<Arto.Laurila@xxxxxxxxx>
Sent by:
dsdp-mtj-dev-bounces@xxxxxxxxxxx
05/30/2007 09:03 AM
|
Please respond
to
Mobile Tools for The Java Platform mailing list
<dsdp-mtj-dev@xxxxxxxxxxx> |
|
|
To
| <dsdp-mtj-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [dsdp-mtj-dev] Going from mdl
to source code |
|
Kevin,
make a proposal to solve this and we will analyze it.
-Arto
From: dsdp-mtj-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of
ext Kevin M Horowitz
Sent: 30 May, 2007
16:00
To: Mobile Tools for The Java Platform mailing
list
Cc: dsdp-mtj-dev@xxxxxxxxxxx;
dsdp-mtj-dev-bounces@xxxxxxxxxxx
Subject: RE: [dsdp-mtj-dev]
Going from mdl to source code
There is just one structure in the rpm to duplicate the
config that is in the dpp and is no longer being used in the code.
-----------------------------------------------------------------
Kevin
Horowitz
khorowit@xxxxxxxxxx
Expeditor Tools Development
Workplace
Portal and Collaboration Software
IBM - Boca Raton, +1-561-862-2113
<Arto.Laurila@xxxxxxxxx>
Sent by:
dsdp-mtj-dev-bounces@xxxxxxxxxxx
05/30/2007 08:08 AM
|
Please respond
to
Mobile Tools for The Java Platform mailing list
<dsdp-mtj-dev@xxxxxxxxxxx> |
|
|
To
| <dsdp-mtj-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [dsdp-mtj-dev] Going from mdl
to source code |
|
Kevin, as I did fastly compare the models, I did not
see your changes.
Could you point me the design changes and reason behind of
that?
-Arto
From: dsdp-mtj-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of
ext Kevin M Horowitz
Sent: 01 May, 2007
18:02
To: dsdp-mtj-dev@xxxxxxxxxxx
Subject:
[dsdp-mtj-dev] Going from mdl to source code
Importance:
High
Arto,
I am trying to resolve the problem I have now
that we are not persisting the deviceplatform data. I have looked at adding
some configuration data to the device to give me the same items we had in the
runtime platform, but can't figure out what the steps are to go from the Rose
.mdl file to compatible code in the source tree.
I have looked at the
org.eclipse.mtj.core.model plugin and see the MtjEmfModel_1_20.2.genmodel
code. If I use this to generate code, the code is different then the code
already in CVS. How do you go from this representation to code that matches
our existing base.
I found documentation on how to go from a .mdl file
to the genmodel code, but if you could document the entire process, that would
be great.
If you can't do that quickly, I have checked in the update
to the model I made as 1_21, and you can review the changes, and generate the
code for now. I am new at doing this, so it may not be correct, but since I
couldn't generate the code, I couldn't verify that I did everything
correctly.
Thanks.
kevin
-----------------------------------------------------------------
Kevin
Horowitz
khorowit@xxxxxxxxxx
Client Platforms and Technology
Development
Workplace Portal and Collaboration Software
IBM - Boca
Raton, +1-561-862-2113_______________________________________________
dsdp-mtj-dev mailing
list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev_______________________________________________
dsdp-mtj-dev mailing
list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev_______________________________________________
dsdp-mtj-dev mailing
list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev_______________________________________________
dsdp-mtj-dev mailing
list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev_______________________________________________
dsdp-mtj-dev mailing
list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
