[Esapi-user] ESAPI proper Maven groupId and artifactId
Daniel Serodio (lists)
daniel.lists at mandic.com.br
Wed Nov 23 16:28:45 EST 2011
Hello everyone,
On the instructions for building ESAPI[1], we're told to install
AntiSamy using the "OWASP" groupId and the "AntySamy" groupId, but on
the Maven Central repository[2], AntiSamy is deployed using the
"org.owasp.antisamy" groupId and "antisamy-project" artifactId.
Should these build instructions be updated for the correct groupId and
artifactId (the ones in Maven Central)?
Regards,
Daniel Serodio
[1]https://www.owasp.org/index.php/ESAPI-Building
[2]
http://search.maven.org/remotecontent?filepath=org/owasp/antisamy/antisamy-project/1.4.5/antisamy-project-1.4.5.pom
PS.: I had posted this to the java-project list but judging by that
list's archives, it's not very active, so I'm cross-posting to this list.
More information about the Esapi-user
mailing list