This is a follow up to 60d95da97b (Bug
399460) as in that change the reporting option inadvertently changed.
Change-Id: I1afe70632107ab388be09a707e8e9fc419f76b91
The package import was actually causing grief in our downstream
tests. Appears to really confuse equinox, or more likely myself,
and cause the java.xml classes to get loaded differently causing a
bizarre error.
Change-Id: I12f80f335a40b11e2f600dc67ff0a0d5e13eecc7
This is a convenience for working in combination with the source
of o.e.tools.template which is not unusual.
Also add a few more missing things to Oomph setup for Java 11.
Change-Id: Ifc6105e251a7b8d855cf76401cdb3740c55f79c9
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
- add new ContainerPortDialog class to allow user to specify
ports in the launch configuration Container tab
- add new ContainerTabModel and ExposedPortModel classes to
support new functionality
- add new Ports group to ContainerTab and have a table
where a user can add, edit, remove, and select ports
for publishing to the host
- add new attribute ATTR_EXPOSED_PORTS to ILaunchConstants for
saving and restoring user selected ports in C launch
configuration
- add needed internal messages to support new port settings
functionality
- bump up org.eclipse.cdt.docker.launcher version
Change-Id: I93b7503bdc141e3077418800352507ef38e65ab1
o.e.launchbar.ui.controls uses annotations and thus imports
javax.annotations package. This package is removed in Java 11 and
equinox doesn't put javax.annotation bundle on the classpath resulting
in launchbar not functioning at all.
The fix is to Import-Package: javax.annotation like eclipse platform
bundles do and letting equinox resolve it either from the jvm or the
bundle shipped with platform.
Change-Id: Id5702919b233b3fea424fa2f1db15505eee8ecb7
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
- If the argument for a template template paramter is unknown
(ICPPUnknownType), don't create a problem.
- Ensure that a possible argument-parameter mismatch is caught at
template instantiation time.
Change-Id: Ief61ef93f9d0c19d043aedb89f1c5e66c0374ef2
Signed-off-by: Hannes Vogt <hannes@havogt.de>
- use of CommandLaunchManager requires higher version of cdt.core
than Autotools specified so up to 6.5.0
Change-Id: I315e69defeee9d7d1e6c016edff2d96013fe13e9
It is not used anywhere and it's internal.
Change-Id: I4e157ec7fd1184118aea8f6bef35a850dfeb0945
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
For more recent versions fo LLDB (8.0.0-r345563) this work-around is not required.
This is a follow-up to bug 539641.
See also https://reviews.llvm.org/D52953
Change-Id: If5f951a33fab8781a594175571d0ad5131e9ef15
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
This class is gone in Java 11. Instead use the one from Orbit. Also, this used
com.sun.xml.internal.bind.v2.ContextFactory which is also gone so we have to
directly use com.sun.xml.bind.v2.ContextFactory also from Orbit.
Change-Id: I808ebe5a6ade19e86d4c31f2f2789063dc3bf3b4
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
- add check that buildConfig field has been set before performing any
activities on it
Change-Id: If3ab7a0b20b54a9c16b26902c06b615e4c514ffa
(cherry picked from commit 9031090393)
As part of this change, ReturnChecker was refactored to compute the
return type as an IType, which allowed for removal of some logic in
ReturnChecker which duplicated CPPVisitor's type resolution work.
Change-Id: I9cd8512164d650a5ee11d2e58fdae477e3c428a2
- bump up minimum org.eclipse.cdt.core needed for
org.eclipse.cdt.docker.launcher plug-in so that
ICBuildConfigurationManager2 interface is available
Change-Id: I5e77e7b43bdea1f0b59c79fcdfced7c162b64e9a
If the build command in a container build terminates with non zero exit
code (e.g. make command not found) an error is displayed.
Change-Id: Ib6349aa6c22c1a3bb9c0d2920110bc69773f8da1
Signed-off-by: Hannes Vogt <hannes@havogt.de>
Sort the configuration list in the same order as used by the project
property pages (case-insensitive nonlocalized), almost the same order as
used in the Project > Build Configurations > Set Active menu
(case-sensitive nonlocalized), not in the internal order coming from the
.cproject file.
Change-Id: Ia05bd163043f762dd96da4c69d409ecee9accb8c
Signed-off-by: Christian Walther <walther@indel.ch>
- modify ContainerGCCToolChainProvider.init so that the
CBuildConfigurationManager.recheckConfigs() call is done
within a separate job so the init() call will return
without causing deadlock
- do the same for ContainerTargetTypeProvider
- modify CBuildConfigurationManager initProviders() method to
be synchronized
Change-Id: I4ca9371fb340887233872b6d315621a24450fb2b
Add handling of constructor/destructor attributes and some improvement
when functions were previously declared but not defined as used.
Change-Id: I7537bc87c6c4bc5b294d8e15fe5b42c92b3f2974
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
- Fixed delegating constructor resolution for templated classes in
ClassMembersInitializationChecker
- Added a unit test for this bug
Change-Id: Idb072ec05e66e0f10af53db8258459ad14f7f329
Signed-off-by: Bassem Girgis <brgirgis@gmail.com>
Since the Eclipse Platform 4.10 is dropping support for 32-bit,
it doesn't make sense to still build these and it will ultimately
fail once we start building against 4.10.
Change-Id: Ia83a93b99092b7a3378ed95607411da5835118a6
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
In some situations, it's convenient to create option categories on the
abstract tool and use an option applicability calculator to hide the
option category if no option is added to the category in an extending
instance of the tool.
To make the decision, the calculator needs to know what category is
to be checked.
Change-Id: Id4a269ee583f1f3dee88dee797ba89a0e92d1a42
Signed-off-by: Torbjörn Svensson <torbjorn.svensson@st.com>
In order to work around
https://bugs.eclipse.org/bugs/show_bug.cgi?id=539902
Also update the target to make it closer to the Oomph setup.
Change-Id: Ie581ea499d7cd0956780717f3a34e0762f868c0d
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
lldb-mi doesn't implement "-gdb-set breakpoint pending"
so instead we always use "-break-insert -f" to always use pending breakpoints.
Once the -gdb-set is implemented in lldb-mi, we can remove this.
See also https://reviews.llvm.org/D52953
Change-Id: Id07da58e0530898401d2f7285c44c97b38637542
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
