[jira] Closed: (MAVEN-645) add "How do I upload to Ibiblio" to FAQ

Message: The following issue has been closed. Resolver: Ben Walding Date: Fri, 1 Aug 2003 5:38 PM Applied. Thanks. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-645 Here is an overv

cvs commit: maven/xdocs faq.fml

bwalding2003/08/01 15:33:53 Modified:xdocsfaq.fml Log: Added how to upload to ibiblio entry PR: MAVEN-645 Submitted by: Martin Skopp Revision ChangesPath 1.3 +7 -0 maven/xdocs/faq.fml Index: faq.fml

is HEAD relatively safe to use again?

I know after the refactoring last week it was not recommended that HEAD be touched for a while. Is it relatively usable again? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (MAVEN-645) add "How do I upload to Ibiblio" to FAQ

The following issue has been updated: Updater: Martin Skopp (mailto:[EMAIL PROTECTED]) Date: Fri, 1 Aug 2003 8:01 AM Comment: ... and here's the patch to apply to faq.fml Pretty easy, just need a commiter since I don't heve the rights... Changes: Attachment changed

[jira] Created: (MAVEN-645) add "How do I upload to Ibiblio" to FAQ

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-645 Here is an overview of the issue: --

Re: [jira] Closed: (MAVEN-633) Contributing an ejb:ejb-client goal

Thanks dion! > Message: > >The following issue has been closed. > >Resolver: dion gillard >Date: Thu, 31 Jul 2003 11:34 PM > > Applied with fixes and docs > - > View the issue: > > http://jira.codehaus.org/secur

[jira] Updated: (MAVEN-639) Add maven.javadoc.overview property to the javadoc plugin

The following issue has been updated: Updater: Kai Runte (mailto:[EMAIL PROTECTED]) Date: Fri, 1 Aug 2003 3:37 AM Comment: For convenience I attached the patch. Changes: Attachment changed to javadoc.patch

[jira] Created: (MAVEN-644) Site "Project Documentation" content customization

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-644 Here is an overview of the issue: --

[jira] Created: (MAVEN-643) ejb-2.1.jar cannot be downloaded due to incorrect location on ibiblio

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-643 Here is an overview of the issue: --

cvs commit: maven/src/java/org/apache/maven/plugin JellyPlugin.java PluginManager.java

dion2003/08/01 00:39:24 Modified:src/java/org/apache/maven/plugin PluginManager.java Added: src/java/org/apache/maven/plugin JellyPlugin.java Log: Start to move plugin related processing into its own class. This leaves JellyScriptHousing as a very similar class, but wit

cvs commit: maven/src/java/org/apache/maven/jelly JellyUtils.java

dion2003/08/01 00:38:02 Modified:src/java/org/apache/maven/jelly JellyUtils.java Log: Fix bug in not performing same logic independent of params Revision ChangesPath 1.15 +2 -2 maven/src/java/org/apache/maven/jelly/JellyUtils.java Index: JellyUtils.java

[jira] Created: (MAVEN-642) Add a class/category to POM dependecies

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-642 Here is an overview of the issue: --

Re: Fixes and changes for maven 1.0

Rafal Krzewski wrote: > [EMAIL PROTECTED] wrote: > >>I've added the ability for normal jira users to edit the issues. > > > That will certainly make nominating bugs easier, but on the second > though is this a good idea in the long run? Sheduling isssues is > the responsibility of the developmen

Re: Fixes and changes for maven 1.0

[EMAIL PROTECTED] wrote: > I've added the ability for normal jira users to edit the issues. That will certainly make nominating bugs easier, but on the second though is this a good idea in the long run? Sheduling isssues is the responsibility of the development team, not the users. We can try how