The m1 weblogic plugin is hosted at Sourceforge:
http://maven-plugins.sourceforge.net/maven-weblogic-plugin/
You also might want to try their mailing list.
-Lukas
Hines, John wrote:
I've inherited a maven 1.0.2 build process we use in both development
and production of three different produc
Hi Joerg,
AFAICT, the version.id element is only used by the announcement plugin
for generating release announcements; version.name and version.tag are
used by the scm plugin.
It would be nice though if we had an easy way to find out which pom
settings are used by a particular plugin.
-Luk
Hi,
That means version.name and version.id is supposed to be the same?
I don't think they are supposed to be the same, but in practice it seems
to be the case, - does anybody have a different use case?
Or if they would be used more regularly ... e.g. the changes plugin could
generate use t
Wendy,
Are you running m1.0 or m1.1? I suspect you are seeing
http://jira.codehaus.org/browse/MPARTIFACT-54 .
If you are running m1.1, just upgrade the artifact-plugin to at least 1.6.
-Lukas
Wendy Smoak wrote:
This worked on December 2nd... none of the changes to project.xml
since then lo
Arnaud,
I noticed one queer thing, I'm just not sure if it's a multiproject
issue or something we can fix in the linkcheck plugin: the linkcheck
report for the master project is not generated in a multiproject build
if maven.multiproject.navigation=aggregate is used. Eg, in the m1
plugins tru
Hi,
Most likely you are behind a proxy and the proxy isn't configured
to allow REPORT requests. Solution: either re-configure your proxy, or
use the https:// protocol, which will circumvent the proxy.
-Lukas
Anthony Kong wrote:
Hi, all,
When I tried to use svn to check out the latest plu
This is fixed only in the current maven 1.1-beta-3:
http://jira.codehaus.org/browse/MAVEN-1657
(jira seems to have some problems again, right now you can't see any
comments, just wait a bit).
Lukas
Afkham Azeez wrote:
Hi Folks,
I'm using Maven 1.0.2. I have a problem with the ant zip task.
-
# subprojects to include (relative maven.multiproject.basedir)
maven.multiproject.includes=client-src/java/project.xml
maven.multiproject.includes=src/java/project.xml
-
Hi,
This has been reported already but apparently we forgot to fix it. As a
workaround, you can download the batik jar from ibiblio [1] by hand and
place it in your local repo. Or temporarily disable the pdf generation
in your project.
HTH,
Lukas
[1] http://www.ibiblio.org/maven2/batik/bat
Hi,
As some of you might know, we are still working on a Maven 1.1 release,
which is unfortunately quite behind schedule. The advance of Maven 2
has dragged away a lot of attention and we are currently only three people
actively developing and maintaining the Maven 1 core and 65 plugins.
It has
Did you set the maven.multiproject.type property for each subproject?
-Lukas
Nicolas De Loof wrote:
I was first thinking about "org.apache.commons.attributes.enable" not
beeing correctly set, but I've was wrong.
I've created http://jira.codehaus.org/browse/MAVEN-1691
I've attached a minima
What happens if you replace the by
?
-Lukas
Ashish Srivastava wrote:
Hi,
I created a remote repository for a bunch of jars
we use in our application. The way I did is manually
created the library.pom as :
4.0.0
libName
libName
1.0
When I compile the project I get the fol
Sorry, this is somewhat hidden in the properties:
http://maven.apache.org/maven-1.x/reference/plugins/dashboard/properties.html
Look for the maven.dashboard.sort and maven.dashboard.sort.property
properties. The latter defaults to 'name', but can be any element
defined in your pom, eg 'develop
Hi Jeff,
I thought we had resolved all your problems with javadoc warnings ;)
Would you mind opening another issue with more detailed information, ie
the exact versions of javadoc, xdoc and site plugin that you are using,
and the files that are generated in target/javadoc? Or even better, a
s
Are you sure on this? I thought declaring a plugin dependency lets your
project depend on a particular version of a plugin without actually
installing it - so you can use that plugin on the fly without messing up
your (and every developer's) Maven installation.
There is actually a documentatio
Matteo Melani wrote:
Let's see if I get it:
I use plugin X and Y for building my project therefore I put 2
dependencies in the project.xml.
Now when other developers check out the code and run Maven the *.jar
file of the plugins get downloaded in the repository.
Right.
Now the develope
Put "maven.xdoc.crumb.separator=|" into your project.properties file.
Check the documentation on the maven site and for the xdoc plugin:
http://maven.apache.org/maven-1.x/reference/plugins/xdoc/index.html
http://maven.apache.org/maven-1.x/start/ten-minute-test.html
http://maven.apache.org/maven
Ahhh... I think "in the root classloader" is the key there. :) I only
added the tag to Jalopy and jalopy-ant. (How did this
ever work the way it is??)
That's what I would like to know, too...
I'm afraid we really have to overhaul the jalopy plugin, it would be
nice if you could lend us a
Maven 1 doesn't know anything about scope, so I don't see how this could
be useful?
-Lukas
Nicolas De Loof wrote:
suggestion :
Could xdoc plugin use also a "scope" property, with same use as maven 2
element ?
This may be usefull in dependencies.html !
-
What am I volunteering for? :) Are we talking about branching and
fixing the problem in a maven-jalopy-plugin 1.3.x release? I need to
get that working in order to look at converting to Jalopy 1.5b5 and a
1.4.x version of the plugin.
This is open source, people usually volunteer for what
As the checking is done in a different plugin (the linkcheck-plugin ;)
), you have to execute that goal separately before running xdoc:
maven maven-linkcheck-plugin:report
maven xdoc
Or you add the maven-linkcheck-plugin report to your project.xml and run
maven site
And you don't need to manu
No, it does work with Maven 1.0.2. I tested it, however, not with java 5
(only 1.4.2). If it's a jdk issue then the $JAVA_HOME/lib/endorsed/
solution is probably the only one that's gonna work.
-Lukas
Carlos Sanchez wrote:
AFAIK it needs maven 1.1
On 2/16/06, Andy Fyfe <[EMAIL PROTECTED]>
A prereq is always only called once in a build cycle. This is by design,
since you usually don't want the same goal to be executed again if it
has been executed once already. If you want to make sure it gets
executed, you should use in your sub-projects, ie
HTH,
Lukas
Manisha Sur wro
't it continue to call it
automatically after upgrading LinkCheck to V1.4-SNAPSHOT?
On 2/13/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
As the checking is done in a different plugin (the linkcheck-plugin ;)
), you have to execute that goal separately before running xdoc:
maven maven-li
Hi,
The systemScope.setProperty line was introduced to fix
http://jira.codehaus.org/browse/MPCHECKSTYLE-53
so you are saying that you have to remove it again? Can you attach your
comments to the issue above, or maybe open a new issue to attack the
problem more generally.
Thanks,
-Lukas
Ar
I have deployed a new snapshot which uses a jsl transform instead of
ant's style task. This should eliminate any jdk related issues, please test:
maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
-DgroupId=maven -DartifactId=maven-checks
This was a separate bug, it's fixed. Please re-download the snapshot and
test.
Thanks,
Lukas
Eric Rose wrote:
On Sunday 19 February 2006 08:11, Lukas Theussl wrote:
I have deployed a new snapshot which uses a jsl transform instead of
ant's style task. This should eliminate any j
Hi Lance,
Thanks a lot for your interest and help on this topic! Any of your
contributions will certainly be welcome, even if you only send us
partial translations (even though complete translations would be
preferred ;) ). Please make sure to get the latest properties files from
svn, as we h
I am afraid that, the way it is currently desined, you are supposed to
use properties files. I'd need to have a closer look, but it seems to me
that it would require quite a substantial re-write of our jelly scripts
to make it work the way you suggested. I'd recommend to go with the last
opti
Maybe this can help:
http://jira.codehaus.org/browse/MPJCOVERAGE-21
-Lukas
Siegmann Daniel, NY wrote:
I have a project which uses Maven 1.0.2. We wish to use jcoverage to
generate coverage information. We have used this in other projects. In this
project, it was working for a time, but now i
The artifact plugin is mainly a collection of tag libraries that are
used by other plugins, it doesn't have any goals. Eg, the
artifact:deploy tag is called by the jar|war|ejb|...|:deploy goals, but
it is not supposed to be called directly by a user. You might use it in
a custom jelly script th
item #1277785.
http://sourceforge.net/tracker/index.php?func=detail&aid=1277785&group_id=16035&atid=116035
Maybe we will some some action on this.
Lance
On 12/8/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
It's a known issue: http://jira.codehaus.org/browse/MPXDOC-111
Nothi
properties file, how do I get the xDoc plugin to place that
translated text INSIDE a or element. I understand
how the key= attribute replaces the name= attribute, but I don't see a way
to specify the inner content.
Lance
On 2/27/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
I am af
Lance Bader wrote:
No, I double checked my prototype web site. If a directory does not contain
any xdoc source files (like images or styles in my structure), it is copied
to the base directory but not the language directories. Maybe this is a
defect?
This should be fixed in the current 1.10
The second site was generated with maven 1. The m1 checkstyle plugin
automatically generates links if the jxr plugin is activated.
For the m2 version, there seems to be a problem:
http://jira.codehaus.org/browse/MCHECKSTYLE-34
HTH,
-Lukas
Aaron Freeman wrote:
I have noticed on a few differ
It seems like the escapeText="false" attribute for the tag
should be doing what you want, see
http://jakarta.apache.org/commons/jelly/tags.html#core:set .
However, from some quick test I did this doesn't seem to work...
Another jelly quirk?
-Lukas
jan_bar wrote:
Some samples:
howeve
ideas?
Thanks,
Tim.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
______
Lukas Theussl
T
riginal Message-----
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 13, 2005 9:45 AM
To: Maven Users List
Subject: Re: [m1] license report
The license plugin uses the maven.license.licenseFile property for
generating the license. Actually, I don't know what the license in
If you are using svn then this is a known issue:
http://jira.codehaus.org/browse/MPCHANGELOG-74
If you are using cvs, it should work (you also specified a
inside ?). Which version of the changelog plugin are you using?
-Lukas
Angel Andres Fungueiro wrote:
When maven generates the cha
Are you running maven as root or did you point your local repo to /root?
(neither of which is a good idea). It looks like you don't have read
access to your local repo (/root/.maven/...).
-Lukas
F-a-r-h-a-n-a wrote:
Hi
Ive been trying to deploy maven in my GridPort3.5.1 Project for past
You have to download these jars yourself (due to license issues) and put
them in your local repo by hand:
http://maven.apache.org/reference/standard-sun-jar-names.html
-Lukas
Xavier Toth wrote:
I'm sorry if this has already been addressed but my dependencies for things
like activation and ma
-jars for info.
On 10/18/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
You have to download these jars yourself (due to license issues) and put
them in your local repo by hand:
http://maven.apache.org/reference/standard-sun-jar-names.html
-Lukas
Xavier Toth wrote:
I'm sorry if
This has been fixed recently:
http://jira.codehaus.org/browse/MPPDF-50
It's in SVN, there is also a SNAPSHOT version that has it fixed.
-Lukas
Tim Dyck wrote:
Does the following property work:
maven.pdf.cover.projectCompany
I also thought that by default this property is supposed to refer
If you get the same error then you know which file cannot be deleted.
Try to remove it by hand and you'll see if you have permission.
However, I'd suggest starting from scratch: unpack the maven tar ball
(as normal user), set your environment variables (PATH, MAVEN_HOME) and
delete your loca
The maven site is currently being restructured (as you noticed), a lot
of links are temporarily broken. The maven 1 site should end up here:
http://maven.apache.org/maven-1.x/
but there are some broken links there too at the moment. Please be
patient, the bulk of these issues should be resolve
Probably the file /opt/maven-1.0.2/esidif_checks.xml does not exist? How
did you specify the maven.checkstyle.properties prop? Try prepending
${basedir}, that should work.
-Lukas
Angel Andres Fungueiro wrote:
Hi.
I'm generating checkstyle reports with Maven 1.0 and works fine.
But when us
This is a misunderstanding of the SNAPSHOT functionality, maven does
_not_ replace SNAPSHOT with the latest available version of a project.
Using a SNAPSHOT dependency still assumes that the project that you
depend upon has actually published a SNAPSHOT. This is not the case for
commons-loggin
avior as Stefan and maybe that can be a possible enhancement to
put on the strack? Maybe I miss something but I don't see why it will
not be possible.
Regards.
Gianfranco Oldani
Original Message Follows----
From: Lukas Theussl <[EMAIL PROTECTED]>
Reply-To: "Maven Users List&q
Hi,
What if a released component on remote repository has any bugs?
This just underscores my point, no? Generally, I think upgrading (or
downgrading) a dependency is always something that should be done very
carefully and very consciously, I wouldn't want to have that done
automatically.
stable snapshot builds and without having
to manually update all the poms everytime a new module is published.
-Original Message-----
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Monday, October 31, 2005 1:01 PM
To: Maven Users List
Subject: Re: keyword "SNAPSHOT" in dep
The definite place for finding rpms of java applications is JPackage:
http://www.jpackage.org/
HTH,
-Lukas
Allison, Bob wrote:
One place with a lot of source RPMs to browse is Fedora:
fedora.redhat.com
-Original Message-
From: Xavier Toth [mailto:[EMAIL PROTECTED]
Sent: Monday, Oc
Hi Thomas,
The maven.xdoc.theme.url property only works as an absolute URL (the
documentation on this has recently been updated), what you want is a
project.css file in xdocs/style/, this will automatically be picked up.
HTH,
-Lukas
[EMAIL PROTECTED] wrote:
hello,
I put a custom.css f
This is a known issue: http://jira.codehaus.org/browse/MPXDOC-179
For stand-alone projects, you can make it work by specifying an absolute
path for the external entity, but this will not work in a multiproject
set-up. Otherwise, I'm afraid I can't offer anything else right now.
-Lukas
Phil
ks again for your help.
Tom
Lukas Theussl
<[EMAIL PROTECTED]
org>
Don't know if you are aware of this:
http://doodleproject.sourceforge.net/projects/mavenite/maven-batik-plugin/index.html
Never used it though...
-Lukas
Martin van den Bemt wrote:
See http://www.mvdb.org/maven/plugins/svg/
The first line on How to use? is a bit outdated though and I am not s
It's at
http://cvs.apache.org/repository/maven/plugins/
so you can download and install it with
maven plugin:download
-Dmaven.repo.remote=http://cvs.apache.org/repository/ -DgroupId=maven
-DartifactId=maven-test-plugin -Dversion=1.8-SNAPSHOT
-Lukas
Tim Dyck wrote:
Where can I go to downl
For the checkstyle plugin this should be fixed in the current
3.0-SNAPSHOT (see http://jira.codehaus.org/browse/MPCHECKSTYLE-39 ), but
it might still be a problem for other plugins.
Gisbert, which plugins/reports do you have problems with?
-Lukas
Arnaud HERITIER wrote:
I have no workaround
ssage d'origine-
De : Lukas Theussl [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 16 novembre 2005 00:03
À : Maven Users List
Objet : Re: [M 1.1b1] Maven-Reports: Encoding Problems
For the checkstyle plugin this should be fixed in the current
3.0-SNAPSHOT (see
http://jira.codehaus.org/browse/MP
This page is deprecated, the new homepages for m1 plugins are at
http://maven.apache.org/maven-1.x/reference/plugins/index.html
I will update the documentation about the faq plugin.
Cheers,
Lukas
Wendy Smoak wrote:
On 11/19/05, Arik Kfir <[EMAIL PROTECTED]> wrote:
Try this: http://maven
Hi Ian,
You are accessing a deprecated page, the whole m1 site has moved to
http://maven.apache.org/maven-1.x/
the page that you want is here:
http://maven.apache.org/maven-1.x/reference/plugins/ejb/cvs-usage.html
I hope that some one here cares ;-)
I am sure a lot of people care, there
Hi Weston,
The maven.multiproject.includes is constructed relative to
maven.multiproject.basedir (which defaults to ${basedir}), so in your
example, ${basedir} is prepended twice.
-Lukas
Weston, Toby wrote:
Thanks for the tip Michael, that seems to work great! Out of interest, I
tried the
Make sure the developer 's in your project.xml match those of the
repository user name. The needs to contain the id that is used in
your source version control.
-Lukas
Chawla, Sampreet Kaur (Cognizant) wrote:
Hi Arnaud & Everybody,
I am able to generate the ChangeLog, Developer-Activity
The only thing that the xdoc plugin puts in front of the "Doc for" is
the special character entity " " (non-breaking space), do you see
that if you look at the source of the generated html? Maybe an encoding
problem?
-Lukas
Antonyan, Tigran(GE Infrastructure) wrote:
Thanks for your reply!
It's not the same issue. The docs for the m2 plugins have not been
updated to reflect the SVN move, which is what was referred to.
You're right, sorry about the mix-up.
But it just underscores the point even more - not only our users are
confused by all the ancient documentation sites that
Hmm, 'navigation-top' and 'navigation-bottom' seem to be broken, but
'bottom' works for me. I'll have a look at it.
-Lukas
Gisbert Amm wrote:
Unfortunately, adding maven.xdoc.date=navigation-top or
maven.xdoc.date=bottom to my build.properties or project.properties has
not the desired effec
(setting of LC_CTYPE was necessary aswell)
and set the following Maven properties:
maven.docs.outputencoding=UTF-8
maven.xdoc.locale.default=de_DE.utf8
Now the German umlauts are displayed correctly within the checkstyle
report and the documents generated out of the xdocs (like index.xml).
We have to publish the artifact-plugin-1.7 and plugin-plugin-1.7 first
to satisfy the dependency chain. Problem is that in the current state,
these are maven-1.1 plugins only.
-Lukas
Joshua Smith wrote:
Carlos (and others)-
I installed the plugin using the command below, but when I build m
Maybe it's just me.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
______
Lukas Theussl
TRIUMF email:
Should the filename for the .jar and the .pom match? I suppose it
won't matter for Maven 1, but this is what got uploaded:
I fixed this one just yesterday
(http://jira.codehaus.org/browse/MPARTIFACT-56), but it will be in
artifact-plugin-1.7 only, which means you won't profit from it in m1
something like ${basedir}/../resource dir/file.txt (this doesn't work) ?
Is there a space in 'resource dir'? Can you try if it works with
directories without spaces?
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Fo
I think that's correct, at least this is the behaviour that I would
expect. You wouldn't want your Maven installation be changed just
because one project uses a specific version of a dependency, would you?
-Lukas
Dennis Lundberg wrote:
Hello
A project I'm working on requires a specific vers
Hi Ken,
First make sure that your browser's encoding property is set to UTF-8.
But then, there may be still problems with some reports as has been
discussed recently here [1], you will also find some hints in this
thread about encoding properties to set.
Good luck!
Lukas
[1]
http://www.na
We are working on it right now but we are having difficulties
maintaining backwards compatibility with m1.0.2 in many cases. A bunch
of plugins should be released in the coming two weeks (just hope I'm not
promising too much here ... ;) . In any case, we will re-publish all
maven core plugins b
ownloading the jar
file, but the message appears in question mark like file.name.jar
??.
On 12/7/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
Hi Ken,
First make sure that your browser's encoding property is set to UTF-8.
But then, there may be still problems with some reports
It's a known issue: http://jira.codehaus.org/browse/MPXDOC-111
Nothing we can do about in xdoc, it's a dom4j bug.
-Lukas
Lance Bader wrote:
In HTML there are tags that are forbidden to have content or end tags,
namely
In XHTML, of course, everything needs an end tag, even if co
Hi Lance,
I tried a few things but I couldn't get it work like you want, so I'm
afraid the preliminary answer to your question is no. Unfortunately,
jelly is not very consistent with the treatment of entities, we've had
several related problems in the past.
-Lukas
Lance Bader wrote:
By de
Can you tell us what the incompatibilities are? Anyway, the xsd that
Vincent pointed you to is out of date, you should try the latest version
from the m1 xdoc plugin:
http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/xdoc/src/xsd/
-Lukas
Jean-Charles Giardina wrote:
So the mave
The upcoming checkstyle-plugin-3.0 uses Checkstyle 4.0. A snapshot is
available for testing:
maven plugin:download -DartifactId=maven-checkstyle-plugin
-DgroupId=maven -Dversion=3.0-SNAPSHOT
-Dmaven.repo.remote=http://cvs.apache.org/repository
-Lukas
Girish Nagaraj wrote:
Hello,
Current c
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I haven't had the time to investigate.
-Lukas
Jeff Jensen wrote:
We miss this report for summarizing Javadoc errors.
I entered this JIRA on 27/Sep/05:
http://jira.codehaus.org/browse/MPJAVAD
You can set the maven.repo.local property. Check [1] for other relevant
properties you can set in maven 1.x.
-Lukas
[1] http://maven.apache.org/maven-1.x/reference/properties.html
Blaise Gosselin wrote:
Hello,
Is it possible to define another directory for the local repository in Maven 1.
All I can say is that we are working on it but it's probably not going
to happen this year anymore :(
-Lukas
PS Contributions and patches are more than welcome!
Guy Rixon wrote:
Hi,
are there any known, probable dates for releases of Maven 1.1?
Guy Rixon
ls to
use?
Quoting Lukas Theussl <[EMAIL PROTECTED]>:
Can you tell us what the incompatibilities are? Anyway, the xsd that
Vincent pointed you to is out of date, you should try the latest version
from the m1 xdoc plugin:
http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/x
/maven-1.x/reference/plugins/xdoc/reference/navfile.html#Validation
[2]
http://maven.apache.org/maven-1.x/reference/plugins/xdoc/reference/maven-navigation.xsd
Lukas Theussl wrote:
I can put it on the xdoc plugin site, but it's still part of the
current development version, the final version
Hope this gets resolved soon :-)
Seems to be resolved already :) - see my comment on JIRA.
-Lukas
Thanks,
Girish
On 12/9/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
If it's not the same issue please open a new one. I am seeing empty
javadoc warning reports too, but I
-b10.jar
Any suggestions to overcome this issue?
Thanks,
Girish
On 12/9/05, Lukas Theussl <[EMAIL PROTECTED]> wrote:
The upcoming checkstyle-plugin-3.0 uses Checkstyle 4.0. A snapshot is
available for testing:
maven plugin:download -DartifactId=maven-checkstyle-plugin
-DgroupId=maven
For m1:
First make sure maven is properly installed [1], then type
maven plugin:download -DgroupId=andromda
-DartifactId=maven-andromdapp-plugin -Dversion=3.1
-Dmaven.repo.remote=http://team.andromda.org/maven/
HTH,
-Lukas
[1] http://maven.apache.org/maven-1.x/start/install.html
Somasu
Try with lower 'c'.
-Lukas
Hayat Amine wrote:
hi,
I want to generate the change log report, I put in my project.xml this line:
scm|cvs|pserver|h.Amine|[EMAIL PROTECTED]|repository
But when I generate the site with maven site:generate, I haven’t any exception
but my change
You are using the same variable name (portlet_projects) twice in the
tag. Since you do the same tokenize again in the build
goal, I guess it doesn't see the same variable anymore. Try something like
${portlet_projects}
or call on the variable after each goal.
HTH,
Lukas
Lou Sacco wrote:
Just a comment: I am having basically the same problem with maven
1.1-beta-1 (everything works fine with 1.0.2).
However, I noticed something weird: I have a project B that extends
project A.
If I run 'site' in project A, I get the above error (Could not start
validation: null not found),
I have a project A that contains a sub-project B.
If I run 'multiproject:site' in A, the linkcheck report for project B
gets generated correctly, but the one for the parent project A contains
just an empty placeholder (' This file is used as a placeholder until
the final link check can occur.
We discussed that problem shortly before the pdf-plugin-2.3 release on
the devel list (check
http://mail-archives.apache.org/mod_mbox/maven-dev/200506.mbox/[EMAIL PROTECTED]
and follow-ups) but I don't know exactly what the status is right now.
I suppose you are using maven-1.0.2 ?
FWIK, you
I just noticed that in 1.1-beta-1 running 'maven -X' with any goal
produces a bunch of debug warnings:
[DEBUG] Adding reference: maven.dependency.classpath
Caching Taglib Uri --> deploy
running script null
[DEBUG] Could not load class
(org.apache.tools.ant.taskdefs.optional.PropertyFile) for
dan tran wrote:
in 1.1 you need to load the optional jars yourself
http://maven.apache.org/reference/backwards-compatibility.html
-D
I was aware of that but that's the point: I am not using any optional
tasks. It already happens if I just run the genapp plugin inside an
empty directory. I
Arnaud should have specified further that this plugin is for maven 1.1
only (I don't think the restriction to java 5 is correct). Maven 1.0.2
users will have to put a xalan jar into $MAVEN_HOME/lib/endorsed.
Lukas
-
To unsubsc
Thanks, that was it. Now I'm down to a duplicate id problem, which I
see is
a known issue. That will take a little longer to clean up. :)
Yes, we are working on that right now (MPPDF-40). Currently you have to
avoid identical name and id tags within one source document (which you
shoul
Still trying to get this to work on 1.4...:)
Jeff Jensen wrote:
I found using 1.5 eliminates the problem (did you see my follow-up post?).
I have not pursued making 1.4 work though.
Java 5 includes xerces while 1.4 doesn't. So I figured I'd just have to
include xerces somewhere explicitly to
This new snapshot has a new bug I didn't fixed actually : SVG support is
broken (again :-( )
As far as I can tell, SVG is working fine really, - just not with the
.svg samples I included for the test cases :-P . For them, batik fails
due to a bug that has apparently only been fixed in a l
It's weird because I downloaded the fop 0.25 distrib used in this plugin and I
successfully created the pdf from our project.fo
generated in our test n°2 :-(
You're right, this is very puzzling - I did the same with only the jars
in my local repository in the classpath and it worked too!
I found the solution by accident: you just have to remove the
'dir="${internal_pdf_workingDir}"' option when you call fop in plugin.jelly.
Apparently a problem of relative url resolution (it only failed for svgs
containing relative url links within the same document, ie starting with
#, and only
Please read the "Getting started" section of the i18n documentation:
http://maven.apache.org/reference/plugins/xdoc/i18n.html
Briefly, you have to define your own default locale with your own
resource bundle where you can override these properties.
-
1 - 100 of 514 matches
Mail list logo
