Community
Participate
Working Groups
An AspectJ dev build is called something like: DEVELOPMENT-20060510223158 but by the time it finds its way into AJDT, it needs to have a proper version number, like: 1.5.2.20060511152204 It would be more consistent, with less potential for confusion, if the AspectJ dev builds were assigned an appropriate version number - currently AJDT has to pick a version to give it when incorporating a new AJ build.
nice to have, shouldnt be too much work
What needs to happen here?
The reason for this bug is that the AspectJ build process needs changing to prefix the dev build with the release of which it is a dev build (eg. 1.6.4), so that those linked on the download page are more apparently dev builds of a particular level. Also the php that manages the AspectJ download web page will need upgrading to allow for the extra prefix on the version. I don't think AJDT has to do anything. Currently AJDT gets a fully correct version string, although that matches the build I've just made locally (and not usually anything on the download page). As discussed a week or so ago, I might either: - start including the dev build version in AJDT itself so that anyone who feels they need a precisely matching download version can immediately access it from inside AJDT - have a separate download space on the AspectJ eclipse.org area for 'dev builds that are included in AJDT' and have an easy link accessible in AJDT through which it can be accessed.
unsetting the target field which is currently set for something already released
