You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Oliver Kleen (JIRA)" <ji...@apache.org> on 2019/04/30 12:28:00 UTC
[jira] [Updated] (NETBEANS-2483) Break points for maven based RCP
module do not work property
[ https://issues.apache.org/jira/browse/NETBEANS-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Kleen updated NETBEANS-2483:
-----------------------------------
Description:
Setting break points for a maven based RCP module do not work properly if the module does also deploy its sources as an artifact to the repository.
It seem to be the case that the break points set in the sources of the opened project are fully ignored. I.e. when starting the debugger the break points do not trigger at all.
However, if a break point is set for the read-only sources of the deployed source code artifact (via dependency section of the main application) then everything works as expected.
The problem can be reproduced as follows:
* download the attached sample project
* tar -xzvf debugtest.tgz
* open the maven RCP project within netbeans
* clean and build
* open Installer.java from sub-module debugtest-sample
* set a break point for the run method of the @OnStart callback
* start the debugtest application in debug mode
* bad: observe that the break point does not trigger
* remove the file "com/mycompany/debugtest-sample/1.0-SNAPSHOT/debugtest-sample-1.0-SNAPSHOT-sources.jar" from the local maven repository
* try to debug again
* good: observe that the break point triggers as expected
* therefore it is supposed that the problem is somehow related to the deployed source artifact
was:
Setting break points for a maven based RCP module does not work properly if the module does also deploy its sources as an artifact to the repository.
It seem to be the case that the break points set in the sources of the opened project are fully ignored. I.e. when starting the debugger the break points do not trigger at all.
However, if a break point is set for the read-only sources of the deployed source code artifact (via dependency section of the main application) then everything works as expected.
The problem can be reproduced as follows:
* download the attached sample project
* tar -xzvf debugtest.tgz
* open the maven RCP project within netbeans
* clean and build
* open Installer.java from sub-module debugtest-sample
* set a break point for the run method of the @OnStart callback
* start the debugtest application in debug mode
* bad: observe that the break point does not trigger
* remove the file "com/mycompany/debugtest-sample/1.0-SNAPSHOT/debugtest-sample-1.0-SNAPSHOT-sources.jar" from the local maven repository
* try to debug again
* good: observe that the break point triggers as expected
* therefore it is supposed that the problem is somehow related to the deployed source artifact
Summary: Break points for maven based RCP module do not work property (was: Break points for maven based RCP module does not work property)
> Break points for maven based RCP module do not work property
> ------------------------------------------------------------
>
> Key: NETBEANS-2483
> URL: https://issues.apache.org/jira/browse/NETBEANS-2483
> Project: NetBeans
> Issue Type: Bug
> Components: debugger - Java
> Affects Versions: 11.0
> Environment: java version "1.8.0_172"
> Java(TM) SE Runtime Environment (build 1.8.0_172-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.172-b11, mixed mode)
> CentOS Orthogon Linux release 7.2.1511
> Kernel 3.10.0-327.el7.x86_64 on an x86_64
> Reporter: Oliver Kleen
> Priority: Major
> Fix For: Next
>
> Attachments: debugtest.tgz
>
>
> Setting break points for a maven based RCP module do not work properly if the module does also deploy its sources as an artifact to the repository.
> It seem to be the case that the break points set in the sources of the opened project are fully ignored. I.e. when starting the debugger the break points do not trigger at all.
> However, if a break point is set for the read-only sources of the deployed source code artifact (via dependency section of the main application) then everything works as expected.
> The problem can be reproduced as follows:
> * download the attached sample project
> * tar -xzvf debugtest.tgz
> * open the maven RCP project within netbeans
> * clean and build
> * open Installer.java from sub-module debugtest-sample
> * set a break point for the run method of the @OnStart callback
> * start the debugtest application in debug mode
> * bad: observe that the break point does not trigger
> * remove the file "com/mycompany/debugtest-sample/1.0-SNAPSHOT/debugtest-sample-1.0-SNAPSHOT-sources.jar" from the local maven repository
> * try to debug again
> * good: observe that the break point triggers as expected
> * therefore it is supposed that the problem is somehow related to the deployed source artifact
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists