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: Per O. <po...@no...> - 2004-04-13 20:53:44
|
> > 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. |
From: Andy J. <an...@aj...> - 2004-04-13 17:58:16
|
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 |
From: Andy J. <an...@aj...> - 2004-04-12 15:54:40
|
On Monday 12 Apr 2004 16:14, Per Olesen wrote: > Here's a followup on my problems building site. > > I think we are unable to build with the official maven-rc2, which can be > downloaded from maven.apache.org (at least I am). I can't build with it either FWIW. I'm guessing there's something screwed in multiproject because I've used rc2 on other projects with no problems (but not used multiproject on those). I've no desire to download and build Maven CVS HEAD either ... hope they release an updated plugin (whichever one is causing the problem) sometime soon. -- Andy |
From: Per O. <po...@no...> - 2004-04-12 15:47:03
|
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 |
From: Per O. <po...@no...> - 2004-04-12 15:14:24
|
Hi, Here's a followup on my problems building site. I just did a fresh build of maven from HEAD and tried building site with that, and it works fine with the exception of a lot of linkcheck errors (think they are due to HTTP redirects). I think we are unable to build with the official maven-rc2, which can be downloaded from maven.apache.org (at least I am). Hmm. /Per |
From: Per O. <po...@no...> - 2004-04-12 13:49:38
|
Hi Andy, > Put in a placeholder in your repository for it ... there are many others > like this ... its because Maven doesn't support the idea of having a > runtime dependency. You just need to have a file there ... no matter what > it is! Okay, thanks. I updated your fix to maven.xml, and I get further. But I seem to be hit by some other problem, which seems to only happen with rc2 of maven. I get a "null" exception: BUILD FAILED File...... file:/home/polesen/.maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly Element... j:include Line...... 345 Column.... 54 null:-1:-1: <null> Could not parse Jelly script com.werken.werkz.UnattainableGoalException: Unable to obtain goal [multiproject:site] -- file:/home/polesen/.maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly:345:54: <j:include> could not include jelly script: file://home/polesen/.maven/plugins/maven-xdoc-plugin-1.6/plugin-resources/site.jsl. Reason: org.apache.commons.jelly.JellyException: null:-1:-1: <null> Could not parse Jelly script at com.werken.werkz.Goal.fire(Goal.java:646) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) If I run with "-X", I get additional exception in chain, which says it is in parsing an xml, that I get a "UnknownHostException: home". My guess is, that i get some "file://home/.." or, from the stacktrace "ftp://home/.." but I simply can't find out where. Here is (some of) the unknownhost stacktrace: Root cause java.net.UnknownHostException: home at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153) at java.net.Socket.connect(Socket.java:452) at java.net.Socket.connect(Socket.java:402) at sun.net.NetworkClient.doConnect(NetworkClient.java:139) at sun.net.NetworkClient.openServer(NetworkClient.java:118) at sun.net.ftp.FtpClient.openServer(FtpClient.java:423) at sun.net.ftp.FtpClient.<init>(FtpClient.java:692) at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java:175) at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:257) at java.net.URL.openStream(URL.java:913) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:357) at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java:489) Any ideas? Others able to build with a rc2-distribution without problems? Per |
From: Andy J. <an...@aj...> - 2004-04-12 11:54:41
|
> A copule of questions: > * Can we have projects under the ASF license? Doesn't that imply that the > ASF will support us if there was any license issues etc? No idea. Anyone can choose their license from all of those on www.opensource.org if they wish for it to be Open Source. What implications that has for licensing issues you may find over at that site, or by asking ASF directly. Maven-Plugins has been under the Apache license since it started AFAIK. > * Could you add the BSD license also? I would like to keep the copyright > and thus have it under the BSD license. I've added the BSD license now. > > Please make sure that any plugin you are responsible for has a > > LICENSE.txt file relevant to what it is released under. > > Do you have a template that we can use? Nope, but you can look at http://www.opensource.org/licenses/ That has all of the accepted licenses -- Andy |
From: Andy J. <an...@aj...> - 2004-04-12 11:32:00
|
I've just updated the Maven-Plugins project to allow both Apache and GPL licenses on SourceForge - previously was all under Apache. Please make sure that any plugin you are responsible for has a LICENSE.txt file relevant to what it is released under. -- Andy |
From: Andy J. <an...@aj...> - 2004-04-12 10:41:25
|
On Monday 12 Apr 2004 11:34, Per Olesen wrote: > Hi, > > I'm unable to build site docs, because of a dependency in JPOX plugin. It > depends upon "jpox-1.0.0-beta-3.jar", which is not in ibiblio repository. > > Is there another repository I'm missing? Put in a placeholder in your repository for it ... there are many others like this ... its because Maven doesn't support the idea of having a runtime dependency. You just need to have a file there ... no matter what it is! -- Andy |
From: Per O. <po...@no...> - 2004-04-12 10:34:57
|
Hi, I'm unable to build site docs, because of a dependency in JPOX plugin. It depends upon "jpox-1.0.0-beta-3.jar", which is not in ibiblio repository. Is there another repository I'm missing? /Per |
From: Andy J. <an...@aj...> - 2004-04-12 06:37:04
|
> 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 |
From: Per O. <po...@no...> - 2004-04-11 21:16:33
|
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 |
From: Richard Lewis-S. <rle...@ma...> - 2004-04-02 23:38:58
|
The was40 plugin won't work with WAS5.1, but I expect the was5 plugin would - though I have only tested it with WAS5. (the wsanttasks that it uses appear to be the same in WAS5 and 5.1 so it should just work). http://maven-plugins.sourceforge.net/maven-was5-plugin/ Richard ----- Original Message ----- From: "Michael MATTOX" <mic...@ve...> To: <mav...@li...> Sent: Saturday, April 03, 2004 12:30 AM Subject: [Maven-plugins-developer] Is there a Maven plugin for WebSphere 5.1 > I see there is a plugin for WebSphere 4.0 but I'm curious if it works for > 5.1.1 or if there is a plugin for WebSphere 5.1? > > Thanks, > Michael > > > -- > This E-mail is confidential. It may also be legally privileged. If you are > not the addressee you may not copy, forward, disclose or use any part of it. > If you have received this message in error, please delete it and all copies > from your system and notify the sender immediately by return E-mail. > Internet communications cannot be guaranteed to be timely, secure, error or > virus-free. The sender does not accept liability for any errors or omissions. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer |
From: Michael M. <mic...@ve...> - 2004-04-02 14:31:47
|
I see there is a plugin for WebSphere 4.0 but I'm curious if it works for 5.1.1 or if there is a plugin for WebSphere 5.1? Thanks, Michael -- This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. |
From: <po...@no...> - 2004-03-17 15:52:51
|
Hi Siegfried, > Hi all, > > sorry for not responding properly - don't have any good execuse for it. > And your conversation showed more knowledge about DocBook than I have !! > > Welcme, Per Oleson ... :-) Thanks :-) Are you ok with me taking the responsibility of the sdocbook plugin from here on? /Per |
From: Andy J. <an...@aj...> - 2004-03-17 08:10:06
|
On Wednesday 17 Mar 2004 07:14, Per Olesen wrote: > So how's the usual practice here? Should I just commit my changes to the > sdocbook plugin right away, or are there someone, which should take a > closer look? Just commit your changes. Having the changes in CVS is the first step. Releasing a new version of the plugin is the second step. I'd hope that someone who's actually used the plugin will have time to look at it by the time you want it releasing. I've never used it. -- Andy |
From: Per O. <po...@no...> - 2004-03-17 07:19:01
|
On Wednesday 17 March 2004 07:19, Andy Jefferson wrote: > Per, > > you're now added with CVS commit rights. Great, thanks! So how's the usual practice here? Should I just commit my changes to the sdocbook plugin right away, or are there someone, which should take a closer look? Actually, Trygve has taken such a look I think, but he also told me, that he was not himself actively using that plugin. /Per |
From: Andy J. <an...@aj...> - 2004-03-17 06:19:38
|
On Tuesday 16 Mar 2004 21:25, Per Olesen wrote: > My sf.net username is "perolesen". Per, you're now added with CVS commit rights. -- Andy |
From: Per O. <po...@no...> - 2004-03-16 21:29:54
|
Hi, > I would like to add Per Olesen as a comitter for the sbook plugin. > He has a big patch for it and the maintainer Siegfried Goeschl > hasn't responded to any of his emails. I said I could apply them > but it grew a bit out of my hand and he might as well get commit > rights. > > So, if this is ok, Per will respond with his sf.net username and > Andy can add him. My sf.net username is "perolesen". BTW: If anyone wants to have a look at the patch, it can be found in the patches section on the project page (http://sourceforge.net/tracker/?atid=497855&group_id=61626&func=browse). In addition, there has been a little thread between me and Trygve on the maven-plugins-user list about the changes (http://sourceforge.net/mailarchive/forum.php?thread_id=3871273&forum_id=11777). Kind Regards, Per |
From: <try...@st...> - 2004-03-16 19:45:07
|
Hi! I would like to add Per Olesen as a comitter for the sbook plugin. He has a big patch for it and the maintainer Siegfried Goeschl hasn't responded to any of his emails. I said I could apply them but it grew a bit out of my hand and he might as well get commit rights. So, if this is ok, Per will respond with his sf.net username and Andy can add him. Thanks, Trygve |
From: Richard Lewis-S. <rle...@ma...> - 2004-03-12 02:02:03
|
I tried to keep the names the same as the .bat/.sh = scripts/wsanttasks.jar task class names. I agree the name is = misleading, but that's the name IBM uses, so I figured it makes it = easier for those who know the tools already. Richard ----- Original Message -----=20 From: di...@mu...=20 To: mav...@li...=20 Sent: Friday, March 12, 2004 12:23 PM Subject: [Maven-plugins-developer] WAS5 and WAS4 plugin inconsistency The WAS5 plugin uses was5:ejbDeploy to generate ejb code for = deployment.=20 The WAS4 plugin uses was40:generate-ejb-code.=20 If ejbDeploy is the preferred name, I'll change the was4 plugin to = match. The reason I didn't use it is that 'ejbDeploy' doesn't actually = 'deploy' anything and could be confusing.=20 -- dIon Gillard, Multitask Consulting |
From: <di...@mu...> - 2004-03-12 01:37:23
|
The WAS5 plugin uses was5:ejbDeploy to generate ejb code for deployment. The WAS4 plugin uses was40:generate-ejb-code. If ejbDeploy is the preferred name, I'll change the was4 plugin to match. The reason I didn't use it is that 'ejbDeploy' doesn't actually 'deploy' anything and could be confusing. -- dIon Gillard, Multitask Consulting |
From: <di...@mu...> - 2004-03-12 01:33:04
|
Hi guys, I've updated the project.xml and published the web site for the WAS5 plugin. Hope noone minds. I had a couple of emails asking for a binary version and some docs..... See http://maven-plugins.sourceforge.net/maven-was5-plugin/ -- dIon Gillard, Multitask Consulting |
From: Andy J. <an...@aj...> - 2004-03-08 06:44:14
|
On Sunday 07 Mar 2004 23:25, di...@mu... wrote: > Guys (on maven-plugins-developer), can we add Richard as a developer for > the new plugin? Done. -- Andy |
From: <try...@st...> - 2004-03-07 23:53:04
|
On Mon, 8 Mar 2004 10:25:49 +1100, <di...@mu...> wrote: > ----- 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? +1 > > -- > dIon Gillard, Multitask Consulting -- Trygve |