Hi Graham On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
These two features together, with some scripting and a place to host the repository, is in theory all that would be needed to make eclipse jars automatically available to maven users.
I think that at the moment having a manually-updated repo could be enough, at least for some time. It's just a matter of downloading an eclipse release and run the mvn eclipse plugin that takes care of generating jars and uploading them. I think that it's better to have a final repository and to allow some more testing: at the moment everything looks really good (I am developing rcp applications since a couple of months and I am pretty happy of what we have now), but there is still something that requires a human eye. For example the versioning scheme of eclipse artifacts doesn't perfectly match the one used by maven: eclipse jars always have a qualifier (build number in maven) and there is no difference between a final release and a nightly build. The mvn eclipse plugin is now able to convert qualifiers to the mvn version scheme or to strip them in order to generate the "final" released artifacts, but you have to tell it how to do: for example you should be careful in turning the build number on when deploying eclipse 3.3 Mx artifacts and turn it off when deploying eclipse 3.3 (final). If you don't do that, any 3.3 nightly/intergration/milestone build will generate artifacts with the same version. That should not be a problem if we plan to only release eclipse major versions, but it's something that need to be checked... a fix to the build number conversion is also in place only from a couple of weeks, so it's better to let it settle for a while before starting to make everything automatic... fabrizio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
