Re: [VOTE] Archiva release 2.2.3
+1. Looks good. Hadrian (non-binding) On 05/14/2017 08:44 PM, Olivier Lamy wrote: +1 Our instance has been updated https://archiva-repository.apache.org/archiva/index.html?request_lang=en Good job!! On 14 May 2017 at 02:10, Martin wrote: Hi, I dropped the 2.2.2 release because of some issues that popped up with the URL validation. But now these issues are fixed and the new 2.2.3 release is prepared. Parent pom changed, and Redback Core switched to 2.6. We fixed these issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12316920&version=12340517 The staging repository is available here: https://archiva-repository.apache.org/archiva/repository/ archiva-releases-stage/ Dist artifacts here: https://dist.apache.org/repos/dist/dev/archiva/ The documentation is available at: http://archiva.apache.org/docs/2.2.3/ Vote open for 72H [+1] [0] [-1] Greetings Martin Stockhammer
Re: Failed builds
Using a local instance of archiva as a proxy would speed downloads up significantly :). Hadrian On 10/23/2016 08:05 PM, Olivier Lamy wrote: well. Ideally that should be same plugin version in main build and archetype. As the archetype build try to resolve locally to avoid downloading everything again. But there is probably few versions mismatch. A solution is to not using local but download everything (this will make build longer) On 23 October 2016 at 19:56, Martin Stockhammer wrote: Hi, the builds are currently very unstable. The ubuntu-eu nodes seem to be different, so I excluded them in the build config. The archiva-master-empty-repo fails always at the "Archiva Consumers :: Consumers Archetype" module. And mainly because of dependency failures. The archetype pom.xml has some hard coded build dependencies, that do not match the versions used in the builds before. E.g. maven-compiler-plugin is used in version 3.5.1. So I'm not sure where these versions come from and if these should be changed to match the current build environment. Otherwise it may help to add a repository to the archetype pom.xml, because the archetype tests do only look in the local repository that is filled by the dependencies of the modules before. There is no lookup to the central maven repository. archiva/archiva-modules/archiva-base/archiva-consumers/archiva-consumer- archetype/src/main/resourcesstatic/archetype-resources/pom.xml org.apache.maven.plugins maven-clean-plugin 2.6.1 org.apache.maven.plugins maven-compiler-plugin 3.2 org.apache.maven.plugins maven-resources-plugin 2.7 org.apache.maven.plugins maven-jar-plugin 2.5 org.apache.maven.plugins maven-surefire-plugin 2.18.1 org.apache.maven.plugins maven-compiler-plugin 1.7 1.7
Re: Where to start?
Hi Martin, Olivier, I had good experience with jooq [1][2] which is not jpa and is imho easier to use. It's also ALv2, maybe something to consider? Hadrian [1] http://www.jooq.org/ [2] https://github.com/jOOQ/jOOQ On 09/18/2016 08:13 PM, Olivier Lamy wrote: Hi Martin, Where to start is always a good question :-) Regarding JPA it concerns only redback-core part as we do not use anymore database in archiva core. IMHO this one can be fun to implement (remember we cannot use library such hibernate because GPL but jpa has many other implementation even @ apache :-) ) Otherwise have a look at issues scheduled for 2.2.2 https://issues.apache.org/jira/browse/MRM/fixforversion/12335832/ HTH Olivier On 17 September 2016 at 22:56, Martin Stockhammer wrote: Hi, I looked at the JIRA tickets and think many of the are obsolete because they are very old or for different versions. I'm willing to help but currently do not know where to start. I'm currently trying to understand the codebase, but I'm a bit lost. I do not really know which parts are more historic , which important. If some of you know some specific issues that should be fixed and may be fixed without changing the complete codebase, please tell me or better give me the JIRA link. Or if there are some major tasks that are needed to bring the project forward, tell me. Olivier mentioned switching the persistence library to JPA is one thing that may be tried, because of some JDK incompatibilities with the current implementation. I will look at this, but it would be helpful, if someone can give some hints what components may be involved in such a change. I would like to keep the product stable working and I'm more interested in fixing bugs and improving the usability. I think major changes that break the build and does not produce a running product for a long time will be fatal for the project. Another question: The project page shows a lot of committers, are there any of them still active or is this list more like a gallery of ancestral committers? And who keeps the automatic build running? Greetings Martin
Re: Archiva to Attic? Asking contribution
Hi Olivier, Archiva is very much used. I personally believe that you're doing such a great job that it's become a bit of an expectation for you to fix everything :). I also believe that a bit of community development will reflect that. I got questions about Archiva in the recent past. Let me dig into my emails and see if I could help you with raising awareness about the project. We could talk about it in Sevilla if you (or others interested) show up. Cheers, Hadrian On 09/06/2016 06:57 AM, Olivier Lamy wrote: Hi everyone, I'm a bit sad to say I don't have anymore a lot of time to contribute to the project. We have a very limited number of contributor. So we ask if you are interested to help/contribute to the project. Otherwise we will have to move the project to the Attic land [1] Let us know if you are interested! Cheers
