I've tried the patch and it works for me too. Without it, it's a
painfully manual process. . .any maven developers out there care to take
a look and commit?
David
Rob Baily wrote:
If this is the wrong forum for this question please let me know and I'll
take whatever other path is recommende
> On 28/06/2006 8:01 PM, Jason van Zyl wrote:
> > I assume for this we are going to release a series of alphas? How
> > about for each major feature implemented we release an alpha?
>
> When we last discussed it on the development process, we
> talked about instead doing regular promotion of
[ http://jira.codehaus.org/browse/MNG-1517?page=all ]
David H. DeWolf updated MNG-1517:
-
Attachment: guide-helping.diff
> broken link to issue tracker on "How to Help" page
> ---
>
[ http://jira.codehaus.org/browse/MNG-1373?page=all ]
David H. DeWolf updated MNG-1373:
-
Attachment: introduction-to-repositories.diff
> Broken links and improperly formatted headings in
> http://maven.apache.org/guides/introduction/introduct
[ http://jira.codehaus.org/browse/MNG-1278?page=comments#action_53387 ]
David H. DeWolf commented on MNG-1278:
--
Just clicked through this entire page and I didn't find any broken links. This
issue can probably be closed.
> Broken Links on
[ http://jira.codehaus.org/browse/MNG-1178?page=comments#action_50477 ]
David H. DeWolf commented on MNG-1178:
--
I have sporadically received this error message using both maven-2.0 and the
latest trunk revision 332027 (on 11/09/2005). In 2.0 this is
directory structure invalid for legacy deploy
-
Key: MNG-731
URL: http://jira.codehaus.org/browse/MNG-731
Project: Maven 2
Type: Bug
Versions: 2.0-alpha-3
Reporter: David H. DeWolf
When utilizing a "l
