You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shale.apache.org by James Mitchell <jm...@apache.org> on 2006/10/14 18:04:54 UTC

Maven strict dependency declaration [was Re: svn commit: r463684 - in /shale/f...]

The only thing worse than a broken maven plugin is when it works for  
some people, some of the time, and for others, most of the time, but  
never everyone, all of the time.

I'm wondering if it would be worth our time to add plugin  
configuration to shale-master that defines exactly which plugins and  
versions should be used for given phases, so that everyone is using  
the same versions across the entire build/site processes.

Your thoughts?

--
James Mitchell
678.910.8017




On Oct 13, 2006, at 2:35 PM, Craig McClanahan wrote:

> On 10/13/06, Rahul Akolkar <ra...@gmail.com> wrote:
>>
>> On 10/13/06, Wendy Smoak <ws...@gmail.com> wrote:
>> > On 10/13/06, Rahul Akolkar <ra...@gmail.com> wrote:
>> >
>> > > Is the error in the shale-dialog-scxml module (as it seems  
>> from the
>> > > above output)? If so, then this particular commit is unlikely  
>> to have
>> > > caused that problem (since there were no mods to that module  
>> in this
>> > > commit).
>> > >
>> > > There might be something else there that needs looking at though.
>> >
>> > Yes, it's happening in shale-dialog-scxml.  The site is building  
>> fine
>> > for Craig, so it's probably just Maven being weird again.
>> >
>> <snip/>
>>
>> FWIW, I successfully ran a framework site, so we must have variations
>> in our local build setups.
>
>
> FWIW, I'm building successfully on Windows, using JDK 1.5 and Maven  
> 2.0.4.
>
> Based on the error message (jx.s.j.e.FunctionMapper not found), can
>> you try adding the import to o.a.s.d.s.ShaleDialogELEvaluator ? Thats
>> the only place I can think of where it could matter (superclass has a
>> protected method that contains the FunctionMapper in its signature).
>> Thanks!
>
>
> This sounded to me like it might be a versioning problem on the JSP  
> API ...
> FunctionMapper was added in 2.0, so you wouldn't find it on earlier
> versions.  But why that would cause JavaDoc to fail the build is  
> beyond me.
>
> -Rahul
>
>
> Craig
>
>
>> Thanks,
>> > --
>> > Wendy
>> >
>>


Re: Maven strict dependency declaration [was Re: svn commit: r463684 - in /shale/f...]

Posted by Wendy Smoak <ws...@gmail.com>.
On 10/14/06, James Mitchell <jm...@apache.org> wrote:

> I'm wondering if it would be worth our time to add plugin
> configuration to shale-master that defines exactly which plugins and
> versions should be used for given phases, so that everyone is using
> the same versions across the entire build/site processes.

We should add a <version> element for each plugin, so we're not
surprised by changes.  (That should already be the case for the site
plugin, as we're still using 2.0-beta-4.)

I'm not sure what you mean about phases.  Most plugins are bound to a
certain phase by default, if not we specify that in an <execution>
section.

Probably easier if you just do whatever it is you have in mind, and
we'll go from there. :)

-- 
Wendy