search

beanshell / beanshell

Beanshell scripting language
Apache License 2.0
815 stars 183 forks source link

Please publish bsh-2.1.1 in mvnrepository so it can be easily used in projects #739

Open bugla opened 1 year ago

bugla commented 1 year ago

Please publish bsh-2.1.1 in https://mvnrepository.com/artifact/org.apache-extras.beanshell/bsh so it can be easily used in projects.

bsh-2.1.1 contains important fixes and updates compared to the latest version published there (2.0b6) and it would help a lot fixing software using bsh, if it can be used as a normal gradle / maven dependency as before.

Thank you!

bugla commented 11 months ago

Is there any chance this happens any time soon?

bugla commented 10 months ago

It would be really lovely, if someone who has the necessary rights and permissions could take ~1/2h and publish this to mvnrepository.com so that it doesn't block other projects. PLEASE!

rob-X1 commented 7 months ago

@opeongo @nickl- Do you see a possibility to publish beanshell 2.1.1 on Maven central? Because at the moment the project is unusable, even using jitpack.io it is not possible to use beanshell in a Maven or Gradle project if you want a version later than 2.0b6.

Jar releases on Github are useful if the release is a program, for Java libraries including them in a project is not really useful...

opeongo commented 7 months ago

Duplicate of #603

Hi @rob-X1, @bugla

Please read the issue #603 for details about what was going on with the release of beanshell 2.1.1

The summary is that it requires someone with credentials for Maven Central to make this update. It appears that @jimjag has this authority https://github.com/beanshell/beanshell/issues/603#issuecomment-1461671297 but the update has not been made yet. I do not have Maven credentials so there is nothing that I can do about this. Sorry that I cannot help with this, it seems to be the nature of older, poorly supported open source projects :(

Also note that @nickl- has said that beanshell 2 will not be supported going forward https://github.com/beanshell/beanshell/issues/603#issuecomment-1336535814 . This makes sense from the pov of beanshell 3 because it is confusing to have issues about the old version being discussed within the project for the new version. So the opportunity to discuss beanshell 2 within this particular forum is just about over.

If people are interested in keeping beanshell 2 around for discussion and incremental fixes then it would probably be a good idea to do this in a different project than from within this beanshell 3 project. This means forking the beanshell 2 tree in to a new project, and leaving a note here to say that the beanshell 2 has moved. A good project location would be https://github.com/beanshell/beanshell2

If someone wants to take the initiative to fork beanshell 2 in to it's own project then open a new issue and we can discuss it.

nickl- commented 5 months ago

Will look into publishing the 2.1.1 release but in the meantime please use the BeanShell 3.0 SNAPSHOT release instead, as we cannot do support on 2.1.1.

groupId: org.beanshell artifactId: bsh

slachiewicz commented 4 months ago

looks like release 2.1.1 was configured to do artifact deployment to bintray 

[INFO] --- deploy:3.1.1:deploy (default-deploy) @ bsh ---
Uploading to bintray-beanshell-Beanshell-bsh: https://api.bintray.com/maven/beanshell/Beanshell/bsh/org/apache-extras/beanshell/bsh/2.1.1/bsh-2.1.1.pom
Uploading to bintray-beanshell-Beanshell-bsh: https://api.bintray.com/maven/beanshell/Beanshell/bsh/org/apache-extras/beanshell/bsh/2.1.1/bsh-2.1.1.jar

You need to change distributionManagement in pom to like here https://github.com/beanshell/beanshell/commit/61e880567d2ebaea95b637b2a90e0a4fbf7a206c