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 151937 - 6.5 RC2 External Maven 2.0.9 & Shade Plugin
Summary: 6.5 RC2 External Maven 2.0.9 & Shade Plugin
Status: RESOLVED DUPLICATE of bug 151938
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-31 04:14 UTC by coder_lol
Modified: 2008-10-31 04:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description coder_lol 2008-10-31 04:14:51 UTC 
Windows, JDK 1.6.10 Netbeans 6.5 RC2, Maven 2.0.9

I have 2 3 POMs.

1. base-commons contain a number of pojos in xyz.domain.base
2. app-commons contains a number of pojos in xyz.domain.app
2a. Some classes in app-commons extends from base-commons classes.
2b. app-commons run maven-shade-plugin to combine base-commons into app-commons
3. serviceimpl depends on app-commons
3a. serviceimpl is built a-ok and passes tests even though Netbeans IDE flags a bunch of "types" errors.

operator != cannot be applied to xyz.domain.app.User, <nulltype>
incompatible types

If I don't use shade, then IDE works a-ok and does not annotate any errors.  For Maven projects, does Netbeans pull 
classes from dependent jars?

As-is, maven in Netbeans is un-usable when shade is used.
Comment 1 coder_lol 2008-10-31 04:17:43 UTC 

*** This issue has been marked as a duplicate of 151938 ***