Upload antisamy to maven repository

Laplandia / owaspantisamy

Automatically exported from code.google.com/p/owaspantisamy

0 stars 0 forks source link

Upload antisamy to maven repository #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Please consider uploading AntiSamy to a Maven repository. That makes it
much easier to include it in a Maven-managed project.

A guid on how to upload artifacts to the central repository is here:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html

Please let me know if I can help, eg. creating the POM file.

Original issue reported on code.google.com by joern.za...@gmail.com on 31 Jul 2008 at 9:35

GoogleCodeExporter commented 9 years ago

Attached is a pom file that includes the necessary dependencies. That groupId 
and
artifactId may need to be changed.

Original comment by joern.za...@gmail.com on 6 Aug 2008 at 2:36

Attachments:

antisamy-1.2.pom

GoogleCodeExporter commented 9 years ago

Thanks! We will look into this.

Original comment by arshan.d...@gmail.com on 7 Aug 2008 at 1:06

Added labels: Type-Enhancement, Priority-Low
Removed labels: Type-Defect, Priority-Medium

GoogleCodeExporter commented 9 years ago

So.. any progress on this?

I maintain another project on google, and we're also pushing to the Maven 
Central
Repository: http://code.google.com/p/facebook-java-api/

I did this by maintaining my own repository on my dreamhost account, so that 
Maven
Central could rsync from it (google code doesn't have rsync capabilities).  I 
have
plenty of disk/bandwidth, if you want to push your builds to my server for Maven
Central as well.

Original comment by fern...@gmail.com on 15 Dec 2008 at 7:22

GoogleCodeExporter commented 9 years ago

voting this up.

Original comment by fern...@gmail.com on 15 Dec 2008 at 7:23

GoogleCodeExporter commented 9 years ago

Sorry, Arshan asked me to look at this, and I've been pushed for time.

Appreciate your offer fernman. I will follow up with you by email.

Original comment by diazepam@gmail.com on 15 Dec 2008 at 9:15

GoogleCodeExporter commented 9 years ago

Checked in a functional POM, thanks to fernman for extensive help.

This work is incomplete - because maven is not using the patched version of 
NekoHTML (see issue #12) a unit 
test fails. Leaving this open until we either accept the NekoHTML bug (switch 
off the failing test) or get 
NekoHTML fixed. Or some other solution.

Original comment by diazepam@gmail.com on 7 Jan 2009 at 3:51

Changed state: Started

GoogleCodeExporter commented 9 years ago

The pom.xml is checked in and working in my environment. Major thanks to 
fernman for
holding my hand. We are going to try to get release builds out there as well 
sometime
during March.

Original comment by arshan.d...@gmail.com on 17 Mar 2009 at 2:27

Changed state: Done

GoogleCodeExporter commented 9 years ago

The artifact is still missing on the central Maven repo, do you want any help on
this? I've already done this several times.

Original comment by julien.d...@gmail.com on 5 Nov 2009 at 11:48

GoogleCodeExporter commented 9 years ago

I picked this up and have now migrated the current branch to a more standard 
maven 
layout.  With some help from Fernando Padilla, the maven configuration is now 
set for a 
release to Sonatype.  There are snapshots deployed there already.

Original comment by jonathan...@gmail.com on 25 Mar 2010 at 5:16

Changed state: Started

GoogleCodeExporter commented 9 years ago

AntiSamy 1.4 is now released to the central repository.

Note that this is not a release announcement :)

Original comment by jonathan...@gmail.com on 7 Apr 2010 at 8:40

Changed state: Fixed