Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/23
Not merged, gave up.
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
Github user cstamas closed the pull request at:
https://github.com/apache/maven-indexer/pull/23
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/23
Full codebase reformat, minor cleanup, no code/logic change
Reformatted full codebase, as there was mixed formatting, and
checkstyle did report a huge amount of errors. Now, mostly the
Github user cstamas closed the pull request at:
https://github.com/apache/maven-indexer/pull/21
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/21
Manually merged, only 1st two commits from this PR, while 3rd commit pulled
out and merged separately
(https://github.com/apache/maven-indexer/commit/339eec6052a74fea91a99da2e33cbbd6a95aee3f
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/22
MINDEXER-108: Lift the wildcard prefix restriction
MINDEXER-108: lift the prefix restriction
Historically Lucene needed this, but latest versions
can cope with it. This is still OOM
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/19
@scela
With this PR against current master I have this result:
```
Tests run: 220, Failures: 3, Errors: 199, Skipped: 0
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/21
Prepare for next major release (6.x)
Changes:
- update parent pom
- update dependencies (but remain Java7!)
- update sisu (drop sonatype guice, use vanilla guice)
- update to
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/17
@olamy @scela sounds fine to me
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/16
@sesuncedu could you please close this PR out?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/12
@tstupka could you please close this PR out?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/15
@sesuncedu could you please close this PR out?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/14
@sesuncedu could you please close this PR out?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/13
@sesuncedu could you please close this PR out?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/13
I'd leave maven-indexer-5.x branch as is, everything is on master now.
Sorry for the squashes, but I did not want to fiddle with "arrival times".
All the commit
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/12
Manually merged/squashed as
532ea64eecd499d047bf4211b6a5bde41f1a7c72
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/16
Manually merged/squash as
0ee33793657d37b5475e8b57c97af9ce1358f553
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/15
Manually merged/squashed as
ceb8388e9ca6766877f57901054861bbb713f35f
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/14
Seems I have no perms to manage GH mirror, so cannot close this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/14
Manually merged/squashed as
6cb2fcbe47883cd0decac0295493bef6577d7eb4
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user cstamas commented on the pull request:
https://github.com/apache/maven-indexer/pull/10#issuecomment-94748095
@Enygma2002 sure, sorry for the delay, will apply it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user cstamas commented on the pull request:
https://github.com/apache/maven-indexer/pull/10#issuecomment-69743397
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user cstamas commented on the pull request:
https://github.com/apache/maven-indexer/pull/11#issuecomment-69743162
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/5
WIP Multiple fixes "sixpack"
Multiple fixes:
MINDEXER-84 updater bug
MINDEXER-85 POM reading
MINDEXER-86 legacy transport format removed
MINDEXER-41 unique by GAVCE f
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/2
MINDEXER-77: Update to latest Lucene
Based on work in JIRA issue comments. Thanks
Issue
http://jira.codehaus.org/browse/MINDEXER-77
You can merge this pull request into a Git
Github user cstamas commented on the pull request:
https://github.com/apache/maven-indexer/pull/1#issuecomment-47425580
Merged as 028aef5afe89f6e7976cc24fa240e6d5e2ae35fd
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user cstamas commented on the pull request:
https://github.com/apache/maven/pull/18#issuecomment-45644872
FTR, Manually merged as 18964baa25e9c071d13186e4c03e3957b9381961
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user cstamas closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/6
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user cstamas commented on the pull request:
https://github.com/apache/maven/pull/18#issuecomment-44840750
New IT added
https://github.com/apache/maven-integration-testing/pull/6
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-integration-testing/pull/6
MNG-5640: IT that verifies that lifecycle participant afterSessionEnd is
invoked even with build failure
IT based on Igor's MNG-5389, with addition of a failing UT.
Github user cstamas commented on the pull request:
https://github.com/apache/maven/pull/18#issuecomment-44824659
ITs passed on this PR :+1:
https://gist.github.com/cstamas/5873e5413da65a5258c5
---
If your project is set up for it, you can reply to this email and have your
Github user cstamas commented on the pull request:
https://github.com/apache/maven/pull/18#issuecomment-44653198
Done
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
GitHub user cstamas opened a pull request:
https://github.com/apache/maven/pull/18
[MNG-5640] Change order to make sure participants are called
Even in case of failing build. As currently, in case of failed build
(`session.getResult().hasExceptions()` return `true`), return
Github user cstamas closed the pull request at:
https://github.com/apache/maven/pull/10
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user cstamas closed the pull request at:
https://github.com/apache/maven/pull/9
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
GitHub user cstamas opened a pull request:
https://github.com/apache/maven/pull/10
Upgrade to Eclipse Aether 0.9.0.M3
No code change, just a bit of dependency reshuffling
due to module changes in Aether itself.
You can merge this pull request into a Git repository by running
GitHub user cstamas opened a pull request:
https://github.com/apache/maven/pull/9
[MNG-5513] Artifact filtering not updated for Eclipse Aether filtering
Artifact filtering was not updated when Aether swapped from Sonatype to
Eclipse, causing it to be loaded by Plugin Class Realms
37 matches
Mail list logo
