Community
Participate
Working Groups
There is always a delay at the moment from when an AspectJ version is released and it appears in the maven central repo. That is because it is entirely a manual process - sometimes I do it, sometimes community members help me out and do it. We can't continue like this, it should be automated. There are two parts: 1. Create the repo shaped thing after a build, with all the right poms and md5/sha1 digests 2. Uploading
All the Ant has been written to now construct the repo in the right layout. It includes source jars and is driven from the same local.properties file as the existing build process. To create the repo simply modify the local.properties (to set the right version numbers), then Cleanup: ant clean Build the distribution: ant Create the repo ant repo Now under the aj-build/repo folder will be the entire structure suitable for upload to maven.
I set up an rsync space on my own server for AspectJ to use, cause I badly need AspectJ in Maven. I've modified the build.xml file to call Maven to deploy to a repository. This includes the rsync space that will act as a bridge to the main Maven repository, but can also be used by anyone using a local or intranet repository to manually build and deploy a patched or modified version of AspectJ on their own repos. This took me quite some time cuase there is no current Ant->Maven task (see http://jira.codehaus.org/browse/MANTTASKS-71 ) so Maven has to be called using an Ant exec task. Anyway the advantage is huge, cause all the repository specific stuff is delegated to Maven, that correctly handles a number of other things like metadata.xml that are needed for rsync uploads to main repository. This means, you need to have Maven installed and properly setup for this to work. I also modified the pom files to include all elemente required by the main maven repository, see http://maven.apache.org/guides/mini/guide-central-repository-upload.html for an explanation. I sent Andrew Celement some infos on how to configure it so that it can upload to my rsync space and asking him to perform some more tests on it. Once we're sure it is working correctly, I'll ask Maven folks to sync my space with the central repository and all should be working.
Created attachment 131760 [details] Patches the build.xml file and the *.pom files for maven repo deploy
Isn't this closed?
it is now. I just did a huge batch update for all 1.6.5 bugs and this was caught up in it.
