On 10/18/07, bflaherty [EMAIL PROTECTED] wrote:
I find some the these comments inappropriate and unprofessional.
Wow. I don't think we've even come close to crossing that line. I
can dig up some Tomcat dev threads for comparison if you like. :)
--
Wendy
Well, since you asked :)
On 17/10/2007, at 2:10 PM, Joakim Erdfelt wrote:
ArchivaArtifactConsumer is an abstract-dealing-with-artifacts
consumer.
RepositoryContentConsumer is for files.
A file that isn't an artifact can be *.xml, *.sha1, *.md5, maven-
metadata.xml, bad content, poorly
The db scanning is basically just querying the artifacts from the
database. The list of queried artifacts are iterated and database
consumers perform specific actions on each iteration..
Some of these actions are:
1. Adding the project models of the artifact to the database - during
repo
On 18/10/2007, at 12:36 AM, Joakim Erdfelt wrote:
I know you're somewhat kidding here, but I'm not quite sure how
much, so I'll say it anyway :)
I am not kidding, make this change now.
I'll do it. It's no big deal.
Then try a single sentence statement instead of what appears to be
I'm looking at...
http://maven.apache.org/archiva/ref/latest/apidocs/org/apache/maven/archiva/consumers/package-summary.html
What's the difference between ArchivaArtifactConsumer and
RepositoryContentConsumer? (When is an artifact not considered
repository content?)
Thanks,
--
Wendy
On 10/16/07, Joakim Erdfelt [EMAIL PROTECTED] wrote:
ArchivaArtifactConsumer is an abstract-dealing-with-artifacts consumer.
RepositoryContentConsumer is for files.
A file that isn't an artifact can be *.xml, *.sha1, *.md5,
maven-metadata.xml, bad content, poorly named content, etc.
Would
