Dear Gumpmeisters,
The following 3 nags should have been sent
*** G U M P
[EMAIL PROTECTED]: jakarta-tapestry/ognl failed
[EMAIL PROTECTED]: javasrc/javasrc failed
[EMAIL PROTECTED]: jrefactory/jrefactory-pretty failed
**
> Agreed.
>
> > I think the real challenge is at the project level, projects need to
> > establish naming consistent with their Umbrella group, this is a real
> > growing pain at this point, I suspect eventually the entire Jakarta
> > Commons will need to migrate to
> > jakarta-commons/jakarta-com
Agreed.
> I think the real challenge is at the project level, projects need to
> establish naming consistent with their Umbrella group, this is a real
> growing pain at this point, I suspect eventually the entire Jakarta
> Commons will need to migrate to
> jakarta-commons/jakarta-commons-foo-x
ajack 2004/05/18 15:51:00
Modified:python/gump/syndication Tag: MultiRunner rss.py atom.py
syndicator.py abstract.py
Log:
Safety check-in...
Revision ChangesPath
No revision
No revision
1.23.2.4 +7 -8
sorry, if i came over too strongly. it was the point i was trying to
emphasis (rather than take pot shots at anyone).
gump's certainly proved it's worth (once again) in this case. thanks
for all the hard work that you (and the rest of the gump community)
have put into raising gump back from the
> > Gump isn't just a build script, it is that plus the effects/outcomes of
> > communities trying to get/stay aligned. We can't expect folks to drop
> > what they are doing the second something comes up, it just doesn't work
> > that way in the OSS world. Much as I might think that the C-L folks
o
On 17 May 2004, at 17:20, Adam R. B. Jack wrote:
Given that you have supplied a corrective patch 5 days ago, and that
no commons-logging developer has picked it up, do you think pretending
the problem does not exist is the wisest approach?
It isn't quite that simple, although your comments make me
On Wednesday 19 May 2004 03:19, Adam R. B. Jack wrote:
> I posted to avalon-dev as you posted here. Log4j changed underneath you, I
> suspect...
> [javac] import org.apache.log4j.spi.RootCategory;
> [javac] location: class
> org.apache.avalon.excalibur.logger.log4j.Log4JConfAdapter
> [
ajack 2004/05/18 13:10:45
Modified:python/gump/results Tag: MultiRunner resulter.py
python/gump Tag: MultiRunner update.py debug.py build.py
integrate.py check.py
python/gump/core Tag: MultiRunner gumprun.py misc.py
p
ajack 2004/05/18 13:08:17
gump/python/gump/runner - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
of reusable components.
> >
> > The current state is 'Failed', for reason 'Build Failed'
> >
> > Full details are available at:
> >
> >
http://brutus.apache.org:8080/gump/avalon-excalibur/excalibur-logger/index.
> >html That said, some snipp
excalibur-logger/index.
>html That said, some snippets follow:
>
>
> Gump provided these annotations:
> - Info - Sole jar [excalibur-logger-20040518.jar] identifier set to
> project name - Info - Optional dependency checkstyle prerequisite failed
> with reason build failed - Info
> Avalon is about to move to subversion.
> Is there anything about Gump that we should know about in this respect?
Not a great deal, we'll work with you to point your repository to an SVN
one:
http://brutus.apache.org/gump/public/gump_repo/avalon.html
like (say)
http://brutus.apache.org
Hi,
Avalon is about to move to subversion.
Is there anything about Gump that we should know about in this respect?
Cheers
Niclas
--
+--//---+
/ http://www.bali.ac/
/ http://niclas.hedhman.org /
+--//---+
---
> I joined the gump list because turbine dev list was getting lots of errors
> about the jakarta-turbine-tdk and jakarta-turbine-statum projects failing
> (and other jakarta-turbine-* projects).
Thanks for doing that.
> At this point, I haven't been recieving errors, and I checked, and this is
>
Hi all,
I joined the gump list because turbine dev list was getting lots of errors
about the jakarta-turbine-tdk and jakarta-turbine-statum projects failing
(and other jakarta-turbine-* projects).
At this point, I haven't been recieving errors, and I checked, and this is
due to commons-logging fa
Brett Porter wrote:
Yup, I think we need ASF-wide artefact ids (within group
ids). I'd like to think the community and/or communities can
come to agreement on what the values are, and if that means
defaulting to what Maven/Ibiblio already have, then so be it.
Consistency is the key more than a
At 08:23 AM 5/18/2004, Paul Smith wrote:
[cross posting to both lists, as I am hoping this would give me more chance
of someone knowing what to do here]
As discussed previously, I am keen to integrate log4j Chainsaw v2 and VFS,
to take advantage of VFS's features of transparency of where the files
18 matches
Mail list logo
