[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
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
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature