I've just started working with Maven and I'm porting my company's applications to Maven2. We have a couple of applications using Seam and as far as I now I should use the JBoss Maven2 respository because the Central Maven2 repository doesn't have the Seam libraries.
Does this mean what I think it means? Are you saying that you want to upload the artifact that your pom.xml generates into the JBoss' Maven repository? First question: why? Second question: are you a Red Hat employee working on a JBoss product? Only if you are working on a JBoss product should you be updating the JBoss Maven repository.
If that is not what you are doing, then I am not understanding what you are attempting to accomplish.
Thanks for your reply Peter, I'm sorry if I wasn't clear enough.
I don't know if you have used the m2eclipse plugin. You can add repositories "to the plugin" and when you are writing your POM using the plugin's POM editor you can easily look up for artefacts.
Every time you start Eclipse the plugin updates the indexes of the all repositories that you have. But when the plugin updates the JBoss repository I'm getting a old index, from Jul 08 2008, so the plugin cannot find the latest releases when I use the POM editor to add dependencies, exclusions and so on.
If I manually insert the artefacts, without using the wizard to find the artefacts everything works fine.
Luiz, thanks for the clarification - now I know what you are talking about (I am familiar with and have used that same feature). This points out the importance of being very specific when describing a problem - you might know the context for your question but not everyone will automatically guess what the context is.