This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 42228 - J2SE project type support fails to install due to missing JPDA debugger
Summary: J2SE project type support fails to install due to missing JPDA debugger
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 4.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-21 07:24 UTC by Jan Chalupa
Modified: 2006-03-24 10:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Exception stack trace (5.33 KB, text/plain)
2004-04-21 07:27 UTC, Jan Chalupa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Chalupa 2004-04-21 07:24:55 UTC
[dev-0404201800; Sun JDK 1.4.2_04]

I don't know if this is a debugger, core, or
nbbbuild bug. Feel free to re-assign as appropriate.

I get errors when starting daily build
#04040201800.    JPDA Debugger Ant Task is not
installed.

[org.netbeans.core.modules] *********** Exception
occurred ************ at 7:55 AM on Apr 21, 2004
Annotation: Error encountered while reading
MultiFileObject@4ac216[nbfs://nbhost/SystemFileSystem/Modules/org-netbeans-api-debugger-
jpda.xml]
org.netbeans.core.modules.InvalidException: While
parsing a dependency attribute:
java.lang.IllegalArgumentException: Invalid IDE de
pendency: ${ide.dependencies}

(full stack-tracke attached)

Apparently the ide.dependency property is not set
properly somewhere. Other modules seem to have
dependency on the JPDA Debugger Ant Task and fail
to install, too. The result is that J2SE Project
type is not available at all.

This is a showstopper for the Q-build testing.
Please fix asap.
Comment 1 Jan Chalupa 2004-04-21 07:27:00 UTC
Created attachment 14492 [details]
Exception stack trace
Comment 2 Jan Jancura 2004-04-21 08:51:22 UTC
fixed in the main trunk
Comment 3 Jan Jancura 2004-04-21 10:16:20 UTC
Th problem is in resolving of module-IDE-dependencies. I will fix it
later, but I am reverting my last change of manifests now:

Checking in manifest.mf;
/cvs/debuggerjpda/manifest.mf,v  <--  manifest.mf
new revision: 1.55; previous revision: 1.54
done
Processing log script arguments...
More commits to come...
Checking in ant/manifest.mf;
/cvs/debuggerjpda/ant/manifest.mf,v  <--  manifest.mf
new revision: 1.11; previous revision: 1.10
done
Processing log script arguments...
More commits to come...
Checking in api/manifest.mf;
/cvs/debuggerjpda/api/manifest.mf,v  <--  manifest.mf
new revision: 1.4; previous revision: 1.3
done
Processing log script arguments...
More commits to come...
Checking in ui/manifest.mf;
/cvs/debuggerjpda/ui/manifest.mf,v  <--  manifest.mf
new revision: 1.7; previous revision: 1.6
Checking in manifest.mf;
/cvs/debuggercore/manifest.mf,v  <--  manifest.mf
new revision: 1.66; previous revision: 1.65
done
Processing log script arguments...
More commits to come...
Checking in api/manifest.mf;
/cvs/debuggercore/api/manifest.mf,v  <--  manifest.mf
new revision: 1.4; previous revision: 1.3
done
Processing log script arguments...
More commits to come...
Checking in viewmodel/manifest.mf;
/cvs/debuggercore/viewmodel/manifest.mf,v  <--  manifest.mf
new revision: 1.4; previous revision: 1.3
done
Comment 4 Jan Chalupa 2004-05-08 07:07:07 UTC
Verified.