Timeline for Best way to structure a Git repository for Maven
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 24, 2022 at 19:16 | comment | added | cptully | @JonathanS.Fisher perhaps you could elaborate on your comment in a full answer? I would love to see your thoughts. | |
| Mar 30, 2018 at 11:53 | comment | added | Hosein Aqajani | Dear @parsifal please have a sight at my question about creating java multi layer app stackoverflow.com/questions/49562268/… | |
| May 20, 2013 at 14:05 | comment | added | Jonathan S. Fisher | I'm intimately familiar with how maven works. And no, I don't want my teams building the entire codebase. Typically you would select a small number of projects and pull them out of source control. We have a nexus server to host finished artifacts, so there is no reason to build the entire codebase. And once your organization is a certain size, running on shared infrastructure saves money. Having a central configuration to do that is the only way to make sure that works, every time. | |
| May 20, 2013 at 13:02 | history | answered | parsifal | CC BY-SA 3.0 |