Le jeudi 20 juin 2013 21:50:06 Robert Scholte a écrit : > If the intention for this plugin is to let run standalone on a CI-Server, > then that's good enough for me. > The plugin doesn't use org.apache.maven.plugins as groupId, so it'll be a > bit harder to be found by the general user, which is good. > > I can image that this tool could be interesting for any large project with > staging. So some parts need to be more generic. yes, it is written in the "About" page as "Notice that this plugin is actually intended for Maven itself only: if interest is expressed to use it in other context, it would require more configurations."
but we kept the tool intentionally as simple as possible for the moment: KISS > With less hardcoded values it is also easier to make proper tests. yes, and should be simpler than making the tool usable outside Maven project Regards, Hervé > > Robert > > Op Thu, 20 Jun 2013 10:54:46 +0200 schreef Eric Barboni <sk...@apache.org>: > > Well, I'm late Hervé answered before me. > > > > Of course you can improve the "plugin" which we should maybe rename to > > avoid > > confusion with end user maven plugin. > > > > A todo.md file is available to add RFE that needs a couple of days (my > > definition :p) . Idea was to not overwhelm Hervé (or any other maven > > dev). > > > > Thanks you for the IT settings. > > > > Regards, > > > > Eric - skygo > > > > PS: > > FYI the JDK version choice > > > > (on a feature point ) try with resource feature + new javadoc style. > > > > As a lecturer in HCI field, when you ask student to get java (oracle > > > > version) they found jdk 7, jdk 6 is shown as end of life (with security > > warning everywhere). > > > > Side effect is that, you play with the new features. (student later > > > > learn backward compatibility) > > > > > > -----Message d'origine----- > > De : Hervé BOUTEMY [mailto:herve.bout...@free.fr] > > Envoyé : jeudi 20 juin 2013 07:19 > > À : Maven Developers List > > Objet : Re: dist tooling > > > > this is not a plugin for end users, only for internal Maven team: and > > once > > it is scheduled daily on our Jenkins server, i don't expect us to run it > > on > > our personal machines > > > > so I don't think JDK7 nor Maven version requirements are a problem. > > > > ITs would be nice, yes, to be sure things are detected even when we fix > > errors actually reported > > > > Regards, > > > > Hervé > > > > Le mercredi 19 juin 2013 23:22:13 Robert Scholte a écrit : > >> Hi, > >> > >> I noticed there are no IT's. It shouldn't be too hard to write that. I > >> can make a setup for that in order to be able to execute some ITs > >> > >> Although most of us want to use the latest and greatest, I have my > >> doubts about using JDK7 and M3.0.4 for compilation. Since our advice > >> is to compile with lowest required versions, I think we should aim for > >> JDK5 and M3.0, unless there's a very, very good reason not to. > >> > >> I see some other improvements, put I'll pick these up myself. Should > >> be easy to verify once I've got the ITs running. > >> > >> Robert > >> > >> Op Wed, 19 Jun 2013 21:42:33 +0200 schreef Robert Scholte > >> > >> <rfscho...@apache.org>: > >> > I'd like to have a look at it too. > >> > Give me a couple of days. > >> > > >> > Robert > >> > > >> > Op Wed, 19 Jun 2013 00:11:55 +0200 schreef Hervé BOUTEMY > >> > > >> > <herve.bout...@free.fr>: > >> >> Thanks to Eric, we now have a tool to check dist content > >> >> > >> >> And I just added it to our Jenkins instance, to build once a day: > >> >> you can look at the result [1] I just had to remove the preview of > >> >> site, since Firefox isn't available on the CI server (or not able > >> >> to start in headless mode) > >> >> > >> >> Any feedback? > >> >> > >> >> Regards, > >> >> > >> >> Hervé > >> >> > >> >> > >> >> [1] > >> >> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/ > >> >> ws/tar > >> >> get/site/index.html > >> >> > >> >> ------------------------------------------------------------------- > >> >> -- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For > >> >> additional commands, e-mail: dev-h...@maven.apache.org > >> > > >> > -------------------------------------------------------------------- > >> > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For > >> > additional commands, e-mail: dev-h...@maven.apache.org > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For > >> additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional > > commands, e-mail: dev-h...@maven.apache.org > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org