-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tried the user list with no response, so I figured I'd go the dev route.
Is there any place to get this outside of codehaus? Or a specific URL at
codehaus to use (as it was noted that project specific URLs will work
when the main URLs won't)?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Porter wrote:
Hi,
I think we all agree we need more keen people helping out with plugins!
Jesse has been contributing on the users list and mojo project for some
time, and has recently contributed several patches to the Apache Maven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Porter wrote:
Hi,
Like John, Deng has been helping out on the users list, plugins and the
repository manager for some time. I'd like to propose we give her commit
access.
[ ] +1
[ ] +0
[ ] -1
Cheers,
Brett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 (non-binding)
John Casey wrote:
Hi again,
I wanted to let everyone know that we've got the latest round of
regressions fixed, including:
* Fabrizio's lingering path problems from MNG-2006
* MNG-2136
* MNG-2124
* MNG-2130
These fixes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All in all, I'd have to agree with the sentiments of this. I don't think
anything should be taken personally although I know some personalities
might be inclined to react emotionally at the words used, but if you
look at the sentiment I believe it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse Kuhnert wrote:
I think what everyone is saying sounds more or less correct, but what is the
solution then?
If they can't rely on a runtime container to host the site, options become
MUCH more limited.
Complaints about the UI are fine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It uses anakia to transform, but in true Maven spirit it should be able
to be done - with a plugin. ;-) And maybe maven-site is suited to it
just fine (not a maven-site expert for user sites AT ALL - I'm with
Jesse here that so much more 'whiz-bang'
ScmReport doesn't accept non-artifactId URLs
Key: MPIR-33
URL: http://jira.codehaus.org/browse/MPIR-33
Project: Maven 2.x Project Info Reports Plugin
Type: Bug
Versions: 2.0-beta-3
Reporter: Brian K. Wallace
[ http://jira.codehaus.org/browse/MNG-2129?page=all ]
Brian K. Wallace updated MNG-2129:
--
Attachment: MNG-2129-maven-site.patch
generated source repo page is misleading when added to the general site
[ http://jira.codehaus.org/browse/MPIR-33?page=comments#action_60395 ]
Brian K. Wallace commented on MPIR-33:
--
I believe I have inaccurately reported this issue. The issue appears to be more
with documentation of how/why rather than functional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wendy Smoak wrote:
On 3/7/06, Brett Porter [EMAIL PROTECTED] wrote:
* I'm still a little torn on where plugin docs go. No hurry on this, but
something to ponder. We definitely need to make the references for those
integrate better. Site/skin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wendy Smoak wrote:
On 3/7/06, Brian K. Wallace [EMAIL PROTECTED] wrote:
While I agree that it would be nice to have the 'latest and greatest'
docs on the main site, I don't believe having them as the only
documentation is a good idea at all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Porter (JIRA) wrote:
[ http://jira.codehaus.org/browse/MPA-50?page=all ]
Brett Porter closed MPA-50:
---
Resolution: Fixed
create new Maven dev lists
--
Key:
[ http://jira.codehaus.org/browse/MNG-808?page=comments#action_60298 ]
Brian K. Wallace commented on MNG-808:
--
Aside from the Why Choose/Use Maven, is there really a need for the Why XXX
sections? I view Why perform Unit Testing or Why use CI as issues
14 matches
Mail list logo