I just tried
another test and I think
there is be a problem.
Occasionally
I get an error when I make a
change and MTJ claims I need to save the Application Descriptor info
before
continuing. But I have already saved it and cannot make MTJ happy. This
problem
has been around for a while and is not related to the build hooks.
Perhaps I missed
something in my device import routine. The solution is to delete the
Runtimes
associated with the project and add them again.
What I did
was add two devices, A and B
and then I ran into the above problem, so I added C and deleted A and
B. Now
MTJ is happy with device C.
When I click
“Create Package”,
my code gets build hook notifications about THREE builds. All of them
report
the same active runtime name obtained from
project.getRuntimeList().getActiveMTJRuntime().getName()
The end
result is that my code does not
know when the build that is of interest is occurring.
Yes, that is
clear David. Thanks.
What I find
puzzling, however, is that I
can add device “B” to the list and I get the whole round of build
notifications, even for device “B” when it appears that nothing is
yet being built for device “B”. Is that because there is a lot of
building going on even before anything appears in the deployed folder?
Hi Jon,
Each build hook implementation gets notified both on
incremental and package builds. So if you have N devices then all hooks
will be
called N times one for each device once for every state transition. So
if i
have 2 devices and 5 build states for example, you will have 10 hook
calls. Was
I clear enough ??
Regards,
David Marques
Jon Dearden wrote:
Hi
everyone,
I have been
playing with the nightly build
Diego notified us of yesterday. It is a big leap forward from 1.0 M6.
Well done.
I have a
question for David about the
build hooks. At present, when I add a second device to the Runtime
list, the
SDK for that device gets notified through the whole range of build
steps (twice
actually) even though no JAD or JAR appears on the deployed folder for
that
device. This is before I click “Create Package”. Why is this?
Cheers,
Jon
Hi everyone,
We’ve just
published
our latest nightly build. This build has the latest in MTJ API and
documentation. All MTJ API javadocs were created (except for the
MTJCore class
that still under development.) and two new sections were added to the
Developer
guide: “Extending the build
process with custom build hooks.” and “Creating a Java ME MIDlet Template”.
This build also
have the
latest version of our new features, including documentation:
- Signing UI
Enhancements
- MIDlets templates
- Build Properties
support
- Build hooks
It’s highly recommended to anyone
extending MTJ
to take a look in the Developer Guide as the API was updated since the
latest
drop (a new Extension Point was added (Build Hooks) and the Library API
was
refactored (workspace is incompatible with previous version)).
The nightly build can be downloaded from http://download.eclipse.org/dsdp/mtj/downloads/drops/N-N20090422-200904221509/index.html
Please, take some
time and
try this new version, feedbacks are always welcome.
Regards,
Diego Madruga
Sandin
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public
information. Any use of this information by anyone other than the
intended
recipient is prohibited. If you have received this transmission in
error,
please immediately reply to the sender and delete this information from
your
system. Use, dissemination, distribution, or reproduction of this
transmission
by unintended recipients is not authorized and may be unlawful.
_______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public
information. Any use of this information by anyone other than the
intended
recipient is prohibited. If you have received this transmission in
error,
please immediately reply to the sender and delete this information from
your
system. Use, dissemination, distribution, or reproduction of this
transmission
by unintended recipients is not authorized and may be unlawful.
---------------------------------------------------------------------