Menu
▾
▴
maven-plugins-developer — Mailing List used for development of plugins
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(14) |
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(12) |
Sep
(14) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2004 |
Jan
(4) |
Feb
(8) |
Mar
(14) |
Apr
(18) |
May
(1) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(5) |
Oct
(26) |
Nov
(36) |
Dec
(21) |
| 2005 |
Jan
(10) |
Feb
(20) |
Mar
(15) |
Apr
(11) |
May
(29) |
Jun
(18) |
Jul
(19) |
Aug
(12) |
Sep
(11) |
Oct
(3) |
Nov
(7) |
Dec
(5) |
| 2006 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
(14) |
Jul
(45) |
Aug
(58) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2007 |
Jan
(4) |
Feb
|
Mar
|
Apr
(3) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <di...@mu...> - 2004-03-07 23:37:18
|
----- Forwarded by dIon Gillard/Multitask Consulting/AU on 05/03/2004 01:24 PM ----- "Richard Lewis-Shell" <rle...@ma...> wrote on 05/03/2004 01:15:51 PM: > The difference is that I am just calling/wrapping the ant tasks that IBM > supplies in their wsanttasks.jar, rather than calling the .bat/.sh scripts. That's even better. I wish they worked with 4.0. > My SF id is rlewisshell - I was hoping that this might end up along side the > was40 plugin one day... Guys (on maven-plugins-developer), can we add Richard as a developer for the new plugin? -- dIon Gillard, Multitask Consulting |
|
From: Andy J. <an...@aj...> - 2004-03-03 07:09:55
|
On Wednesday 03 Mar 2004 06:41, di...@mu... wrote: > Kristen (sfid: kgillard) has helped with the was40 plugin, and I'd like to > add him to the list of project developers. Dion, Kristen is now added. -- Andy |
|
From: <di...@mu...> - 2004-03-03 06:50:05
|
Kristen (sfid: kgillard) has helped with the was40 plugin, and I'd like to add him to the list of project developers. As I'm not an admin, I can't do it. Does anyone have any objections/ queries? -- dIon Gillard, Multitask Consulting |
|
From: Eric P. <ep...@up...> - 2004-02-17 14:16:43
|
Hi all, I just finished updating the FindBugs plugin to use FindBugs 0.7.1. I wanted to post a note announcing it in the next couple days.. Anyone want to give it a quick spin before I do? Eric |
|
From: Andy J. <an...@aj...> - 2004-02-17 07:06:33
|
> I rechecked out the source code, and am redeploying the site. Thanks Dion. Looks much better now. -- Andy |
|
From: <di...@mu...> - 2004-02-17 06:49:26
|
mav...@li... wrote on 17/02/2004 05:20:50 PM: > > > What you have on the website at the moment no longer mentions it ... it > > just mentions downloading the dbunit plugin ... presumably from ibiblio. > > Our plugins arent on Ibiblio since the majority of us do not have access > > and it takes ages to get them on their using other means. > > In addition, the current website does not now contain the latest plugin I > added a week ago ... "xmlresume", contributed by David Carr. It was on the > website until yesterday. Can we please make sure that we always do a full > "CVS get" and then build the whole website before publishing it. I'll re-grab the code from CVS again. I thought I was up to date... Seems to be a weird issue with Eclipse. It simply wasn't seeing the extra directories. cvs update was having no effect either. I rechecked out the source code, and am redeploying the site. -- dIon Gillard, Multitask Consulting |
|
From: <di...@mu...> - 2004-02-17 06:37:03
|
mav...@li... wrote on 17/02/2004 05:16:25 PM: > On Tuesday 17 Feb 2004 02:57, di...@mu... wrote: > > The page http://maven-plugins.sourceforge.net/installing.html mentions > > setting maven.repo.remote to the maven-plugins site. > > > > AFAICT, this is plain wrong, and I'd like to change it. > > Dion, > > Well some time back I added a maven/plugins directory to the maven-plugins > website so that people could download these plugins from our site. To do > this, they need to add it to the maven.repo.remote - and people have been > using it. Whether it was spelt correctly is another matter, but it needs to > be there. Got it. It was spelt incorrectly. It needs to use *our* groupId (maven-plugins) rather than maven. I've symlinked /maven/maven-plugins/plugins to /maven/plugins and updated the docs. This should get around it for the people trying to use it at the moment. > What you have on the website at the moment no longer mentions it ... it just > mentions downloading the dbunit plugin ... presumably from ibiblio. Our > plugins arent on Ibiblio since the majority of us do not have access and it > takes ages to get them on their using other means. Yep, fixed that too. There was a typo on the examples as well (groupID instead of groupId). I'll re-update the site. Let me know if there's anything that needs fixing. -- dIon Gillard, Multitask Consulting |
|
From: Andy J. <an...@aj...> - 2004-02-17 06:25:01
|
> What you have on the website at the moment no longer mentions it ... it > just mentions downloading the dbunit plugin ... presumably from ibiblio. > Our plugins arent on Ibiblio since the majority of us do not have access > and it takes ages to get them on their using other means. In addition, the current website does not now contain the latest plugin I added a week ago ... "xmlresume", contributed by David Carr. It was on the website until yesterday. Can we please make sure that we always do a full "CVS get" and then build the whole website before publishing it. -- Andy |
|
From: Andy J. <an...@aj...> - 2004-02-17 06:20:42
|
On Tuesday 17 Feb 2004 02:57, di...@mu... wrote: > The page http://maven-plugins.sourceforge.net/installing.html mentions > setting maven.repo.remote to the maven-plugins site. > > AFAICT, this is plain wrong, and I'd like to change it. Dion, Well some time back I added a maven/plugins directory to the maven-plugins website so that people could download these plugins from our site. To do this, they need to add it to the maven.repo.remote - and people have been using it. Whether it was spelt correctly is another matter, but it needs to be there. What you have on the website at the moment no longer mentions it ... it just mentions downloading the dbunit plugin ... presumably from ibiblio. Our plugins arent on Ibiblio since the majority of us do not have access and it takes ages to get them on their using other means. -- Andy |
|
From: <di...@mu...> - 2004-02-17 02:57:12
|
The page http://maven-plugins.sourceforge.net/installing.html mentions setting maven.repo.remote to the maven-plugins site. AFAICT, this is plain wrong, and I'd like to change it. Is this ok? -- dIon Gillard, Multitask Consulting |
|
From: David C. <da...@ca...> - 2004-02-13 04:50:20
|
I'd like to contribute the Maven plugin I've created for the XML Resume Library (xmlresume.sf.net). It allows easy and flexible transformation of an XML resume to a variety of formats. The current plugin site and the source code can be found at the URLs below. http://david.carr.name/projects/xmlresume/maven-plugin/ http://david.carr.name/projects/xmlresume/maven-plugin/maven-resume-plugin-src.zip ----------------------------- David Carr ----------------------------- Email: da...@ca... Web: http://david.carr.name ----------------------------- |
|
From: Ben W. <be...@wa...> - 2004-01-18 22:07:35
|
Thanks Andy, that worked a treat. Time to start writing some documentation! Cheers, Ben Andy Jefferson wrote: >On Sunday 18 Jan 2004 10:27, Ben Walding wrote: > > >>Could someone update the sdocbook plugin? >> >>sourceforge cvs is down (as per usual), and as far as I can tell, the >>plugin in >>maven-plugins.sf.net/maven/plugins/maven-sdocbook-plugin-1.3.jar is html >>rather than a jar file. >> >> > >Ben, > >try it now. Should be of size 829558 and a jar (built from the current CVS - >which is still at 1.3 for sdocbook as far as I can see). > > > |
|
From: Andy J. <an...@aj...> - 2004-01-18 12:20:09
|
On Sunday 18 Jan 2004 10:27, Ben Walding wrote: > Could someone update the sdocbook plugin? > > sourceforge cvs is down (as per usual), and as far as I can tell, the > plugin in > maven-plugins.sf.net/maven/plugins/maven-sdocbook-plugin-1.3.jar is html > rather than a jar file. Ben, try it now. Should be of size 829558 and a jar (built from the current CVS - which is still at 1.3 for sdocbook as far as I can see). -- Andy |
|
From: Ben W. <be...@wa...> - 2004-01-18 10:35:25
|
Could someone update the sdocbook plugin? sourceforge cvs is down (as per usual), and as far as I can tell, the plugin in maven-plugins.sf.net/maven/plugins/maven-sdocbook-plugin-1.3.jar is html rather than a jar file. Thanks, Ben |
|
From: <try...@if...> - 2004-01-08 12:38:42
|
Hi I have rewritten the runner plugin thats hosted at apache and would like to add it to the maven-plugins project at sf.net I have a go from Jason van Zyl so it really shouldn't be any problems with it. If it's added I'm going to rename it to 'runtime-builder' instead of 'runner' as thats a more appropriate description. -- Trygvis |
|
From: Ludovic C. <lud...@ho...> - 2003-12-08 23:58:26
|
Hello, I would like to contribute a new maven plugin. This plugin performs the deployment of the distribution to the Sourforge web site. It uses SourceForge's File Release System to update the files on the download page of your project. If you want to add me to the maven-plugin developpers, my SF id is ludovicc. Source code is available from http://cvsgrab.sf.net/sourceforge.zip Plugin is available from http://cvsgrab.sf.net/maven/maven-plugins/plugins/maven-sourceforge-plugin-1.0.jar Ludovic |
|
From: <sie...@it...> - 2003-10-17 19:16:53
|
Hi folks, after weeks of holidays and consulting I pushed out the new release of the Simplified DocBook Plugin. Thanks to Andy Jefferson since he fixed two bugs in my project.xml before anybody complained. Cheers, Siegfried Goeschl |
|
From: <try...@st...> - 2003-09-25 16:35:29
|
On Thu, 25 Sep 2003, Andy Jefferson wrote: > On Thursday 25 Sep 2003 15:10, Trygve Laugst=F8l wrote: > > As suggested by Andy on irc, I would like to propose a new 'package' > > plugin for creating deb and rpm packages. It should also support the > > creating of package repositories for apt and the likes. > > > > I've rambeled up a suggestion at my wiki: > > > > http://wiki.nostdal.net/Articles_2fMaven_2fPackagePlugin > > > > I would like some feedback on the suggestion either by comments on the > > list or just change the wiki page. > > > Its a shame that Maven plugins do not support the idea of subclassing > :-) What then would be perfect would be to have the "package" plugin and > then derive RPM, Deb, etc from that so hence we have the same goals and > properties and just add on specific things for particular output > formats. Oh well ... > > I'm not sure of how well Maven plugins support the idea of *using* a > different plugin ... kind of like a sub-plugin ... with this we could > have a package plugin that gives a lot of the logic for packaging > systems, and then we have RPM, Deb plugins that use this package plugin. > > I think the idea of having a common interface is definitely the way to > go ... since the input is basically the same, and the output is a file. > Obviously there are other formats of "package" ... e.g tgz, zip. What > I'm not convinced about is whether to have these as a single plugin (and > have logic internally that checks on the output type and does things > accordingly), or whether to have separate plugins with the same goals > and properties. > > I think i'd tend towards having separate plugins solely because there > are projects where you want to output multiple package formats ... so I > could output a Deb, RPM, and TGZ. If I had these as a single plugin I > would have to edit my project.properties and then run the plugin, and > edit it again and run it ... whereas if i have separate plugins I would > just do "maven rpm", "maven deb", "maven tgz" etc. Having separate > plugins does give us the problem of maintaining consistency in goal and > property naming - adopting your "create", "create-snapshot", and > "copy-resources" in Deb and RPM for now makes a lot of sense. I think you misunderstod my idea. My idea is to create a set of hooks that the different package plugins will use. These hooks will be as simple as a goal named 'package:create'. Then each of the package plugins will have a goal called '<type>:create'. And for intergrating with the package plugin it will have a pre or post goal called called 'package:create' that will simply attain '<type>:create'. When we have a odd cind of subclassing. It might not be the best solution but it works and it opens for extendability. When executing the package:create goal will be something like: (Assuming there is a deb and rpm plugin and they are registered as post goals) package:init-filesystem rpm:init-filesystem deb:init-filesystem package:copy-resources deb:copy-resources rpm:copy-resources package:create deb:create rpm:create Now, if I would like to finetune the packaging for a specific type of package I would use the maven.<type>. namespace for the properties. The common properties would go in maven.package. Did I make things a bit clearer? Does anyone like this idea? Does it add any value to the packaging bit of a project? If there is a consensus about this idea I would like to change the rpm and deb plugins so that they have the 'same' goals and to create the maven-package-plugin. Trygvis |
|
From: Andy J. <an...@aj...> - 2003-09-25 16:14:00
|
On Thursday 25 Sep 2003 15:10, Trygve Laugst=F8l wrote: > As suggested by Andy on irc, I would like to propose a new 'package' > plugin for creating deb and rpm packages. It should also support the > creating of package repositories for apt and the likes. > > I've rambeled up a suggestion at my wiki: > > http://wiki.nostdal.net/Articles_2fMaven_2fPackagePlugin > > I would like some feedback on the suggestion either by comments on the > list or just change the wiki page. Its a shame that Maven plugins do not support the idea of subclassing :-) W= hat=20 then would be perfect would be to have the "package" plugin and then derive= =20 RPM, Deb, etc from that so hence we have the same goals and properties and= =20 just add on specific things for particular output formats. Oh well ... I'm not sure of how well Maven plugins support the idea of *using* a differ= ent=20 plugin ... kind of like a sub-plugin ... with this we could have a package= =20 plugin that gives a lot of the logic for packaging systems, and then we hav= e=20 RPM, Deb plugins that use this package plugin. I think the idea of having a common interface is definitely the way to go .= =2E.=20 since the input is basically the same, and the output is a file. Obviously= =20 there are other formats of "package" ... e.g tgz, zip. What I'm not convinc= ed=20 about is whether to have these as a single plugin (and have logic internall= y=20 that checks on the output type and does things accordingly), or whether to= =20 have separate plugins with the same goals and properties. I think i'd tend towards having separate plugins solely because there are=20 projects where you want to output multiple package formats ... so I could=20 output a Deb, RPM, and TGZ. If I had these as a single plugin I would have = to=20 edit my project.properties and then run the plugin, and edit it again and r= un=20 it ... whereas if i have separate plugins I would just do "maven rpm", "mav= en=20 deb", "maven tgz" etc. Having separate plugins does give us the problem of= =20 maintaining consistency in goal and property naming - adopting your "create= ",=20 "create-snapshot", and "copy-resources" in Deb and RPM for now makes a lot = of=20 sense. =2D-=20 Andy |
|
From: <try...@st...> - 2003-09-25 14:10:55
|
Hi As suggested by Andy on irc, I would like to propose a new 'package' plugin for creating deb and rpm packages. It should also support the creating of package repositories for apt and the likes. I've rambeled up a suggestion at my wiki: http://wiki.nostdal.net/Articles_2fMaven_2fPackagePlugin I would like some feedback on the suggestion either by comments on the list or just change the wiki page. The page actually discuss two things, the maven-package-plugin and a suggestion for common goal naming of the package plugins. As always, I'm online on #maven at irc.werken.com Trygvis |
|
From: Andy J. <an...@aj...> - 2003-09-23 05:50:36
|
On Monday 22 Sep 2003 22:46, Trygve Laugst=F8l wrote:
> I've hacked up the plugin to be ready for a 0.5 release. It's still rather
> basic but I would like to get it out to be able to get some feedback and
> suggestions.
Good work
> I don't know how your routines are for releasing a plugin. What I would
> like to do is to update the pom and tag the /deb directory with a release
> tag.
What we normally do is
* update the site ("maven multiproject") and copy across to Sourceforge
* build your plugin ("maven plugin" in the directory of the plugin) and cop=
y=20
it across to Sourceforge.
> I don't know which version that is recomended for building the site and
> the artifact with when releasing, I'm currently using a rather fresh HEAD.
Version of Maven ? I use beta10 since it is the latest 'released' version -=
=20
but I do use the 1.0 release of the multiproject plugin since that is a=20
requirement.
> And I was wondering about a couple of other issues:
>
> I've noticed some errors in the plugin-project.xml and README file. Is it
> okay if I commit the changes or would some of the project admins like to
> take look at the changes as a patch?
I doubt that there are any 'errors' in these files :-). The README simply=20
provides a list of instructions/guidelines for the project. Do you mean you=
=20
want to add some more guidelines ? If so, then update the file.
As far as the plugin-project.xml goes, it is used by all of the plugins and=
so=20
provides the default values of various things. If you want to specify=20
something different you put it in your plugins project.xml. What specifical=
ly=20
needs changing in that file ?
> And I would like to make a xdoc page listing the responsible persons for
> each of the plugins to make it easier to get in touch with the responsible
> persons of a plugin for both users and developers. Or perhaps have another
> role like Plugin Manager. Or both with the xdoc page beeing generated
> from the roles in the poms. Just a thought.. :)
Sounds like a good idea.
A couple of things I've wanted to do (but not had time yet) are
* Update the multiproject plugin to allow override of the template, so that=
we=20
can update the "plugin overview" page. We can then have links to the goals=
=20
and properties pages of each plugin.
=2D-=20
Andy
|
|
From: <try...@st...> - 2003-09-22 21:46:44
|
Hi I've hacked up the plugin to be ready for a 0.5 release. It's still rather basic but I would like to get it out to be able to get some feedback and suggestions. I don't know how your routines are for releasing a plugin. What I would like to do is to update the pom and tag the /deb directory with a release tag. I don't know which version that is recomended for building the site and the artifact with when releasing, I'm currently using a rather fresh HEAD. And I was wondering about a couple of other issues: I've noticed some errors in the plugin-project.xml and README file. Is it okay if I commit the changes or would some of the project admins like to take look at the changes as a patch? And I would like to make a xdoc page listing the responsible persons for each of the plugins to make it easier to get in touch with the responsible persons of a plugin for both users and developers. Or perhaps have another role like Plugin Manager. Or both with the xdoc page beeing generated from the roles in the poms. Just a thought.. :) Trygve Laugst=F8l |
|
From: <try...@st...> - 2003-09-21 18:06:08
|
Hi I've just spend my sunday creating a deb package plugin for maven. If you like it I would like it to be added to the maven-plugins project. It is available here: http://maven-deb-plugin.nostdal.net Currently it's a but ruff in the edges but still pretty usable. Should be able to pack any .jar file and install it on any plattform. Cheers, Trygve Laugst=F8l |
|
From: Tobias R. <tob...@we...> - 2003-09-19 20:01:40
|
Hi Andy, >Hi Toby, > >What is your SourceForge 'id' =3F We can add you to the project so you can >update your plugin(s) when you need to. my sf-id is "tradem". Would be great to be part of this project ;-). Bye Toby --=20 "Wisest of the Maia was Ol=F3rin. He to dwelt in L=F3rien, but his ways took h= im often to the house of Nienna, and of her he learnt pity and patience. " -- Of the Maiar, Valaquenta, The Simarillion by J.R.R Tolkien=20 =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F Bestes Testergebnis: Stiftung Warentest Doppelsieg fur WEB.DE FreeMail und WEB.DE Club. Nur fuer unsere Nutzer! http://f.web.de/=3Fmc=3D021182 |
|
From: Andy J. <an...@aj...> - 2003-09-18 12:41:34
|
> I have written a maven plugin in order to deploy or undeploy inside of > maven into a remote Oracle Internet Application Server (iAS). > > Are you interested in hosting it in your CVS and on your page. I will > contribute with fixes and further development. > > Should I send someone a zip file or do you grant me access to your cvs > repository? Hi Toby, What is your SourceForge 'id' ? We can add you to the project so you can update your plugin(s) when you need to. -- Andy |
