Andrew Wiley wrote: > For some reason, when I switched from apacheds-all to apacheds-server-integ, > Maven started downloading source code successfully (there might be something > wrong there), so I was able to debug it and found that it was throwing the > error while opening a bad jar file (Maven downloaded the 301 "moved > permanently" error page instead of the actual jar file). I guess that > exceptions like that should really be handled by printing out an error > message and continuing, because even if there are corrupt jar files in the > class path, they should probably just be skipped.
You are totally right. I created a Jira: https://issues.apache.org/jira/browse/DIRSERVER-1491 > However, I'm new here and I don't know your practices. Thanks for your help! Thanks for sharing your experience and for showing the pitfalls. Kind Regards, Stefan
