Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
As mentioned for MINDEXER-102, I'm leaving this PR temporarily open, so I
can file JIRA issue on why it wasn't auto-closed.
---
If your project is set up for it, you can reply to this
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 sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
@cstamas Squashbasing gives the cleanest trees. Just make sure to give
yourself credit for the commits of yours that were cherry-picked.
index-reader should be identical for both
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 origins are on
Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
I have changed the package version for the indexer to 5.2.0 because there
are minor changes from prior 5.1.2.SNAPSHOT versions. The overall 5.x release
version might want to skip to 5.1.3
Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
Also, if I do forward port, should I also try and forward port
index-reader?
And, if you are thinking of releasing 5.1.2, would you like me to do a more
detailed job of bundle
Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
Also, OSGI headers really need a custom analyzer, as they have their own
nested organization and datatyping. It doesn't seem worth it for this change,
but would be worth it for the next
Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
I have been consistently confused about which branch is live, so it would
not surprise me either way âºï¸.
I had been working against main on some code to use the central index to
Github user carlspring commented on the issue:
https://github.com/apache/maven-indexer/pull/13
Hi,
Shouldn't this be applied to the `master` branch and be included in `6.0`
instead?
@cstamas : What do you think?
Cheers,
Martin
Github user balazs-zsoldos commented on the issue:
https://github.com/apache/maven-indexer/pull/13
+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
enabled and wishes so, or
10 matches
Mail list logo
