RE : Fixes for Maven changelog plugin to work with CVS 1.12.9
Is it compatible with older CVS release ?? Can you post it on Jira please? Arnaud > -Message d'origine- > De : Vincent Zang [mailto:[EMAIL PROTECTED] > Envoyé : mardi 10 août 2004 08:27 > À : Maven Users List > Objet : Fixes for Maven changelog plugin to work with CVS 1.12.9 > > > Hi, > > I recompiled maven changelog plug-in so that it works with > CVS 1.12.9 log format. If anyone is also having the same > problem, I'll post the changes to the mailing list. > > cheers, > > Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FTP ant task
Thank you Jeff - it now works perfectly :)
Jesper Linvald
MAERSK DATA TRANSPORT
Tel no.: +45 3911 1891
e-mail: [EMAIL PROTECTED]
"Jefferson K. French" <[EMAIL PROTECTED]>
09-08-2004 19:04
Please respond to
"Maven Users List" <[EMAIL PROTECTED]>
To
Maven Users List <[EMAIL PROTECTED]>
cc
Subject
Re: FTP ant task
What does it do when it doesn't work?
For me, the -X switch showed that there was a CNF exception for an oro
FTP class. I had to put this in my project.xml:
ant-contrib
ant-contrib
20020829
oro
NetComponents
xxx
root
The NetComponents JAR file is not at ibiblio, so I added it to our
company repo. The version 'xxx' I just added because there was no
version number associated with the JAR file.
In retrospect, the ant-contrib part may not be required. It looks like
the Ant FTP class is loaded automatically by Maven from
ant-optional-1.5.3-1.jar. I had to add the property
because it looked like Ant's FTP class was loaded in the root
classloader, but the NetComponents JAR was loaded by the Maven
classloader. I know the is deprecated, but I wasn't sure
how else to get it to work.
I did this in a plugin, so I added this to my plugin.jelly:
before invoking the "ftp" task. For a maven.xml file, you wouldn't use
${plugin}. I think you'd use ${context}, but I'm not positive.
Again, you may be able to drop the whole ant-contrib part.
Jeff
On Mon, 09 Aug 2004, at 12:40:51 [GMT +0200] Jesper Linvald wrote:
> Hello all,
> I am trying to use the ftp ant task from maven. It dosent work! Running
> the task straight from Ant works fine
> Some have suggested a brute hack with a typedef and dependency on Ant
1.6.
> Before trying this I would like to hear if anybody has a solution to the
> problem or another way to use ftp or scp?
> Regards
> Jesper Linvald
> MAERSK DATA TRANSPORT
> Tel no.: +45 3911 1891
> e-mail: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Fixes for Maven changelog plugin to work with CVS 1.12.9
Hi, I recompiled maven changelog plug-in so that it works with CVS 1.12.9 log format. If anyone is also having the same problem, I'll post the changes to the mailing list. cheers, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] New Plugin for Use Case Driven Design
I am releasing a new plugin that helps you manage your use cases. It also helps you document the sequence information and generate the CRC cards. You can find more information here. http://www.itbrain.com.mx/ucdd -- Humberto - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide a private version of a specific plugin?
Dion Gillard schrieb: So you have a plugin, specified as a dependency, using SNAPSHOT as the version and would like maven not to download it but use your version instead? Is that it? yes. On Mon, 09 Aug 2004 20:00:36 +0200, Peter Nabbefeld <[EMAIL PROTECTED]> wrote: Dion Gillard schrieb: On Mon, 09 Aug 2004 16:36:15 +0200, Peter Nabbefeld <[EMAIL PROTECTED]> wrote: Hello, I want a specific plugin not to be updated (so -o does not work, as no plugin would be updated) and provide a private version instead. Could anybody help me, how to achieve this? Updated? By what? AFAIK, maven will download the most recent version of a snapshot version, if not in offline mode? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: disable checkstyle?
Sorry Malachi, I misunderstood your original question. I run javadocs without checkstyle, but I'm using JDK1.4. Jeff On Mon, 09 Aug 2004, at 19:57:30 [GMT -0700] Malachi de AElfweald wrote: > I had tried that; currently, I have the entire report section commented out. > Are you using JDK1.5 enums and static imports? > Malachi > At 07:21 AM 8/8/2004, you wrote: >>I just have this: >> >> >> maven-javadoc-plugin >> >> >>in my project.xml, and get javadocs without checkstyle. What does your >>report section look like? >> >> Jeff >> >>On Sun, 08 Aug 2004, at 06:38:28 [GMT -0700] Malachi de AElfweald >>wrote: >> >> > It appears that checkstyle prevents JDK1.5 source from being compiled >> (enum >> > or static imports). The only way I have been able to disable it was to >> > completely stop all javadoc, site, and reporting. Even deregistering it >> > didn't seem to work. >> >> > Is there any way to still do javadocs without using checkstyle? >> >> > BTW: Yes, I did submit a Jira bug -- would just be nice to have >> javadocs of >> > my code before checkstyle is fixed. >> >> > Thanks, >> > Malachi >> >>-- >>mailto:[EMAIL PROTECTED] >> >> >> >>- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: disable checkstyle?
I had tried that; currently, I have the entire report section commented out. Are you using JDK1.5 enums and static imports? Malachi At 07:21 AM 8/8/2004, you wrote: I just have this: maven-javadoc-plugin in my project.xml, and get javadocs without checkstyle. What does your report section look like? Jeff On Sun, 08 Aug 2004, at 06:38:28 [GMT -0700] Malachi de AElfweald wrote: > It appears that checkstyle prevents JDK1.5 source from being compiled (enum > or static imports). The only way I have been able to disable it was to > completely stop all javadoc, site, and reporting. Even deregistering it > didn't seem to work. > Is there any way to still do javadocs without using checkstyle? > BTW: Yes, I did submit a Jira bug -- would just be nice to have javadocs of > my code before checkstyle is fixed. > Thanks, > Malachi -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard plugin release status?
We weren't talking about bugs. We were talking about new features. > So you'd rather not release early and often? That has nothing to do > with fixing bugs. But it has everything to do with not introducing new ones. > What if there are bugs fixed in the CVS version, critical ones even. I > don't see why they should wait for all outstanding bugs to be fixed > before releasing. That's why we've started with the bugfix releases. Critical, or a set of minor bugs all fixed. But lets not release after every new feature or whenever some code gets reformatted or some documentation gets added (since that can go to the website earlier). I probably got my wires crossed, but the point I wanted to make was that I think we should be fixing bugs before adding features, and doing more testing before officially releasing plugins after features are added. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard plugin release status?
On Mon, 9 Aug 2004 20:34:20 -0400, Brett Porter <[EMAIL PROTECTED]> wrote: > I strongly disagree. So you'd rather not release early and often? That has nothing to do with fixing bugs. > I'd rather we fix all outstanding bugs (or at least scope out a > release) for any release of a plugin now. We too often let bugs slide > and have a bad reputation for it. I think this is a combination of long release schedules and poor testing. If releases are well tested and bugs are fixed quickly, people would be happier than just waiting 'a year' for all outstanding bugs to be fixed. > If people really need new features, build from CVS. Put a new version > on it when it is done and tested. What if there are bugs fixed in the CVS version, critical ones even. I don't see why they should wait for all outstanding bugs to be fixed before releasing. My 2c. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: developing doclets with maven (revised)
Hi Charles & Dion,
Thanks for your recommendations!
Here's what I did:
In my project's build.properties:
maven.doccheck.tools.jar = ${tools.jar}
maven.jar.override = on
maven.jar.javadoc = ${maven.doccheck.tools.jar}
By default, it uses the tools.jar maven uses. In case you are running
it on Java 1.5, you can put the following in your
$HOME/build.properties:
maven.doccheck.tools.jar = /j2sdk1.4.2_04/lib/tools.jar
In Java 1.3 and before, it doesn't seem to compile anyways. Something
about the class version not being right.
Best regards,
-- Shinobu Kawai
On Mon, 9 Aug 2004 17:12:07 +1000
Dion Gillard <[EMAIL PROTECTED]> wrote:
> Maven defines tools.jar as a system property.
>
> On Mon, 9 Aug 2004 07:54:39 +0100, Charles Daniels <[EMAIL PROTECTED]> wrote:
> > My suggestion would be your second solution. Then each developer need only
> > define the property tools.jar in his/her build.properties file. Although,
> > you may want to consider using a version number in the property name (e.g.,
> > tools14.jar) just in case a developer also wants to point to version 1.3 for
> > some other project. This way they can have two distinct properties that
> > they can put in ~/build.properties.
> >
> >
> >
> > > -Original Message-
> > > From: Shinobu Kawai [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, August 09, 2004 6:45 AM
> > > To: Maven Users List
> > > Subject: developing doclets with maven (revised)
> > >
> > >
> > >
> > > Hi!
> > >
> > > I'm looking for a good way to develop doclets using maven. During
> > > compilation, I need the Javadoc API, but I'm probably going to give up
> > > putting the Javadoc 1.4 API in ibiblio.
> > > cf.
> > > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
> > he.org&msgNo=22207
> >
> > Now I'm looking for alternatives. Right now, I can think of two
> > solutions:
> >
> > 1. Make the jar myself (or use tools.jar) and put it in the local
> >repository or a private remote repository. Of course, I need tell
> >other developers that their repositories have to be manually added.
> >
> > 2. Use the maven.jar.override property and point the dependency to such
> >a jar file. I can expect this to work anywhere as long as maven is
> >running under the right version of java.
> > maven.jar.override = on
> > maven.jar.javadoc = ${tools.jar}
> >
> > Any suggestions? or other alternatives?
--
Shinobu Kawai <[EMAIL PROTECTED], [EMAIL PROTECTED]>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven.repo.remote with parameters
If you really want to use CVS (and I don't recommend it for this), you need to URL rewrite a path name to the view CVS URL on the web server I think. - Brett On Mon, 9 Aug 2004 16:42:40 -0400, Karan-Sahni (Contractor) <[EMAIL PROTECTED]> wrote: > How can I specify additional parameters with my remote repository url, For examlple, > if my remote repository is at > http://abc.com/viewcvs/RefLib/jars/configurator.jar?root=myroot > > how would I pass the extra parameter (root=myroot) ? > > Please help. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard plugin release status?
I strongly disagree. I'd rather we fix all outstanding bugs (or at least scope out a release) for any release of a plugin now. We too often let bugs slide and have a bad reputation for it. If people really need new features, build from CVS. Put a new version on it when it is done and tested. - Brett On Tue, 10 Aug 2004 07:35:15 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote: > I'd rather we release early and often > > On Mon, 9 Aug 2004 19:21:12 +0200, Carlos Sanchez > > > <[EMAIL PROTECTED]> wrote: > > Hi Vincent, > > > > If you don't want to make a release yet, you can deploy a SNAPSHOT to > > http://cvs.apache.org/repository/maven/plugins/ > > > > Just use -Dmaven.repo.list=apachecvs > > > > Regards > > > > Carlos Sanchez > > A Coruña, Spain > > > > Oness Project > > http://oness.sourceforge.net > > > > > > > > > > > -Original Message- > > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > > Sent: Monday, August 09, 2004 6:02 PM > > > To: 'Maven Users List' > > > Subject: RE: Dashboard plugin release status? > > > > > > Hi Paul, > > > > > > I'll release it next week end for you. > > > > > > Thanks > > > -Vincent > > > > > > > -Original Message- > > > > From: Paul Spencer [mailto:[EMAIL PROTECTED] > > > > Sent: lundi 9 août 2004 17:06 > > > > To: Maven Users List > > > > Subject: Dashboard plugin release status? > > > > > > > > What is the release of the Dashboard plugin? Currently v1.4 is in > > > > development. I know additional aggregator have been added since 1.3. > > > > > > > > Paul Spencer > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > http://www.multitask.com.au/people/dion/ > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : RE : Maven link legend
or just plugin:install maven-plugins/xdoc from CVS. On Mon, 9 Aug 2004 09:06:58 +0200, Heritier Arnaud <[EMAIL PROTECTED]> wrote: > Yes, it will work if you build maven and maven-plugins from CVS. > > If you want you can build only the maven-xdoc-plugin. > > Arnaud > > > -Message d'origine- > > De : Michael Bolin [mailto:[EMAIL PROTECTED] > > Envoyé : lundi 9 août 2004 09:02 > > À : Maven Users List > > Objet : Re: RE : Maven link legend > > > > > > > > If I build Maven from CVS and use it, will the legend appear > > automatically or do I have to add something to get it? > > > > Thanks, > > Michael > > > > On Mon, 9 Aug 2004 08:58:34 +0200, Heritier Arnaud > > <[EMAIL PROTECTED]> wrote: > > > This legend is only available in the CVS version of the > > > maven-xdoc-plugin. > > > > > > Arnaud. > > > > > > > -Message d'origine- > > > > De : Michael Bolin [mailto:[EMAIL PROTECTED] > > > > Envoyé : lundi 9 août 2004 08:50 > > > > À : [EMAIL PROTECTED] > > > > Objet : Maven link legend > > > > > > > > > > > > > > > > > > On the Maven home page, there is a nice legend explaining the > > > > external link icon. How can I create that legend in my own site? > > > > I've looked through the Maven CVS repository, and I can't > > find the > > > > setting that causes the legend to be created. > > > > > > > > Thanks, > > > > Michael > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide a private version of a specific plugin?
So you have a plugin, specified as a dependency, using SNAPSHOT as the version and would like maven not to download it but use your version instead? Is that it? On Mon, 09 Aug 2004 20:00:36 +0200, Peter Nabbefeld <[EMAIL PROTECTED]> wrote: > Dion Gillard schrieb: > > > On Mon, 09 Aug 2004 16:36:15 +0200, Peter Nabbefeld > > <[EMAIL PROTECTED]> wrote: > > > >>Hello, > >> > >>I want a specific plugin not to be updated (so -o does not work, as no > >>plugin would be updated) and provide a private version instead. Could > >>anybody help me, how to achieve this? > > > > > > Updated? By what? > > AFAIK, maven will download the most recent version of a snapshot > version, if not in offline mode? > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard plugin release status?
I'd rather we release early and often On Mon, 9 Aug 2004 19:21:12 +0200, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > Hi Vincent, > > If you don't want to make a release yet, you can deploy a SNAPSHOT to > http://cvs.apache.org/repository/maven/plugins/ > > Just use -Dmaven.repo.list=apachecvs > > Regards > > Carlos Sanchez > A Coruña, Spain > > Oness Project > http://oness.sourceforge.net > > > > > > -Original Message- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Monday, August 09, 2004 6:02 PM > > To: 'Maven Users List' > > Subject: RE: Dashboard plugin release status? > > > > Hi Paul, > > > > I'll release it next week end for you. > > > > Thanks > > -Vincent > > > > > -Original Message- > > > From: Paul Spencer [mailto:[EMAIL PROTECTED] > > > Sent: lundi 9 août 2004 17:06 > > > To: Maven Users List > > > Subject: Dashboard plugin release status? > > > > > > What is the release of the Dashboard plugin? Currently v1.4 is in > > > development. I know additional aggregator have been added since 1.3. > > > > > > Paul Spencer > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven.repo.remote with parameters
How can I specify additional parameters with my remote repository url, For examlple, if my remote repository is at http://abc.com/viewcvs/RefLib/jars/configurator.jar?root=myroot how would I pass the extra parameter (root=myroot) ? Please help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide a private version of a specific plugin?
Dion Gillard schrieb: On Mon, 09 Aug 2004 16:36:15 +0200, Peter Nabbefeld <[EMAIL PROTECTED]> wrote: Hello, I want a specific plugin not to be updated (so -o does not work, as no plugin would be updated) and provide a private version instead. Could anybody help me, how to achieve this? Updated? By what? AFAIK, maven will download the most recent version of a snapshot version, if not in offline mode? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dashboard plugin release status?
Hi Vincent, If you don't want to make a release yet, you can deploy a SNAPSHOT to http://cvs.apache.org/repository/maven/plugins/ Just use -Dmaven.repo.list=apachecvs Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 6:02 PM > To: 'Maven Users List' > Subject: RE: Dashboard plugin release status? > > Hi Paul, > > I'll release it next week end for you. > > Thanks > -Vincent > > > -Original Message- > > From: Paul Spencer [mailto:[EMAIL PROTECTED] > > Sent: lundi 9 août 2004 17:06 > > To: Maven Users List > > Subject: Dashboard plugin release status? > > > > What is the release of the Dashboard plugin? Currently v1.4 is in > > development. I know additional aggregator have been added since 1.3. > > > > Paul Spencer > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FTP ant task
What does it do when it doesn't work?
For me, the -X switch showed that there was a CNF exception for an oro
FTP class. I had to put this in my project.xml:
ant-contrib
ant-contrib
20020829
oro
NetComponents
xxx
root
The NetComponents JAR file is not at ibiblio, so I added it to our
company repo. The version 'xxx' I just added because there was no
version number associated with the JAR file.
In retrospect, the ant-contrib part may not be required. It looks like
the Ant FTP class is loaded automatically by Maven from
ant-optional-1.5.3-1.jar. I had to add the property
because it looked like Ant's FTP class was loaded in the root
classloader, but the NetComponents JAR was loaded by the Maven
classloader. I know the is deprecated, but I wasn't sure
how else to get it to work.
I did this in a plugin, so I added this to my plugin.jelly:
before invoking the "ftp" task. For a maven.xml file, you wouldn't use
${plugin}. I think you'd use ${context}, but I'm not positive.
Again, you may be able to drop the whole ant-contrib part.
Jeff
On Mon, 09 Aug 2004, at 12:40:51 [GMT +0200] Jesper Linvald wrote:
> Hello all,
> I am trying to use the ftp ant task from maven. It dosent work! Running
> the task straight from Ant works fine
> Some have suggested a brute hack with a typedef and dependency on Ant 1.6.
> Before trying this I would like to hear if anybody has a solution to the
> problem or another way to use ftp or scp?
> Regards
> Jesper Linvald
> MAERSK DATA TRANSPORT
> Tel no.: +45 3911 1891
> e-mail: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dashboard plugin release status?
Hi Paul, I'll release it next week end for you. Thanks -Vincent > -Original Message- > From: Paul Spencer [mailto:[EMAIL PROTECTED] > Sent: lundi 9 août 2004 17:06 > To: Maven Users List > Subject: Dashboard plugin release status? > > What is the release of the Dashboard plugin? Currently v1.4 is in > development. I know additional aggregator have been added since 1.3. > > Paul Spencer > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide a private version of a specific plugin?
On Mon, 09 Aug 2004 16:36:15 +0200, Peter Nabbefeld <[EMAIL PROTECTED]> wrote: > > Hello, > > I want a specific plugin not to be updated (so -o does not work, as no > plugin would be updated) and provide a private version instead. Could > anybody help me, how to achieve this? Updated? By what? -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject:clean problem
On Mon, 9 Aug 2004 16:23:01 +0100 , Peter Bright
<[EMAIL PROTECTED]> wrote:
> Does
>
> banner="Gathering project list"
>includes="${maven.multiproject.includes}"
>excludes="${maven.multiproject.excludes}"
>postProcessing="true"
>
> ignoreFailures="${maven.multiproject.ignoreFailures}"
>collectOnly="true"
>/>
>
>
> dir="${reactorProject.context.getVariable('maven.build.dest')}" />
> dir="${reactorProject.context.getVariable('maven.build.dir')}" />
> file="${reactorProject.context.getVariable('basedir')}/velocity.log"
> quiet="true" failonerror="false" />
>
>
>
> fit your needs? It seems to work well enough.
>
> I imagine it's looking at dependencies because it doesn't know that 'clean'
> doesn't need them.
This is a good alternative.
Maven doesn't know that clean is any different to compile or jar, and
still checks the projects dependencies as it processes them.
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject:clean problem
On Mon, 9 Aug 2004 11:28:53 -0300, Roberto Castro <[EMAIL PROTECTED]> wrote: > My intentions running Multiproject:clean was, exactly, to clean target directory, > before building another project. So, how can I run Multiproject:install first? It > doesn't make sense. In fact, I run Multiproject:install after "clean". You can call multiproject:install first. It will install the projects in the correct order. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiproject:clean problem
Does fit your needs? It seems to work well enough. I imagine it's looking at dependencies because it doesn't know that 'clean' doesn't need them. > -Original Message- > From: Roberto Castro [mailto:[EMAIL PROTECTED] > Sent: 09 August 2004 16:05 > To: Maven Users List > Subject: RES: Multiproject:clean problem > > > It doesn't make sense Carlos, Running "install", then "clean" > to run "install" again. I think "clean" could be used to > delete the directories, only this. Why it looks for the dependencies? > By the way, I'll delete target directory using ant. > Thank you a lot. > Regards, > > > Roberto de Castro > Analista de Suporte > Cetip - Desus Rio de Janeiro > +55 21 2276-7439 > mailto:[EMAIL PROTECTED] > > > > > -Mensagem original- > De: Carlos Sanchez [mailto:[EMAIL PROTECTED] > Enviada em: segunda-feira, 9 de agosto de 2004 11:33 > Para: 'Maven Users List' > Assunto: RE: Multiproject:clean problem > > > You only need to make multiproject:install once, so you have > dependent jars > in repo. Then you can run clean as many times as you want > without running > multiproject:install (until you change your dependencies). > > Regards > > Carlos Sanchez > A Coruña, Spain > > Oness Project > http://oness.sourceforge.net > > > > -Original Message- > > From: Roberto Castro [mailto:[EMAIL PROTECTED] > > Sent: Monday, August 09, 2004 4:29 PM > > To: Maven Users List > > Subject: RE: Multiproject:clean problem > > > > My intentions running Multiproject:clean was, exactly, to > > clean target directory, before building another project. So, > > how can I run Multiproject:install first? It doesn't make > > sense. In fact, I run Multiproject:install after "clean". > > Well, what I'm going to do is, delete target directory using > > ant script, because I'm afraid an old file in target > > directory could interfer when generating project again. > > By the way, thank you all for the comments. > > Regards, > > > > Roberto de Castro > > Analista de Suporte > > Cetip - Desus Rio de Janeiro > > +55 21 2276-7439 > > mailto:[EMAIL PROTECTED] > > > > > > > > > > -Mensagem original- > > De: Milos Kleint [mailto:[EMAIL PROTECTED] Enviada em: > > segunda-feira, 9 de agosto de 2004 10:41 > > Para: Maven Users List > > Assunto: Re: Multiproject:clean problem > > > > > > Dion Gillard wrote: > > > > >AFAIK, the reactor (which multiproject uses), verifies > > projects before > > >calling goals on them. > > > > > >This means, yes, you'll need all the dependent jars in the > > repo before > > >doing a multiproject:clean > > > > > > > > > > IMHO it shouldn't do it, at least for the the artifacts of > > the projects included in the multiproject clean. > > > > Milos > > > > > > >On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint > > <[EMAIL PROTECTED]> wrote: > > > > > > > > >>and what about the scenario when I do a multiproject clean the a > > >>multiproject build which however failt mid-way.. a subsequent > > >>multiproject clean failt, because it cannot resolve all > > dependencies.. > > >>is there a way out? it seems liuke one can only do a clean > > build after > > >>successfully building the multiproject.. > > >> > > >>Milos > > >> > > >> > > >> > > >> > > >>Dion Gillard wrote: > > >> > > >> > > >> > > >>>You typically need to do a multiproject:install or > > >>>multiproject:install-snapshot before using any other goals. > > >>> > > >>>This places the dependent jars in the local repo. > > >>> > > >>>On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro > > <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>> > > >>> > > Hi, when I run "Multiproject:clean" in my master project, > > it tries to find a jar file that was not created yet. > > I use an argument passed to Maven (mm_domain) to create > > the name of jar file. > > Is there a bug in Multiproject:clean? I've looked up in > > faq but I didn't find anything about this error. > > Here is log: > > + > > | Executing clean:clean MM - SPBDns > > | Memory: 3M/6M > > + > > Verifying dependencies for MM:spbdns Getting failed > dependencies: > > [EMAIL PROTECTED] > > Attempting to download spbmessage-cetip-snapshot.jar. > > Getting URL: > > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-sna > > pshot.jar > > Received status code: 404 > > File not found on one of the repos > > java.io.FileNotFoundException: > > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > > at > > org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) > > at > > org.apach
Re: CruiseControl plugin release status?
Sounds like time to release it. On Mon, 09 Aug 2004 11:10:29 -0400, Paul Spencer <[EMAIL PROTECTED]> wrote: > What is the release of the CruiseControl plugin? Currently v1.5 is in > development. I know report and "dependent project" support have been > added since 1.4. > > Paul Spencer > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin taglibs
--- Nigel Magnay <[EMAIL PROTECTED]> wrote: > Hello > > I have a plugin where I have declared a taglib by doing > > > > etc etc > > I can do plugin:install fine > > However, when I try and use it in my script, with > > > > > I get > "Tag library requested that is not present: 'myuri' in plugin 'null' > > > I'm evidently missing something here.. how do I 'register' my plugin? > I've examined the other plugins in the cache and I can't figure it > out... If you have installed your plugin at least once prior to adding your taglib, it may be a cache issue. I have noticed similar behavior when defining a new goal in a plugin that I have already installed. To resolve this, first run plugin:uninstall to clear your plugin from the cache, then run plugin:install again. Your taglib should then be recognized. > > Cheers, > Nigel > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CruiseControl plugin release status?
What is the release of the CruiseControl plugin? Currently v1.5 is in development. I know report and "dependent project" support have been added since 1.4. Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dashboard plugin release status?
What is the release of the Dashboard plugin? Currently v1.4 is in development. I know additional aggregator have been added since 1.3. Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: Multiproject:clean problem
It doesn't make sense Carlos, Running "install", then "clean" to run "install" again. I think "clean" could be used to delete the directories, only this. Why it looks for the dependencies? By the way, I'll delete target directory using ant. Thank you a lot. Regards, Roberto de Castro Analista de Suporte Cetip - Desus Rio de Janeiro +55 21 2276-7439 mailto:[EMAIL PROTECTED] -Mensagem original- De: Carlos Sanchez [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 9 de agosto de 2004 11:33 Para: 'Maven Users List' Assunto: RE: Multiproject:clean problem You only need to make multiproject:install once, so you have dependent jars in repo. Then you can run clean as many times as you want without running multiproject:install (until you change your dependencies). Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: Roberto Castro [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 4:29 PM > To: Maven Users List > Subject: RE: Multiproject:clean problem > > My intentions running Multiproject:clean was, exactly, to > clean target directory, before building another project. So, > how can I run Multiproject:install first? It doesn't make > sense. In fact, I run Multiproject:install after "clean". > Well, what I'm going to do is, delete target directory using > ant script, because I'm afraid an old file in target > directory could interfer when generating project again. > By the way, thank you all for the comments. > Regards, > > Roberto de Castro > Analista de Suporte > Cetip - Desus Rio de Janeiro > +55 21 2276-7439 > mailto:[EMAIL PROTECTED] > > > > > -Mensagem original- > De: Milos Kleint [mailto:[EMAIL PROTECTED] Enviada em: > segunda-feira, 9 de agosto de 2004 10:41 > Para: Maven Users List > Assunto: Re: Multiproject:clean problem > > > Dion Gillard wrote: > > >AFAIK, the reactor (which multiproject uses), verifies > projects before > >calling goals on them. > > > >This means, yes, you'll need all the dependent jars in the > repo before > >doing a multiproject:clean > > > > > > IMHO it shouldn't do it, at least for the the artifacts of > the projects included in the multiproject clean. > > Milos > > > >On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint > <[EMAIL PROTECTED]> wrote: > > > > > >>and what about the scenario when I do a multiproject clean the a > >>multiproject build which however failt mid-way.. a subsequent > >>multiproject clean failt, because it cannot resolve all > dependencies.. > >>is there a way out? it seems liuke one can only do a clean > build after > >>successfully building the multiproject.. > >> > >>Milos > >> > >> > >> > >> > >>Dion Gillard wrote: > >> > >> > >> > >>>You typically need to do a multiproject:install or > >>>multiproject:install-snapshot before using any other goals. > >>> > >>>This places the dependent jars in the local repo. > >>> > >>>On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro > <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > >>> > Hi, when I run "Multiproject:clean" in my master project, > it tries to find a jar file that was not created yet. > I use an argument passed to Maven (mm_domain) to create > the name of jar file. > Is there a bug in Multiproject:clean? I've looked up in > faq but I didn't find anything about this error. > Here is log: > + > | Executing clean:clean MM - SPBDns > | Memory: 3M/6M > + > Verifying dependencies for MM:spbdns Getting failed dependencies: > [EMAIL PROTECTED] > Attempting to download spbmessage-cetip-snapshot.jar. > Getting URL: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-sna > pshot.jar > Received status code: 404 > File not found on one of the repos > java.io.FileNotFoundException: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > at > org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) > at > org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact > (DependencyVerifier.java:326) > at > org.apache.maven.verifier.DependencyVerifier.getDependencies(D > ependencyVerifier.java:255) > at > org.apache.maven.verifier.DependencyVerifier.satisfyDependenci > es(DependencyVerifier.java:171) > at > org.apache.maven.verifier.DependencyVerifier.verify(Dependency > Verifier.java:97) > at > org.apache.maven.project.Project.verifyDependencies(Project.java:1365) > at > org.apache.maven.plugin.Plu
R: Multiproject:clean problem
To resolve this problem I used the following solution: The reactor has to be called using: ignoreFailures="true" (so it keeps going if there is a failure) and then maven can be invoked using: maven -o InfoBUS:clean (-o offline: this way maven ignores the central repo) The rationale is: When you clean-up do not care about dependencies and central-repo. Bye -Messaggio originale- Da: Carlos Sanchez [mailto:[EMAIL PROTECTED] Inviato: lunedì 9 agosto 2004 16.22 A: 'Maven Users List' Oggetto: RE: Multiproject:clean problem Hi, It was the subject of a previous thread and I think there was a solution. The issue is at http://jira.codehaus.org/browse/MAVEN-1270 Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: Milos Kleint [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 3:41 PM > To: Maven Users List > Subject: Re: Multiproject:clean problem > > Dion Gillard wrote: > > >AFAIK, the reactor (which multiproject uses), verifies > projects before > >calling goals on them. > > > >This means, yes, you'll need all the dependent jars in the > repo before > >doing a multiproject:clean > > > > > > IMHO it shouldn't do it, at least for the the artifacts of > the projects included in the multiproject clean. > > Milos > > > >On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint > <[EMAIL PROTECTED]> wrote: > > > > > >>and what about the scenario when I do a multiproject clean the a > >>multiproject build which however failt mid-way.. a subsequent > >>multiproject clean failt, because it cannot resolve all > dependencies.. > >>is there a way out? it seems liuke one can only do a clean > build after > >>successfully building the multiproject.. > >> > >>Milos > >> > >> > >> > >> > >>Dion Gillard wrote: > >> > >> > >> > >>>You typically need to do a multiproject:install or > >>>multiproject:install-snapshot before using any other goals. > >>> > >>>This places the dependent jars in the local repo. > >>> > >>>On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro > <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > >>> > Hi, when I run "Multiproject:clean" in my master project, > it tries to find a jar file that was not created yet. > I use an argument passed to Maven (mm_domain) to create > the name of jar file. > Is there a bug in Multiproject:clean? I've looked up in > faq but I didn't find anything about this error. > Here is log: > + > | Executing clean:clean MM - SPBDns > | Memory: 3M/6M > + > Verifying dependencies for MM:spbdns Getting failed dependencies: > [EMAIL PROTECTED] > Attempting to download spbmessage-cetip-snapshot.jar. > Getting URL: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-sna pshot.jar > Received status code: 404 > File not found on one of the repos > java.io.FileNotFoundException: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > at > org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) > at > org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact > (DependencyVerifier.java:326) > at > org.apache.maven.verifier.DependencyVerifier.getDependencies(D > ependencyVerifier.java:255) > at > org.apache.maven.verifier.DependencyVerifier.satisfyDependenci > es(DependencyVerifier.java:171) > at > org.apache.maven.verifier.DependencyVerifier.verify(Dependency > Verifier.java:97) > at > org.apache.maven.project.Project.verifyDependencies(Project.java:1365) > at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManage > r.java:510) > at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > at > org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag. > java:342) > at > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(Mave > nGoalTag.java:79) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction .performAction(MavenGoalTag.java:110) > at com.werken.werkz.Goal.fire(Goal.java:639) > at com.werken.werkz.Goal.attain(Goal.java:575) > at > com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > at > org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(Mav > enAttainGoalTag.java:127) > at > org.apache.commons.jelly.impl.TagScript.run
RE: Multiproject:clean problem
You only need to make multiproject:install once, so you have dependent jars in repo. Then you can run clean as many times as you want without running multiproject:install (until you change your dependencies). Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: Roberto Castro [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 4:29 PM > To: Maven Users List > Subject: RE: Multiproject:clean problem > > My intentions running Multiproject:clean was, exactly, to > clean target directory, before building another project. So, > how can I run Multiproject:install first? It doesn't make > sense. In fact, I run Multiproject:install after "clean". > Well, what I'm going to do is, delete target directory using > ant script, because I'm afraid an old file in target > directory could interfer when generating project again. > By the way, thank you all for the comments. > Regards, > > Roberto de Castro > Analista de Suporte > Cetip - Desus Rio de Janeiro > +55 21 2276-7439 > mailto:[EMAIL PROTECTED] > > > > > -Mensagem original- > De: Milos Kleint [mailto:[EMAIL PROTECTED] Enviada em: > segunda-feira, 9 de agosto de 2004 10:41 > Para: Maven Users List > Assunto: Re: Multiproject:clean problem > > > Dion Gillard wrote: > > >AFAIK, the reactor (which multiproject uses), verifies > projects before > >calling goals on them. > > > >This means, yes, you'll need all the dependent jars in the > repo before > >doing a multiproject:clean > > > > > > IMHO it shouldn't do it, at least for the the artifacts of > the projects included in the multiproject clean. > > Milos > > > >On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint > <[EMAIL PROTECTED]> wrote: > > > > > >>and what about the scenario when I do a multiproject clean the a > >>multiproject build which however failt mid-way.. a subsequent > >>multiproject clean failt, because it cannot resolve all > dependencies.. > >>is there a way out? it seems liuke one can only do a clean > build after > >>successfully building the multiproject.. > >> > >>Milos > >> > >> > >> > >> > >>Dion Gillard wrote: > >> > >> > >> > >>>You typically need to do a multiproject:install or > >>>multiproject:install-snapshot before using any other goals. > >>> > >>>This places the dependent jars in the local repo. > >>> > >>>On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro > <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > >>> > Hi, when I run "Multiproject:clean" in my master project, > it tries to find a jar file that was not created yet. > I use an argument passed to Maven (mm_domain) to create > the name of jar file. > Is there a bug in Multiproject:clean? I've looked up in > faq but I didn't find anything about this error. > Here is log: > + > | Executing clean:clean MM - SPBDns > | Memory: 3M/6M > + > Verifying dependencies for MM:spbdns Getting failed dependencies: > [EMAIL PROTECTED] > Attempting to download spbmessage-cetip-snapshot.jar. > Getting URL: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-sna > pshot.jar > Received status code: 404 > File not found on one of the repos > java.io.FileNotFoundException: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > at > org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) > at > org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact > (DependencyVerifier.java:326) > at > org.apache.maven.verifier.DependencyVerifier.getDependencies(D > ependencyVerifier.java:255) > at > org.apache.maven.verifier.DependencyVerifier.satisfyDependenci > es(DependencyVerifier.java:171) > at > org.apache.maven.verifier.DependencyVerifier.verify(Dependency > Verifier.java:97) > at > org.apache.maven.project.Project.verifyDependencies(Project.java:1365) > at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManage > r.java:510) > at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > at > org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag. > java:342) > at > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(Mave > nGoalTag.java:79) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction .performAction(MavenGoalTag.java:110) > >
How to provide a private version of a specific plugin?
Hello, I want a specific plugin not to be updated (so -o does not work, as no plugin would be updated) and provide a private version instead. Could anybody help me, how to achieve this? Kind regards Peter Nabbefeld - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiproject:clean problem
My intentions running Multiproject:clean was, exactly, to clean target directory, before building another project. So, how can I run Multiproject:install first? It doesn't make sense. In fact, I run Multiproject:install after "clean". Well, what I'm going to do is, delete target directory using ant script, because I'm afraid an old file in target directory could interfer when generating project again. By the way, thank you all for the comments. Regards, Roberto de Castro Analista de Suporte Cetip - Desus Rio de Janeiro +55 21 2276-7439 mailto:[EMAIL PROTECTED] -Mensagem original- De: Milos Kleint [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 9 de agosto de 2004 10:41 Para: Maven Users List Assunto: Re: Multiproject:clean problem Dion Gillard wrote: >AFAIK, the reactor (which multiproject uses), verifies projects before >calling goals on them. > >This means, yes, you'll need all the dependent jars in the repo before >doing a multiproject:clean > > IMHO it shouldn't do it, at least for the the artifacts of the projects included in the multiproject clean. Milos >On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint <[EMAIL PROTECTED]> wrote: > > >>and what about the scenario when I do a multiproject clean the a >>multiproject build which however failt mid-way.. a subsequent >>multiproject clean failt, because it cannot resolve all dependencies.. >>is there a way out? it seems liuke one can only do a clean build after >>successfully building the multiproject.. >> >>Milos >> >> >> >> >>Dion Gillard wrote: >> >> >> >>>You typically need to do a multiproject:install or >>>multiproject:install-snapshot before using any other goals. >>> >>>This places the dependent jars in the local repo. >>> >>>On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>> Hi, when I run "Multiproject:clean" in my master project, it tries to find a jar file that was not created yet. I use an argument passed to Maven (mm_domain) to create the name of jar file. Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find anything about this error. Here is log: + | Executing clean:clean MM - SPBDns | Memory: 3M/6M + Verifying dependencies for MM:spbdns Getting failed dependencies: [EMAIL PROTECTED] Attempting to download spbmessage-cetip-snapshot.jar. Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar Received status code: 404 File not found on one of the repos java.io.FileNotFoundException: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) at org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326) at org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97) at org.apache.maven.project.Project.verifyDependencies(Project.java:1365) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:342) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.w
RE: Multiproject:clean problem
Hi, It was the subject of a previous thread and I think there was a solution. The issue is at http://jira.codehaus.org/browse/MAVEN-1270 Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: Milos Kleint [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 3:41 PM > To: Maven Users List > Subject: Re: Multiproject:clean problem > > Dion Gillard wrote: > > >AFAIK, the reactor (which multiproject uses), verifies > projects before > >calling goals on them. > > > >This means, yes, you'll need all the dependent jars in the > repo before > >doing a multiproject:clean > > > > > > IMHO it shouldn't do it, at least for the the artifacts of > the projects included in the multiproject clean. > > Milos > > > >On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint > <[EMAIL PROTECTED]> wrote: > > > > > >>and what about the scenario when I do a multiproject clean the a > >>multiproject build which however failt mid-way.. a subsequent > >>multiproject clean failt, because it cannot resolve all > dependencies.. > >>is there a way out? it seems liuke one can only do a clean > build after > >>successfully building the multiproject.. > >> > >>Milos > >> > >> > >> > >> > >>Dion Gillard wrote: > >> > >> > >> > >>>You typically need to do a multiproject:install or > >>>multiproject:install-snapshot before using any other goals. > >>> > >>>This places the dependent jars in the local repo. > >>> > >>>On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro > <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > >>> > Hi, when I run "Multiproject:clean" in my master project, > it tries to find a jar file that was not created yet. > I use an argument passed to Maven (mm_domain) to create > the name of jar file. > Is there a bug in Multiproject:clean? I've looked up in > faq but I didn't find anything about this error. > Here is log: > + > | Executing clean:clean MM - SPBDns > | Memory: 3M/6M > + > Verifying dependencies for MM:spbdns Getting failed dependencies: > [EMAIL PROTECTED] > Attempting to download spbmessage-cetip-snapshot.jar. > Getting URL: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-sna pshot.jar > Received status code: 404 > File not found on one of the repos > java.io.FileNotFoundException: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > at > org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) > at > org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) > at > org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact > (DependencyVerifier.java:326) > at > org.apache.maven.verifier.DependencyVerifier.getDependencies(D > ependencyVerifier.java:255) > at > org.apache.maven.verifier.DependencyVerifier.satisfyDependenci > es(DependencyVerifier.java:171) > at > org.apache.maven.verifier.DependencyVerifier.verify(Dependency > Verifier.java:97) > at > org.apache.maven.project.Project.verifyDependencies(Project.java:1365) > at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManage > r.java:510) > at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > at > org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag. > java:342) > at > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(Mave > nGoalTag.java:79) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction .performAction(MavenGoalTag.java:110) > at com.werken.werkz.Goal.fire(Goal.java:639) > at com.werken.werkz.Goal.attain(Goal.java:575) > at > com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > at > org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(Mav > enAttainGoalTag.java:127) > at > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(Mave > nGoalTag.java:79) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction .performAction(MavenGoalTag.java:110) > at com.werken.werkz.Goal.fire(Goal.java:639) > at com.werken.werkz.Goal.attain(Goal.java:575) > at > com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > at > org.apache
Plugin taglibs
Hello I have a plugin where I have declared a taglib by doing etc etc I can do plugin:install fine However, when I try and use it in my script, with I get "Tag library requested that is not present: 'myuri' in plugin 'null' I'm evidently missing something here.. how do I 'register' my plugin? I've examined the other plugins in the cache and I can't figure it out... Cheers, Nigel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiproject:clean problem
Milos Kleint wrote on Monday, August 09, 2004 3:34 PM: > and what about the scenario when I do a multiproject clean the a > multiproject build which however failt mid-way.. a subsequent > multiproject clean failt, because it cannot resolve all > dependencies.. is there a way out? it seems liuke one can > only do a clean build after > successfully building the multiproject.. find . -type d -name "target" | xargs rm -rf ;-) - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiproject:clean problem
Dion Gillard wrote: AFAIK, the reactor (which multiproject uses), verifies projects before calling goals on them. This means, yes, you'll need all the dependent jars in the repo before doing a multiproject:clean IMHO it shouldn't do it, at least for the the artifacts of the projects included in the multiproject clean. Milos On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint <[EMAIL PROTECTED]> wrote: and what about the scenario when I do a multiproject clean the a multiproject build which however failt mid-way.. a subsequent multiproject clean failt, because it cannot resolve all dependencies.. is there a way out? it seems liuke one can only do a clean build after successfully building the multiproject.. Milos Dion Gillard wrote: You typically need to do a multiproject:install or multiproject:install-snapshot before using any other goals. This places the dependent jars in the local repo. On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro <[EMAIL PROTECTED]> wrote: Hi, when I run "Multiproject:clean" in my master project, it tries to find a jar file that was not created yet. I use an argument passed to Maven (mm_domain) to create the name of jar file. Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find anything about this error. Here is log: + | Executing clean:clean MM - SPBDns | Memory: 3M/6M + Verifying dependencies for MM:spbdns Getting failed dependencies: [EMAIL PROTECTED] Attempting to download spbmessage-cetip-snapshot.jar. Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar Received status code: 404 File not found on one of the repos java.io.FileNotFoundException: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) at org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326) at org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97) at org.apache.maven.project.Project.verifyDependencies(Project.java:1365) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:342) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.cli.App.doMain(App.java:486) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMetho
Re: Multiproject:clean problem
AFAIK, the reactor (which multiproject uses), verifies projects before calling goals on them. This means, yes, you'll need all the dependent jars in the repo before doing a multiproject:clean On Mon, 09 Aug 2004 15:33:41 +0200, Milos Kleint <[EMAIL PROTECTED]> wrote: > and what about the scenario when I do a multiproject clean the a > multiproject build which however failt mid-way.. a subsequent > multiproject clean failt, because it cannot resolve all dependencies.. > is there a way out? it seems liuke one can only do a clean build after > successfully building the multiproject.. > > Milos > > > > > Dion Gillard wrote: > > >You typically need to do a multiproject:install or > >multiproject:install-snapshot before using any other goals. > > > >This places the dependent jars in the local repo. > > > >On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro <[EMAIL PROTECTED]> wrote: > > > > > >>Hi, when I run "Multiproject:clean" in my master project, it tries to find a jar > >>file that was not created yet. > >>I use an argument passed to Maven (mm_domain) to create the name of jar file. > >>Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find > >>anything about this error. > >>Here is log: > >>+ > >>| Executing clean:clean MM - SPBDns > >>| Memory: 3M/6M > >>+ > >>Verifying dependencies for MM:spbdns > >>Getting failed dependencies: [EMAIL PROTECTED] > >>Attempting to download spbmessage-cetip-snapshot.jar. > >>Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > >>Received status code: 404 > >>File not found on one of the repos > >>java.io.FileNotFoundException: > >>http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > >>at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) > >>at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) > >>at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) > >>at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) > >>at > >> org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326) > >>at > >> org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255) > >>at > >> org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171) > >>at > >> org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97) > >>at org.apache.maven.project.Project.verifyDependencies(Project.java:1365) > >>at > >> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510) > >>at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > >>at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:342) > >>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > >>at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) > >>at com.werken.werkz.Goal.fire(Goal.java:639) > >>at com.werken.werkz.Goal.attain(Goal.java:575) > >>at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) > >>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > >>at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) > >>at com.werken.werkz.Goal.fire(Goal.java:639) > >>at com.werken.werkz.Goal.attain(Goal.java:575) > >>at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) > >>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > >>at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) > >>at > >> org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) > >>at com.werken.werkz.Goal.fire(Goal.java:639) > >>at com.werken.werkz.Goal.attain(Goal.java:575) > >>at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > >>at > >> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634) > >>at org.apache.maven.MavenSession.attai
Re: Multiproject:clean problem
and what about the scenario when I do a multiproject clean the a multiproject build which however failt mid-way.. a subsequent multiproject clean failt, because it cannot resolve all dependencies.. is there a way out? it seems liuke one can only do a clean build after successfully building the multiproject.. Milos Dion Gillard wrote: You typically need to do a multiproject:install or multiproject:install-snapshot before using any other goals. This places the dependent jars in the local repo. On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro <[EMAIL PROTECTED]> wrote: Hi, when I run "Multiproject:clean" in my master project, it tries to find a jar file that was not created yet. I use an argument passed to Maven (mm_domain) to create the name of jar file. Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find anything about this error. Here is log: + | Executing clean:clean MM - SPBDns | Memory: 3M/6M + Verifying dependencies for MM:spbdns Getting failed dependencies: [EMAIL PROTECTED] Attempting to download spbmessage-cetip-snapshot.jar. Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar Received status code: 404 File not found on one of the repos java.io.FileNotFoundException: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) at org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326) at org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97) at org.apache.maven.project.Project.verifyDependencies(Project.java:1365) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:342) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.cli.App.doMain(App.java:486) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) WARNING: Failed to download spbmessage-cetip-snapshot.jar. Root cause Fi
Re: Multiproject:clean problem
You typically need to do a multiproject:install or multiproject:install-snapshot before using any other goals. This places the dependent jars in the local repo. On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro <[EMAIL PROTECTED]> wrote: > Hi, when I run "Multiproject:clean" in my master project, it tries to find a jar > file that was not created yet. > I use an argument passed to Maven (mm_domain) to create the name of jar file. > Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find > anything about this error. > Here is log: > + > | Executing clean:clean MM - SPBDns > | Memory: 3M/6M > + > Verifying dependencies for MM:spbdns > Getting failed dependencies: [EMAIL PROTECTED] > Attempting to download spbmessage-cetip-snapshot.jar. > Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > Received status code: 404 > File not found on one of the repos > java.io.FileNotFoundException: > http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar > at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) > at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) > at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) > at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) > at > org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326) > at > org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255) > at > org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171) > at > org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97) > at org.apache.maven.project.Project.verifyDependencies(Project.java:1365) > at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510) > at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:342) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) > at com.werken.werkz.Goal.fire(Goal.java:639) > at com.werken.werkz.Goal.attain(Goal.java:575) > at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > at > org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) > at com.werken.werkz.Goal.fire(Goal.java:639) > at com.werken.werkz.Goal.attain(Goal.java:575) > at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > at > org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) > at com.werken.werkz.Goal.fire(Goal.java:639) > at com.werken.werkz.Goal.attain(Goal.java:575) > at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) > at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634) > at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > at org.apache.maven.cli.App.doMain(App.java:486) > at org.apache.maven.cli.App.main(App.java:1215) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > WARNING: Failed to download spbmessage-cetip-snapshot.jar. > Root cause > Final Memory: 3M/6M > Total time: 32 seconds > Finished at: Mon Aug 09 12:57:57 GMT 2004 > > Thanks in advance, > > Robert
Multiproject:clean problem
Hi, when I run "Multiproject:clean" in my master project, it tries to find a jar file that was not created yet. I use an argument passed to Maven (mm_domain) to create the name of jar file. Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find anything about this error. Here is log: + | Executing clean:clean MM - SPBDns | Memory: 3M/6M + Verifying dependencies for MM:spbdns Getting failed dependencies: [EMAIL PROTECTED] Attempting to download spbmessage-cetip-snapshot.jar. Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar Received status code: 404 File not found on one of the repos java.io.FileNotFoundException: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287) at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181) at org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326) at org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97) at org.apache.maven.project.Project.verifyDependencies(Project.java:1365) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:342) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.cli.App.doMain(App.java:486) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) WARNING: Failed to download spbmessage-cetip-snapshot.jar. Root cause Final Memory: 3M/6M Total time: 32 seconds Finished at: Mon Aug 09 12:57:57 GMT 2004 Thanks in advance, Roberto de Castro Analista de Suporte Cetip - Desus Rio de Janeiro +55 21 2276-7439 mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [scm] Provide property for cvs binary
Hi, Could you please raise an issue to JIRA http://jira.codehaus.org/browse/MPSCM ? Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Peter Nabbefeld > Sent: Monday, August 09, 2004 12:56 PM > To: [EMAIL PROTECTED] > Subject: [scm] Provide property for cvs binary > > > Hello, > > please provide a property to set the cvs binary to be used: > My PATH environment variable contains nearly about 700 > characters (more than 8 lines in the cmd window), so I'd > prefer not to add a path element for every helper > application. I suggest to temporarily add the > path-to-cvs-binary during evaluation of the jelly script only > if the property is set. > > Kind regards > > Peter Nabbefeld > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plans for m2?
Hello, is there a complete list of planned features for m2? Kind regards Peter Nabbefeld - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[scm] Provide property for cvs binary
Hello, please provide a property to set the cvs binary to be used: My PATH environment variable contains nearly about 700 characters (more than 8 lines in the cmd window), so I'd prefer not to add a path element for every helper application. I suggest to temporarily add the path-to-cvs-binary during evaluation of the jelly script only if the property is set. Kind regards Peter Nabbefeld - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Maven Return Codes
Hi, I found the solution myself. Instead of calling 'cmd /c maven' I have to call 'cmd /c call maven'. In this case the error code is corretly returned and interpreted by Ant and the build aborts. For completeness here the correct maven.xml section Joern -Ursprüngliche Nachricht- Von: Jörn Gebhardt [mailto:[EMAIL PROTECTED] Gesendet: Montag, 9. August 2004 11:27 An: [EMAIL PROTECTED] Betreff: Maven Return Codes Hi, we have modularized our build by using Maven. However, because the build runs into OutOfMemoryExceptions when we compile all modules within one Maven Reactor call, we are using the reactor only to determine the build order and call afterwards each module via the ant:exec call. Now we have the problem, that the build goes on even if one module fails. It seems that the failonerror Ant property doesn't work correctly. Does the maven.bat batch file return any error code that is passed on by the cmd shell? Does anybody know, how we can make sure that our build fails if one Maven call fails? Thanks in advance, Jörn
FTP ant task
Hello all, I am trying to use the ftp ant task from maven. It dosent work! Running the task straight from Ant works fine Some have suggested a brute hack with a typedef and dependency on Ant 1.6. Before trying this I would like to hear if anybody has a solution to the problem or another way to use ftp or scp? Regards Jesper Linvald MAERSK DATA TRANSPORT Tel no.: +45 3911 1891 e-mail: [EMAIL PROTECTED]
RE: Maven Return Codes
Hi,
The OutOfMemoryExceptions have been already discussed in previous threads.
Forking the jvm should help, also you can increase the memory available.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -Original Message-
> From: Jörn Gebhardt [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 09, 2004 11:27 AM
> To: [EMAIL PROTECTED]
> Subject: Maven Return Codes
>
> Hi,
>
> we have modularized our build by using Maven. However,
> because the build runs into OutOfMemoryExceptions when we
> compile all modules within one Maven Reactor call, we are
> using the reactor only to determine the build order and call
> afterwards each module via the ant:exec call.
>
> basedir="${basedir}"
> includes="*/project.xml"
> ignoreFailures="false"
> collectOnly="true"
> postProcessing="true"/>
>
>
> dir="${reactorProject.context.getVariable('basedir')}"
> failonerror="true">
>
>
>
>
> Now we have the problem, that the build goes on even if one
> module fails. It seems that the failonerror Ant property
> doesn't work correctly.
> Does the maven.bat batch file return any error code that is
> passed on by the cmd shell? Does anybody know, how we can
> make sure that our build fails if one Maven call fails?
>
> Thanks in advance,
> Jörn
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: release plugin future
Hi, To make releases you should use the scm:prepare-release and scm:perform-release goals. For distributions you can use the distribution plugin, if it suits your needs. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net > -Original Message- > From: Marcin Gurbisz [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 12:00 PM > To: Maven Users List > Subject: release plugin future > > I'm thinking about automating releasing tasks and building > distributions. > I was about to check how maven release plugin works, but I > saw that it has just been deprecated. > What is a future of releasing? > > Thanks, > Marcin > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
release plugin future
I'm thinking about automating releasing tasks and building distributions. I was about to check how maven release plugin works, but I saw that it has just been deprecated. What is a future of releasing? Thanks, Marcin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Return Codes
Hi, we have modularized our build by using Maven. However, because the build runs into OutOfMemoryExceptions when we compile all modules within one Maven Reactor call, we are using the reactor only to determine the build order and call afterwards each module via the ant:exec call. Now we have the problem, that the build goes on even if one module fails. It seems that the failonerror Ant property doesn't work correctly. Does the maven.bat batch file return any error code that is passed on by the cmd shell? Does anybody know, how we can make sure that our build fails if one Maven call fails? Thanks in advance, Jörn
Re: Maven shared via Samba-Share
It's posted [MAVEN-1420]. Thanks! Am So, den 08.08.2004 schrieb Brett Porter um 14:33: > I'll try this out in a week when I have access to a samba share. If > you haven't already, can you post to JIRA? > > Thanks, > Brett > > On Thu, 05 Aug 2004 09:08:07 +0200, Christian Mouttet > <[EMAIL PROTECTED]> wrote: > > Brett, > > > > here comes the output of 'maven -X -e'. 'maven --info' prints the same > > lines. > > > > --%<-- > > __ __ > > | \/ |__ _Apache__ ___ > > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > > |_| |_\__,_|\_/\___|_||_| v. 1.0 > > > > Initializing Plugins! > > org.apache.maven.MavenException: Maven was badly installed. Please > > reinstall it. > >at > > org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:240) > >at > > org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:207) > >at > > org.apache.maven.MavenSession.initialize(MavenSession.java:174) > >at org.apache.maven.cli.App.doMain(App.java:473) > >at org.apache.maven.cli.App.main(App.java:1215) > >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > >at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > >at java.lang.reflect.Method.invoke(Method.java:324) > >at com.werken.forehead.Forehead.run(Forehead.java:551) > >at com.werken.forehead.Forehead.main(Forehead.java:581) > > > > You have encountered an unknown error running Maven. Please help us to > > correct > > this problem by following these simple steps: > > - read the Maven FAQ at http://maven.apache.org/faq.html > > - run the same command again with the '-e' parameter, eg maven -e jar > > - search the maven-user archives for the error at > > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED] > > - post the output of maven -e to JIRA at > > http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign up > > first) > > - run 'maven --info' and post the output as the environment to the bug > > above > > > > > > Final Memory: 0M/1M > > Total time: 18 seconds > > Finished at: Thu Aug 05 08:58:30 CEST 2004 > > --%<-- > > > > I think this doen't help you very much. > > > > Regards > > > > -Christian > > > > Am Mi, den 04.08.2004 schrieb Brett Porter um 22:19: > > > > > > > could be a bug... can you send the output of -X? > > > > > > Thanks, > > > Brett > > > > > > On Wed, 04 Aug 2004 17:00:15 +0200, Christian Mouttet > > > <[EMAIL PROTECTED]> wrote: > > > > Hi Brett, > > > > > > > > thank's for your answer. I don't exactly understand what plugins > > > > directory are you talking about. Is it the 'plugins' directory that was > > > > untar'ed out of 'maven-1.0.tar.gz'? This directory isn't empty - there > > > > are plugin-jars. > > > > > > > > With Maven-1.0-rc I had a directory 'plugins' under $HOME/.maven > > > > (%USERPROFILE%\.maven). The final release uses cache to hold the > > > > unjar'ed plugins. > > > > > > > > Regards > > > > > > > > -Christian > > > > > > > > >Date: Fri, 30 Jul 2004 10:11:22 -0400 > > > > >From: Brett Porter <[EMAIL PROTECTED]> > > > > >Subject: Maven shared via Samba-Share > > > > >Content-Type: text/plain; charset=US-ASCII > > > > > > > > > > > > > > > > > >this error appears when the plugins directory is empty. The message > > > > >should be improved I think. > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: developing doclets with maven (revised)
Maven defines tools.jar as a system property.
On Mon, 9 Aug 2004 07:54:39 +0100, Charles Daniels <[EMAIL PROTECTED]> wrote:
> My suggestion would be your second solution. Then each developer need only
> define the property tools.jar in his/her build.properties file. Although,
> you may want to consider using a version number in the property name (e.g.,
> tools14.jar) just in case a developer also wants to point to version 1.3 for
> some other project. This way they can have two distinct properties that
> they can put in ~/build.properties.
>
>
>
> > -Original Message-
> > From: Shinobu Kawai [mailto:[EMAIL PROTECTED]
> > Sent: Monday, August 09, 2004 6:45 AM
> > To: Maven Users List
> > Subject: developing doclets with maven (revised)
> >
> >
> >
> > Hi!
> >
> > I'm looking for a good way to develop doclets using maven. During
> > compilation, I need the Javadoc API, but I'm probably going to give up
> > putting the Javadoc 1.4 API in ibiblio.
> > cf.
> > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
> he.org&msgNo=22207
>
> Now I'm looking for alternatives. Right now, I can think of two
> solutions:
>
> 1. Make the jar myself (or use tools.jar) and put it in the local
>repository or a private remote repository. Of course, I need tell
>other developers that their repositories have to be manually added.
>
> 2. Use the maven.jar.override property and point the dependency to such
>a jar file. I can expect this to work anywhere as long as maven is
>running under the right version of java.
> maven.jar.override = on
> maven.jar.javadoc = ${tools.jar}
>
> Any suggestions? or other alternatives?
>
> Best regards,
> -- Shinobu Kawai
>
> --
> Shinobu Kawai <[EMAIL PROTECTED], [EMAIL PROTECTED]>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE : RE : Maven link legend
Yes, it will work if you build maven and maven-plugins from CVS. If you want you can build only the maven-xdoc-plugin. Arnaud > -Message d'origine- > De : Michael Bolin [mailto:[EMAIL PROTECTED] > Envoyé : lundi 9 août 2004 09:02 > À : Maven Users List > Objet : Re: RE : Maven link legend > > > If I build Maven from CVS and use it, will the legend appear > automatically or do I have to add something to get it? > > Thanks, > Michael > > On Mon, 9 Aug 2004 08:58:34 +0200, Heritier Arnaud > <[EMAIL PROTECTED]> wrote: > > This legend is only available in the CVS version of the > > maven-xdoc-plugin. > > > > Arnaud. > > > > > -Message d'origine- > > > De : Michael Bolin [mailto:[EMAIL PROTECTED] > > > Envoyé : lundi 9 août 2004 08:50 > > > À : [EMAIL PROTECTED] > > > Objet : Maven link legend > > > > > > > > > > > > > On the Maven home page, there is a nice legend explaining the > > > external link icon. How can I create that legend in my own site? > > > I've looked through the Maven CVS repository, and I can't > find the > > > setting that causes the legend to be created. > > > > > > Thanks, > > > Michael > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : Maven link legend
If I build Maven from CVS and use it, will the legend appear automatically or do I have to add something to get it? Thanks, Michael On Mon, 9 Aug 2004 08:58:34 +0200, Heritier Arnaud <[EMAIL PROTECTED]> wrote: > This legend is only available in the CVS version of the maven-xdoc-plugin. > > Arnaud. > > > -Message d'origine- > > De : Michael Bolin [mailto:[EMAIL PROTECTED] > > Envoyé : lundi 9 août 2004 08:50 > > À : [EMAIL PROTECTED] > > Objet : Maven link legend > > > > > > > > On the Maven home page, there is a nice legend explaining the > > external link icon. How can I create that legend in my own > > site? I've looked through the Maven CVS repository, and I > > can't find the setting that causes the legend to be created. > > > > Thanks, > > Michael > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
