Sorry for wrong addressing... The maven-checkstyle-plugin and dependency-check-maven CAN load the configuration from the file system. But when you do that, it's no longer possible to build only a sub-module, e.g. an example. That's the reason why these configuration in a Maven artifact. "It's just available".
Regards, Udo Am 12.04.18 um 10:12 schrieb Thomas Andraschko: > Hi Udo, you only sent it to me, now adding dev@myfaces. > > > What do you mean exactly? > This are just checkstyle files, which can be placed inside tobago itself. > e.g. > /myfaces-tobago/pom.xml > /myfaces-tobago/checkstyle.xml > > there is no need to give the checkstyle a own project, it coudl be just > a project file. > > > > 2018-04-12 10:08 GMT+02:00 Udo Schnurpfeil <lof...@apache.org > <mailto:lof...@apache.org>>: > > Hi Thomas, > > I've checked how to put the tobago-checkstyle stuff inside of > Tobago. The easy way (with 1 release cycle) will not work, because > in that case we will have cyclic dependencies. > > The other way would be: Having 2 release numbers and 2 releases. But > in that case we have no advantage. The number of releases and votes > are the same. > > We shouldn't mix the git migration too much with project refactoring. > > > What's about /keys and /myfaces-site-skins > <https://svn.apache.org/repos/asf/myfaces/myfaces-site-skins/>? > > > Regards, > > Udo > > > Am 12.04.18 um 09:50 schrieb Thomas Andraschko: >> We should really think about it we need to migrate >> myfaces-build-tools. >> The only active stuff maintained here is the checkstyle, we can be >> simply moved the projects. >> >> Extensions is also.... ExtVal and CODI are not maintained, only >> ExtScripting got a small update this year. >> >> >> >> 2018-04-12 8:47 GMT+02:00 Dennis Kieselhorst <d...@apache.org >> <mailto:d...@apache.org>>: >> >> Yes, everything is working. It's good idea to do the migration. >> >> As far as I can see we need the following repos: >> myfaces (for myfaces-core, already exists as old mirror >> https://github.com/apache/myfaces >> <https://github.com/apache/myfaces>) >> myfaces-master-pom >> myfaces-build-tools >> myfaces-extensions >> myfaces-test >> >> The other stuff has not been updated for over a year >> (http://svn.apache.org/viewvc/myfaces/?sortby=date >> <http://svn.apache.org/viewvc/myfaces/?sortby=date>) so looks >> like no need to migrate it?! >> >> Is anyone willing to do further cleanup? >> >> Regards >> Dennis >> >> On 2018/04/11 18:37:23, Thomas Andraschko >> <andraschko.tho...@gmail.com >> <mailto:andraschko.tho...@gmail.com>> wrote: >> > Is everything fine now for tobago and trinidad? >> > >> > +1 for migrating core now as 2.3.0 is out, maybe we have to >> wait for 2.3.1 >> > >> > we could also do a bit a cleanup and only migrate the active >> projects >> > We must also check e.g. the maven plugins and master poms... >> > E.g. we could remove the checkstyle files and move them to >> the tobago and >> > core itself instead maintain a projects which contains both... >> > >> > It think it would be the right momemt to do a cleanup now, >> to make it >> > easier to maintain in the future. >> > >> > >> > 2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst >> <d...@apache.org <mailto:d...@apache.org>>: >> > >> > > >> > > > https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ >> <https://svn.apache.org/repos/asf/myfaces/trinidad-maven/> has >> not been >> > > > migrated yet, I've requested a new repo for it. >> > > Migration of trinidad-maven is finished: >> > > https://github.com/apache/myfaces-trinidad-maven >> <https://github.com/apache/myfaces-trinidad-maven> or >> > > >> https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git >> <https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git> >> > > >> > >> >> > >