-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/4/10 11:06 , Casper Bang wrote:
> Thanks for covering this, I did notice Dick's Twitter post but
> imagined he already got lots of replies. I just want to point out
> that if it's merely a fail-to-update issue, then the -offline mode
> can be very helpful. If it's an entirely new dependency (as I think
> Dick mentioned after-worth) and the central repo is somehow down (a
> kin to website maintenance), it's still possible to hunt for the
> JAR and just install in your local repo via mvn
> install:install-file. There will be plenty of times after-all where
> you do not have access to what you need in a public repo (i.e.
> Oracle JDBC drivers).
I blogged a few days ago about another problem that I had with Maven
repos - this time due to a bug at Kenai (keep in mind that Kenai
doesn't explicitly offer Maven repositories, but WebDAV-based).
Details on my blog. I had decided since a few months to close the
three WebDAV-based Maven repos that I had at Kenai, but I never did.
It took until yesterday to move everything to Sonatype and close the
faulty Kenai repos (but also consider that I'm in vacation and I'm
doing other things too). This indeed is not a Maven problem, but a
Kenai minor bug that translated into a showstopper for the special use
I made of it.

Then, when I started pushing the new releases to Sonatype, I
experienced another problem because of the way I customized my release
process: first I deploy everything to a temporary folder, and then
copy everything to Sonatype by means of the maven-wagon-plugin. This
specific plugin turned out to be incompatible with the staging feature
deployed at Sonatype with latest Nexus release (it worked fine for
several months earlier). The guys at Sonatype have been very fast in
getting back to me, we found a workaround that allows me to be
operative as usual, and I suppose that the bug will be fixed in the
next release of Nexus.

I agree with the original poster - this is due to the extra complexity
that arises out of the use of repositories. It's the price to pay when
you don't want to manually copy artifacts for a project to another and
commit together with sources. I've tried this for several months, even
with some automation, then I gave up and moved to Maven. Also, it's
worth while saying that these are problems that arise when you work
with FLOSS projects relying on external services (such as Kenai or
Sonatype). They sometimes can fail - in such a way that if you have
your website hosted by a provider and it fails, your website is
broken. Of course, problems with Maven repos are worse since they
probably cost you more, as they can jeopardize the development process
(I'm basically one week in delay for a release of blueBill Mobile).
But if you're within a corporate, it's just a matter of properly
managing your own infrastructure (your own instance of Nexus or such).

The point that I want to convey is that if you want to use Maven, you
_do need_ a decent external infrastructure (there are also there
reasons for which you want to have a local Nexus or such repo). This
of course costs and everything must be balanced with the advantages.
My point is that we make a favour to Maven if we properly explain to
people what they really need in order to use it, rather than letting
them try at random and later being burned by it.

To me Maven is well worth while the costs.

- -- 
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxZYQ0ACgkQeDweFqgUGxdIdACgtRDzOFmZl64ykOfBdsmospXG
H8QAnAm2nOVCht8FB0Bp2rcirR5AULs4
=/U73
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to