The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 21 Aug 2003 7:51 PM
Body:
do we need better documentation for this feature?
-
View the issue:
http://jira.codehaus.org/secur
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 21 Aug 2003 8:29 PM
Body:
The patch failed to apply
C:\source\maven>patch < c:\temp\javadoc
Hmm... Looks like a unified diff to me...
The text leading up to this was:
---
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Thu, 21 Aug 2003 8:43 PM
I've applied the patch changes manually, and noticed I think a typo in properties.xml
in the maven.javadoc.offlineLinks section.
Can you please check it (looks ok to me!)
--
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 8:44 PM
Changes:
Version changed to 1.0-rc1
Version changed to 1.0-beta-10
Fix Version changed to 1.1
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 7:53 PM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, see:
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 8:12 PM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, see:
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 7:52 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
h
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-708
Here is an overview of the issue:
--
dion2003/08/21 18:34:09
Modified:src/plugins-build/javadoc plugin.jelly
src/plugins-build/javadoc/xdocs properties.xml
Log:
Fix for MAVEN-694
Thanks to Martin Skopp.
Patch was applied with some changes
Revision ChangesPath
1.18 +35 -3 ma
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 8:10 PM
Comment:
A patch would be even greater
Changes:
Fix Version changed to 1.1
-
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 8:00 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
h
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 7:59 PM
Changes:
Version changed to 1.0-rc1
Version changed to 1.0-beta-10
Fix Version changed to 1.0-rc1
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Thu, 21 Aug 2003 7:57 PM
Patch applied, thanks
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-705
Here is a
dion2003/08/21 17:47:47
Modified:src/plugins-build/plugin plugin.jelly
Log:
Apply patch for MAVEN-705.
Thanks to David Zeleznik
Revision ChangesPath
1.12 +7 -0 maven/src/plugins-build/plugin/plugin.jelly
Index: plugin.jelly
==
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 7:51 PM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, see:
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 21 Aug 2003 7:48 PM
Body:
I added maven.javadoc.additionalparam=-charset ISO-8859-2
to my project.properties and it works fine.
Try maven.javadoc.additionalparam=-charset UTF-8
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-707
Here is an overview of the issue:
--
evenisse2003/08/21 15:48:43
Modified:src/test/java/org/apache/maven/project BuildTest.java
Removed: src/java/org/apache/maven/project TestResource.java
Log:
Remove old deprecated TestResource class.
Revision ChangesPath
1.4 +0 -6 maven/src/test/java/org/a
+1 makes it easier to track what needs to be uploaded. Also, maybe allow
people to take turns dealing with upload requests so it doesn't all land on
just a couple people.
Eric
> -Original Message-
> From: Martin Skopp [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 21, 2003 11:14 AM
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-706
Here is an overview of the issue:
--
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-705
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Martin Skopp (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 12:04 PM
Comment:
Here's my patch, dion. Finished cleaning up and documenting faster I first thought
It covers offline javadoc generation as well as offline generation
The following comment has been added to this issue:
Author: Simon Matic Langford
Created: Thu, 21 Aug 2003 1:09 PM
Body:
Martin,
(almost) looks fine.
i say almost, in that when you're behind an authentication proxy, maven will still go
through it, only javadoc won't. Thus, we ru
The following comment has been added to this issue:
Author: Ryan Hoegg
Created: Thu, 21 Aug 2003 1:10 PM
Body:
Re: the taglib. I am new to jelly, so I wasn't aware this was even possible. Perhaps
someone more experienced with jelly can help out? I was under the impression that
There's a component under the Maven project called "Repo Jar Requests"
for just that purpose. I'd probably call it as "Task" as far as the
type of issue it should be.
Since Jira notifies the list, going via Jira accomplishes both dev@
notification and archival of the request (and who made it) in
+0 from me
(yeah I'm lazy, and I want to see more people +0ing things rather than
+1 and then not helping)
Martin Skopp wrote:
On Wed, 2003-08-20 at 01:48, [EMAIL PROTECTED] wrote:
So send me a patch to update the docs and have a vote up here.
Ok guys, please vote!
Shall the preferred
The following comment has been added to this issue:
Author: Martin Skopp
Created: Thu, 21 Aug 2003 11:30 AM
Body:
Dear dion,
I finished programming. Will upload the patch as soon as I cleaned up the code and
finished the doc!
P.S.: gaining commit rights would help this be done fa
The following issue has been updated:
Updater: David Zeleznik (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 10:11 AM
Comment:
Patch file for src/plugins-build/plugin/plugin.jelly r1.7.2.1 (the MAVEN_RC1_STABLE
branch).
Changes:
Attachment changed to install-plu
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-703
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author:
Created: Thu, 21 Aug 2003 8:45 AM
Body:
Making a tag lib in the same fashion as the plexus plugin is the best approach. Then
in each plugin that may wish to use genapp they can just provide the necessary
parameters.
---
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-704
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Michael Brown (mailto:[EMAIL PROTECTED])
Date: Thu, 21 Aug 2003 7:47 AM
Comment:
Here's the patch - just set maven.site.deploy.method=ftp and the ftp password in
maven.password.
Changes:
Attachment changed to patch.txt
The following comment has been added to this issue:
Author: Brian Ewins
Created: Thu, 21 Aug 2003 7:19 AM
Body:
Just a comment on the war:genapp and the like. I don't think this is a brilliant idea.
Consider where for example you have a 'struts based webapp' template, a 'tapestry
The following comment has been added to this issue:
Author: Rafal Krzewski
Created: Thu, 21 Aug 2003 4:30 AM
Body:
I've just noticed a problem with the feature I've proposed (after some discussions
with Norbert Pabis).
Extending a project in the current implementation involves in
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 21 Aug 2003 3:51 AM
Body:
I think the best way for create a genapp functionality in several plugin is to create
a jelly tag that include your actual code. Then, all plugins that want to an a
abarantsev2003/08/21 01:41:21
Removed: src/plugins-build/xdoc/src/plugin-resources/jelly-templates
dependencies.xml issue-tracking.xml
maven-reports.xml team-list.xml cvs-usage.xml
index.xml mail-lists.xml project-in
evenisse2003/08/21 02:24:36
Modified:.project.xml
Log:
Fix viewcvs url.
Revision ChangesPath
1.298 +1 -1 maven/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/project.xm
evenisse2003/08/21 02:01:08
Modified:src/plugins-build/xdoc plugin.jelly
Log:
set the default value of state in itemLink tag to none.
Revision ChangesPath
1.42 +3 -0 maven/src/plugins-build/xdoc/plugin.jelly
Index: plugin.jelly
===
On Wed, 2003-08-20 at 01:48, [EMAIL PROTECTED] wrote:
> So send me a patch to update the docs and have a vote up here.
Ok guys, please vote!
Shall the preferred method for upload request be changed to create a
JIRA issue (is currently: send mail to maven-dev)?
> > Martin Skopp <[EMAIL PROTECTED
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 21 Aug 2003 2:21 AM
Body:
ok, how about:
pom:ant-1.5.3
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key
The following comment has been added to this issue:
Author: Rafal Krzewski
Created: Thu, 21 Aug 2003 2:58 AM
Body:
Do you mean defining custom URL schema for refferring to artifacts
available through maven?
If we decide to do that, that notation should be also used for
declaring
Thanks!!
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
[EMAIL PROTECTED] wrote on 21/08/2003 06:19:06 PM:
> evenisse2003/08/21 01:19:06
>
> Modified:xdocs/reference project-descriptor.xml
>xdocs/start integrate.xml
> Log:
>
evenisse2003/08/21 01:19:06
Modified:xdocs/reference project-descriptor.xml
xdocs/start integrate.xml
Log:
revert modification. Relative path works fine with Brett patch, and it's the prefer
way.
Revision ChangesPath
1.25 +0 -2 maven/xdocs/refere
The following comment has been added to this issue:
Author: Rafal Krzewski
Created: Thu, 21 Aug 2003 2:16 AM
Body:
According to the specs maven.repo.remote may contain a comma separated list of URL, so
this is a bad idea.
What's more you've put information about remote repo orgai
44 matches
Mail list logo
