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
> After more googling I found this discussion
>
> http://www.yeap.de/blog2.0/archives/183-Upgrading-flex-mojos-2.0.0-to-flexmojos-m
euvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Fri, 11 Dec 2009 18:27:11 -0500
> Subject: Re: What happens to cause a build to not work after blowing out your
> repo - how to force so things are always ch
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
abou
On Fri, Dec 11, 2009 at 6:37 PM, Rick R 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]
> ---
On Fri, Dec 11, 2009 at 6:27 PM, Rick R wrote:
>
> On Fri, Dec 11, 2009 at 5:22 PM, Wayne Fay wrote:
>
>> > runs just fine when going against my OLD repo. With a fresh EMPTY repo
>> I'll
>> > end up with the following:
>> >
>> >
>> app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plug
On Fri, Dec 11, 2009 at 5:22 PM, Wayne Fay wrote:
> > runs just fine when going against my OLD repo. With a fresh EMPTY repo
> I'll
> > end up with the following:
> >
> > app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2]
>
> What version of the flexmojos-maven-plugin is us
> runs just fine when going against my OLD repo. With a fresh EMPTY repo I'll
> end up with the following:
>
> app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2]
What version of the flexmojos-maven-plugin is used in your successful
build, against the old repo? Use -X for deb
On Fri, Dec 11, 2009 at 2:25 PM, Wayne Fay wrote:
>
> I think there's an extremely good chance you do not have your plugin
> versions locked down in your pom files with
> [1.2.3].
>
I'm pretty sure my small project hasn't changed version numbers of plugins
so I'm completely stumped. For example
> 2) What happens that causes my initial build to work but then later not work
> if I start with a cleaned out local repository? Does it mean some dependency
> repository got borked somehow? (Again, it would sure be nice to know about
I think there's an extremely good chance you do not have your p
It's hard to say why this might be happening without seeing your pom
file(s). But this should be considered a bug in FlexMojos. Plugins
shouldn't have NoClassDefFoundErrors.
Justin
On 12/11/09 2:08 PM, Rick R wrote:
Hopefully I describe this situation correctly, because I'm constantly
getting
Hopefully I describe this situation correctly, because I'm constantly
getting burned on it at work it seems and the non-maven co-workers always
end up going "sheesh this stuff seems to happen all the time with maven."
Here's a situation:
I run an archetype command to create a project setup (happe
11 matches
Mail list logo
