> > > the question is: how to start? should i look at a kind of meta-scm > plugin or > > rather directly enhance the existing scm plugins? > > any input is welcome! > > I've read your message twice and it still isn't clear to me what > you're trying to accomplish. Can you provide a use case for how this > enhancement would be exploited? Would it echo m-eclipse-p > functionality? > > http://maven.apache.org/plugins/maven-eclipse-plugin/ >
thanks for your response. for those not familiar with psf files: eclipse .psf files are xml formatted files which contain a list of plugins and their scm type/origin - basically a description of which plugins belong into an eclipse workspace and where they are checked out from. i would like to extend the job configuration "source code management" section with the possibility to specify such a psf file instead of manually entering all the, for example, subversion modules. this would be very useful for our situation here where the scm repository layout (hierarchical) does not correspond to the eclipse workspace layout (flat) needed for the (pde) build. of course, one workaround would be using symlinks on *nix, but on windows platforms there is only a very expensive copy/move operation as alternative. i just stumbled over the "multiple scm" plugin and i think it could make sense to extend it with a psf input line whose content is then translated into checkout calls for the various "real" scm plugins. will look into that. cheers, simon > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. >
