We are pleased to announce the Maven XDoc Plugin 1.10 release!
http://maven.apache.org/maven-1.x/plugins/xdoc/
Convert xdocs into HTML.
===
Changes in this version include:
New Features:
o Add a public DTD
t
casting an explicit vote.
I'll do the release ASAP, voting thread is here:
http://www.nabble.com/-vote---m1--release-xdoc-plugin-1.10-t1743303.html
Cheers,
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED] For addi
st
Cc: Maven Project Management Committee List
Subject: [Result] [vote] [m1] release xdoc-plugin-1.10
We had a bit of noise on this thread so I hope I quote the result
accurately, please correct me if something's wrong.
There are 3 binding +1's (Stephane, Arnaud, Lukas) and two people (
solved, I'm +1. The rest
seems to be Commons specific, which shouldn't hold back the release
of the xdoc plugin.
I deployed another snapshot, please test.
Cheers,
-Lukas
Without maven.xdoc.distributionUrl set the downloads link no longer
show up in either of the commons components
M
To: Maven Developers List
Cc: Maven Project Management Committee List
Subject: [Result] [vote] [m1] release xdoc-plugin-1.10
We had a bit of noise on this thread so I hope I quote the result
accurately, please correct me if something's wrong.
There are 3 binding +1's (Stephane, Arnaud,
I don't have a vote! :-) But it would be +1. Thanks Lukas...
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 6:13 PM
To: Maven Developers List
Cc: Maven Project Management Committee List
Subject: [Result] [vote] [m1] release xdoc-p
licit vote.
I'll do the release ASAP, voting thread is here:
http://www.nabble.com/-vote---m1--release-xdoc-plugin-1.10-t1743303.html
Cheers,
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
;
>>>
>>>
>>>> If the Downloads link problem above and another problem I found
>>>> (will send another mail about that) can be solved, I'm +1. The rest
>>>> seems to be Commons specific, which shouldn't hold back the release
>&g
solved, I'm +1. The rest
seems to be Commons specific, which shouldn't hold back the release
of the xdoc plugin.
I deployed another snapshot, please test.
Cheers,
-Lukas
Without maven.xdoc.distributionUrl set the downloads link no longer
show up in either of the commons components
which shouldn't hold back the release of the
xdoc plugin.
I deployed another snapshot, please test.
Cheers,
-Lukas
Without maven.xdoc.distributionUrl set the downloads link no longer show
up in either of the commons components. So thats good.
But if I set
maven.xdoc.distributi
Lukas Theussl wrote:
If the Downloads link problem above and another problem I found (will
send another mail about that) can be solved, I'm +1. The rest seems to
be Commons specific, which shouldn't hold back the release of the xdoc
plugin.
I deployed another snapshot, p
>> Do you have a component where there is a title? - I don't see one
>> anywhere, but you have that problem already on your current site (eg
>> http://jakarta.apache.org/commons/beanutils/dependencies.html) which
>> was built with xdoc-plugin-1.9.2 (I presume). It's du
Check the plugins that use plexus-utils at [1] and try to upgrade at
least those (again: careful with the artifact plugin).
Cheers,
-Lukas
[1]
http://maven.apache.org/maven-1.x/plugins/bundled/dependency-convergence-report.html
Dennis Lundberg wrote:
OK, maven-plugins works for me when I up
-tasklist-plugin-2.4
maven-test-plugin-1.6.2
maven-tjdo-plugin-1.0.0
maven-uberjar-plugin-1.2
maven-vdoclet-plugin-1.2
maven-war-plugin-1.6.1
maven-webserver-plugin-2.0
maven-wizard-plugin-1.1
maven-xdoc-plugin-1.10-SNAPSHOT
eady on your current site (eg
>> http://jakarta.apache.org/commons/beanutils/dependencies.html) which
>> was built with xdoc-plugin-1.9.2 (I presume). It's due to an issue
>> with your custom site.jsl (commons-site.jsl) file, it doesn't take
>> into account that the sta
Do you have a component where there is a title? - I don't see one
anywhere, but you have that problem already on your current site (eg
http://jakarta.apache.org/commons/beanutils/dependencies.html) which
was built with xdoc-plugin-1.9.2 (I presume). It's due to an issue
with y
If the Downloads link problem above and another problem I found (will
send another mail about that) can be solved, I'm +1. The rest seems to
be Commons specific, which shouldn't hold back the release of the xdoc
plugin.
I deployed another snapshot, please test.
Chee
erjar-plugin-1.2
maven-vdoclet-plugin-1.2
maven-war-plugin-1.6.1
maven-webserver-plugin-2.0
maven-wizard-plugin-1.1
maven-xdoc-plugin-1.10-SNAPSHOT
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
-plugin-1.2
maven-vdoclet-plugin-1.2
maven-war-plugin-1.6.1
maven-webserver-plugin-2.0
maven-wizard-plugin-1.1
maven-xdoc-plugin-1.10-SNAPSHOT
--
Dennis Lundberg
Lukas Theussl wrote:
I'd rather suspect a classloader issue. Can you send me the list of your
installed plugins (mav
I'd rather suspect a classloader issue. Can you send me the list of your
installed plugins (maven -i)? Because of the single classloader, another
plugin can load the required class (StringUtils), which in the xdoc
plugin, should be from commons.lang.StringUtils.
-Lukas
Dennis Lun
PROTECTED]> wrote:
Right on,
I replaced
by
and now it works also with m1.0.2. The point is: the empty function is
used all over the place in the xdoc plugin (plugin.jelly, site.jsl,
various templates), do I have to replace it everywhere?
-Lukas
Arnaud HERITIER wrote:
> In the
Right on,
I replaced
by
and now it works also with m1.0.2. The point is: the empty function is
used all over the place in the xdoc plugin (plugin.jelly, site.jsl,
various templates), do I have to replace it everywhere?
-Lukas
Arnaud HERITIER wrote:
In the Jelly release bundled in
at com.werken.forehead.Forehead.main(Forehead.java:581)
File.. C:\Documents and
Settings\dlg01\.maven\cache\maven-xdoc-plugin-1.10-SNAPSHOT\plugin.jelly
Element... velocity:merge
Line.. 728
Column 13
Invocation of method 'anonymousAccessCVS' in class
org.apache.maven.xdoc.util.Scm
I cannot reproduce this one, neither with m1.0.2 nor m11b3. I'd be
surprised, too, as the xdoc-plugin doesn't use plexus. Can you run with
-e, to see the full stack trace?
-Lukas
Dennis Lundberg wrote:
I decided to try out a Sourceforge project that I work on, but it failed
mise
In the Jelly release bundled in maven 1.0.x there was some bugs in the
empty() function.
cheers
Arnaud
On 6/12/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> I just did a "maven clean site" and I still get the "Downloads" link
> when building it using the 1.10-SNAPSHOT version.
>
Ok, I can
I just did a "maven clean site" and I still get the "Downloads" link
when building it using the 1.10-SNAPSHOT version.
Ok, I can reproduce it now using maven-1.0.2, I don't see it with
m1.1-beta-3. Certainly a jelly issue, I'll look into it.
-Lukas
-
maven-plugins from sourceforge.net
* cd maven-plugins\tasks
* maven site
This is the results I get:
...
xdoc:generate-from-pom:
[echo] Generating xdocs from POM ...
BUILD FAILED
File.. C:\Documents and
Settings\dlg01\.maven\cache\maven-xdoc-plugin-1.10-SNAPSHOT\plugin.jelly
El
, however, I don't think this
behavior has changed since xdoc-1.9.2.
Beanutils has a dependency on maven-xdoc-plugin 1.9.2 so you need to
either change the version to 1.10-SNAPSHOT or remove the dependency. I
forgot to mention that.
I just did a "maven clean site" and I still get the
project name, on the scm-usage page.
Do you have a component where there is a title? - I don't see one
anywhere, but you have that problem already on your current site (eg
http://jakarta.apache.org/commons/beanutils/dependencies.html) which was
built with xdoc-plugin-1.9.2 (I presume). It
on't see one
anywhere, but you have that problem already on your current site (eg
http://jakarta.apache.org/commons/beanutils/dependencies.html) which was
built with xdoc-plugin-1.9.2 (I presume). It's due to an issue with your
custom site.jsl (commons-site.jsl) file, it doesn'
Here's some feedback on the new xdoc plugin. I've ran it on a couple of
Jakarta Commons components, which have various degrees of
xdoc-complexity. This is what has caught my eye:
- There is no longer a pdf.gif file under /images/. None of the tested
products has PDF docs generate
-plugin-1.10
Hi again,
This is a big one so I do it separately. The xdoc-plugin-1.10 has been
feature complete since a while, but with the re-introduction of xerces into
the core and the upcoming dom4j upgrade (which it should be compatible
with), it is only now that I'd like to release it.
I'll vote based on whether it works in Commons.
Lukas Theussl wrote:
No problem Dennis, I guess I can wait those few more days, too. ;)
I'd certainly appreciate the feedback though.
Cheers,
-Lukas
Dennis Lundberg wrote:
Lukas,
I would really like to try this version out on Jakarta Commons
No problem Dennis, I guess I can wait those few more days, too. ;)
I'd certainly appreciate the feedback though.
Cheers,
-Lukas
Dennis Lundberg wrote:
Lukas,
I would really like to try this version out on Jakarta Commons
components, but I won't have enough time to do it until Sunday.
---
Lukas,
I would really like to try this version out on Jakarta Commons
components, but I won't have enough time to do it until Sunday.
--
Dennis Lundberg
Lukas Theussl wrote:
Hi again,
This is a big one so I do it separately. The xdoc-plugin-1.10 has been
feature complete since a
+1
Stéphane
On 6/6/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
Hi again,
This is a big one so I do it separately. The xdoc-plugin-1.10 has been
feature complete since a while, but with the re-introduction of xerces
into the core and the upcoming dom4j upgrade (which it should be
comp
Hi again,
This is a big one so I do it separately. The xdoc-plugin-1.10 has been
feature complete since a while, but with the re-introduction of xerces
into the core and the upcoming dom4j upgrade (which it should be
compatible with), it is only now that I'd like to release it. Ther
[ http://jira.codehaus.org/browse/MPXDOC-134?page=all ]
Lukas Theussl closed MPXDOC-134:
Resolution: Won't Fix
Obsoleted by MPXDOC-130
> rewrite - scm support for xdoc plugin
> -
>
>
[ http://jira.codehaus.org/browse/MPXDOC-183?page=all ]
Lukas Theussl closed MPXDOC-183:
Resolution: Fixed
Fix Version: 1.10
Patch applied. Thanks!
> Enable User Templates in XDOC plugin
>
>
>
[ http://jira.codehaus.org/browse/MPXDOC-183?page=all ]
Lukas Theussl moved MAVEN-1725 to MPXDOC-183:
-
Workflow: jira (was: Maven)
Key: MPXDOC-183 (was: MAVEN-1725)
Project: maven-xdoc-plugin (was: Maven)
> Enable U
ates in XDOC plugin
>
>
> Key: MAVEN-1725
> URL: http://jira.codehaus.org/browse/MAVEN-1725
> Project: Maven
> Type: New Feature
> Reporter: Niall Pemberton
> Priority: Minor
> Attachments: x
Enable User Templates in XDOC plugin
Key: MAVEN-1725
URL: http://jira.codehaus.org/browse/MAVEN-1725
Project: Maven
Type: New Feature
Reporter: Niall Pemberton
Priority: Minor
Attachments: xdoc-user-template.patch
It
http://maven.apache.org/reference/plugins/xdoc/maven-navigation-${xdoc-plugin-release}.xsd
> Move navigation.xsd in the xdoc plugin
> --
>
> Key: MAVEN-1685
> URL: http://jira.codehaus.org/browse/MAVEN-1685
> Project: Mav
Move navigation.xsd in the xdoc plugin
--
Key: MAVEN-1685
URL: http://jira.codehaus.org/browse/MAVEN-1685
Project: Maven
Type: Task
Reporter: Arnaud Heritier
Assigned to: Arnaud Heritier
Priority: Minor
Move the
+1
> If some of you can test it, and especially with maven 1.0 he would be nice
> because I hadn't the time to do it!
Works for me.
Regards,
Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
Author: aheritier
Date: Mon Sep 5 13:56:42 2005
New Revision: 278836
URL: http://svn.apache.org/viewcvs?rev=278836&view=rev
Log:
[maven-scm] copy for tag maven-xdoc-plugin-1.9.2
Added:
maven/maven-1/plugins/tags/maven-xdoc-plugin-1.9.2/
- copied from r278824, maven/maven-1/plu
Arnaud HERITIER <[EMAIL PROTECTED]> writes:
>My +1
Please. +1
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED]+49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Deve
+1 (finally)
Thanks Arnaud!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
Recently we (Lukas and me) fixed a lot of issues on the xdoc plugin and we
would like to release it to incorporate it in maven 1.1 beta 2.
If some of you can test it, and especially with maven 1.0 he would be nice
because I hadn't the time to do it!
You'll find the future doc
Just a couple though: 154 and 162 are scheduled for 1.9.2 and don't have
patches.
I'll do a patch for 154 right now. 162 I couldn't reproduce as I
mentioned in my comment but I still have to investigate a bit more. I'll
do it today.
Lukas
--
e to
>> include the xdoc plugin v 1.9.2 in the release. Could you give us an
>> ETA?
>>
>>
>
> All the issues that are scheduled for 1.9.2 are resolved, but I still
> don't have my commit privs. I hope that Arnaud can apply the patches
> if I don't
We'd like to release Maven 1.1 beta 2 ASAP. We think it would be nice to
include the xdoc plugin v 1.9.2 in the release. Could you give us an ETA?
All the issues that are scheduled for 1.9.2 are resolved, but I still
don't have my commit privs. I hope that Arnaud can apply the
rote:
>
> Hi Lukas/Arnaud,
>
> We'd like to release Maven 1.1 beta 2 ASAP. We think it would be nice to
> include the xdoc plugin v 1.9.2 in the release. Could you give us an ETA?
>
> Thanks
> -Vincent
>
>
> ---
Hi Lukas/Arnaud,
We'd like to release Maven 1.1 beta 2 ASAP. We think it would be nice to
include the xdoc plugin v 1.9.2 in the release. Could you give us an ETA?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROT
[ http://jira.codehaus.org/browse/MPXDOC-13?page=all ]
Lukas Theussl closed MPXDOC-13:
---
Resolution: Fixed
This patch has been applied a long time ago (revision 114649).
> Add a tag to the xdoc plugin to easily transform a file using the site st
Hi Henning,
I'm sorry but I didn't see your mail (mixed with all issues).
Like a lot of committers I have a day job (not maven related), a familly and
I receive hundreds mails each day.
As Brett told it, the xdoc plugin is certainly the more difficult plugin to
maintain and ac
Lukas Theussl wrote:
>
> Woops, seems I'm getting quite a share of high expectations and
> pressure right on my first day of work ... at least I know now why
> I've been hired ;-) .
>
> But yes, sure we'll get it fixed.
>
:)
I just noticed that you started going through issues. Thanks - it is
muc
We'll get it fixed. Thanks to our recently elected committer
Lukas, it seems we have someone looking after getting xdoc back under
control.
Woops, seems I'm getting quite a share of high expectations and pressure
right on my first day of work ... at least I know now why I've been
hired ;
Henning P. Schmiedehausen wrote:
>It's ok. I vented some steam and I apologize. I didn't open another
>issue because there was already one opened in June (MPXDOC-148) and
>closed by Arnaud on Jun 28th. But after the bug was closed, nothing
>happened. Shall we reopen the issues until something happ
However, a polite request in June would be more helpful than this
message which I find rather abrasive.
In Henning's defence: he did already post a (polite) request (
http://marc.theaimsgroup.com/?l=turbine-maven-dev&m=112316469012033&w=2
) which remained unanswered. Anyway, I think we coul
ers. It did not work. I was frustrated. End of
story.
>In the mean time:
>maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin
>-Dversion=1.8
>If you had no specific reason to upgrade in the first place, this is
>obviously the more sensible approach. But we'll get
.org/repository/
>Great advice. Not.
>
>
This is not helpful. I'm all for constructive criticism and getting
called on mistakes made. But this along with others just sets a negative
tone for the email.
>This is a plea for an immediate release of maven-xdoc-plugin
>1.9.2. I
Hi,
since June 9th, maven-xdoc-plugin 1.9.1 is the most current release of
the xdoc plugin. Ever since then, maven sites with things like
"???template.mail_lists.section.title???" pop up. Even on the maven
plugin site itself (see e.g. at the simian plugin at
http://maven.apache.org
[ http://jira.codehaus.org/browse/MPXDOC-13?page=all ]
Arnaud Heritier updated MPXDOC-13:
--
Assign To: (was: Arnaud Heritier)
> Add a tag to the xdoc plugin to easily transform a file using the site style
> and navi
[ http://jira.codehaus.org/browse/MPXDOC-134?page=all ]
Arnaud Heritier updated MPXDOC-134:
---
Assign To: (was: Arnaud Heritier)
> rewrite - scm support for xdoc plugin
> -
>
> Key
Author: brett
Date: Wed Jun 15 08:38:57 2005
New Revision: 190763
URL: http://svn.apache.org/viewcvs?rev=190763&view=rev
Log:
[maven-scm] copy for tag maven-xdoc-plugin-1.9.1
Added:
maven/maven-1/plugins/tags/maven-xdoc-plugin-1.9.1/
- copied from r190751, maven/maven-1/plugins/t
-117. Thanks to
Dennis Lundberg.
o Allow header images and links to use relative paths Issue: MPXDOC-115.
Thanks to Brent Worden.
To automatically install the plugin, type the following on a single line:
maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin
-Dversion=1.9
Author: brett
Date: Wed Jun 8 19:42:24 2005
New Revision: 189688
URL: http://svn.apache.org/viewcvs?rev=189688&view=rev
Log:
[maven-scm] copy for tag maven-xdoc-plugin-1.9
Added:
maven/maven-1/plugins/tags/maven-xdoc-plugin-1.9/
- copied from r189686, maven/maven-1/plugins/trunk/
Done.
Arnaud
>
>
> >I didn't see how to do it.
> >If you cannot, I implemented the fix in the xdoc plugin and
> I'll be able to commit it.
> >But I would prefer that we modify the model in 1.1 to match the 1.0.
> >
> >
> >
>
I didn't see how to do it.
If you cannot, I implemented the fix in the xdoc plugin and I'll be able to commit it.
But I would prefer that we modify the model in 1.1 to match the 1.0.
Oh, if you've already done that - go
ee how to do it.
If you cannot, I implemented the fix in the xdoc plugin and I'll be able to
commit it.
But I would prefer that we modify the model in 1.1 to match the 1.0.
Arnaud
-
To unsubscribe, e-mail: [EMAIL PROT
is that it could be better to copy existing services (getScmType, ...)
about SCM repositories from maven 1.0.2 core to the
maven 1.1 one (in an utilities class for example).
But if we do that we'll not be able to keep the compatibility for the xdoc
plugin with maven 1.1 and maven 1.0.2.
Th
ility for the xdoc
plugin with maven 1.1 and maven 1.0.2.
Thus I think that actually it is more interesting to have this code in the xdoc
plugin.
Thoughts ?
Arnaud
>
> Hi guys,
>
> Yesterday night I found a new issue with the xdoc plugin
> and maven 1.1.
> The gene
Hi guys,
Yesterday night I found a new issue with the xdoc plugin and maven 1.1.
The generated cvs-usage page is empty.
I quickly look at the problem and I think I found its origin.
In maven 1.0, we defined our own model for the POM, and some services were
added to the
ined.
http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk/project.xml
Cheers,
Vincent
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 02, 2005 8:57 AM
> To: Maven Developers List
> Subject: Re: [vote] release xdoc plugin 1.9
&g
Thursday, June 02, 2005 8:57 AM
> To: Maven Developers List
> Subject: Re: [vote] release xdoc plugin 1.9
>
> ok, so you can do it and release it for maven 1.0.2.
> We'll fix the problem with 1.1 after if necessary (except if you want to
> bundle it in 1.1-beta 1 ?).
> A
compatibility tests with maven 1.0.2 because actually I
> focus on maven 1.1.
> >
> >
> > Yesterday evening I found a problem but I didn't have the time (and I
> certainly can't do it today) to analyse it.
> > Can you try to launch "maven multiproject:
gins/trunk" directory with maven 1.1 and xdoc
plugin 1.9?
I have this error :
xdoc:jelly-transform:
About to use JSL stylesheet
file:/D:/Work/Data/maven/cache/maven-xdoc-plugin-1.9-SNAPSHOT/plugin-resources/site.jsl
[echo] en
[echo] The current Locale is the default one
[
oject:site" (or maven site) in the
"plugins/trunk" directory with maven 1.1 and xdoc
plugin 1.9?
I have this error :
xdoc:jelly-transform:
About to use JSL stylesheet
file:/D:/Work/Data/maven/cache/maven-xdoc-plugin-1.9-SNAPSHOT/plugin-resources/site.jsl
[echo] en
[e
On Thu, 2005-06-02 at 11:22 +1000, Brett Porter wrote:
> [X] +1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
The xdoc plugin has grown internationalisation support and had some
other fixes.
Arnaud, are you happy it is ready for release? I see you've given it a
once over since. Is it being tested against Maven 1.0.2?
[ ] +1
[ ] +0
[ ] -1
From me, I think it is a +1 now. I am happy to d
Author: brett
Date: Thu May 12 17:58:53 2005
New Revision: 169915
URL: http://svn.apache.org/viewcvs?rev=169915&view=rev
Log:
the updated plugin list
Modified:
maven/components/trunk/maven-site/src/site/xdoc/plugin-list.xml
Modified: maven/components/trunk/maven-site/src/site/xdoc/pl
nd a source change not being reflected in the
generated site.
I went ahead and submitted a JIRA issue with a patch.
(http://jira.codehaus.org/browse/MPXDOC-141)
This is what I have so far, but hopefully someone who understands the XDOC
plugin better than me will improve the patch and apply it.
-
- Original Message -
From: "M. Sean Gilligan" <[EMAIL PROTECTED]>
To: dev@maven.apache.org
Subject: XDOC Plugin Optimization
Date: Fri, 22 Apr 2005 07:08:21 -0700
>
> I've wanted to speed up the "maven site" command be eliminating tranforms of
> unchanged do
I've wanted to speed up the "maven site" command be eliminating tranforms of
unchanged documents for some time now. I added some code to the XDOC plugin
that seems to work:
${outFile} is up to date.
DO TRANSFORM AS BEFORE
Is there anyt
[ http://jira.codehaus.org/browse/MPXDOC-139?page=history ]
Brett Porter resolved MPXDOC-139:
-
Resolution: Duplicate
Assign To: (was: Arnaud HERITIER)
bug in maven core, already fixed for 1.1
> XDoc Plugin not found after Ca
[ http://jira.codehaus.org/browse/MPXDOC-139?page=history ]
Brett Porter closed MPXDOC-139:
---
> XDoc Plugin not found after Cache Inavlidation
> --
>
> Key: MPXDOC-139
>
XDoc Plugin not found after Cache Inavlidation
--
Key: MPXDOC-139
URL: http://jira.codehaus.org/browse/MPXDOC-139
Project: maven-xdoc-plugin
Type: Bug
Versions: 1.8
Reporter: Andreas Schönknecht
Assigned to
rewrite - scm support for xdoc plugin
-
Key: MPXDOC-134
URL: http://jira.codehaus.org/browse/MPXDOC-134
Project: maven-xdoc-plugin
Type: Improvement
Reporter: Henning Schmiedehausen
Assigned to: Arnaud HERITIER
Attachments
Vincent Massol wrote:
Hi,
I'm trying to build the xdoc plugin from SVN trunk. I got:
C:\dev\maven\maven-1\plugins\xdoc>maven clean plugin:install
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Tentative de tΘlΘ
Hi,
I'm trying to build the xdoc plugin from SVN trunk. I got:
C:\dev\maven\maven-1\plugins\xdoc>maven clean plugin:install
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Tentative de tΘlΘchargement de comm
line:
maven plugin:download
-DgroupId=maven
-DartifactId=maven-xdoc-plugin
-Dversion=1.8
For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-xdoc-plugin-1.8.jar
Have fun!
-The maven team
Hi folks,
after waiting for 5 months to have my patch applied, I want to nag the list, to have
somebody of the committers to look and apply that patch:
http://jira.codehaus.org/browse/MPXDOC-80.
It solves the problem for custom themes in a multiproject environment, because the css
have current
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: lundi 28 juin 2004 01:20
> To: Maven Developers List
> Subject: Re: [Solved] my problem with xdoc plugin
>
> Perhaps you were using a SNAPSHOT version of jelly, jelly-tags-xml or
> jexl
Perhaps you were using a SNAPSHOT version of jelly, jelly-tags-xml or jexl?
Great to hear you sorted it out!
- Brett
Quoting Vincent Massol <[EMAIL PROTECTED]>:
> I had sent several emails about a problem I had with the xdoc plugin. It was
> prefixing dirs with the basedir, leadi
I had sent several emails about a problem I had with the xdoc plugin. It was
prefixing dirs with the basedir, leading to a full path specifying twice the
basedir… I have now sorted this and it’s working fine. I don’t really know
what was the exact problem but it seems it was due to some jar I had
run plugin against the installed version of Maven
To automatically install the plugin, type the following on a single line:
maven plugin:download
-DgroupId=maven
-DartifactId=maven-xdoc-plugin
-Dversion=1.7.2
For a manual installation, you can download the plugin here:
http
> -Message d'origine-
> De : Dion Gillard [mailto:[EMAIL PROTECTED]
> Envoyé : dimanche 23 mai 2004 23:19
> À : Maven Developers List
> Objet : Re: Xdoc plugin and "goals" documents
>
> On Sun, 23 May 2004 19:20:02 +0200, Arnaud Heritier
> <[E
On Sun, 23 May 2004 19:20:02 +0200, Arnaud Heritier
<[EMAIL PROTECTED]> wrote:
>
> +1, I'm ok with your proposal.
> In any case, I won't have the time to work on this before several weeks (so
> I hope that the 1.0 will be released). I prefer to fix bugs and enhance
> documentations if possible bef
ECTED]
> Envoyé : dimanche 23 mai 2004 01:10
> À : Maven Developers List
> Objet : Re: Xdoc plugin and "goals" documents
>
> Well,
>
> my take would be to (post 1.0):
> 1) deprecate the current transformations in the jsl file using a warning.
> 2) U
1 - 100 of 200 matches
Mail list logo
