Comments (7)
Hello @tjaskula, couldn't you just move all projects into a single repo ? then building and publishing multiple dependent nuget packages from a mono repo is just brain dead simple ...
from xoom-net-platform.
@jrouaix no, it's not the goal.
from xoom-net-platform.
@tjaskula I have a few questions to get this straight.
- The idea is to generate a *.sln with *.csproj files where no nuget vlingo dependencies are used. csproj all reference each other.
- When generating sln and csproj files, we need to specify if the libraries should be pulled from github repositories or local github repositories, branches and forms? This way we can configure the generator and use Git library to get the files.
- What do you mean by pushing the code? For example, you can edit the actor library from the plaftform solution and you want to push the files back to local /remote library repository?
Current PR suggests the use of Nuke builder and git submodules. This looks promising but needs further investigation.
from xoom-net-platform.
@jrouaix no, it's not the goal.
@tjaskula, sorry to bother, but again, I think you try to tackle a problem you just shouldn't have.
A monorepo will fix all your "goals":
- an all in one solution
- working with forks
- having nuget dependencies when publishing nugets while having project references while working on the code.
Only if you plan to be able to "version bump" projects independently .. perhaps is this the goal you wanna achieve ? otherwise I don't see it. Could you explain the goal of all this ?
from xoom-net-platform.
Perhaps @VaughnVernon ? you have an idea about the "why" behind all this ?
Is this to be aligned with the java practices ? having some kind of 1<=>1 bijection between the implementations ?
from xoom-net-platform.
@jrouaix I don't have strong opinions on this and the simpler the better. However, we have found in the Java platform that nested/submodule repos don't work out well. This has a lot to do with out CI/CD toolchain. (Currently our CI is not the greatest, but it works. We will improve this.) For example from Travis-CI to Bintray and Bintray to release repositories Sonatype and Maven Central the multiple artifacts per git repo causes big problems.
Another concern is that once you start moving things around and into one repo you lose all history. I have tried to retain history and several have claimed that it can be done, but IMO it really cannot.
from xoom-net-platform.
@jrouaix We need to release them independently and version independently
from xoom-net-platform.
Related Issues (1)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from xoom-net-platform.