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: | [codehaus] Enhance editor tab for pom.xml files to have ${artifactId} (similar to how ant scripts are represented) | ||
|---|---|---|---|
| Product: | projects | Reporter: | Jaromir Uhrik <juhrik> |
| Component: | Maven | Assignee: | Jesse Glick <jglick> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | CC: | anebuzelsky, jglick, mmetelka, vstejskal |
| Priority: | P2 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 195914 | ||
| Bug Blocks: | 178090 | ||
|
Description
Jaromir Uhrik
2008-12-03 16:29:52 UTC
...I am linking the following file which resides in Jira system: http://jira.codehaus.org/secure/attachment/36987/AntScriptAndPomsInNetbeansEditor.gif *** Issue 168902 has been marked as a duplicate of this issue. *** It's a shame that maven projects can't be confortably edited. Last releases of NB brings a lot of powerfull feature for working with Maven projects, but the browsing through the pom.xml opened is always a pain. Milos, you said that it is hard, I can understand as I had tried to look (quickly) to the code. If it is so hard, maybe tab management in the NB platform should be reconsidered. Could you give some more details on the blocking things ? Or how it is achieved for build.xml ant files, and different for pom.xml files ? Thank you a lot. ant build files have their own data loader, data object and multiple other classes that need to be maintained and kept in sync with the xml editor generic data loader & co. That sounds like a too high price to me for having an editor tab annotation. I agree with comment #3. I disagree with comment #4. Much of the Java world is moving to Maven. This will will make developement a lot, LOT easier. Having 8 tabs saying "pom.xml" is really not much helping. If not ${artifactId}, could at least the containing dir name be shown? Even if it would need an ugly if-hack... (In reply to comment #5) > If not ${artifactId}, could at least the containing dir name be shown? Even if > it would need an ugly if-hack... See other blockers of bug #178090. But ${artifactId} might be more useful in the case of pom.xml. For example, hudson/trunk/main/test/pom.xml has ${artifactId} = 'hudson-test-harness', which is compact but descriptive, whereas the dir name 'test' is not distinctive. Rather a P2 enhancement than a P4 defect. Any idea if this is going to be completed for 6.10? core-main #5a389672bb91 Integrated into 'main-golden', will be available in build *201010060000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/5a389672bb91 User: Jesse Glick <jglick@netbeans.org> Log: #154508: [codehaus] Enhance editor tab for pom.xml files to have ${artifactId} (similar to how ant scripts are represented) Works in NetBeans IDE Build 201102160501. Good work, thanks! Now only if Bug 194773 and Bug 178682 were done and I'd be completely happy regarding my most often pom.xml use cases not yet covered by NetBeans. Feel free to verify bugs you can confirm are fixed as expected. Works as expected. Thanks for implementing this, it is very helpful. |
