[jira] [Commented] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836956#comment-17836956 ] Richard N. Hillegas commented on DERBY-7162: Can you describe the problem you had when trying to build Derby locally? Maybe someone can advise you on how to get over that hurdle. > Update Git mirror for db-derby. Current mirror is out of date, hasn't been > updated since 2019 > - > > Key: DERBY-7162 > URL: https://issues.apache.org/jira/browse/DERBY-7162 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Bob Neugebauer >Priority: Major > > There is an existing GIT mirror for DB-DERBY available at > [https://github.com/apache/derby] however this mirror is out of date. Last > commit was Aug 2019. This mirror is missing all branches and tags that the > derby SVN repo contains. > I had opened an INFRA ticket INFRA-25623 to request an update to git but > Chris said this had to come from the derby maintainers. > I have a project that is using derby, in particular 10.17, and I am looking > for the best way to avoid having our build servers hit ASF frequently to pull > from SVN. Using a git fork would seem the best way to achieve this. > > Thanks, Bob -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836955#comment-17836955 ] Richard N. Hillegas commented on DERBY-7162: Linking this issue to DERBY-6645, a previous attempt to create a parallel maven-based build for Derby. If I remember correctly, that attempt foundered on the complexity of message-file generation. Maven-related discussion should be moved to DERBY-6645. I am happy to coach you through a follow-on mavenization effort there. > Update Git mirror for db-derby. Current mirror is out of date, hasn't been > updated since 2019 > - > > Key: DERBY-7162 > URL: https://issues.apache.org/jira/browse/DERBY-7162 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Bob Neugebauer >Priority: Major > > There is an existing GIT mirror for DB-DERBY available at > [https://github.com/apache/derby] however this mirror is out of date. Last > commit was Aug 2019. This mirror is missing all branches and tags that the > derby SVN repo contains. > I had opened an INFRA ticket INFRA-25623 to request an update to git but > Chris said this had to come from the derby maintainers. > I have a project that is using derby, in particular 10.17, and I am looking > for the best way to avoid having our build servers hit ASF frequently to pull > from SVN. Using a git fork would seem the best way to achieve this. > > Thanks, Bob -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836893#comment-17836893 ] Steinar Bang commented on DERBY-7162: - Please note: this isn't a complaint. Maybe a shout of despair, but not a complaint. I could live with subversion (though I don't understand it. I switched from subversion to git in 2010 and have never felt the urge to go back. Main reason is that branching and merging works. Branching is something I really, really, ,tried to do in subversion), but I would be really really happy if derby switched from ant to maven for the build. Right now the OSGi support of derby is thoroughly broken (the exported package(s) don't match the package names found in the class files, which don't match the class files directory structure in the jar files. Also different jars contain the same packages) and I looked into providing a patch/pull request. A pull request is out since derby doesn't use git. And a patch is out because I can't make derby build locally. I tried following [Using Eclipse to Build Derby|https://cwiki.apache.org/confluence/display/DERBY/BuildingDerby#BuildingDerby-UsingEclipsetoBuildDerby] but I couldn't get it to work on eclipse 2024-03 on java 17. There is both an ant build and a separate maven hierarchy (something I've never seen before in the time I've used maven) in the project but I have no idea which one is used.. I tried importing the maven project(s) into eclipse but that contained no source files. In my opinion: To make the maven build work right, heavy reorganization would be needed: java source should be moved down into the src/main/java directory of the projects. Also files should be moved into directories to match their package names. Also it would be really, really nice from an OSGi point of view if two jar files didn't contain the same packages. I could contribute to such a reorganization (but if it isn't something anybody wants there is no point spending time on it). > Update Git mirror for db-derby. Current mirror is out of date, hasn't been > updated since 2019 > - > > Key: DERBY-7162 > URL: https://issues.apache.org/jira/browse/DERBY-7162 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Bob Neugebauer >Priority: Major > > There is an existing GIT mirror for DB-DERBY available at > [https://github.com/apache/derby] however this mirror is out of date. Last > commit was Aug 2019. This mirror is missing all branches and tags that the > derby SVN repo contains. > I had opened an INFRA ticket INFRA-25623 to request an update to git but > Chris said this had to come from the derby maintainers. > I have a project that is using derby, in particular 10.17, and I am looking > for the best way to avoid having our build servers hit ASF frequently to pull > from SVN. Using a git fork would seem the best way to achieve this. > > Thanks, Bob -- This message was sent by Atlassian Jira (v8.20.10#820010)
