Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BeanShell 2.1.0 not on Maven Central #603

Open
garethhurley opened this issue Mar 26, 2021 · 24 comments
Open

BeanShell 2.1.0 not on Maven Central #603

garethhurley opened this issue Mar 26, 2021 · 24 comments
Assignees
@stain @nickl-

Comments

@garethhurley
Copy link

Hi,
The 2.1.0 release of BeanShell has not been published to Maven Central unlike previous releases. Is there a reason for this and could it be published?

In your README.md you say that:
'Beanshell releases are published to Maven Central.'

Note also that your link to Maven Central in the README is no longer valid and should be https://repo.maven.apache.org/maven2/ AFAIK.

Regards
@KroArtem
Copy link

I'm doubling the question. @pgiffuni , @Pilot-Pirx , @stain , isn't it possible to add new release to maven central? Some other libraries like maven-enforcer-plugin depend on an old 2.0b4 version.

@Pilot-Pirx
Copy link
Contributor

Sorry, I am not a maintainer of the code, just fixed some typos recently... ;-)

@jimjag
Copy link
Member

jimjag commented Apr 13, 2021 via email

@pgiffuni
Copy link
Member

Hmm.. either stainl or nickl can do that. I think it was discussed in the issue related to a next "inminnent" release ;)

@KroArtem
Copy link

KroArtem commented May 4, 2021

Any news here? Afaik beanshell is being used in a lot of projects (according to https://mvnrepository.com/artifact/org.beanshell/bsh/2.0b5/usages), previous beta-version has even more usages 🙀

@zhanghai
Copy link

zhanghai commented Jun 9, 2021

Bumping this as it has been another month - are there any updates?

@wilx
Copy link

wilx commented Jul 16, 2021

Ping.

KroArtem referenced this issue in apache/maven-enforcer Jul 16, 2021
@rfscholte
[MENFORCER-373] TestRequireOS uses hamcrest via transitive dependency
5788a00
@wilx
Copy link

wilx commented Jul 24, 2021

Can we involve someone who can fix this? This is a real bummer.

@nickl-
Copy link
Member

nickl- commented Nov 12, 2021

This is a duplicate issue, see #561 and as discussed there (and also spelled out on the project Readme):

Making of a new release is pending testing and resolution of the outstanding 200 odd issues that were imported from the sourceforge and google code projects.

The reason for holding back the release is to motivate the community to lend a hand and help work through the outstanding issues, or they will never be resolved. The original poster are not even the owners anymore as they were registered on the other platforms. This task is too big for the project team to resolve and we therefor urge the community to please take ownership of the outstanding issues and assist in getting them resolved.

So to the question who can make a release? It is not up to the team, but all up to you! The quicker we kill off all the outstanding issues, the sooner we can see release of Beanshell 3.0.

I must say, coming here to a duplicate issue created when the information you seek and the remedy is easily found, right on the project home page. Instead of rolling up sleeves and answering the call for assistance these users instead opt for nagging and entitlement. Shame on you, but that is not the worst part, imagine how you are motivating the team to pour more of their precious time and effort into such ungrateful and selfish attitudes. Makes me sick!

Closed: Duplicate

Best ship this foul tasting experience to /dev/null. I will not respond to further comments on this thread again, if you are keen to see a release you know what to do. See you on the outstanding issues, and we consider it a clean sheet.

@nickl- nickl- closed this as completed Nov 12, 2021
@nickl- nickl- mentioned this issue Nov 12, 2021
Closed
@wilx
Copy link

wilx commented Nov 12, 2021

@nickl- Dude... WTF? I suggest you calm down and read this thread again. Nobody here is asking for a perfect 3.0.0 release. Literally nobody in this thread. However, there is a tag and a record of a 2.1.0 release that has some incremental improvements and this 2.1.0 release is missing from Maven Central. That's it.

@peterkronenberg
Copy link

Any update on this? I know 3.0 isn't ready, but 2.1.0 still isn't on Maven Central

@nickl-
Copy link
Member

nickl- commented Dec 1, 2022

Release 2.1.0 was broken, happened before the fork merges and we cannot maintain that.

The only version we are maintaining is master branch version 3.0 and we will release that as soon as the outstanding issues are resolved. Please assist with the outstanding issues as they were ported from other repositories like sourceforge and therefor do not have owners anymore. It is up to the community to take ownership of the outstanding issues and assist us to get through them. The sooner they are done the sooner we'll have a release.

Thank you for your understanding.

P.S.
I have deleted the 2.1.0 release which was never published to Maven.

@wilx
Copy link

wilx commented Dec 1, 2022

We do not need a perfect release. We need non-regressing incremental improvement release that fixes vulnerabilities.

@jimjag
Copy link
Member

jimjag commented Dec 1, 2022 via email

@nickl-
Copy link
Member

nickl- commented Dec 1, 2022 •
edited

Reopened issue to look at new releases.

@nickl- nickl- reopened this Dec 1, 2022
@jimjag
Copy link
Member

jimjag commented Dec 1, 2022

Another option would be to review the Roadmap and maybe postpone/delay some future features for a later release. Let's assess the current 3.0.0-snapshot and see how it aligns with the roadmap and see what's in, what's out and what can wait.

Just my 2c ;)

@nickl-
Copy link
Member

nickl- commented Dec 1, 2022

v3.0.0 was ready for release but we needed a way to close the sourceforge issues. I also vote for a single release instead of maintaining two separate version trees.

There were some new issues that came up in the time being but they can be resolved within the next week or two allowing us time to wrap a Christmas bow around a release.

@jimjag
Copy link
Member

jimjag commented Dec 2, 2022 via email

@wilx
Copy link

wilx commented Dec 4, 2022

@jimjag Will 2.1.1 be released on Maven Central? I don't see it there.

@jimjag
Copy link
Member

jimjag commented Dec 4, 2022 via email

@nickl-
Copy link
Member

nickl- commented Dec 4, 2022

+1 for release

Just keep in mind there will be no further support on the 2.x branch we need to get 3.0 shipped.

@jimjag
Copy link
Member

jimjag commented Feb 8, 2023

Who can push the v2.1.1 artifacts to Maven Central??

@nickl-
Copy link
Member

nickl- commented Feb 9, 2023

Who can push the v2.1.1 artifacts to Maven Central??

I was under the impression you were going to do it, wasn't this why we organized Sonatype access for you?

@smmribeiro
Copy link

smmribeiro commented Mar 9, 2023 •
edited

@jimjag, @nickl-, @stain
Under OSSRH-86958, 'jimjag' was granted publishing permission for "org.beanshell" groupId.
This was December 2022... are there any predictions on when the 2.1.1 version could be made available thru Maven Central?
By the way, thank you for all the work on this project.

@opeongo opeongo mentioned this issue Oct 18, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stain stain

@nickl- nickl-

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests