Community
Participate
Working Groups
E.g., if you write declare warning and compile against an injar, it won't let you jump to the line in the source that underlies the woven jar, although it can list the file and line #. Likewise, it won't let you navigate crosscutting links (e.g., advises/advised by) in the outline view. We also hit a bug whereby a single class in the jar that matched the declare warnings wasn't producing any class name or lines for its warnings (whereas all the others did). This might be an AspectJ bug.
I guess the status should really be "semi-fixed" but there isn't a bugzilla category for that! If you create a project dependency from the project using the injar to another Java/AspectJ project that contains the corresponding source, markers will now be created correctly. In the absence of such a project dependency, the behaviour is as before. It would be nice to be able to "attach source" to the injar and have the markers relate to that instead, but such a solution will have to wait pending a proper piece of design work to look carefully at how AspectJ's various input and output jars should properly dovetail with the JDT defined jars for a project.
