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: Jeff J. <jef...@up...> - 2006-06-03 13:41:18
|
Giving it some thought this morning, I strongly prefer to release the
plugins code as-is (since they've had many weeks of problem-free running)
and update the docs to note the debug setting issue, and do another snapshot
soon after with any debug code-handling decision.
I think this because the debug issue is not new/not a regression, and this
change should have more than casual testing to avoid any issues when the
user wants debug off.
Even though the code change appears minor, small "innocent" changes are
famous for causing problems. :-) I really am against the "last minute
change" syndrome.
Additionally, new FindBugs and Cobertura releases are on the horizon, so
additional plugin releases are forthcoming when they are available and have
some miles on them.
-----Original Message-----
From: mav...@li...
[mailto:mav...@li...] On Behalf Of
Jeff Jensen
Sent: Friday, June 02, 2006 12:10 PM
To: Lukas Theussl
Cc: mav...@li...
Subject: Re: [Maven-plugins-developer] [vote]
Releasemaven-cobertura-plugin-1.2
Great info Lukas, thanks. I will change the plugin and add a doc note.
Quoting Lukas Theussl <lth...@ap...>:
>
> +1
>
> However, not having used cobertura for a long time, I had forgotten
> that you need to set maven.compile.debug=on when running the plugin,
> otherwise you don't get any coverage data. I had
> maven.compile.debug=off in one of my properties files and it took me a
> while to figure out what was wrong.
>
> AFAICS, this is nowhere mentioned in the docs on the web page.
> However, instead of letting the user figure this out himself, I'd
> suggest we force debug=on when executing the plugin, since otherwise,
> the report is completely useless anyway. Just put something like this
> in the cobertura:report goal when calling cobertura:on:
>
> <!-- Make sure maven.compile.debug = on -->
> <j:set var="compileDebugOld" value="${maven.compile.debug}"/>
> <j:set var="maven.compile.debug" scope="parent" value="on"/>
> <attainGoal name="cobertura:on"/>
> <j:set var="maven.compile.debug" scope="parent"
> value="${compileDebugOld}"/>
>
>
> Actually, I just noticed that also findbugs needs debug=on for getting
> the line number information. You should do the same as above when
> calling java:compile in maven-findbugs-plugin:report.
>
>
> Cheers,
> -Lukas
>
>
> Jeff Jensen wrote:
> > Please vote to release Cobertura plugin from snapshot. I will do so
> > on
> Sunday
> > if no objections.
> >
> >
> >
> > _______________________________________________
> > Maven-plugins-developer mailing list
> > Mav...@li...
> > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer
> >
>
_______________________________________________
Maven-plugins-developer mailing list
Mav...@li...
https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer
|
|
From: Arnaud H. <ahe...@gm...> - 2006-06-02 20:59:18
|
+1 to release findbugs 1.2 and cobertura 1.2 Arnaud |
|
From: Jeff J. <jef...@up...> - 2006-06-02 17:37:41
|
Great info Lukas, thanks. I will change the plugin and add a doc note.
Quoting Lukas Theussl <lth...@ap...>:
>
> +1
>
> However, not having used cobertura for a long time, I had forgotten tha=
t
> you need to set maven.compile.debug=3Don when running the plugin,
> otherwise you don't get any coverage data. I had maven.compile.debug=3D=
off
> in one of my properties files and it took me a while to figure out what
> was wrong.
>
> AFAICS, this is nowhere mentioned in the docs on the web page. However,
> instead of letting the user figure this out himself, I'd suggest we
> force debug=3Don when executing the plugin, since otherwise, the report=
is
> completely useless anyway. Just put something like this in the
> cobertura:report goal when calling cobertura:on:
>
> <!-- Make sure maven.compile.debug =3D on -->
> <j:set var=3D"compileDebugOld" value=3D"${maven.compile.debug}"/>
> <j:set var=3D"maven.compile.debug" scope=3D"parent" value=3D"on"/>
> <attainGoal name=3D"cobertura:on"/>
> <j:set var=3D"maven.compile.debug" scope=3D"parent"
> value=3D"${compileDebugOld}"/>
>
>
> Actually, I just noticed that also findbugs needs debug=3Don for gettin=
g
> the line number information. You should do the same as above when
> calling java:compile in maven-findbugs-plugin:report.
>
>
> Cheers,
> -Lukas
>
>
> Jeff Jensen wrote:
> > Please vote to release Cobertura plugin from snapshot. I will do so =
on
> Sunday
> > if no objections.
> >
> >
> >
> > _______________________________________________
> > Maven-plugins-developer mailing list
> > Mav...@li...
> > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer
> >
>
|
|
From: Lukas T. <lth...@ap...> - 2006-06-02 17:37:12
|
+1
However, not having used cobertura for a long time, I had forgotten that
you need to set maven.compile.debug=on when running the plugin,
otherwise you don't get any coverage data. I had maven.compile.debug=off
in one of my properties files and it took me a while to figure out what
was wrong.
AFAICS, this is nowhere mentioned in the docs on the web page. However,
instead of letting the user figure this out himself, I'd suggest we
force debug=on when executing the plugin, since otherwise, the report is
completely useless anyway. Just put something like this in the
cobertura:report goal when calling cobertura:on:
<!-- Make sure maven.compile.debug = on -->
<j:set var="compileDebugOld" value="${maven.compile.debug}"/>
<j:set var="maven.compile.debug" scope="parent" value="on"/>
<attainGoal name="cobertura:on"/>
<j:set var="maven.compile.debug" scope="parent"
value="${compileDebugOld}"/>
Actually, I just noticed that also findbugs needs debug=on for getting
the line number information. You should do the same as above when
calling java:compile in maven-findbugs-plugin:report.
Cheers,
-Lukas
Jeff Jensen wrote:
> Please vote to release Cobertura plugin from snapshot. I will do so on Sunday
> if no objections.
>
>
>
> _______________________________________________
> Maven-plugins-developer mailing list
> Mav...@li...
> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer
>
|
|
From: Lukas T. <lth...@ap...> - 2006-06-02 17:36:41
|
+1 Even though there is no voting policy on sf, it's probably good to give interested people a heads-up for final testing. Thanks for doing this! -Lukas Jeff Jensen wrote: > Please vote to release FindBugs plugin from snapshot. I will do so on Sunday if > no objections. > > > > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > |
|
From: Jeff J. <jef...@up...> - 2006-06-02 14:05:08
|
Please vote to release Cobertura plugin from snapshot. I will do so on S= unday if no objections. |
|
From: Jeff J. <jef...@up...> - 2006-06-02 14:04:53
|
Please vote to release FindBugs plugin from snapshot. I will do so on Su= nday if no objections. |
|
From: Steve C. <ste...@gm...> - 2006-02-23 15:14:07
|
Hi Seigfried Great, I am very pleased that you would like to add it. 1) Javadoc plugin - ah, this must be in my local repo from ages ago, I will change it. 2) I haven't considered JSR 223 or BSH, I have nothing against adding support for them provided it doesn't make things complicated for the users of the plugin. I will look into these. 3) I have no problem changing the package names and fitting into whatever the development standards are at maven-plugins 4) Yes I have an sf ID, it is "uanda" (http://sourceforge.net/users/uanda/)= , I am the admin on http://dspro.sourceforge.net . I will look into BSH and JSR 223 over the next week or so, could you let me know what happens next? Just so that you are aware (I am not sure how the decision making process works), I have also received the following communication from Brett Porter: "There are some plugins similar to this at mojo.codehaus.org. Maybe you could propose it there?" Regards Stephen On 2/23/06, Siegfried Goeschl <sie...@it...> wrote: > > Hi Steve, > > I had a quick look at your plugin > > +) it looks nice anf I would like to add it > > +) I had a tiny problem with you maven-javadoc-plugin > 2.0-beta-3-SNAPSHOT since it was nowhere found in the M2 repos > > +) have you considered using JSR 223 or BSF instead of plain BSH - I > admit this i a cheeky question but would allow to run Groovy or Pnuts as > well > > +) do you mind changing package names to something like > net.sf.mavenplugins > > +) do you have a SF id > > Cheers > > Siegfried Goeschl > > mav...@li... wrote: > > Send Maven-plugins-developer mailing list submissions to > > mav...@li... > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > or, via email, send a message with subject or body 'help' to > > mav...@li... > > > > You can reach the person managing the list at > > mav...@li... > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Maven-plugins-developer digest..." > > > > > > Today's Topics: > > > > 1. Beanshell plugin (Steve Cowx) > > > > --__--__-- > > > > Message: 1 > > Date: Tue, 21 Feb 2006 02:24:31 +0000 > > From: "Steve Cowx" < ste...@gm...> > > To: mav...@li... > > Subject: [Maven-plugins-developer] Beanshell plugin > > > > ------=3D_Part_15965_4148378.1140488671327 > > Content-Type: text/plain; charset=3DISO-8859-1 > > Content-Transfer-Encoding: quoted-printable > > Content-Disposition: inline > > > > Hi All > > > > I have developed a Maven 2 plugin for running beanshell scripts. I am > > interested in releasing the plugin as open source and I have been > advised > > (by Eric Pugh) to submit it to the maven-plugins project to see if you > are > > interested. > > > > I feel that this is a very powerful and useful plugin. It allows > > functionality to be quickly and easily added to Maven 2 builds without > > having to write dedicated plugins. It is easy to use and fits in well > with > > the build process. This plugin will suit all those who wish it were > easy t=3D > > o > > add scripted functionality to their projects in a similar way to what > Jelly > > used to do in Maven 1. > > > > If you would like to look at it and use it, I have created a zip file > which > > contains the entire project. You can download it at: > > http://www.explosion-it.net/downloads/beanshell.zip > > > > The zip file contains a fully built project, the site in the target > > directory if you want to get a look at the docs etc. > > It should build using Maven 2 (I am using version 2.02) if you want to > buil=3D > > d > > it yourself. > > > > I look forward to your feedback. > > > > Should you decide to incorporate this plugin into the maven-plugins > project=3D > > , > > I would be grateful if I could play a part in it's future maintenance > and > > development. > > -- > > Kind regards > > > > Stephen Cowx > > Email: sc...@ex... > > > > ------=3D_Part_15965_4148378.1140488671327 > > Content-Type: text/html; charset=3DISO-8859-1 > > Content-Transfer-Encoding: quoted-printable > > Content-Disposition: inline > > > > Hi All<br> > > > > <br> > > > > I have developed a Maven 2 plugin for running beanshell scripts. > > I am interested in releasing the plugin as open source and I have been > advi=3D > > sed (by > > Eric Pugh) to submit it to the maven-plugins project to see if you are > inte=3D > > rested.<br> > > > > <br> > > > > I feel that this is a very powerful and useful plugin. It allows > > functionality to be quickly and easily added to Maven 2 builds without > > having to write dedicated plugins. It is easy to use and > > fits in well with the build process. This plugin will suit all > > those who wish it were easy to add scripted functionality to their > > projects in a similar way to what Jelly used to do in Maven 1.<br> > > > > <br> > > If you would like to look at it and use it, I have created a zip file > > which contains the entire project. You can download it at: > > <a href=3D3D" http://www.explosion-it.net/downloads/beanshell.zip"> > http://www.=3D > > explosion-it.net/downloads/beanshell.zip</a><br> > > <br> > > The zip file contains a fully built project, the site in the target > directo=3D > > ry if you want to get a look at the docs etc.<br> > > It should build using Maven 2 (I am > > using version 2.02) if you want to build it yourself.<br> > > > > <br> > > > > I look forward to your feedback.<br> > > > > <br> > > > > Should you decide to incorporate this plugin into the maven-plugins > project=3D > > , I would be > > grateful if I could play a part in it's future maintenance and > > development. <br> > > > > -- <br> > > Kind regards<br> > > <br> > > Stephen Cowx<br> > > > > Email: <a href=3D3D"mailto:sc...@ex..." target=3D3D"_blank" > onclick=3D > > =3D3D"return top.js.OpenExtLink(window,event,this)"> > sc...@ex...</a=3D > > > >><br> > > > > <br> > > <br> > > > > > > ------=3D_Part_15965_4148378.1140488671327-- > > > > > > > > --__--__-- > > > > _______________________________________________ > > Maven-plugins-developer mailing list > > Mav...@li... > > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > > > > End of Maven-plugins-developer Digest > > > -- Kind regards Stephen Cowx 07748 490 323 0208 349 0005 |
|
From: Siegfried G. <sie...@it...> - 2006-02-23 10:39:20
|
Hi Steve, I had a quick look at your plugin +) it looks nice anf I would like to add it +) I had a tiny problem with you maven-javadoc-plugin 2.0-beta-3-SNAPSHOT since it was nowhere found in the M2 repos +) have you considered using JSR 223 or BSF instead of plain BSH - I admit this i a cheeky question but would allow to run Groovy or Pnuts as well +) do you mind changing package names to something like net.sf.mavenplugins +) do you have a SF id Cheers Siegfried Goeschl mav...@li... wrote: > Send Maven-plugins-developer mailing list submissions to > mav...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > or, via email, send a message with subject or body 'help' to > mav...@li... > > You can reach the person managing the list at > mav...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Maven-plugins-developer digest..." > > > Today's Topics: > > 1. Beanshell plugin (Steve Cowx) > > --__--__-- > > Message: 1 > Date: Tue, 21 Feb 2006 02:24:31 +0000 > From: "Steve Cowx" <ste...@gm...> > To: mav...@li... > Subject: [Maven-plugins-developer] Beanshell plugin > > ------=_Part_15965_4148378.1140488671327 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > Hi All > > I have developed a Maven 2 plugin for running beanshell scripts. I am > interested in releasing the plugin as open source and I have been advised > (by Eric Pugh) to submit it to the maven-plugins project to see if you are > interested. > > I feel that this is a very powerful and useful plugin. It allows > functionality to be quickly and easily added to Maven 2 builds without > having to write dedicated plugins. It is easy to use and fits in well with > the build process. This plugin will suit all those who wish it were easy t= > o > add scripted functionality to their projects in a similar way to what Jelly > used to do in Maven 1. > > If you would like to look at it and use it, I have created a zip file which > contains the entire project. You can download it at: > http://www.explosion-it.net/downloads/beanshell.zip > > The zip file contains a fully built project, the site in the target > directory if you want to get a look at the docs etc. > It should build using Maven 2 (I am using version 2.02) if you want to buil= > d > it yourself. > > I look forward to your feedback. > > Should you decide to incorporate this plugin into the maven-plugins project= > , > I would be grateful if I could play a part in it's future maintenance and > development. > -- > Kind regards > > Stephen Cowx > Email: sc...@ex... > > ------=_Part_15965_4148378.1140488671327 > Content-Type: text/html; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > Hi All<br> > > <br> > > I have developed a Maven 2 plugin for running beanshell scripts. > I am interested in releasing the plugin as open source and I have been advi= > sed (by > Eric Pugh) to submit it to the maven-plugins project to see if you are inte= > rested.<br> > > <br> > > I feel that this is a very powerful and useful plugin. It allows > functionality to be quickly and easily added to Maven 2 builds without > having to write dedicated plugins. It is easy to use and > fits in well with the build process. This plugin will suit all > those who wish it were easy to add scripted functionality to their > projects in a similar way to what Jelly used to do in Maven 1.<br> > > <br> > If you would like to look at it and use it, I have created a zip file > which contains the entire project. You can download it at: > <a href=3D"http://www.explosion-it.net/downloads/beanshell.zip">http://www.= > explosion-it.net/downloads/beanshell.zip</a><br> > <br> > The zip file contains a fully built project, the site in the target directo= > ry if you want to get a look at the docs etc.<br> > It should build using Maven 2 (I am > using version 2.02) if you want to build it yourself.<br> > > <br> > > I look forward to your feedback.<br> > > <br> > > Should you decide to incorporate this plugin into the maven-plugins project= > , I would be > grateful if I could play a part in it's future maintenance and > development. <br> > > -- <br> > Kind regards<br> > <br> > Stephen Cowx<br> > > Email: <a href=3D"mailto:sc...@ex..." target=3D"_blank" onclick= > =3D"return top.js.OpenExtLink(window,event,this)">sc...@ex...</a= > >><br> > > <br> > <br> > > > ------=_Part_15965_4148378.1140488671327-- > > > > --__--__-- > > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > End of Maven-plugins-developer Digest > |
|
From: Steve C. <ste...@gm...> - 2006-02-21 02:24:41
|
Hi All I have developed a Maven 2 plugin for running beanshell scripts. I am interested in releasing the plugin as open source and I have been advised (by Eric Pugh) to submit it to the maven-plugins project to see if you are interested. I feel that this is a very powerful and useful plugin. It allows functionality to be quickly and easily added to Maven 2 builds without having to write dedicated plugins. It is easy to use and fits in well with the build process. This plugin will suit all those who wish it were easy t= o add scripted functionality to their projects in a similar way to what Jelly used to do in Maven 1. If you would like to look at it and use it, I have created a zip file which contains the entire project. You can download it at: http://www.explosion-it.net/downloads/beanshell.zip The zip file contains a fully built project, the site in the target directory if you want to get a look at the docs etc. It should build using Maven 2 (I am using version 2.02) if you want to buil= d it yourself. I look forward to your feedback. Should you decide to incorporate this plugin into the maven-plugins project= , I would be grateful if I could play a part in it's future maintenance and development. -- Kind regards Stephen Cowx Email: sc...@ex... |
|
From: Arnaud H. <ahe...@gm...> - 2006-02-16 14:58:31
|
I'm not a developer on mavenn plugins @ sf and I don't if there's lot of activity. If nobody can do it, I'll ask to add me to the dev team to do it. Arnaud On 2/16/06, Nicolas De Loof <nic...@ca...> wrote: > > Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ? > > I'm using AspectJ and JiBX that both operate on bytecode and are not > compatible with cobertura 1.6 instrumentation (plugin fails) > > Upgrading dependency to 1.7 solves this problem > > I've created > http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1432911&grou= p_id=3D61626&atid=3D497853 > for this. > > Nico. > > This message contains information that may be privileged or confidential = and is the property of the Capgemini Group. It is intended only for the per= son to whom it is addressed. If you are not the intended recipient, you ar= e not authorized to read, print, retain, copy, disseminate, distribute, or= use this message or any part thereof. If you receive this message in erro= r, please notify the sender immediately and delete all copies of this mess= age. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: use...@ma... > For additional commands, e-mail: use...@ma... > > |
|
From: Jeff J. <jef...@up...> - 2006-01-19 14:50:51
|
Hi, RFE 1406821 has a patch attached. Would the correct person(s) please rev= iew it for commit consideration please? TIA Is there a process to get it reviewed other than an email such as this? |
|
From: Stephen C. <sco...@bt...> - 2006-01-10 01:24:58
|
Thanks for the help. Maven sourceforge plugin v1.3 is now released, repository updated, website refreshed etc, etc. The following is a good setup if you want to use it for maven-plugins: maven.sourceforge.project.groupId = 61626 maven.sourceforge.project.packageName = ********-plugin maven.sourceforge.publish.includes = *.jar,distributions/*-src.zip,distributions/*-src.tar.gz maven.sourceforge.publish.excludes = *-bundle.jar plus maven.sourceforge.username maven.sourceforge.password This setup will publish the src zip/gz and the jar file to SF release area. Just do 'maven dist sourceforge:deploy'. Stephen Eric Pugh wrote: > Stephen, > > That is great... Now, in terms of releasing it, we don't use the > release stuff that SF provides.. INstead, we deploy into our own > repository, which gets synced over to ibiblio. So, go through the > release process like you normally would, and just deploy it into / > htdocs/repository/maven-plugins/... directory path. Now, are you > saying you can't close bugs/patches? > > Eric > > > On Jan 7, 2006, at 11:08 PM, Stephen Colebourne wrote: > >> Thanks Eric. I have now checked in the (large) update, which is to >> most of the files in the plugin. >> >> I have verified that this works by uploading http://joda- >> time.sourceforge.net/contrib/jsptags v1.0 >> >> What next? Will you or someone else review it? And release it? >> >> If you want, I am happy to be granted Release Manager and Forum >> update capabilities so I can release it and close all the outstanding >> bugs/patches etc. >> >> Thanks >> >> Stephen >> >> >> Eric Pugh wrote: >> >>> We have pretty low barrier to entry, and I know you from ASF.... >>> I've gone ahead and added you. Can't wait to see the fixes. >>> Also, I've seen Eclipse do some things with XML parsers that differ >>> from Maven.... >>> Lastly, check out the fork mode for running junit tests... >>> Eric >>> On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: >>> >>>> Hi all, >>>> I would like to contribute my sourceforge plugin changes back. Is >>>> anyone interested in reviewing them, or giving scolebourne direct >>>> commit access? Please! >>>> >>>> Stephen >>>> >>>> >>>> >>>> Jörg Schaible wrote: >>>> >>>>> Stephen Colebourne wrote: >>>>> >>>>>> The code in CVS seeemed to be far from usable, so I've dived in and >>>>>> tried to patch it up. >>>>>> >>>>>> I've got the plugin working from within Eclipse fine, however I >>>>>> don't >>>>>> seem to be able to successfully get the plugin built. >>>>>> >>>>>> The first problem is that 50% of the tests fail when running 'maven >>>>>> clean plugin:install' (they all succeed when run inside Eclipse). >>>>> >>>>> >>>>> Does it run if you don't clean before? >>>>> >>>>>> So, has anyone else worked on getting the sf plugin running? >>>>>> Would you >>>>>> be interested in me fixing it? (scolebourne if you want to grant >>>>>> access). >>>>>> >>>>>> More importantly though, how do you go about solving a problem >>>>>> when it >>>>>> works in Eclipse but doesn't outside? >>>>> >>>>> >>>>> Most of the time you forgot, that Eclipse will automatically copy any >>>>> resource from the source path into target, while you have to tell >>>>> Maven >>>>> explicitly, what files are resources. >>>>> - Jörg >>>>> ------------------------------------------------------- >>>>> This SF.net email is sponsored by: Splunk Inc. Do you grep >>>>> through log files >>>>> for problems? Stop! Download the new AJAX search engine that makes >>>>> searching your log files as easy as surfing the web. DOWNLOAD >>>>> SPLUNK! >>>>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >>>>> _______________________________________________ >>>>> Maven-plugins-developer mailing list >>>>> Mav...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/maven-plugins- developer >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: Splunk Inc. Do you grep through >>>> log files >>>> for problems? Stop! Download the new AJAX search engine that makes >>>> searching your log files as easy as surfing the web. DOWNLOAD >>>> SPLUNK! >>>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >>>> _______________________________________________ >>>> Maven-plugins-developer mailing list >>>> Mav...@li... >>>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. Do you grep through >>> log files >>> for problems? Stop! Download the new AJAX search engine that makes >>> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >>> http://ads.osdn.com/?ad_idv37&alloc_id865&op=click >>> _______________________________________________ >>> Maven-plugins-developer mailing list >>> Mav...@li... >>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > |
|
From: Eric P. <ep...@up...> - 2006-01-09 15:21:29
|
Stephen, That is great... Now, in terms of releasing it, we don't use the =20 release stuff that SF provides.. INstead, we deploy into our own =20 repository, which gets synced over to ibiblio. So, go through the =20 release process like you normally would, and just deploy it into /=20 htdocs/repository/maven-plugins/... directory path. Now, are you =20 saying you can't close bugs/patches? Eric On Jan 7, 2006, at 11:08 PM, Stephen Colebourne wrote: > Thanks Eric. I have now checked in the (large) update, which is to =20 > most of the files in the plugin. > > I have verified that this works by uploading http://joda-=20 > time.sourceforge.net/contrib/jsptags v1.0 > > What next? Will you or someone else review it? And release it? > > If you want, I am happy to be granted Release Manager and Forum =20 > update capabilities so I can release it and close all the =20 > outstanding bugs/patches etc. > > Thanks > > Stephen > > > Eric Pugh wrote: >> We have pretty low barrier to entry, and I know you from =20 >> ASF.... I've gone ahead and added you. Can't wait to see the =20 >> fixes. Also, I've seen Eclipse do some things with XML parsers =20 >> that differ from Maven.... >> Lastly, check out the fork mode for running junit tests... >> Eric >> On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: >>> Hi all, >>> I would like to contribute my sourceforge plugin changes back. =20 >>> Is anyone interested in reviewing them, or giving scolebourne =20 >>> direct commit access? Please! >>> >>> Stephen >>> >>> >>> >>> J=F6rg Schaible wrote: >>> >>>> Stephen Colebourne wrote: >>>> >>>>> The code in CVS seeemed to be far from usable, so I've dived in =20= >>>>> and >>>>> tried to patch it up. >>>>> >>>>> I've got the plugin working from within Eclipse fine, however =20 >>>>> I don't >>>>> seem to be able to successfully get the plugin built. >>>>> >>>>> The first problem is that 50% of the tests fail when running =20 >>>>> 'maven >>>>> clean plugin:install' (they all succeed when run inside Eclipse). >>>> >>>> Does it run if you don't clean before? >>>> >>>>> So, has anyone else worked on getting the sf plugin running? =20 >>>>> Would you >>>>> be interested in me fixing it? (scolebourne if you want to =20 >>>>> grant access). >>>>> >>>>> More importantly though, how do you go about solving a problem =20= >>>>> when it >>>>> works in Eclipse but doesn't outside? >>>> >>>> Most of the time you forgot, that Eclipse will automatically =20 >>>> copy any >>>> resource from the source path into target, while you have to =20 >>>> tell Maven >>>> explicitly, what files are resources. >>>> - J=F6rg >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: Splunk Inc. Do you grep =20 >>>> through log files >>>> for problems? Stop! Download the new AJAX search engine that =20 >>>> makes >>>> searching your log files as easy as surfing the web. DOWNLOAD =20= >>>> SPLUNK! >>>> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >>>> _______________________________________________ >>>> Maven-plugins-developer mailing list >>>> Mav...@li... >>>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-=20 >>>> developer >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. Do you grep =20 >>> through log files >>> for problems? Stop! Download the new AJAX search engine that makes >>> searching your log files as easy as surfing the web. DOWNLOAD =20 >>> SPLUNK! >>> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >>> _______________________________________________ >>> Maven-plugins-developer mailing list >>> Mav...@li... >>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through =20= >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD =20 >> SPLUNK! >> http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through =20 > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD =20 > SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer |
|
From: Stephen C. <sco...@bt...> - 2006-01-07 23:08:51
|
Thanks Eric. I have now checked in the (large) update, which is to most of the files in the plugin. I have verified that this works by uploading http://joda-time.sourceforge.net/contrib/jsptags v1.0 What next? Will you or someone else review it? And release it? If you want, I am happy to be granted Release Manager and Forum update capabilities so I can release it and close all the outstanding bugs/patches etc. Thanks Stephen Eric Pugh wrote: > We have pretty low barrier to entry, and I know you from ASF.... I've > gone ahead and added you. Can't wait to see the fixes. Also, I've > seen Eclipse do some things with XML parsers that differ from Maven.... > > Lastly, check out the fork mode for running junit tests... > > Eric > > On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: > >> Hi all, >> I would like to contribute my sourceforge plugin changes back. Is >> anyone interested in reviewing them, or giving scolebourne direct >> commit access? Please! >> >> Stephen >> >> >> >> Jörg Schaible wrote: >> >>> Stephen Colebourne wrote: >>> >>>> The code in CVS seeemed to be far from usable, so I've dived in and >>>> tried to patch it up. >>>> >>>> I've got the plugin working from within Eclipse fine, however I don't >>>> seem to be able to successfully get the plugin built. >>>> >>>> The first problem is that 50% of the tests fail when running 'maven >>>> clean plugin:install' (they all succeed when run inside Eclipse). >>> >>> Does it run if you don't clean before? >>> >>>> So, has anyone else worked on getting the sf plugin running? Would you >>>> be interested in me fixing it? (scolebourne if you want to grant >>>> access). >>>> >>>> More importantly though, how do you go about solving a problem when it >>>> works in Eclipse but doesn't outside? >>> >>> Most of the time you forgot, that Eclipse will automatically copy any >>> resource from the source path into target, while you have to tell Maven >>> explicitly, what files are resources. >>> - Jörg >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. Do you grep through >>> log files >>> for problems? Stop! Download the new AJAX search engine that makes >>> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >>> _______________________________________________ >>> Maven-plugins-developer mailing list >>> Mav...@li... >>> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > |
|
From: Eric P. (OSC) <ep...@op...> - 2006-01-03 02:58:20
|
The maven-plugins team is pleased to announce the FindBugs Plug-in 1.1 release! http://maven-plugins.sourceforge.net/maven-findbugs-plugin A plugin to automate FindBugs tasks Changes in this version include: Changes: o Update to findbugs 0.9.4. (Special thanks to Carlos Sanchez for his coaching on upload requests!) To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven-plugins -DartifactId=maven-findbugs-plugin -Dversion=1.1 For a manual installation, you can download the plugin here: http://maven-plugins.sourceforge.net/repository/maven-plugins/plugins/ maven-findbugs-plugin-1.1.jar Have fun! -The maven-plugins team |
|
From: Eric P. <ep...@up...> - 2006-01-03 02:27:54
|
We have pretty low barrier to entry, and I know you from ASF.... =20 I've gone ahead and added you. Can't wait to see the fixes. Also, =20 I've seen Eclipse do some things with XML parsers that differ from =20 Maven.... Lastly, check out the fork mode for running junit tests... Eric On Jan 2, 2006, at 6:54 PM, Stephen Colebourne wrote: > Hi all, > I would like to contribute my sourceforge plugin changes back. Is =20 > anyone interested in reviewing them, or giving scolebourne direct =20 > commit access? Please! > > Stephen > > > > J=F6rg Schaible wrote: >> Stephen Colebourne wrote: >>> The code in CVS seeemed to be far from usable, so I've dived in and >>> tried to patch it up. >>> >>> I've got the plugin working from within Eclipse fine, however I =20 >>> don't >>> seem to be able to successfully get the plugin built. >>> >>> The first problem is that 50% of the tests fail when running 'maven >>> clean plugin:install' (they all succeed when run inside Eclipse). >> Does it run if you don't clean before? >>> So, has anyone else worked on getting the sf plugin running? =20 >>> Would you >>> be interested in me fixing it? (scolebourne if you want to grant =20 >>> access). >>> >>> More importantly though, how do you go about solving a problem =20 >>> when it >>> works in Eclipse but doesn't outside? >> Most of the time you forgot, that Eclipse will automatically copy any >> resource from the source path into target, while you have to tell =20 >> Maven >> explicitly, what files are resources. >> - J=F6rg >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through =20= >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD =20 >> SPLUNK! >> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >> _______________________________________________ >> Maven-plugins-developer mailing list >> Mav...@li... >> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through =20 > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD =20 > SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer |
|
From: Stephen C. <sco...@bt...> - 2006-01-02 23:54:25
|
Hi all, I would like to contribute my sourceforge plugin changes back. Is anyone interested in reviewing them, or giving scolebourne direct commit access? Please! Stephen Jörg Schaible wrote: > Stephen Colebourne wrote: > > >>The code in CVS seeemed to be far from usable, so I've dived in and >>tried to patch it up. >> >>I've got the plugin working from within Eclipse fine, however I don't >>seem to be able to successfully get the plugin built. >> >>The first problem is that 50% of the tests fail when running 'maven >>clean plugin:install' (they all succeed when run inside Eclipse). > > > Does it run if you don't clean before? > > >>So, has anyone else worked on getting the sf plugin running? Would you >>be interested in me fixing it? (scolebourne if you want to grant access). >> >>More importantly though, how do you go about solving a problem when it >>works in Eclipse but doesn't outside? > > > Most of the time you forgot, that Eclipse will automatically copy any > resource from the source path into target, while you have to tell Maven > explicitly, what files are resources. > > - Jörg > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Maven-plugins-developer mailing list > Mav...@li... > https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer > |
|
From: S. <joe...@gm...> - 2005-12-29 22:44:14
|
Stephen Colebourne wrote: > The code in CVS seeemed to be far from usable, so I've dived in and > tried to patch it up. > > I've got the plugin working from within Eclipse fine, however I don't > seem to be able to successfully get the plugin built. > > The first problem is that 50% of the tests fail when running 'maven > clean plugin:install' (they all succeed when run inside Eclipse). Does it run if you don't clean before? > So, has anyone else worked on getting the sf plugin running? Would you > be interested in me fixing it? (scolebourne if you want to grant access). > > More importantly though, how do you go about solving a problem when it > works in Eclipse but doesn't outside? Most of the time you forgot, that Eclipse will automatically copy any resource from the source path into target, while you have to tell Maven explicitly, what files are resources. - Jörg |
|
From: Stephen C. <sco...@bt...> - 2005-12-29 22:09:52
|
The code in CVS seeemed to be far from usable, so I've dived in and tried to patch it up. I've got the plugin working from within Eclipse fine, however I don't seem to be able to successfully get the plugin built. The first problem is that 50% of the tests fail when running 'maven clean plugin:install' (they all succeed when run inside Eclipse). So, has anyone else worked on getting the sf plugin running? Would you be interested in me fixing it? (scolebourne if you want to grant access). More importantly though, how do you go about solving a problem when it works in Eclipse but doesn't outside? Stephen |
|
From: Siegfried G. <sie...@it...> - 2005-12-01 14:31:15
|
Hi Scott, +) sf.net maven plugins is a breeding ground for plugins - a lot of committers and no pressure. If a plugin becomes popular enough to be moved to codehaus or core maven plugins that's fine - mission completed +) this is not the first and will not the last plugin moving out - the PMD plugin moved over to Maven a long time ago Cheers, Siegfried Goeschl Scott Ryan wrote: >>From the looks of it many of the existing sf.net maven plugins are moving > over to codehaus mojo project. It is an unusual process to get it accepted > over there but I may go ahead and submit it over there since they already > have a pretty thorough setup to automatically build and maintain the plugins > as part of the Maven 2 process. They have jira support for each plugin as > well. > > I am open to any input that anyone has for me not to move the Weblogic Maven > 2 plugin but I just want to get it delivered out to the community for > feedback and further enhancement. I am sensitive to the fact this plugin > had it genesis at SourceForge and that I am just a late entrant to the > development cycle. I want to keep the plugin alive and growing and > anyplace that we can put it to get the community involved is a good thing. > > If we can come up with a structure or plan among the maven development > community within sourceforge I am more than happy to support that as well > but the community looks a little stronger at codehaus. > > I welcome your input and support. > > Scott Ryan > Chief Technology Officer > Soaring Eagle L.L.C. > sc...@th... > www.soaringeagleco.com > (303) 263-3044 > > -----Original Message----- > From: Siegfried Goeschl [mailto:sie...@it...] > Sent: Thursday, December 01, 2005 4:06 AM > To: Scott Ryan; mav...@li... > Subject: Supporting Maven2 - WAS Re: How to contribute to the Weblogic > plugin > > > Hi Scott, > > I was the original author but I'm not the owner of the plugin - it > became your kid a long time ago ... :-). Consequently is the decision > where to host the plugin yours. > > Since I'm out of touch with Maven 2 plugin development - what are the > current plans for supporting the development of Maven 2 plugins? > > If there are no further plans/ideas I propose > > +) creating ${CVSROOT}/maven-plugins/maven2-plugins/ in parallel to the > existing ${CVSROOT}/maven-plugins/maven-plugins/ directory > > +) setting up a master build fro the Maven 2 plugins > > +) updating the website to distict between Maven 1 and Maven 2 > > Cheers, > > Siegfried Goeschl > > > Scott Ryan wrote: > >>Hi, >>I wanted to follow up on the version 2 of the plugin. I have been >>swamped with requests for the plugin but it is a pain to build and >>distribute on an individual basis so I wanted to put the code up on the >>Sourceforge repository but not sure if there was decision to start a new >>Maven 2 tree. Another alternative would be to put it over at codehaus >>or on apache proper. Not sure I would get permission to put it on >>Apache but codehaus has expressed interest in hosting it to combine it >>with the Cargo plugin. >> >>Since you are the owner and orginal author of the plugin what do you >>think should be done? I really want to put the version 2.0 plugin out >>to the public and get feedback via Jira asap. I also want to see about >>automating the build process so I can continue to upgrade the plugin as >>I have time. >> >>I look forward to your input. >> >> >>Scott Ryan >>Chief Technology Officer >>Soaring Eagle L.L.C. >>sc...@th... >>www.soaringeagleco.com >>(303) 263-3044 >> >> > > > > |
|
From: Scott R. <sc...@th...> - 2005-12-01 13:47:42
|
From the looks of it many of the existing sf.net maven plugins are moving over to codehaus mojo project. It is an unusual process to get it accepted over there but I may go ahead and submit it over there since they already have a pretty thorough setup to automatically build and maintain the plugins as part of the Maven 2 process. They have jira support for each plugin as well. I am open to any input that anyone has for me not to move the Weblogic Maven 2 plugin but I just want to get it delivered out to the community for feedback and further enhancement. I am sensitive to the fact this plugin had it genesis at SourceForge and that I am just a late entrant to the development cycle. I want to keep the plugin alive and growing and anyplace that we can put it to get the community involved is a good thing. If we can come up with a structure or plan among the maven development community within sourceforge I am more than happy to support that as well but the community looks a little stronger at codehaus. I welcome your input and support. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. sc...@th... www.soaringeagleco.com (303) 263-3044 -----Original Message----- From: Siegfried Goeschl [mailto:sie...@it...] Sent: Thursday, December 01, 2005 4:06 AM To: Scott Ryan; mav...@li... Subject: Supporting Maven2 - WAS Re: How to contribute to the Weblogic plugin Hi Scott, I was the original author but I'm not the owner of the plugin - it became your kid a long time ago ... :-). Consequently is the decision where to host the plugin yours. Since I'm out of touch with Maven 2 plugin development - what are the current plans for supporting the development of Maven 2 plugins? If there are no further plans/ideas I propose +) creating ${CVSROOT}/maven-plugins/maven2-plugins/ in parallel to the existing ${CVSROOT}/maven-plugins/maven-plugins/ directory +) setting up a master build fro the Maven 2 plugins +) updating the website to distict between Maven 1 and Maven 2 Cheers, Siegfried Goeschl Scott Ryan wrote: > Hi, > I wanted to follow up on the version 2 of the plugin. I have been > swamped with requests for the plugin but it is a pain to build and > distribute on an individual basis so I wanted to put the code up on the > Sourceforge repository but not sure if there was decision to start a new > Maven 2 tree. Another alternative would be to put it over at codehaus > or on apache proper. Not sure I would get permission to put it on > Apache but codehaus has expressed interest in hosting it to combine it > with the Cargo plugin. > > Since you are the owner and orginal author of the plugin what do you > think should be done? I really want to put the version 2.0 plugin out > to the public and get feedback via Jira asap. I also want to see about > automating the build process so I can continue to upgrade the plugin as > I have time. > > I look forward to your input. > > > Scott Ryan > Chief Technology Officer > Soaring Eagle L.L.C. > sc...@th... > www.soaringeagleco.com > (303) 263-3044 > > |
|
From: Siegfried G. <sie...@it...> - 2005-12-01 11:02:00
|
Hi Scott,
I was the original author but I'm not the owner of the plugin - it
became your kid a long time ago ... :-). Consequently is the decision
where to host the plugin yours.
Since I'm out of touch with Maven 2 plugin development - what are the
current plans for supporting the development of Maven 2 plugins?
If there are no further plans/ideas I propose
+) creating ${CVSROOT}/maven-plugins/maven2-plugins/ in parallel to the
existing ${CVSROOT}/maven-plugins/maven-plugins/ directory
+) setting up a master build fro the Maven 2 plugins
+) updating the website to distict between Maven 1 and Maven 2
Cheers,
Siegfried Goeschl
Scott Ryan wrote:
> Hi,
> I wanted to follow up on the version 2 of the plugin. I have been
> swamped with requests for the plugin but it is a pain to build and
> distribute on an individual basis so I wanted to put the code up on the
> Sourceforge repository but not sure if there was decision to start a new
> Maven 2 tree. Another alternative would be to put it over at codehaus
> or on apache proper. Not sure I would get permission to put it on
> Apache but codehaus has expressed interest in hosting it to combine it
> with the Cargo plugin.
>
> Since you are the owner and orginal author of the plugin what do you
> think should be done? I really want to put the version 2.0 plugin out
> to the public and get feedback via Jira asap. I also want to see about
> automating the build process so I can continue to upgrade the plugin as
> I have time.
>
> I look forward to your input.
>
>
> Scott Ryan
> Chief Technology Officer
> Soaring Eagle L.L.C.
> sc...@th...
> www.soaringeagleco.com
> (303) 263-3044
>
>
|
|
From: <Ste...@em...> - 2005-11-15 15:54:00
|
The maven-kodo-plugin team is pleased to announce the Kodo Plugin 4.0.0-EA3 release! http://maven-plugins.sourceforge.net/maven-kodo-plugin Maven plugin for Solarmetric's Kodo JDO implementation Changes in this version include: New Features: o This version requires Kodo 4.0.0EA3 jars. Please note that this version is in an early stage. Add a new property "maven.kodo.properties.filename" if the property file used is not "kodo.properties". Thanks to Mark Slater. For a manual installation, you can download the plugin here: https://sourceforge.net/project/showfiles.php?group_id=61626&package_id=93912&release_id=371112 Have fun! -The maven-kodo-plugin team |
|
From: Carlos S. <ca...@ap...> - 2005-11-08 18:14:50
|
I'll add this to the maven-plugins cvs so people can take a look at it, specially the ones working in the other history plugin. ---------- Forwarded message ---------- From: Morten Kristiansen <mor...@ms...> Date: Nov 8, 2005 2:28 AM Subject: Re: Maven dashboard history plugin To: ca...@ap... Do whatever you want with it Carlos. If there is something you find useful, just use it :) Morten >From: Carlos Sanchez <ca...@ap...> >To: Morten Kristiansen <mor...@ms...> >Subject: Re: Maven dashboard history plugin >Date: Mon, 7 Nov 2005 15:10:57 -0800 > >Hi, > >I'd like to know if you don't mind if I post it in the >maven-plugins.sf.net site so the other people can take a look at it. > >Regards > >On 11/7/05, Morten Kristiansen <mor...@ms...> wrote: > > Hi Carlos. Sorry for the late response. > > I haven't been working on the plugin for quite some time now, but we us= e >it > > daily in my current project. > > > > I have attached the plugin source for you. The site documentation is >still > > on my web: http://www.mortenkristiansen.net/maven-history-plugin/ > > > > Let me know if there is anything I can help you with! > > > > Morten > > > > > > > > >From: Carlos Sanchez <ca...@ap...> > > >To: mor...@ms... > > >Subject: Maven dashboard history plugin > > >Date: Thu, 13 Oct 2005 19:35:00 -0700 > > > > > >Hi Morten, > > > > > >I'm one of the maven developers and I'm interested in your dashboard > > >history plugin. Can you send me the sources? which license are they > > >under? > > > > > >I'm interested in unifying all those history plugins out there under > > >maven-plugins.sf.net, let me know if you're interested. > > > > > >Regards > > > > > >Carlos Sanchez > > > > > > > > |
