[dbutils] Project release cycle
Hello, I would like to clarify the reason why there were no releases for so long time period? There have been solved some critical bugs, and it would be nice to get them live. But instead, while waiting for a release, we need to fork the lib and release it internally ourselves. Could you please coordinate the schedule of releases? If you need any help I can also assist here. Regards, Alexey
Re: [dbutils] Project release cycle
Hi, The reason is probably the lack of volunteer time by one of the committers. I am planning a release soon as I am leaving my current $work and must have 1 month in-between jobs to release components. I can try dbutils, but no promises since I never released it (not sure if I ever worked on it). But again, if I find myself having to work on a $project during that time, then I'd have to postpone these releases (i.e. I would not be able to _volunteer_ for this.) One thing that is always welcome is reviews of pull requests and issues that could block a release (e.g. any regression in the code, RAT or Jacimp reports missing, increasing test coverage, etc). If you have time to help with that it would be great. Cheers Bruno On Mon, 2 May 2022 at 21:47, Alexey Anufriev wrote: > Hello, > > I would like to clarify the reason why there were no releases for so long > time period? There have been solved some critical bugs, and it would be > nice to get them live. But instead, while waiting for a release, we need to > fork the lib and release it internally ourselves. > > Could you please coordinate the schedule of releases? If you need any help > I can also assist here. > > Regards, > Alexey >
Re: [dbutils] Project release cycle
Hi Alexey, We are volunteers here, there is no traditional schedule or management. Your message now puts dbutils on our collective todo list for a release. Personally, I plan on releasing "soon" lang, io, pool, dbcp, cvs, text, configuration, but likely not in that order. Gary On Mon, May 2, 2022, 05:47 Alexey Anufriev wrote: > Hello, > > I would like to clarify the reason why there were no releases for so long > time period? There have been solved some critical bugs, and it would be > nice to get them live. But instead, while waiting for a release, we need to > fork the lib and release it internally ourselves. > > Could you please coordinate the schedule of releases? If you need any help > I can also assist here. > > Regards, > Alexey >
Re: BCEL How to create a field with a parameterized type?
Hi Gary, I'm not sure what to add frankly. If anything, a full-fledged generic type signature generator would be cool, but that's beyond my reach... :) And my simple case (think List) works perfectly fine right now. Many greetings, Stefan On Sun, 1 May 2022 at 13:45, Gary Gregory wrote: > Hi Stefan, > > Feel free to provide a PR on GitHub ;-) > That is the best way to nudge the component in the direction you need. > > Gary > > On Sat, Apr 30, 2022, 18:36 Stefan Reich > wrote: > > > OK I think I figured it out. There is setSignature in > > org.apache.bcel.generic.Type which I need to call with my generic field > > signature (since direct representations of generic types are actually not > > built into BCEL yet). > > > > Not a problem, what's unfortunate is just that setSignature is > > package-protected so I'd have to patch BCEL to call it. > > > > The field signature itself is protected so I could set it directly in a > > subclass of ObjectType. > > > > However, there is a note that say this practice will be made impossible > in > > the future. So, in conclusion, I am proposing to change that note (in > > org/apache/bcel/generic/Type.java): > > > > /** > > * @deprecated (since 6.0) will be made private; do not access > > directly, use getter/setter > > */ > > @Deprecated > > protected String signature; // signature for the type TODO should be > > private > > > > > > and/or making the setSignature method in the same class public. > > > > Greetings, > > Stefan > > > > > > > > On Sat, 30 Apr 2022 at 17:42, Stefan Reich < > > stefan.reich.maker.of@googlemail.com> wrote: > > > > > Hi, the title basically says it... I'm trying to create a field with a > > > parameterized type (e.g. List), but I can't find a subclass of > > Type > > > representing a parameterized type that I could pass to the FieldGen > > > constructor. > > > > > > Thanks, > > > Stefan > > > > > > -- > > > == Gaz.AI == > > > > > > > > > -- > > == Gaz.AI == > > > -- == Gaz.AI ==
[lang] What does the animal-sniffer-maven-plugin compare against?
Hi, I am currently preparing a feature for Lang, that makes use of MethodHandle.invoke(Object...) According to the Javadocs [1], this should be fine, but I am getting this from the animal-sniffer-maven-plugin: [INFO] --- animal-sniffer-maven-plugin:1.21:check (checkAPIcompatibility) @ commons-lang3 --- [INFO] Checking unresolved references to org.codehaus.mojo.signature:java18:1.0 [ERROR] C:\Work\git\ASF\commons-lang\src\main\java\org\apache\commons\lang3\function\access\Getter.java:139: Undefined reference: Object java.lang.invoke.MethodHandle.invoke(Object) Can anyone help, please? Thanks, Jochen 1: https://docs.oracle.com/javase/8/docs/api/java/lang/invoke/MethodHandle.html#invoke-java.lang.Object...- -- Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [lang] What does the animal-sniffer-maven-plugin compare against?
Followup question: Should the following reveal a property definition?
Because, I only see uses of ${javaTarget.majorVersion}, and no
definition.
$ mvn help:effective-pom | grep -i majorVersion
java${javaTarget.majorVersion}${javaTarget.minorVersion}
java${javaTarget.majorVersion}${javaTarget.minorVersion}
java${javaTarget.majorVersion}${javaTarget.minorVersion}
On Mon, May 2, 2022 at 7:57 PM Jochen Wiedmann
wrote:
>
> Hi,
>
> I am currently preparing a feature for Lang, that makes use of
> MethodHandle.invoke(Object...)
>
> According to the Javadocs [1], this should be fine, but I am getting
> this from the animal-sniffer-maven-plugin:
>
> [INFO] --- animal-sniffer-maven-plugin:1.21:check
> (checkAPIcompatibility) @ commons-lang3 ---
> [INFO] Checking unresolved references to
> org.codehaus.mojo.signature:java18:1.0
> [ERROR]
> C:\Work\git\ASF\commons-lang\src\main\java\org\apache\commons\lang3\function\access\Getter.java:139:
> Undefined reference: Object
> java.lang.invoke.MethodHandle.invoke(Object)
>
> Can anyone help, please?
>
> Thanks,
>
> Jochen
>
>
> 1:
> https://docs.oracle.com/javase/8/docs/api/java/lang/invoke/MethodHandle.html#invoke-java.lang.Object...-
>
> --
> Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits)
--
Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits)
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [lang] What does the animal-sniffer-maven-plugin compare against?
BTW Interesting that those signatures are 6 years old, but the coordinates
seems to be correct (don’t know if the content is correct)
https://repo1.maven.org/maven2/org/codehaus/mojo/signature/
Older major versions have vendor specific suffixes, none of them use minor
version numbers.
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: Jochen Wiedmann
Gesendet: Monday, May 2, 2022 8:05:48 PM
An: Apache Commons Developers List
Betreff: Re: [lang] What does the animal-sniffer-maven-plugin compare against?
Followup question: Should the following reveal a property definition?
Because, I only see uses of ${javaTarget.majorVersion}, and no
definition.
$ mvn help:effective-pom | grep -i majorVersion
java${javaTarget.majorVersion}${javaTarget.minorVersion}
java${javaTarget.majorVersion}${javaTarget.minorVersion}
java${javaTarget.majorVersion}${javaTarget.minorVersion}
On Mon, May 2, 2022 at 7:57 PM Jochen Wiedmann
wrote:
>
> Hi,
>
> I am currently preparing a feature for Lang, that makes use of
> MethodHandle.invoke(Object...)
>
> According to the Javadocs [1], this should be fine, but I am getting
> this from the animal-sniffer-maven-plugin:
>
> [INFO] --- animal-sniffer-maven-plugin:1.21:check
> (checkAPIcompatibility) @ commons-lang3 ---
> [INFO] Checking unresolved references to
> org.codehaus.mojo.signature:java18:1.0
> [ERROR]
> C:\Work\git\ASF\commons-lang\src\main\java\org\apache\commons\lang3\function\access\Getter.java:139:
> Undefined reference: Object
> java.lang.invoke.MethodHandle.invoke(Object)
>
> Can anyone help, please?
>
> Thanks,
>
> Jochen
>
>
> 1:
> https://docs.oracle.com/javase/8/docs/api/java/lang/invoke/MethodHandle.html#invoke-java.lang.Object...-
>
> --
> Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits)
--
Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits)
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [lang] What does the animal-sniffer-maven-plugin compare against?
Thanks for the reply, Bernd. Any suggestions on how I could proceed?
On Mon, May 2, 2022 at 8:17 PM Bernd Eckenfels wrote:
>
> BTW Interesting that those signatures are 6 years old, but the coordinates
> seems to be correct (don’t know if the content is correct)
>
> https://repo1.maven.org/maven2/org/codehaus/mojo/signature/
>
> Older major versions have vendor specific suffixes, none of them use minor
> version numbers.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
> Von: Jochen Wiedmann
> Gesendet: Monday, May 2, 2022 8:05:48 PM
> An: Apache Commons Developers List
> Betreff: Re: [lang] What does the animal-sniffer-maven-plugin compare against?
>
> Followup question: Should the following reveal a property definition?
> Because, I only see uses of ${javaTarget.majorVersion}, and no
> definition.
>
> $ mvn help:effective-pom | grep -i majorVersion
>
> java${javaTarget.majorVersion}${javaTarget.minorVersion}
>
> java${javaTarget.majorVersion}${javaTarget.minorVersion}
>
> java${javaTarget.majorVersion}${javaTarget.minorVersion}
>
> On Mon, May 2, 2022 at 7:57 PM Jochen Wiedmann
> wrote:
> >
> > Hi,
> >
> > I am currently preparing a feature for Lang, that makes use of
> > MethodHandle.invoke(Object...)
> >
> > According to the Javadocs [1], this should be fine, but I am getting
> > this from the animal-sniffer-maven-plugin:
> >
> > [INFO] --- animal-sniffer-maven-plugin:1.21:check
> > (checkAPIcompatibility) @ commons-lang3 ---
> > [INFO] Checking unresolved references to
> > org.codehaus.mojo.signature:java18:1.0
> > [ERROR]
> > C:\Work\git\ASF\commons-lang\src\main\java\org\apache\commons\lang3\function\access\Getter.java:139:
> > Undefined reference: Object
> > java.lang.invoke.MethodHandle.invoke(Object)
> >
> > Can anyone help, please?
> >
> > Thanks,
> >
> > Jochen
> >
> >
> > 1:
> > https://docs.oracle.com/javase/8/docs/api/java/lang/invoke/MethodHandle.html#invoke-java.lang.Object...-
> >
> > --
> > Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits)
>
>
>
> --
> Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Philosophy is useless, theology is worse. (Industrial Desease, Dire Straits)
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
