Hi, I just realised why the git repo approach does not work for me and maybe other developers.
I'm using Intellij Idea and, in contrast with Eclipse, Intellij cannot open multiple projects into the same window. I'm not sure how other developers go around this but it makes working on multiple project a bit of a pain, at least for me. I have to open a lot of windows and manage them independently. This kind of breaks my flow. Having an aggregator project that allows me to see all related projects together will easy this task. Regards, [1] https://intellij-support.jetbrains.com/hc/en-us/community/posts/206326369-How-to-have-multiple-projects-in-same-window- On 15.06.2018 12:35, Ioan Eugen Stan wrote: > Hello Oliver, > > On 15.06.2018 10:51, Oliver Lietz wrote: >> On Thursday 14 June 2018 12:30:48 Ioan Eugen Stan wrote: >>> Hello, >> Hi, >> >>> I've made some PR's for Sling Karaf related projects and I would like to >>> ask for review/merge. Developing on top of Sling Started project is not >>> the best experience and since I've learned more about Sling internals I >>> decided to improve Karaf. >>> >>> I would like to share my way of handling karaf related packages for easy >>> development - it might be useful for other situations. >>> >>> The problem that it solves for me is: >>> >>> - Sling has a lot of repositories that keep each component in it's own >>> repo. This is great for modularity and having a different version + >>> history for that module however I have found it is not the best thing >>> when you need to iterate fast and have it easy to build related packages. >>> >>> My solution is to rely on git submodules and create an aggregator >>> repository/project that adds and manages the related projects. >>> >>> For something like Sling Karaf projects, it fits very nicely. I believe >>> it might be good for other situations in Sling eco-system. >>> >>> I have pushed this setup here [1]. >> our current solution is Google's repo. You can set up your own set of >> modules >> easily. For Sling Karaf see https://github.com/oliverlietz/sling-karaf-repo > Thank you for the feedback. I will check git-repo as it seems to be > another solution to the problem of managing multiple git repositories. > > We kind of have the same problem internally but so far we managed with > sub-modules. > >>> Also the PR's are available here [2] [3] and [4] . >>> >>> I've seen that there is another PR that needs some TLC by Christian >>> Schneider. I would like to help out with Karaf maintenance - it seems it >>> could use some help. I would love to be able to do that as part of Sling >>> project. >> Your PRs are rather large and touch different scopes. Please be more focused >> and start a discussion on dev first or add issues to JIRA whenever an issue >> is >> not just a typo or javadoc fix. > Yes, they where kind of done in a hurry and more to fix my itch. I also > saw that there is currently no release of sling karaf so I hoped that > the requirements can be more relaxed until an intial version is pushed. > > I will come back over the next weeks with more refined PR's. Regarding > the configfile issue - I've noticed that files referenced with `config` > are not packaged with karaf custom distribution - and not available > offline - so I have changed to configfile. After reading about the > issues in [1] I think a better (slower) approach is to adress this with > Karaf and file a bug/issue there. > > > Thanks, > > [1] > https://issues.apache.org/jira/browse/KARAF-4829?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=15948530#comment-15948530 >> Thanks, >> O. >> >>> Thanks, >>> >>> Eugen >>> >>> >>> [1] https://github.com/netdava/sling-org-apache-sling-karaf >>> >>> [2] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/2 >>> >>> [3] >>> https://github.com/apache/sling-org-apache-sling-karaf-distribution/pull/1 >>> >>> [4] https://github.com/apache/sling-org-apache-sling-karaf-configs/pull/1 >>> >>> [5] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/1 >
signature.asc
Description: OpenPGP digital signature
