Maven repository being maintained?

[mosabua]

Hi!

I am wondering if the Maven repository is being maintained. I am running a JBoss Seam based project with Maven and we have to add the seam, jbpm and other artifacts to our internal repository all the time.

When will a new release of a new jboss product automatically also update the repo so all I need to do is add the jboss repo to my pom and change version numbers?

manfred

[starksm64]

Its up the the individual projects to maintain the repository. If its not part of their normal build then its not being maintained.

[mosabua]

So what can I do to get stuff into the repo? Should I just hazzle each project? Or can I just push release jars into the repo myself somehow? Since I maintain our repo I might as well push the stuff to the maven one... even though the poms do not have the correct dependencies.. better than nothing though.

Also... is there any move towards a policy that dictates release into the repo?

[starksm64]

The project have to convert over. You cannot push content to the jboss repository. Conversion of project to use maven is underway. Check with the projects your using to find out the status.

[pgier]

"mosabua" wrote:
So what can I do to get stuff into the repo? Should I just hazzle each project? Or can I just push release jars into the repo myself somehow? Since I maintain our repo I might as well push the stuff to the maven one... even though the poms do not have the correct dependencies.. better than nothing though.

Also... is there any move towards a policy that dictates release into the repo?

Like Scott said, we are gradually moving projects to maven. Once a project is built with Maven instead of ant, the release artifacts will always be uploaded to the jboss repository. We are also looking into automatic synchronization with the central maven repo, so that those artifacts stay up to date too.

You can also create Jira issues either in the projects that you are using, or in the JBBUILD project, and I will try to prioritize the conversion of those projects.

[mosabua]

Thanks guys. I will do that. Is there any plan to at least host the artifacts generated from the current build in the repo. All you would have to do it use the maven install plugin to install into a svn checkout of the repo and commit the new files. That would mean that the dependencies are not correct but at least the artifacts would be available somewhere. At the moment every Maven user will do that internally in their organisation or manually on their machine only.

I will post a list of issues I comment/voted/watched a bit later.

manfred

[mosabua]

Here is a list of JIRA issue numbers I added to:

JBPM-899
JBRULES-522
JBSEAM-983

There are probably others that will result from these since the dependencies will also need to added to the repo. Thats it for now though.