You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Petar Tahchiev <pa...@gmail.com> on 2014/04/22 16:07:52 UTC
[all] Dependency resolution.
Hi guys,
I found out I'm using quite a lot of the commons-*:commons-* artifacts in
my project so I decided to upgrade them to their new version in
org.apache.commons:whatever. I only upgraded those that I could so now I
have for instance org.apache.commons:commons-lang3 in my classpath, but
unfortunately I also have commons-confguration:commons-configuration:1.9
and there I get exceptions like these:
Caused by: java.lang.NoClassDefFoundError:
org/apache/commons/configuration/ConfigurationException
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
at java.lang.Class.getDeclaredMethods(Class.java:1845)
at
org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:402)
at
org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:332)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:908)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
So because commons-configuration:commons-configuration requires
commons-lang2 as a dependency I'm forced to downgrade to commons-lang2.
My request is this: is it possible to upgrade ALL the commons artifacts to
the correct repository groupId (org.apache.commons) and upgrade their
dependencies? Most of them are already there, and those which are not will
most certainly benefit from a new release (i guess there's been quite a
while they haven't been released and there might be some resolved issues in
the JIRA).
Is there anyone against having a new release on: commons-logging,
commons-fileupload, commons-codec,
commons-configuration,commons-beanutils,commons-digester and the rest of
the projects which are still using the incorrect groupId.
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: [all] Dependency resolution.
Posted by Jörg Schaible <jo...@gmx.de>.
Petar Tahchiev wrote:
> Hi guys,
>
> my exception occurs if I have only commons-lang2 in my classpath. I wasn't
> aware you can have both in the classpath, but now that I put them both in
> the classpath it all works. It's not very nice solution, but I'll stick
> them both in. I still think we should issue a new release for the
> mentioned projects if they have enough issues solved. This way we can
> update the dependencies and refactor to the correct groupId.
This is not possible without breaking binary compatibility of the commons-
configuration package - unfortunately. The problem is the
ConfigurationException which is derived from an Exception of the old
commons-lang and therefore part of the Configuration API which requires old
commons-lang to be part of the compiler classpath ... :-/
For configuration2 we should have ConfigurationException derived directly
from an Exception of the Java runtime.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] Dependency resolution.
Posted by Petar Tahchiev <pa...@gmail.com>.
Hi guys,
my exception occurs if I have only commons-lang2 in my classpath. I wasn't
aware you can have both in the classpath, but now that I put them both in
the classpath it all works. It's not very nice solution, but I'll stick
them both in. I still think we should issue a new release for the mentioned
projects if they have enough issues solved. This way we can update the
dependencies and refactor to the correct groupId.
2014-04-22 17:46 GMT+03:00 Duncan Jones <du...@wortharead.com>:
> On 22 April 2014 15:45, Duncan Jones <du...@wortharead.com> wrote:
> > Hi Paul,
> >
> > On 22 April 2014 15:25, Paul Benedict <pb...@apache.org> wrote:
> >> Yup. I have depend on Lang 3 for my own code and many of my transitive
> >> dependencies relies on Lang 2. There's no problem with having both
> >> libraries in your code.
> >
> > I haven't fully understood your description of the problem. You say
> > you've got commons-confguration:commons-configuration:1.9 on your
> > classpath and this requires commons-lang(2), yet you also acknowledge
> > that it's ok to have both commons-lang and commons-lang3 in your
> > classpath. I agree this shouldn't be a problem.
>
> Apparently I'm confusing my Pauls with my Petars. My comments about
> not understanding the exception (below) still stand, but the first
> paragraph (above) can be ignored!
>
>
> > The exception you've shown looks more like something isn't happy with
> > the version of commons-configuration you're using; I'm not sure how
> > that relates to [lang]. Also, NoClassDefFoundError is typically thrown
> > *after* a previous failed attempt to find a class [1] - perhaps there
> > are more useful stack-traces elsewhere in your logs?
> >
> > Can you perhaps provide another example of how things are breaking?
> >
> > Duncan
> >
> >
> > [1] http://stackoverflow.com/a/5756989/474189
> >
> >>
> >>
> >> On Tue, Apr 22, 2014 at 9:22 AM, Matt Benson <gu...@gmail.com>
> wrote:
> >>
> >>> Note that you can use [lang] v2 and v3 together in the same project as
> both
> >>> the Maven coordinates and package names have been changed with the
> major
> >>> version upgrade.
> >>>
> >>> Matt
> >>>
> >>>
> >>> On Tue, Apr 22, 2014 at 9:07 AM, Petar Tahchiev <paranoiabla@gmail.com
> >>> >wrote:
> >>>
> >>> > Hi guys,
> >>> >
> >>> > I found out I'm using quite a lot of the commons-*:commons-*
> artifacts in
> >>> > my project so I decided to upgrade them to their new version in
> >>> > org.apache.commons:whatever. I only upgraded those that I could so
> now I
> >>> > have for instance org.apache.commons:commons-lang3 in my classpath,
> but
> >>> > unfortunately I also have
> commons-confguration:commons-configuration:1.9
> >>> > and there I get exceptions like these:
> >>> >
> >>> > Caused by: java.lang.NoClassDefFoundError:
> >>> > org/apache/commons/configuration/ConfigurationException
> >>> > at java.lang.Class.getDeclaredMethods0(Native Method)
> >>> > at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> >>> > at java.lang.Class.getDeclaredMethods(Class.java:1845)
> >>> > at
> >>> >
> >>> >
> >>>
> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:402)
> >>> > at
> >>> >
> >>> >
> >>>
> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:332)
> >>> > at
> >>> >
> >>> >
> >>>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:908)
> >>> > at
> >>> >
> >>> >
> >>>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)
> >>> > at
> >>> >
> >>> >
> >>>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
> >>> > at
> >>> >
> >>> >
> >>>
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
> >>> > at
> >>> >
> >>> >
> >>>
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
> >>> >
> >>> >
> >>> > So because commons-configuration:commons-configuration requires
> >>> > commons-lang2 as a dependency I'm forced to downgrade to
> commons-lang2.
> >>> >
> >>> > My request is this: is it possible to upgrade ALL the commons
> artifacts
> >>> to
> >>> > the correct repository groupId (org.apache.commons) and upgrade their
> >>> > dependencies? Most of them are already there, and those which are not
> >>> will
> >>> > most certainly benefit from a new release (i guess there's been
> quite a
> >>> > while they haven't been released and there might be some resolved
> issues
> >>> in
> >>> > the JIRA).
> >>> >
> >>> > Is there anyone against having a new release on: commons-logging,
> >>> > commons-fileupload, commons-codec,
> >>> > commons-configuration,commons-beanutils,commons-digester and the
> rest of
> >>> > the projects which are still using the incorrect groupId.
> >>> >
> >>> > --
> >>> > Regards, Petar!
> >>> > Karlovo, Bulgaria.
> >>> > ---
> >>> > Public PGP Key at:
> >>> >
> >>>
> https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
> >>> > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> Cheers,
> >> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: [all] Dependency resolution.
Posted by Duncan Jones <du...@wortharead.com>.
On 22 April 2014 15:45, Duncan Jones <du...@wortharead.com> wrote:
> Hi Paul,
>
> On 22 April 2014 15:25, Paul Benedict <pb...@apache.org> wrote:
>> Yup. I have depend on Lang 3 for my own code and many of my transitive
>> dependencies relies on Lang 2. There's no problem with having both
>> libraries in your code.
>
> I haven't fully understood your description of the problem. You say
> you've got commons-confguration:commons-configuration:1.9 on your
> classpath and this requires commons-lang(2), yet you also acknowledge
> that it's ok to have both commons-lang and commons-lang3 in your
> classpath. I agree this shouldn't be a problem.
Apparently I'm confusing my Pauls with my Petars. My comments about
not understanding the exception (below) still stand, but the first
paragraph (above) can be ignored!
> The exception you've shown looks more like something isn't happy with
> the version of commons-configuration you're using; I'm not sure how
> that relates to [lang]. Also, NoClassDefFoundError is typically thrown
> *after* a previous failed attempt to find a class [1] - perhaps there
> are more useful stack-traces elsewhere in your logs?
>
> Can you perhaps provide another example of how things are breaking?
>
> Duncan
>
>
> [1] http://stackoverflow.com/a/5756989/474189
>
>>
>>
>> On Tue, Apr 22, 2014 at 9:22 AM, Matt Benson <gu...@gmail.com> wrote:
>>
>>> Note that you can use [lang] v2 and v3 together in the same project as both
>>> the Maven coordinates and package names have been changed with the major
>>> version upgrade.
>>>
>>> Matt
>>>
>>>
>>> On Tue, Apr 22, 2014 at 9:07 AM, Petar Tahchiev <paranoiabla@gmail.com
>>> >wrote:
>>>
>>> > Hi guys,
>>> >
>>> > I found out I'm using quite a lot of the commons-*:commons-* artifacts in
>>> > my project so I decided to upgrade them to their new version in
>>> > org.apache.commons:whatever. I only upgraded those that I could so now I
>>> > have for instance org.apache.commons:commons-lang3 in my classpath, but
>>> > unfortunately I also have commons-confguration:commons-configuration:1.9
>>> > and there I get exceptions like these:
>>> >
>>> > Caused by: java.lang.NoClassDefFoundError:
>>> > org/apache/commons/configuration/ConfigurationException
>>> > at java.lang.Class.getDeclaredMethods0(Native Method)
>>> > at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
>>> > at java.lang.Class.getDeclaredMethods(Class.java:1845)
>>> > at
>>> >
>>> >
>>> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:402)
>>> > at
>>> >
>>> >
>>> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:332)
>>> > at
>>> >
>>> >
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:908)
>>> > at
>>> >
>>> >
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)
>>> > at
>>> >
>>> >
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
>>> > at
>>> >
>>> >
>>> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
>>> > at
>>> >
>>> >
>>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
>>> >
>>> >
>>> > So because commons-configuration:commons-configuration requires
>>> > commons-lang2 as a dependency I'm forced to downgrade to commons-lang2.
>>> >
>>> > My request is this: is it possible to upgrade ALL the commons artifacts
>>> to
>>> > the correct repository groupId (org.apache.commons) and upgrade their
>>> > dependencies? Most of them are already there, and those which are not
>>> will
>>> > most certainly benefit from a new release (i guess there's been quite a
>>> > while they haven't been released and there might be some resolved issues
>>> in
>>> > the JIRA).
>>> >
>>> > Is there anyone against having a new release on: commons-logging,
>>> > commons-fileupload, commons-codec,
>>> > commons-configuration,commons-beanutils,commons-digester and the rest of
>>> > the projects which are still using the incorrect groupId.
>>> >
>>> > --
>>> > Regards, Petar!
>>> > Karlovo, Bulgaria.
>>> > ---
>>> > Public PGP Key at:
>>> >
>>> https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
>>> > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
>>> >
>>>
>>
>>
>>
>> --
>> Cheers,
>> Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] Dependency resolution.
Posted by Duncan Jones <du...@wortharead.com>.
Hi Paul,
On 22 April 2014 15:25, Paul Benedict <pb...@apache.org> wrote:
> Yup. I have depend on Lang 3 for my own code and many of my transitive
> dependencies relies on Lang 2. There's no problem with having both
> libraries in your code.
I haven't fully understood your description of the problem. You say
you've got commons-confguration:commons-configuration:1.9 on your
classpath and this requires commons-lang(2), yet you also acknowledge
that it's ok to have both commons-lang and commons-lang3 in your
classpath. I agree this shouldn't be a problem.
The exception you've shown looks more like something isn't happy with
the version of commons-configuration you're using; I'm not sure how
that relates to [lang]. Also, NoClassDefFoundError is typically thrown
*after* a previous failed attempt to find a class [1] - perhaps there
are more useful stack-traces elsewhere in your logs?
Can you perhaps provide another example of how things are breaking?
Duncan
[1] http://stackoverflow.com/a/5756989/474189
>
>
> On Tue, Apr 22, 2014 at 9:22 AM, Matt Benson <gu...@gmail.com> wrote:
>
>> Note that you can use [lang] v2 and v3 together in the same project as both
>> the Maven coordinates and package names have been changed with the major
>> version upgrade.
>>
>> Matt
>>
>>
>> On Tue, Apr 22, 2014 at 9:07 AM, Petar Tahchiev <paranoiabla@gmail.com
>> >wrote:
>>
>> > Hi guys,
>> >
>> > I found out I'm using quite a lot of the commons-*:commons-* artifacts in
>> > my project so I decided to upgrade them to their new version in
>> > org.apache.commons:whatever. I only upgraded those that I could so now I
>> > have for instance org.apache.commons:commons-lang3 in my classpath, but
>> > unfortunately I also have commons-confguration:commons-configuration:1.9
>> > and there I get exceptions like these:
>> >
>> > Caused by: java.lang.NoClassDefFoundError:
>> > org/apache/commons/configuration/ConfigurationException
>> > at java.lang.Class.getDeclaredMethods0(Native Method)
>> > at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
>> > at java.lang.Class.getDeclaredMethods(Class.java:1845)
>> > at
>> >
>> >
>> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:402)
>> > at
>> >
>> >
>> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:332)
>> > at
>> >
>> >
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:908)
>> > at
>> >
>> >
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)
>> > at
>> >
>> >
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
>> > at
>> >
>> >
>> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
>> > at
>> >
>> >
>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
>> >
>> >
>> > So because commons-configuration:commons-configuration requires
>> > commons-lang2 as a dependency I'm forced to downgrade to commons-lang2.
>> >
>> > My request is this: is it possible to upgrade ALL the commons artifacts
>> to
>> > the correct repository groupId (org.apache.commons) and upgrade their
>> > dependencies? Most of them are already there, and those which are not
>> will
>> > most certainly benefit from a new release (i guess there's been quite a
>> > while they haven't been released and there might be some resolved issues
>> in
>> > the JIRA).
>> >
>> > Is there anyone against having a new release on: commons-logging,
>> > commons-fileupload, commons-codec,
>> > commons-configuration,commons-beanutils,commons-digester and the rest of
>> > the projects which are still using the incorrect groupId.
>> >
>> > --
>> > Regards, Petar!
>> > Karlovo, Bulgaria.
>> > ---
>> > Public PGP Key at:
>> >
>> https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
>> > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
>> >
>>
>
>
>
> --
> Cheers,
> Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] Dependency resolution.
Posted by Paul Benedict <pb...@apache.org>.
Yup. I have depend on Lang 3 for my own code and many of my transitive
dependencies relies on Lang 2. There's no problem with having both
libraries in your code.
On Tue, Apr 22, 2014 at 9:22 AM, Matt Benson <gu...@gmail.com> wrote:
> Note that you can use [lang] v2 and v3 together in the same project as both
> the Maven coordinates and package names have been changed with the major
> version upgrade.
>
> Matt
>
>
> On Tue, Apr 22, 2014 at 9:07 AM, Petar Tahchiev <paranoiabla@gmail.com
> >wrote:
>
> > Hi guys,
> >
> > I found out I'm using quite a lot of the commons-*:commons-* artifacts in
> > my project so I decided to upgrade them to their new version in
> > org.apache.commons:whatever. I only upgraded those that I could so now I
> > have for instance org.apache.commons:commons-lang3 in my classpath, but
> > unfortunately I also have commons-confguration:commons-configuration:1.9
> > and there I get exceptions like these:
> >
> > Caused by: java.lang.NoClassDefFoundError:
> > org/apache/commons/configuration/ConfigurationException
> > at java.lang.Class.getDeclaredMethods0(Native Method)
> > at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> > at java.lang.Class.getDeclaredMethods(Class.java:1845)
> > at
> >
> >
> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:402)
> > at
> >
> >
> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:332)
> > at
> >
> >
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:908)
> > at
> >
> >
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)
> > at
> >
> >
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
> > at
> >
> >
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
> > at
> >
> >
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
> >
> >
> > So because commons-configuration:commons-configuration requires
> > commons-lang2 as a dependency I'm forced to downgrade to commons-lang2.
> >
> > My request is this: is it possible to upgrade ALL the commons artifacts
> to
> > the correct repository groupId (org.apache.commons) and upgrade their
> > dependencies? Most of them are already there, and those which are not
> will
> > most certainly benefit from a new release (i guess there's been quite a
> > while they haven't been released and there might be some resolved issues
> in
> > the JIRA).
> >
> > Is there anyone against having a new release on: commons-logging,
> > commons-fileupload, commons-codec,
> > commons-configuration,commons-beanutils,commons-digester and the rest of
> > the projects which are still using the incorrect groupId.
> >
> > --
> > Regards, Petar!
> > Karlovo, Bulgaria.
> > ---
> > Public PGP Key at:
> >
> https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
> > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
> >
>
--
Cheers,
Paul
Re: [all] Dependency resolution.
Posted by Matt Benson <gu...@gmail.com>.
Note that you can use [lang] v2 and v3 together in the same project as both
the Maven coordinates and package names have been changed with the major
version upgrade.
Matt
On Tue, Apr 22, 2014 at 9:07 AM, Petar Tahchiev <pa...@gmail.com>wrote:
> Hi guys,
>
> I found out I'm using quite a lot of the commons-*:commons-* artifacts in
> my project so I decided to upgrade them to their new version in
> org.apache.commons:whatever. I only upgraded those that I could so now I
> have for instance org.apache.commons:commons-lang3 in my classpath, but
> unfortunately I also have commons-confguration:commons-configuration:1.9
> and there I get exceptions like these:
>
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/commons/configuration/ConfigurationException
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> at java.lang.Class.getDeclaredMethods(Class.java:1845)
> at
>
> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:402)
> at
>
> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:332)
> at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:908)
> at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512)
> at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
> at
>
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
> at
>
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
>
>
> So because commons-configuration:commons-configuration requires
> commons-lang2 as a dependency I'm forced to downgrade to commons-lang2.
>
> My request is this: is it possible to upgrade ALL the commons artifacts to
> the correct repository groupId (org.apache.commons) and upgrade their
> dependencies? Most of them are already there, and those which are not will
> most certainly benefit from a new release (i guess there's been quite a
> while they haven't been released and there might be some resolved issues in
> the JIRA).
>
> Is there anyone against having a new release on: commons-logging,
> commons-fileupload, commons-codec,
> commons-configuration,commons-beanutils,commons-digester and the rest of
> the projects which are still using the incorrect groupId.
>
> --
> Regards, Petar!
> Karlovo, Bulgaria.
> ---
> Public PGP Key at:
> https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
>