Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-09 Thread via GitHub
epugh commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2580490017 Thanks @dsmiley ...I guess I was thinking as developer of Solr versus a user of Solr! And Changes.txt is meant for the user primarily! -- This is an automated message from the Apache G

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-08 Thread via GitHub
dsmiley commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2579179289 I'm going to move the CHANGES.txt entry from "Bug fix" into the "Other" category because Solr itself does not have a bug. Also note the Lucene project uses "GITHUB#1234" pattern; we mi

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-08 Thread via GitHub
epugh commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2578193783 Thanks for the contribution @tylerbertrand! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-08 Thread via GitHub
epugh merged PR #2680: URL: https://github.com/apache/solr/pull/2680 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-07 Thread via GitHub
tylerbertrand commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2575726167 Hi @janhoy and @epugh, the conflicts have been resolved -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-03 Thread via GitHub
tylerbertrand commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2569431235 @janhoy Sure, sounds good -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific c

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-03 Thread via GitHub
epugh commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2569244408 thanks for reminding us @janhoy -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific co

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2025-01-03 Thread via GitHub
janhoy commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2569162075 @tylerbertrand Will you resolve the conflicts, then me or @epugh will get it merged? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2024-12-28 Thread via GitHub
github-actions[bot] closed pull request #2680: Use separate nodeProjectDir for each subproject URL: https://github.com/apache/solr/pull/2680 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the speci

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2024-12-28 Thread via GitHub
github-actions[bot] commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2564560956 This PR is now closed due to 60 days of inactivity after being marked as stale. Re-opening this PR is still possible, in which case it will be marked as active again. -- This

Re: [PR] Use separate nodeProjectDir for each subproject [solr]

2024-10-29 Thread via GitHub
github-actions[bot] commented on PR #2680: URL: https://github.com/apache/solr/pull/2680#issuecomment-2445536283 This PR has had no activity for 60 days and is now labeled as stale. Any new activity will remove the stale label. To attract more reviewers, please tag people who might be fam