Also restructures the pom.xmls to put the modules in the top level
so we can order them to have the test plugins build after them.
Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
This removes a lot of pom.xml from the source tree. This is using the
"POM-less" Tycho functionality.
See
https://wiki.eclipse.org/Tycho/Release_Notes/0.24#POM-less_Tycho_builds
One advantage of this is that you do not need to update the version in
the pom.xml when you change it in the MANIFEST.MF because the pom.xml is
automatically generated. This also reduces a lot of the duplicated
information and pom.xml repetition.
- Maven 3.3 and up is required.
- Only eclipse-plugins and eclipse-features can be pom-less.
Repositories, target and others still have pom.xml.
- New parent poms are added because a parent is necessary directly one
level above the plug-in/feature that will have its pom generated
- Some test plug-ins had to be renamed .test -> .tests because it's
required so that it detects that it's a test plug-in
- Some suites were renamed so that they all use the same consistent name
"AutomatedIntegrationSuite"
- Profiles were added for the more common test configurations. They are
activated by the presence of simple .properties files that only serve to
activate the correct profile. The profiles:
- One for UI tests (UI present and start in UI thread)
- One for SWTBot tests (UI present and do not start in UI thread)
Other test plug-ins that are too different are kept intact and still
have
a pom.xml
- Fragments are kept intact since they all have different target
platform configurations
Change-Id: I9d73380eb766f547830c552daf08053a30b1845c
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
may be wrong in Little Endian presentation
The enclosing markings are meant to reflect contiguous regions of
memory,
however the current Little Endian representation in the traditional
render modifies the memory map to attempt to reflect how the memory
would
be loaded into registers with a size matching the cell size.
The markings are therefore unsuitable for for this special case,
this change removes these markings when the Little Endian formatting is
selected.
Change-Id: I1d7879f8b23329b33e2b17e8c8444d1266b9ef0a
This patch fixes a variable overlay issue, that causes two overlays to
become mistakenly mangled together.
Change-Id: Idbee5b95f85810144dd71e2a397bd38fcd0bcec5
- Adding default methods can now be ignored
- Adding fields is now an error but we probably want to ignore this
because it is quite restrictive
Change-Id: Ie57c69f54c64e4913d1498b02e86d00c93f8101a
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
This commit removes explicit source features and has tycho create them
automatically, along with all other source features that were not
previously defined. The logic to auto-generate is in the root pom.xml
For all pre-existing source feature, the name presented to the user has
been changed to use the default name used by Tycho, which is "Developer
Resources". This will provide a more standard user-experience with
respect to other source features built by Tycho.
Existing SDK features are kept for backwards compatibility.
All the names of the auto-generated source features that replace an
existing source feature have stayed the same except for the
'testsrunner' feature; for that one name change, a p2.inf file is added
to allow upgrading from the old named feature to the new named feature.
Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
This apply to the Floating Point and Traditional Renderings,
When calling these preferences from the drop down inside the memory
view, the associated preferences dialog comes up with the left side
empty, this left side shall reflect the preference page three path.
The call to the preference dialog has been replaced to use
PreferenceUtil.createPreferenceDialogOn which takes care of this.
Change-Id: I89d6b1289a7eac5ffcca54a1ca6d8b3c3ed831df
* Added an adjustment to the calculation of the addressable char width
so it does not go beyond the containing cell size when using radixes
where the number of characters does not grow linearly with the number
of octets being represented.
This adjustment is only necessary when the cell can contain the same
number of octets as the addressable size
Change-Id: Ic9643c98094bc28621e6807eeed0c283dbe6672a
information
This facility is dependent of the issues below.
Bug 489512 - Show local variables in the traditional memory render
Bug 489513 - Show registers in the traditional memory render
Allow the user to choose visibility of the available cross reference
information e.g. Variables, Registers
In addition to the preferences at a instance level, a global preference
is introduced to disable the resolution of additional information
altogether.
Change-Id: I9f8b9b612ff288b369ba6fca3402c0c911aa5f48
When using a `StringBuilder` or `StringBuffer` to create a string message,
using implicit string concatenation inside an `.append()` call will
create a nested StringBuilder for the purposes of creating the arguments,
which will subsequently be converted to a String and then passed to
the outer StringBuilder.
Skip the creation of the intermediate object and String by simply
replacing such calls with `buffer.append(a).append(b)`.
Where values are compile time String constants, leave as is so
that the javac compiler can perform compile-time String concatenation.
Ensure that NEWLINE isn't appended in such a way since it is not
a compile time constant `System.getProperty("line.separator")`
Change-Id: I4126aefb2272f06b08332e004d7ea76b6f02cdba
Signed-off-by: Alex Blewitt <alex.blewitt@gmail.com>
There are many opportunities for replacing `StringBuffer` with
`StringBuilder` provided that the type isn't visible from the
public API and is used only in internal methods. Replace these
where appropriate.
Change-Id: Ic2f50c5b6f3c3a4eae301bb3b40fb6faed235f79
Signed-off-by: Alex Blewitt <alex.blewitt@gmail.com>
Using `new Integer` and other wrapper types such as `new Character` results in
potential extra heap utilisation as the values are not cached. The built-in
`Integer.valueOf` will perform caching on numbers in the range -128..127 (at
least) using a flyweight pattern. In addition, parsing `int` values can be done
with `Integer.parseInt` which avoids object construction.
Adjust tests such as `"true".equals(expr)` to `Boolean.parseBoolean(expr)`.
Change-Id: I0408a5c69afc4ca6ede71acaf6cc4abd67538006
Signed-off-by: Alex Blewitt <alex.blewitt@gmail.com>
When using DSF-GDB, the handleSuspend event is received only when a
breakpoint is hit (i.e. not when it's actually suspended),
However memory changed events are received when applicable during
stepping, however the base code does not call the "archiveDeltas()" for
this event.
This change adds a call to archiveDeltas if the update mode is set to
UPDATE_ALWAYS upon reception of memory change events.
TO REPRODUCE this problem:
The issue is that only one snap shot of history is applied with the first
address / expression search, and this is used for all other comparissions,
So you can search for a variable with bigger address value as a first
memory search, and then step the code and see that variables close by
with smaller address values will be updated but not colored.
e.g.
&Test -> address 0x110
&X -> address 0x100
if &Test is used as the first memory search, and then the code changes
value of &X while stepping the code, the cell holding &X will not be
colored as expected.
Change-Id: Ibdc1fae6ed73ec2819fe9539d56f9ea9b6302535
spaces with 64-bit address
- Fix scroll adjustments according to current viewport addresses
- Add CTRL-Home/CTRL-END to go to start/end of memory space
- Add Home/END to go to start/end of the row
- Add eclipse debug tracing support
Change-Id: Ifba9f1e6c67e1cc6ccb8f6f8787a55520d8bf9be
Signed-off-by: Teodor Madan <teodor.madan@freescale.com>
This would make Tycho 0.23.0 fail. See bug 464649.
Change-Id: I4e4ce6fc2714b5179eeb7fdd16c9461517d67a47
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
getAdaptable() in 4.5 M6 has changed to use generics, making casting its
result no longer necessary.
Change-Id: Idd943216a925576bb72c784b2c5a2a4b8e8b00d2
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
features
Change-Id: I52a71e62f8161990657e96ef52403fd7f69698a2
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/27499
This means that:
- feature.xml files now make a reference to the shared license plugin
using version 0.0.0
- feature.properties files no longer have the text for the license
- license.html and epl-v10.html files are removed as they are part
of the shared license plugin
- build.properties files no longer reference removed files
- the main pom.xml file references the license repository
Change-Id: Ibd880480de3a07597084d44cce7b822903509079
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/27250
Change-Id: I0e72b6a4d685197191427c93b67b9a96d80da682
Signed-off-by: Ling Wang <ling.wang@silabs.com>
Reviewed-on: https://git.eclipse.org/r/15214
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
IP-Clean: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
Bug 398332 : The validation logic and feedback for all of the Importers/Exporters is very bad
Added more error checking. See comments in the bugzillas for the details.
Bug 398332 : The validation logic and feedback for all of the Importers/Exporters is very bad
I found some more editing edge cases as well as an NPE on starting a
new connection with the Browser up, which was the result of a previous
edit.
This is an initial solution which is made up of 2 parts
1.) Changed the lower-level renderer to filter based on memory block as well as debug target.
2.) Changed the parent render to become a listener for model changed events which are translated
in to direct calls to the renderer to update the displayed values.
This is an initial solution which is made up of 2 parts
1.) Changed the lower-level renderer to filter based on memory block as well as debug target.
2.) Changed the parent render to become a listener for model changed events which it translated in
to the older debug events the lower-level renderer is expecting.
Pawel has suggested a more compact implementation which I will persue. But for now this is at least
a current fix.
Create the Find/Replace dialog with the new memory block reference to
fix RejectedExecutionException problem when find after re-launching
project
Change-Id: I1d9b2ec5ace5bbc4d82adb14075f613dbe7c5d57
Reviewed-on: https://git.eclipse.org/r/6323
Reviewed-by: Mikhail Khodjaiants <mikhailkhod@googlemail.com>
IP-Clean: Mikhail Khodjaiants <mikhailkhod@googlemail.com>
Tested-by: Mikhail Khodjaiants <mikhailkhod@googlemail.com>
addresses that are more than 32-bits
Change-Id: I529b9a85d25327c4a48d809f52fd2d87d80a80fd
Reviewed-on: https://git.eclipse.org/r/5787
Reviewed-by: Randy Rohrbach <Randy.Rohrbach@Windriver.com>
IP-Clean: Randy Rohrbach <Randy.Rohrbach@Windriver.com>
Tested-by: Randy Rohrbach <Randy.Rohrbach@Windriver.com>
