When I see things like this, I see three outcomes:
1) The originator of the code reverse their change (maybe they weren't
realizing it would leak through the interface). [Easy]
2) The originator of the code determines a change that allows them to
'deprecate and migrate', giving users a reasonable time window to change.
[Medium]
3) The originator of the code determines the change was mandatory (for long
term health) so requests that the community change to meet it. [Hardest =
Community Work, and disconnects remain.]
Change happens, right? Nothing we can do about it [when 1 & 2 can't occur],
other than observe it, know it, communicate it. I wonder if somehow we could
have folks 'comment' on changes in their Gump descriptor (or related) so we
could publish their motivations for a change/determination not to undo [link
to jira or eyebrowse or ...], so other Gump users could know to migrate.
Anything in this? I get the feeling it could be powerful.
[Side note ... I've had a side (pet) project for a while -- 'Version' in
Depot in Incubator -- that wants to represent version disconnects in a
separate (introspectable) XML file. Maybe this could loop in somehow.]
BTW: I +1 to a shared blog for Gump. Stating the obvious, I feel that it
ought be considered the voice of Gump/Gumpers, and be only on Gump
issues/events. As part of that, I think we need to track case studies
(completed events/outcomes w/ some analysis), and this is as good a form as
any. If we track the case studies (and can view them separately over time)
we might extract some insights that we just never expected.
That said, nothing to stop us personally commenting on Gump on personal
(well read :-) blogs also. All references increase traffic, and could lead
to increased awareness/community.
http://stefanbodewig.blogger.de/stories/63974/
regards,
Adam
----- Original Message -----
From: "Antoine L�vy-Lambert" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "jakarta-gump list"
<[EMAIL PROTECTED]>
Sent: Monday, February 09, 2004 7:21 AM
Subject: Re: DefaultJDOMFactory class removed from jdom causing
jakarta-velocity build to fail
> It looks like the org.jdom.input.DefaultJDOMFactory has been moved one
> package up as org.jdom.DefaultJDOMFactory.
> Antoine
>
> Antoine L�vy-Lambert wrote:
>
> > Hi Jdom.org,
> >
> > you seem to have recently removed the class
> > org.jdom.input.DefaultJDOMFactory .
> > This causes the build of jakarta-velocity in Gump to fail [1].
> > Geir Magnusson Jr was wondering what was actually failing in the build
> > of velocity [2].
> > The error messages are reproduced below [3]:
> >
> > Is there a replacement for this DefaultJDOMFactory ?
> >
> > Antoine
> >
> > [1]
> >
http://lsd.student.utwente.nl/gump/jakarta-velocity/work/build_jakarta-velocity_jakarta-velocity.html
> >
> > [2] http://marc.theaimsgroup.com/?l=velocity-dev&m=107619083628831&w=2
> >
>
> --------------------------------------------------------------------------
----------------------------------------------
> >
> > [3]
> >
/data/gump/jakarta-velocity/bin/src/org/apache/velocity/anakia/AnakiaJDOMFac
tory.java:59:
> >
> > cannot resolve symbol
> > [javac] symbol : class DefaultJDOMFactory
> > [javac] location: package input
> > [javac] import org.jdom.input.DefaultJDOMFactory;
> > [javac] ^
> > [javac]
> >
/data/gump/jakarta-velocity/bin/src/org/apache/velocity/anakia/AnakiaJDOMFac
tory.java:68:
> >
> > cannot resolve symbol
> > [javac] symbol : class DefaultJDOMFactory
> > [javac] location: class org.apache.velocity.anakia.AnakiaJDOMFactory
> > [javac] public class AnakiaJDOMFactory extends DefaultJDOMFactory
> > [javac] ^
> > [javac]
> >
> >
>
> --------------------------------------------------------------------------
-----------------------------------------
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
