maven-plugins-developer

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

[Per O. <po...@no...>]

Hi,

I would like to release a SNAPSHOT version of the upcoming 1.4 of the sdocbook 
plugin to get some feedback before the real 1.4 release. In addition, I would 
like to do a site update of the docs.

This will be the first time for me to do that in maven-plugins project. So, I 
would just hear you guys if these are the correct steps, before performing 
them.

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?

Site docs release:
1. standing in top-level dir, doing "maven multiproject"
2. still in top-level, "maven site:deploy"

? this will update all project docs, so I would like to do it correctly :-)

Also, which version of maven are we building with? I'm currently using the 
1.0-RC1 release.

/Per

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

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

[Per O. <po...@no...>]

Hi,

> ...
> 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.

Someone forgot the "chmod" part :-)

I'm unable to unzip my site into "maven-sdocbook-plugin" and 
"maven-javaapp-plugin", as they contain files owned by "wsdgoe" with mode 
755.

Is Siegfried around to change these rights?

Mostly, I'm concerned with the sdocbook of course, but the other one should be 
fixed too, I guess.

/Per

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

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

On Monday 12 Apr 2004 16:46, Per Olesen wrote:
> Someone forgot the "chmod" part :-)
>
> I'm unable to unzip my site into "maven-sdocbook-plugin" and
> "maven-javaapp-plugin", as they contain files owned by "wsdgoe" with mode
> 755.
>
> Is Siegfried around to change these rights?

Per,

you should be able to unzip it now ... I got SourceForge to give us group 
write on those directories :-)


-- 
Andy

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

[Per O. <po...@no...>]

>
> you should be able to unzip it now ... I got SourceForge to give us group
> write on those directories :-)

Thank you!
And as a result of that, I've just updated (the rest of) the site.