Re: [jboss-dev] Maven repo screwed up on org.jboss.metadata:jboss-metadata
The best part is that I have a project which defines a version range:
[1.0.0.CR1] which does compile, but the project which depends on that
project doesn't. In the first project Maven chooses Beta37 for some reason.
Carlo
Dimitris Andreadis wrote:
Alexey committed only the 1.0.0.CR1 directory, not the top level
info.
Carlo de Wolf wrote:
> The metadata xml doesn't contain the CR1 release:
>
http://repository.jboss.org/maven2/org/jboss/metadata/jboss-metadata/mave...
>
>
> What happened?
>
> Carlo
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development