"corrected" v. 1.1 to Maven central - issues/voting

[nskmda]

Hello, all

Here is a brief description of a problem:
=============
When I tried to help George to get GWT SL 1.1 into Maven central I
mistakenly promoted a newer version which had some significant code
changes / dependencies updates.

Unfortunately, I'm not allowed to remove GWT SL 1.1 from central. And
whoever from the community using Maven for builds will now get wrong
1.1 version from central repository.
=============

Last week I spend some time trying to realize how to make Gilead to
get to Maven central repo (this is the only dependency of GWT SL 1.1
which is not in Maven central).

What I managed to figure out was Gilead itself has dependencies on
"non-central" artifacts. That would not be an issue but some of those
Gilead dependencies (like xerces-api) were present in JBoss repository
and now they're are considered deprecated (in fact, Gilead seems to
have transitive dependencies on quite a few of those deprecated ones)
- see http://community.jboss.org/wiki/JBossDeprecatedRepository.

Basically, I can try to replace deprecated dependencies in GWT SL pom
and add correct ones. But I don't really have much time verifying if
packages structure/APIs haven't changed between the deprecated and
correct version.

Of course, I can add new dependency but that would be at GWT SL users'
own risk (since we'll start having new libraries in classpath instead
of old ones).

Please, let me know if we want to accept that risk and have
'corrected' GWT SL 1.1 in Maven central.
This way I will just try to upload Gilead to Maven central (I guess I
can create a bundle and have it put to central repository via
Sonatype).

Any opinions?

Regards,
Dmitry