Dennis Lundberg wrote:
Jason van Zyl wrote:
On 19 Dec 06, at 12:28 PM 19 Dec 06, Steve Loughran wrote:
Jason van Zyl wrote:
Hi,
Just checking in with folks to see if anyone is planning ApacheCon
talks.
1. "fear the repository police". We will pick people in the audience
and beat them with rolled up copies of the pom schema until they
promise not to publish invalid metadata. we will start off with "Is
there anyone here who works on commons-logging?",
It will soon be impossible to publish invalid metadata.
Speaking as someone who also works on commons-logging (*ducking*), is
there work being done on a maven-repo-compliant-plugin or something
similar that could be run on every pom that is submitted through
MAVENUPLOAD? I.e. confirming to the rules set up here:
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
If not, I think I could put something together.
1. dont worry, we wouldnt do any serious public humilation in the talk.
Mainly through fear you'd ban all user.name=stevel &&
ipaddres.startswith("15.") from commons logging.
2. There's been lots of discussion on the repo list at automating this.
We need something to audit artifacts in a staging place (like all stuff
rsynced over), as well as do a piece-by-piece analysis of submitted
files. For the latter, you could do something fancy that uses the Jira
APis to automate pulling down the pom+JAR and auditing them. A web based
thing would make it easier for people to test their artifacts before
submission.
Once the RDF conversion stuff goes into the MIT codebase Apache code can
use it to create a large repository of all the facts, which may then be
easy to analyze and audit. I say may, as it might just be harder. I'm
kind of biased towards implementing my auditing code in prolog/jprolog,
but not committed. maybe jruby would integrate w/ java better.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
