0

What is intended is to give everyone access to the source code but to restrict what they modify.

So what first came to mind is if there's any way to, when building the plugin/project, some sort of restriction is applied to the files that have been modified and if some unnauthorized modifications have been made the build fails.

An example would be that only some users may modify the java files, but all users can modify XML configurations and build the jar.

Or if this isn't possible what alternative do I have to restrict source code modifications?

CMPSoares
  • 4,175
  • 3
  • 24
  • 42
  • To be honest this does not make sense...You should have a limited group of people who are allowed to change the code incl. configuration...The question is of what kind of configuration we are talking about? Furthermore i would suggest to use a CI solution where jars will be build and not on a dev machine... – khmarbaise Nov 12 '15 at 14:24

1 Answers1

1

Don't do this in maven, do this in your version control system.

Either use one where you can give different levels of access to different users or just use the fact that it's a version control system and if anyone makes changes they shouldn't roll the changes back out and tell them not to do it again.

Tim B
  • 40,716
  • 16
  • 83
  • 128
  • I'm using SVN at the moment and rolling changes back has beaurocratic implications as the application is used by a wide range of teams and verify if they add a java file to the compiled .jar is dificult. – CMPSoares Nov 12 '15 at 12:45
  • Try something like this then: http://stackoverflow.com/questions/6091743/svn-how-to-restrict-user-access-to-certain-folders – Tim B Nov 12 '15 at 12:52