Re: [Maven-plugins-developer] Releasing docs and a plugin snapshot

[Andy J. <an...@aj...>]

> sdocbook plugin release:
> How to do that? The sdocbook plugin has a "maven.xml" file, which defines a
> "plugin" goal, which seems to construct a versionen .jar. There are also
> some other goals, but none of them dist anything to remote repository.
>
> I took a peek into was40 and was5 plugins and they have nothing the like of
> a maven.xml.
>
> So, how to release plugin?

maven plugin

This builds the plugin ... under target. You then need to 
ftp upload.sf.net

cd incoming
put 'plugin-name'

You then go through the SourceForge File Release section (under Admin) and 
select this file you've added, selecting the release name etc.


You will also need to put the plugin onto the website under
/home/groups/m/ma/maven-plugins/htdocs/maven/maven-plugins/plugins/
using scp (or equivalent)



> Site docs release:
> 1. standing in top-level dir, doing "maven multiproject"

Yes.

What I then do is create a tar.gz (or zip if you're a Windows person) and scp 
it across to our web space
scp filename use...@sh...:/home/groups/m/ma/maven-plugins/htdocs

and unzip it (ssh to the same place first, of course). Then do a "chmod -R g+w 
*" to make sure the rest of us still have permissions on things you've added.

There are instructions on SourceForge somewhere.



> Which version of Maven

The current website was built by Dion with RC2 I think, so use that.


There is also a "SourceForge" plugin on our site which may make some of the 
above redundant ... but someone else can confirm or deny that part.


If you get into difficulty with any of these, let us know.

-- 
Andy