Hi Dan
We decided not to solve your question since we believed that in the open source world
that approach (not to hide dependencies) is widely accepted.
Anyway if you really want to do it one solution would be to update the jar plugin so
it accepts a jar.bunlde property that basically includes
Hi,
I had sent the email below asking for some information about modifying
the maven javadoc plugin to properly support the maven.compile.src.set.
I've generated a patch that seems to do the right thing: it's attached
below. Comments quite welcome.
I looked at making a patch against 1.5, but
I'm thinking that if you only copy the jar it won't work because we define
the classpath for FOP in the plugin script.
What you must do:
1) Copy the jar where you want.
2) Add a new pathelement where we call FOP in the pdf's plugin.jelly file.
I'm sorry but I didn't think about this.
Can you add
Did you try to add the jar in $MAVEN_HOME/lib ??
Arnaud.
> -Message d'origine-
> De : Fabio Uechi [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 17 mai 2004 18:01
> À : maven maven
> Objet : pdf plugin - png images - jimi and jai libraries
>
>
> Hello everybody!
>
> I'm trying to generate
There's no branch in maven-plugins.
You must get the HEAD one.
Arnaud
> -Message d'origine-
> De : Eric Giguere [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 17 mai 2004 16:04
> À : Maven User List
> Objet : Source for new Plugin release
>
> Hi
>
> In which branch can we get the sources o
There's no branch in maven-plugins.
You must get the HEAD one.
Arnaud
> -Message d'origine-
> De : Eric Giguere [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 17 mai 2004 16:04
> À : Maven User List
> Objet : Source for new Plugin release
>
> Hi
>
> In which branch can we get the sources o
Sorry but I sent this mail 5 hours ago but it wasn't received on the ML.
==
I'm thinking that if you only copy the jar it won't work because we define
the classpath for FOP in the plugin script.
What you must do:
1) Copy the jar where you want.
2)
Morning all,
I have a question regarding dependencies.
If for example my project depends on a library called common and common
depends on several other libraries (for example castor). Is there a
nice/easy way of determining what libraries I should include in my project
based on the dependencie
Post the entire POM to one of us to validate.
--
dIon Gillard, Multitask Consulting
[EMAIL PROTECTED] wrote on 17/05/2004 11:21:07 PM:
> then I understood you correctly
>
> if (projectFile.exists() && projectFile.canRead())
> 130 {
> 131 return MavenUtils.getProject(
> 132
I think the version in $MAVEN_HOME/plugins gets deleted as is shown below.
What probably happened was that you have built to your local repository
using "3.0" as the version instead of bumping the project.xml to
"3.0-SNAPSHOT", so you are keeping an old version you've built in the local
repo. Try
You are right - thanks. I don't know how this happened.
Will correct and verify shortly.
- Brett
> -Original Message-
> From: Dominik Dahlem [mailto:[EMAIL PROTECTED]
> Sent: Monday, 17 May 2004 6:08 PM
> To: Maven Users List
> Cc: [EMAIL PROTECTED]
> Subject: Re: Maven console plugin 1
Return Receipt
Your scm:bootstrap-project problem : cannot compile java sources
document
:
It works fine for me. I believe you have an old version in your
MAVENHOME/plugins directory. You need to remove it.
-Vincent
> -Original Message-
> From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
> Sent: 17 May 2004 22:27
> To: Maven Users List
> Subject: Re: Maven AspectJ plugin 3.
Clearing the cache didn't work either. Still getting the old one.
I'm wondering (and I bet everyone else is too) how this is even possible
since the version I am getting was never released.
Charlie
Charles N. Harvey III wrote:
[EMAIL PROTECTED] ~/projects/pcu2] maven plugin:download
-DgroupId=mav
[EMAIL PROTECTED] ~/projects/pcu2] maven plugin:download -DgroupId=maven
-DartifactId=maven-aspectj-plugin -Dversion=3.0
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2
build:start:
plugin:download-artifact:
plugin:downloa
How weird. I did exactly what was instructed in the e-mail.
maven plugin:download -DgroupId=maven -DartifactId=maven-aspectj-plugin -Dversion=3.0
And I got a slightly older version. I'll try again and see if
it makes any difference.
Charlie
Vincent Massol wrote:
Hi Charles,
I'm puzzled by your c
Hi Charles,
I'm puzzled by your comment. I've just downloaded the version 3.0 of the
plugin to make sure I had applied the patches correctly and there are
only 3 goals in there and the properties are weaveInto and weaveWith...
Could you please tell us where exactly you have seen this problem?
Th
Not to sound strange here, but Carlos and I slimmed down that plugin.jelly
file much more than what was released. What happened? The only goals we
left in there were: aspectj, aspectj:init and aspectj:compile.
We got rid of the rest of them because they didn't make sense. And we
changed the aspe
Hi again,
I found a workaround. Don't know if it's the best solution but
it's working now.
I created 3 new properties in my project.properties. Each of
them just point to the respective library location.
maven.pdf.jimi.jar = ${maven.repo.local}/jimi/jars/jimi-1.0.jar
maven.pdf.jaicore.jar =
${m
Hello all,
In my multiproject setup subprojects all have versions specified in their
poms….
Is there a way for me to declaratively state that I want to build/assemble
an ear (or any other task for that matter) from subproject-version-2.0.jar
and othersubproject-version.-1.4.jar etc.
…without ch
Hello everybody!
I'm trying to generate the pdf doc for my project but I'm having
some problems with the insertion of PNG image files.
The plugin conplains that the JIMI library is not present.
Checking the FOP website I saw that I should download and
install this library (or JAI) manually becau
Hi,
I'm using scm:bootstrap-project goal to build a project using maven configuration
files stored in cvs.
Everything works fine but when I want to compile my java source files, I get the
following message :
'No java source files to compile'
I have checked the maven.src.dir properties and it poi
> -Original Message-
> From: Eric Giguere [mailto:[EMAIL PROTECTED]
> Sent: 17 May 2004 16:04
> To: Maven User List
> Subject: Source for new Plugin release
>
> Hi
>
> In which branch can we get the sources of all the newly released
plugins
> from the apache CVS?
In CVS HEAD of the mav
Hi
In which branch can we get the sources of all the newly released plugins
from the apache CVS?
thx
Eric.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
then I understood you correctly
if (projectFile.exists() && projectFile.canRead())
130 {
131 return MavenUtils.getProject(
132 projectFile,
133 null,
134 false);
135 }
that is in fact what I am using I locate my File() containing the POM and
then
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 2:50 PM
> To: Maven Users List
> Cc: 'Maven Users List'
> Subject: RE: Again about the POM Parser in Maven 1
>
>
> Probably I have misunderstand you sorry for wasting in
> case yo
Hello Michal,
I tried to understand how to use that API, from what I can see the
following
public void build(Project projectValue) requires already the Project
avalable it means :
something like
File f=new File(s);
if (f.exists()){
Project p=MavenUtils.getProject(f); // Usi
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 1:32 PM
> To: Maven Users List
> Cc: Maven Users List
> Subject: RE: Again about the POM Parser in Maven 1
>
>
> Hello Michal,
>
> Probably I was not precise enough. My initial aim is
Hello Michal,
Probably I was not precise enough. My initial aim is to be able to parse
using the API an already working project.xml. Using the maven.bat I can
normally work with it. I made before using it in this test also a
verification using the POM plugin.
maven -e pom:contentValidate pom:val
It seems to me that really something is not OK with your POM
Maybe this example will be helpful? :
http://maven.apache.org/reference/plugins/xdoc/xref/org/apache/maven/Depende
ncyDescriberBean.html
(you can look at the method
private Project resolveProject(Dependency dependency)
)
Michal
> -
Hi all,
is there a way to resolve a property in jelly explicitly? The checkstyle
plugin internally sets the checkstyleProperties property which in my
case is based on maven.checkstyle.properties. I set
maven.checkstyle.properties to
${projectA.home}/master/src/config/checkstyle.xml in ~/build.prop
Thanks for the hint to point to MavenUtils, I played around a bit with that
class, using a know working project.xml. I wrote a small test
public class PomParserTest extends TestCase {
public void setUp() throws Exception {
}
public void testPomParserDoesStuff() throws Exception {
S
Hi,
I tried to download the new version of the console plugin and noticed
that it is not up yet.
Cheers,
Dominik
On Sun, 2004-05-16 at 03:28, [EMAIL PROTECTED] wrote:
> The maven team is pleased to announce the Maven Console Plugin 1.1 release!
>
> http://maven.apache.org/reference/plugins/con
Hi,
I'm using own goal to generate struts xml using xdoclet.
I accidentally have missed xdoclet-apache-module in my xdoclet
dependency, as a result struts-config.xml hasn't been generated.
I'm almost sure that in maven rc1 I could find info about missing class
in maven.log. In rc2 using -X option
34 matches
Mail list logo
