Hi Ed,
Can you send me the output of the build? Send it to me directly.
Please use "mvn install -e -X".
Thanks,
Jane
Ed Burns wrote:
>>>>>> On Thu, 17 Sep 2009 15:00:05 -0500, Jason Lee <jasondlee_at_Sun.COM> said:
>>>>>>
>
> JL> It worked for me. How up-to-date is your tree? You might try and svn
> JL> up or deleting ~/.m2/repository/org.jvnet (total swag) or the whole
> JL> ~/.m2/repository and see if that helps.
>
> JL> On Sep 17, 2009, at 2:54 PM, Ed Burns wrote:
>
> EB> I'm seeing this error when I do a top level mvn clean
> EB>
> EB> The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not
> EB> exist or
> EB> no valid version could be found
>
> EB> Interestingly, it works if I pull in Jane's workaround profile from
> EB> last
> EB> week
>
> EB> mvn -Prepo clean
>
> EB> Any idea why it's not working without the workaround profile
> EB> activated?
>
> This must be just a problem I'm observing, but I still need a solution.
>
> When I build HEAD, I'm finding the build fails in the two poms that
> depend on org.jvnet.jaxb2.maven2:maven-jaxb2-plugin. It turns out that
> the <dependency> element for this artifact is missing a <version>
> element in both cases. When I add a <version> element, say with 0.7.2,
> the build succeeds. Should the poms have a <version> element, or not?
>
> The offending poms are
>
> appclient/client/acc-config/pom.xml
> admin/cli/pom.xml
>
>
>