Build: NetBeans IDE 6.0 (Build 200711261600)
VM: Java HotSpot(TM) Client VM, 10.0-b19
OS: Windows XP, 5.1, x86
Integrating Profiler with project.
Created attachment 60111 [details]
Reassigning to new module owner jskrivanek.
Created attachment 62215 [details]
This issue has already 5 duplicates
Profiler integration relies on a specific name of your ant build file. Namely, it tries to find "build.xml".
Problem is that for Java projects with existing sources the build file name is fully customizable. Due to this the
profiler will have to recognize this situation and search for the custom build file instead of the default one.
Integrated into 'main-golden', available in NB_Trunk_Production #324 build
User: Jarslav Bachorik <firstname.lastname@example.org>
Log: #132721 - NPE while integrating profiler with a project with existing sources
*** Issue 136614 has been marked as a duplicate of this issue. ***
*** Issue 154571 has been marked as a duplicate of this issue. ***
See issue #136614
The problem was not fully fixed - the profiler correctly modifies the custom build file but it still tries to use the
hard-wired "build.xml" when profiling is started.
It's fully fixed now : http://hg.netbeans.org/profiler-main/rev/05aea724a0ef
The workaround for a time being would be not to use the folder with the existing build script as a new project directory
- which should be a recommended approach anyway.
*** Issue 75953 has been marked as a duplicate of this issue. ***
The correct changeset for fixes is http://hg.netbeans.org/profiler-main/rev/901c6f4dcb70
one last update - due to problems with the local hg repository I had to rollback the fix and reintroduce it in
Integrated into 'main-golden', will be available in build *200812091520* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jaroslav Bachorik <email@example.com>
Log: #132721 - custom ant build script name support
VERIFIED in build 200812180001
Could you please state what the correct changeset to port to the release65_fixes branch is? There are three possible changesets 05aea724a0ef, 901c6f4dcb70 and de061552d2b7 in descriptions. Should they be applied all one by one? Or should just the last one be applied and the remaining two
changesets could be apprehended as mistakes?
The correct changeset to apply is de061552d2b7.
The fix has been ported into the release65_fixes repository.
The changes are in eager modules (org.netbeans.modules.profiler.j2ee and org.netbeans.modules.profiler.j2se). Even though the specification versions were
incremented for both of them, they are not updated by plugin manager during update. In other words, the fix isn't deliverable via a patch. It seems to be a
bug in the plugin manager.
The issue has been rolled back from the release65_fixes branch (http://hg.netbeans.org/release65_fixes/rev/c74c8b261099). Now, it is the 65patch3
The status whiteboard "65fixes4-candidate" has been removed.
At this time our proactive patches for the NetBeans 6.5.x IDE have concluded.
If you own a Sun service plan contract for NetBeans, you may wish to contact
Sun Service http://www.sun.com/contact/support.jsp to request a fix via the
product defect escalation process.
For more information on purchasing a Sun service plan contract for NetBeans,
refer to the service plan item "Sun Software Service Plans (S3P) for Developers"
in the Sun Service table found on our NetBeans Support Resources