Hi Olivier,
do you know what's the problem with the archiva VM instance?
https://archiva-repository.apache.org
It shows: 503 - Service down for maintenance
Kind Regards
Martin
index directory for each
test.
I think several failed tests on windows are caused by the open index
files, but I don't have a better solution than using unique directories
for these tests.
Regards
Martin
On 24.02.20 18:01, Martin Stockhammer wrote:
Hi Eric,
the maven indexer uses
.
Error during recursive delete of
E:\jj\workspace\a\archiva-modules\archiva-maven\archiva-maven-indexer\target\repositories\test-repo\.index-test
Maybe insuring each test on his own repo can be a solution
Best Regards
Eric
De : Martin Stockhammer
Envoyé : jeudi 20
ss to file, used by another processus
>
>Regards
>Eric
>
>-Message d'origine-
>De : Martin Stockhammer
>Envoyé : vendredi 14 février 2020 08:37
>À : dev@archiva.apache.org
>Objet : Re: Test fails( on Windows)
>
>Hi Eric,
>
>sorry, I missed y
Hi Eric,
sorry, I missed your last mail about the filelock issue. I will check
the PR today.
Regards
Martin
On 14.02.20 01:09, Eric Barboni wrote:
Hi,
Jumping late in the conversation for the failing test on windows.
Hi Frederick,
what ldap server do you use? Is it active directory or any other type?
How are the members stored in the group? Is it using 'member' attribute on the
group object? Are the member entries the full DN of the members?
Do you see errors in the logs?
Regards
Martin
Am 17. Januar
Hi together,
during dependency cleanup of archiva and redback I came to the
conclusion that I would like to consolidate the redback-components
projects. I know that these are mostly independent modules, but they use
the same site configuration and the same parent and it would make them
much
Yeah, that's what I hoped. Saves me some headaches
Regards
Martin
Am 8. Oktober 2019 02:27:59 MESZ schrieb Olivier Lamy :
>Hi
>We can definitely get rid of code converting repo 1.x to repo 2.x :)
>
>
>On Sat, 5 Oct 2019 at 23:12, Martin wrote:
>
>> Hi,
>>
>> while trying to cleanup the
Hi Joel,
great to hear. You should start with a checkout from the GitHub repository.
And provide your contribution via pull request. The PR should be related to a
jira issue.
If you have questions about getting the build environment to work, this list is
the right place.
Regards
Martin
Hi Joseph,
better to start with a clone of the repository on GitHub. Use the 2.x branch.
mvn clean install
is the right thing to do. And then send us the mvn output, if there are errors.
You need access to the internet for building archiva.
Regards
Martin
Am 23. Juli 2019 03:37:08 MESZ
martin_s
Regards
Martin
Am 22. März 2019 01:47:32 MEZ schrieb Olivier Lamy :
>Hi Martin
>I just tested and I was able to login.
>What is your username?
>cheers
>Olivier
>
>On Fri, 22 Mar 2019 at 04:23, Martin Stockhammer
>wrote:
>
>> Hi Olivier,
>>
Hi Olivier,
I would like to prepare the release. For this I tried to login to the archiva
repo server https://archiva-repository.apache.org to recreate the staging
repository.
But the login hangs. Form is waiting infinitely for some response.
Can you please have a look.
Thanks
Martin
--
Hi together,
I'm preparing a new release for the archiva-2.x branch. If everything goes well
it will be 2.2.4.
It's a bugfix release which just releases the commits in this branch since the
last release.
If you have (minor) changes that should be included, or concerns, please tell
me.
If
Hi Ovidiu,
the project is still under development, but slow progress at the time, because
of the limited resources.
If you would like to contribute, it's best to start with a PR.
The master branch is development for the new version 3.0, and there is a lot of
refactoring going on.
For bugfixes
at
>Jenkins
>master is successful.
>
>Much appreciated for your help,
>- Alex
>
>
>On Mon, Dec 10, 2018 at 5:13 AM Martin Stockhammer
>
>wrote:
>
>> Hi,
>>
>> did you run mvn clean before?
>> Sometimes there are files not cleaned up correctly. You c
Hi together,
after my last request about the status on the JIRA ticket, the
infrastructure guys changed the publish process from svn to git publish
without further asking.
So I will not ask for any votes, just raise your hand, if you have still
concerns about it.
I checked the publish
Hi,
did you run mvn clean before?
Sometimes there are files not cleaned up correctly. You can use the script
src/main/ci/cleanupWorkspace.sh which is used by our build on the ci server.
Regards
Martin
Am 10. Dezember 2018 01:26:22 MEZ schrieb Alexandru Zbarcea
:
>Hi,
>
>Any advice for
Hi Olivier,
not sure, if I understand you correctly. This repo is just another source repo
for the redback content site.xml and page sources.
I oversaw it during the git migration.
The repo with the content data (archiva + redback) is archiva-web-content.git .
Every mvn site publish has to
Hi Olivier,
we are using maven-indexer-core 6.0.0 shaded_lucene
But it seems there are duplicate classes with maven-resolver.
The whole org.eclipse.aether package is part of maven-resolver now. Is it
possible to remove this package from indexer-core?
Regards
Martin
--
This message was
Hi Olivier,
yes. I opened a infra ticket months ago about moving from svnpubsub to
gitpubsub. But hadn't the time to convert the repo and checking the final size.
I think the size is manageable and after that, we have all our repos on git
then.
Regards
Martin
Am 2. November 2018 05:20:45
commit 24ee701d1daee202e799b5ca17f9dff19d398c6e
>> Author: Martin Stockhammer
>> AuthorDate: Fri Oct 26 22:23:45 2018 +0200
>>
>> Changing aether dependencies from sonatype to eclipse. Compile
>OK.
>> ---
>> .../artifact/LegacyToD
about the webui tests:
Parallel might be the wrong term. I would like to run these tests more or less
indepentently that does not affect the normal build job of archiva if it fails.
Currently its a separate job with its own configuration and report.
I cannot have multiple jenkinsfiles in a
65
>> URL: https://issues.apache.org/jira/browse/MRM-1965
>> Project: Archiva
>> Issue Type: Question
>> Components: Maven 2 Support
>>Reporter: Giuliano diego barbarra
>>Assignee: Martin Stockhammer
>
Hi Olivier,
I added retries to the unit tests of the metadata stores. This is needed
because the jcr oak index updates are asynchronous (and theoretically should
update in near real-time but that's not fast enough for the unit tests) . I'm
not sure if we get problems with the asynchronous
ecting users to be able to configure this via ui (i.e
>dynamically) not only via spring so the comment.
>But never got time to finish that :-)
>
>
>On 29 August 2017 at 01:59, Martin Stockhammer <marti...@apache.org>
>wrote:
>
>> Hi,
>>
>> I stumbled about s
Hi,
I stumbled about some fixme comments on RepositorySessionFactory injection
fields:
FIXME: this could be multiple implementations and needs to be configured.
Are these still relevant? As I understand there is a
RepositorySessionFactoryBean that selects the factory based on configuration.
ions: 2.2.3
> Environment: CentOS 7, Docker 17.0.6
> Reporter: Gregory Zyrek
>Assignee: Martin Stockhammer
>Priority: Minor
> Labels: CI, beginner, features, github-import, newbie
> Attachments: archiva_bug.p
dexer.git;a=summary
>> > and I pushed what I started for Archiva in the branch called
>> feature/jcr_oak
>> > So in order to test it you need to build first maven-indexer from
>the
>> > branch feature/jar_shaded_lucene
>> >
>> > On 6 July 2017
Hi,
the ticket is for archiva version 1.0.2 which is not maintained anymore. Which
archiva version do you use?
Greetings
Martin
Am 12. Juli 2017 11:36:00 MESZ schrieb "Bruno Cros (JIRA)" :
>
>[
We have different lucene (incompatible) dependencies that prevents us to update
the maven indexer and/or jackrabbit. And this will happen again with each
upgrade from one of these two packages in the future.
So would be really good if we can find a solution that removes one of the
lucene
. Juni 2017 07:46:07 MESZ schrieb Olivier Lamy <ol...@apache.org>:
>Maybe we should rewrite the configuration as it's a mix of legacy
>properties xml etc...
>I guess it's not really clear :-)
>Maybe for 3.0.0?
>
>On 1 June 2017 at 15:20, Martin Stockhammer <marti...@
Hi Olivier,
I think I have fixed the configuration issue. And modified the header checks.
You should be able to add a comma separated list for the rest.baseUrl param.
Could you please check with the latest source. The Jenkins builds currently
fail, because there seems something wrong with the
idationInterceptor
>[] - HTTP Header check failed. Assuming CSRF attack.
>
>
>Well I can disable that but I'd like to not have too many users
>complaining
>:-)
>
>On 25 April 2017 at 16:54, Martin Stockhammer <marti...@apache.org>
>wrote:
>
>> Hi,
>>
>>
Hi Olivier,
and another question regarding this:
To reorganize the JIRA issues, could you please add a 3.0 version to the JIRA
project.
And I think it makes sense to add a 3.1 version to move the unresolved issues,
that are tagged with the 2.3 version.
Greetings
Martin
Am Samstag, 18. März
Hi,
seems OK for me. I'm on vacation this week. I will prepare the branch next week.
Greetings
Martin
Am 1. Januar 2017 09:23:18 MEZ schrieb Olivier Lamy :
>Hi Martin,
>Great effort!!
>So I did more cleanup on redback-core jpa branch :-)
>Why not bump the version to 3.x and
Hi,
currently the built packages cannot be uploaded to the repository server.
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could
not transfer artifact
org.apache.archiva:archiva-jetty:tar.gz:bin:2.2.2-20161027.220655-19
from/to archiva-repository.snapshots
Ok, I will try to find out, but have to put it to the working queue. I will
open a ticket as reminder.
Martin
Am 20. Oktober 2016 04:06:34 MESZ, schrieb Olivier Lamy :
>Hi Martin
>I think archiva-proxy is/was dependent on maven2-repository.
>But I'm not sure as maybe it's not
Ok, I got it. It was hidden in pom dependencies.
The dependencies for the redback-users provider implementations are hidden
deeper in the dependency tree (e.g. redback-users-jdo is a dependency in
redback-rbac-cached).
I put the jpa modules into the redback-core pom as dependency, but not
not asking anything to
the user
On Wednesday, 21 September 2016, Martin Stockhammer <m.stockham...@web.de>
wrote:
> Hi,
>
> I looked at the code and started to create the new modules. I think
> openjpa is the right thing. The database model created by jpox is not
> ve
ng 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
ment (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/12
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
Hi,
the last attempt showed errors, that userjdo class cannot be persisted,
because the class contained no persistence methods. I think that's because the
persistence library does some bytecode enhancement and either this does not
work in my IDE or the class path for unit test run is not
Hi Olivier,
I like archiva, because it's simple and lightweight comparing to nexus and
artifactory.
It has some advantages to the other two main repository implementations:
- You can deploy it on any application server (e.g. we use it on WebSphere)
- it does not claim to be a "multipurpose all
44 matches
Mail list logo