| Summary: | [aspectj] Not showing build.xml in linked outline | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Ron Bodkin <rbodkin+LISTS> |
| Component: | Mylyn | Assignee: | Mylyn Inbox <mylyn-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | minor | ||
| Priority: | P4 | Keywords: | helpwanted |
| Version: | 2.0 M2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Ron Bodkin
This used to be a bug in Mylar a while back and I can no longer reproduce it with 2.0M2, so we need to figure out if this is something AJDT-specific or not (e.g. it mucking with the child content of a Java package). First, can you try to set up the same structure in a non AJDT project and verify that the build.xml file shows? Also, I'm I need to know what you mean "subdirectory of a source folder", do you mean that it shows in a thing that looks like a grayed out a package with a little folder icon? *** Bug 183473 has been marked as a duplicate of this bug. *** Any news on this? Hi Mik, I tried a similar structure on a pure Java project that uses Subclipse and I am able to see the build.xml resource in a subfolder. So this is probably related to AJDT. In the AJDT case, the build.xml file is actually in a subdirectory of a source folder, i.e., src is a source folder of the project and the build.xml file was in a location where Java code would be in a package (glassbox.web.installer or something like that). So the icon is a folder with the little grid in the top right showing it's within a source folder. Yes I can reproduce this Thanks Ron. I hope to take a pass through AspectJ/AJDT compatibilities for 1.0. It's a bit tricky because we rely so much on the normal Java model rules and AJDT changes some of those. We hope to create an AspectJ/AJDT structure bridge sometime in the 3.0 timeframe. Will talk to the AJDT folks about contributing this. *** This bug has been marked as a duplicate of bug 168475 *** |