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.
| Summary: | Add Dependency disregards classifier | ||
|---|---|---|---|
| Product: | projects | Reporter: | _ gtzabari <gtzabari> |
| Component: | Maven | Assignee: | Milos Kleint <mkleint> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jglick |
| Priority: | P3 | ||
| Version: | 7.0.1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
(In reply to comment #0) > 5. Bug #1: Classifier "null" is listed. This row shouldn't exist. Not sure what you are talking about. I see 5.11 [ jar,jdk15 ] - central 5.11 [ jar,jdk14 ] - central 5.11 [ pom ] - central Possibly a separate bug. Please use one issue for one bug. > 6. Bug #2: When [jar, jdk14] is selected the POM is missing the "jdk14" > classifier. True. I thought this was already filed but I cannot find it now. Bug #197235 is similar. > 7. Enhancement request: Code-complete doesn't work on <classifier>. Should I > file a RFE? Yes, this is unrelated and should be filed separately. >> 5. Bug #1: Classifier "null" is listed. This row shouldn't exist. > Not sure what you are talking about. Odd. It doesn't show up on my home computer (running 7.1 dev build 201107300600) but it did on my work computer running 7.0.1 final. Either my userdir is corrupt or this is fixed in 7.1. Either way, let's skip it. > 7. Enhancement request: Code-complete doesn't work on <classifier>. Should I > file a RFE? > Yes, this is unrelated and should be filed separately. Filed issue #200852 > 6. Bug #2: When [jar, jdk14] is selected the POM is missing the "jdk14" > classifier. > True. I thought this was already filed but I cannot find it now. Bug #197235 is similar. Okay, so I'll this issue will be dedicated to this specific bug. (In reply to comment #2) > > > 6. Bug #2: When [jar, jdk14] is selected the POM is missing the "jdk14" > > classifier. > > True. I thought this was already filed but I cannot find it now. Bug #197235 is > similar. > > Okay, so I'll this issue will be dedicated to this specific bug. from what I can tell this was most probably fixed in the 7.1 timeframe, at least on my 7.1.1 instance, the classifier *is* added (and is visible as a text field) (In reply to comment #1) > (In reply to comment #0) > > 5. Bug #1: Classifier "null" is listed. This row shouldn't exist. > > Not sure what you are talking about. I see > > 5.11 [ jar,jdk15 ] - central > 5.11 [ jar,jdk14 ] - central > 5.11 [ pom ] - central > > Possibly a separate bug. Please use one issue for one bug. I think the [pom] entry is caused by us or indexer getting confused by missing main artifact (main == without classifier). in that sense it's probably correct. Or at least not easily detectable what the correct approach is. In this case it's leaving it out, but there can be other cases as well. Classifier artifact can be anything. from what I can tell, this is fixed already, not sure if a result of another bug report (I could not find any) *** This bug has been marked as a duplicate of bug 188440 *** |
1. Add Dependency 2. Query: "org.testng" 3. Select org.testng : testng 4. Scroll down to version 5.11 5. Bug #1: Classifier "null" is listed. This row shouldn't exist. 6. Bug #2: When [jar, jdk14] is selected the POM is missing the "jdk14" classifier. I am getting: <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <version>5.11</version> </dependency> I am expecting: <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <version>5.11</version> <classifier>jdk14</classifier> </dependency> 7. Enhancement request: Code-complete doesn't work on <classifier>. Should I file a RFE?