You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Rick R <ri...@gmail.com> on 2009/12/12 02:09:28 UTC
SOLVED I guess. Re: What happens to cause a build to not work after
blowing out your repo - how to force so things are always checked locally?
After more googling I found this discussion
http://www.yeap.de/blog2.0/archives/183-Upgrading-flex-mojos-2.0.0-to-flexmojos-maven-plugin-3.x.htmlwhere
others had the same issue. Apparently jdom is needed in your maven lib
if a certain dependency relies on it. Something with plexus was bitching
about it but no idea what that was about. Seems really bad though that
someone would have to manually add that jar to the maven lib so I'd like to
get the root cause of thatissue at some point. Apparently in the older maven
projects it was part of the uber-jar?
I need a drink now for all the time wasted on this today:) I had tried
adding a dependency to the pom for the jdom jar (actually that was one of
the first things I did), but that didn't help. I wouldn't have thought that
it was needed in the actual lib dir.
(Now a crazier question though is why would my old repo have worked though
without adding this jar? I'm too tired to try to figure that one out.)
On Fri, Dec 11, 2009 at 7:51 PM, Rick R <ri...@gmail.com> wrote:
>
>
> On Fri, Dec 11, 2009 at 6:37 PM, Rick R <ri...@gmail.com> wrote:
>
>>
>> Now to add to the confusion, not sure it's the firewall at all ... on the
>> Mac and Windows machine both behind company firewall...the Mac now gives the
>> errors like:
>>
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> ----------
>> 1) com.adobe.flex:compiler:pom:3.2.0.3958
>> Path to dependency:
>> 1)
>> org.sonatype.flexmojos:flexmojos-maven-plugin:maven-plugin:3.4.2
>> 2) com.adobe.flex:compiler:pom:3.2.0.3958
>>
>>
>>
> For what it's worth I got past my recent errors by changing the repository
> http://repository.sonatype.org/content/groups/public/
>
> Now the project that I provided earlier that was zipped up builds, but I
> still have the issue in my current project related to the below. But I'll
> work now on debugging better since the archetype works it must be something
> conflicting in my code causing an issue. Still really odd my old repo works
> with the same code base though. That part has me really stumped.
>
>
> [WARNING] Not defined if locales should be merged or not
> [WARNING] Unable to find license.jar on classpath. Check wiki for
> instructions about how to add it:
> https://docs.sonatype.org/display/FLEXMOJOS/FAQ#FAQ-1.3
> [FATAL ERROR] org.sonatype.flexmojos.compiler.LibraryMojo#execute() caused
> a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date.
> Check the realms:
> [FATAL ERROR] Plugin realm =
> app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2]
> ....
> urls[93] =
> file:/Users/rick/.m2/repository/org/apache/maven/shared/maven-plugin-testing-harness/1.1/maven-plugin-testing-harness-1.1.jar
>
> [FATAL ERROR] Container realm = plexus.core
> urls[0] = file:/Users/rick/java/maven/lib/maven-2.2.1-uber.jar
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] org/jdom/input/SAXBuilder
> org.jdom.input.SAXBuilder
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NoClassDefFoundError: org/jdom/input/SAXBuilder
> at
> org.sonatype.flexmojos.utilities.FDKConfigResolver.getConfig(FDKConfigResolver.java:95)
>
>
--
Rick R
Re: SOLVED I guess. Re: What happens to cause a build to not work
after blowing out your repo - how to force so things are always checked
locally?
Posted by Baptiste MATHUS <ml...@batmat.net>.
Please never change the subject. It appears as a new thread, and if someone
finds the original entry, he won't see this one in the end...
Thanks.
2009/12/12 Rick R <ri...@gmail.com>
> After more googling I found this discussion
>
> http://www.yeap.de/blog2.0/archives/183-Upgrading-flex-mojos-2.0.0-to-flexmojos-maven-plugin-3.x.htmlwhere
> others had the same issue. Apparently jdom is needed in your maven lib
> if a certain dependency relies on it. Something with plexus was bitching
> about it but no idea what that was about. Seems really bad though that
> someone would have to manually add that jar to the maven lib so I'd like to
> get the root cause of thatissue at some point. Apparently in the older
> maven
> projects it was part of the uber-jar?
>
> I need a drink now for all the time wasted on this today:) I had tried
> adding a dependency to the pom for the jdom jar (actually that was one of
> the first things I did), but that didn't help. I wouldn't have thought that
> it was needed in the actual lib dir.
>
> (Now a crazier question though is why would my old repo have worked though
> without adding this jar? I'm too tired to try to figure that one out.)
>
> On Fri, Dec 11, 2009 at 7:51 PM, Rick R <ri...@gmail.com> wrote:
>
> >
> >
> > On Fri, Dec 11, 2009 at 6:37 PM, Rick R <ri...@gmail.com> wrote:
> >
> >>
> >> Now to add to the confusion, not sure it's the firewall at all ... on
> the
> >> Mac and Windows machine both behind company firewall...the Mac now gives
> the
> >> errors like:
> >>
> >>
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Failed to resolve artifact.
> >>
> >> Missing:
> >> ----------
> >> 1) com.adobe.flex:compiler:pom:3.2.0.3958
> >> Path to dependency:
> >> 1)
> >> org.sonatype.flexmojos:flexmojos-maven-plugin:maven-plugin:3.4.2
> >> 2) com.adobe.flex:compiler:pom:3.2.0.3958
> >>
> >>
> >>
> > For what it's worth I got past my recent errors by changing the
> repository
> > http://repository.sonatype.org/content/groups/public/
> >
> > Now the project that I provided earlier that was zipped up builds, but I
> > still have the issue in my current project related to the below. But I'll
> > work now on debugging better since the archetype works it must be
> something
> > conflicting in my code causing an issue. Still really odd my old repo
> works
> > with the same code base though. That part has me really stumped.
> >
> >
> > [WARNING] Not defined if locales should be merged or not
> > [WARNING] Unable to find license.jar on classpath. Check wiki for
> > instructions about how to add it:
> > https://docs.sonatype.org/display/FLEXMOJOS/FAQ#FAQ-1.3
> > [FATAL ERROR] org.sonatype.flexmojos.compiler.LibraryMojo#execute()
> caused
> > a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date.
> > Check the realms:
> > [FATAL ERROR] Plugin realm =
> > app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2]
> > ....
> > urls[93] =
> >
> file:/Users/rick/.m2/repository/org/apache/maven/shared/maven-plugin-testing-harness/1.1/maven-plugin-testing-harness-1.1.jar
> >
> > [FATAL ERROR] Container realm = plexus.core
> > urls[0] = file:/Users/rick/java/maven/lib/maven-2.2.1-uber.jar
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] FATAL ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] org/jdom/input/SAXBuilder
> > org.jdom.input.SAXBuilder
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Trace
> > java.lang.NoClassDefFoundError: org/jdom/input/SAXBuilder
> > at
> >
> org.sonatype.flexmojos.utilities.FDKConfigResolver.getConfig(FDKConfigResolver.java:95)
> >
> >
>
>
>
> --
> Rick R
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !