Skip to content

Clean up Maven issues #73

@meg23

Description

@meg23

From manico.james@gmail.com on November 28, 2009 06:27:24

It would be nice to place the final jar in a public maven repo... The
"snapshots" like rc1 should be in the maven repo as well and the
documentation should reflect that. The details for pushing to the public
repo are here: https://docs.sonatype.com/display/NX/OSS+Repository+Hosting Also there appears to be a copy and paste error in the maven section of the
JavaEE-ESAPI-2.0a_install.doc. Page 7, section #2, part c it reads: mvn
deploy:deploy-file -DgroupId=OWASP -DartifactId=AntiSamy -Dversion=1.2 -
Dpackaging=jar -Dfile= ESAPI-2.0rc2.jar -Durl=[your_repo_url] -
DrepositoryId=[your_repo_id]

This appears to be a copy from AntiSamy... it should me more consistent
with Section 2, part b. Also if we push to a public repo, then most of
this maven section of the install guide will change.

Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=63

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions