On 5/20/11 10:33, Carsten Ziegeler wrote:
Richard S. Hall wrote
I agree that I won't worry about (a), but for (b) especially since it
appears it will be fixed, it doesn't seem like it makes sense for us to
have releases in the meantime that are missing the artifact. So, I think
we should create a local workaround until it is officially fixed.
Ok, makes sense - for the ongoing vote of the event admin, I suggest I
create a tar.gz and try to deploy it by hand to the staging repo.
The alternative, of course, is for us to decide that we only want to
have ZIP files going forward (despite the potential fix to the parent
pom)...
But if we are going to maintain the status quo, then yes, we need to
create the missing artifact.
-> richard
Regards
Carsten
-> richard
Regards
Carsten