RE: continuum-1.1-beta-1: Error while generating mail contents.
You're right the workflow to attached installation to a profile is actually confusing. It's fixed in trunk. In beta-2, you will have an other option to automatically create a profile when you create an installation. -- Olivier -Message d'origine- De : Andreas Guther [mailto:[EMAIL PROTECTED] Envoyé : vendredi 10 août 2007 02:22 À : continuum-users@maven.apache.org Objet : RE: continuum-1.1-beta-1: Error while generating mail contents. Found the problem: I did not fully configure the profile: it had no JDK installation assigned. This is not very clear in the current documentation. After fixing this the build succeeded and email were sent. Andreas -Original Message- From: Andreas Guther [mailto:[EMAIL PROTECTED] Sent: Thursday, August 09, 2007 4:55 PM To: continuum-users@maven.apache.org Subject: RE: continuum-1.1-beta-1: Error while generating mail contents. Hi, I have the feeling it is the other way around. Projects without a profile send email but the one with profile does not. But need to look at the Issue CONTINUUM-1374. Andreas -Original Message- From: LAMY Olivier [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 07, 2007 1:21 PM To: continuum-users@maven.apache.org Subject: RE: continuum-1.1-beta-1: Error while generating mail contents. Issue CONTINUUM-1374. Simple workaround add a jdk to your profile. Will be fix in beta-2. -- Olivier -Message d'origine- De : Andreas Guther [mailto:[EMAIL PROTECTED] Envoyé : mardi 7 août 2007 03:05 À : continuum-users@maven.apache.org Objet : continuum-1.1-beta-1: Error while generating mail contents. Hi, After installing continuum-1.1-beta-1 last week all went fine and I was very pleased with the changes and new features. We just discovered that since a few days we do not get email messages anymore. The logs say: Error while generating mail contents. (Stack trace below) I can send email from the Linux box continuum is running. I also got emails in the beginning. I also restarted the server. Where should I look to find out what causes the problem? Andreas 285551 [pool-1-thread-1] INFO org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Working directory: /opt/continuum-1.1-beta-1/apps/continuum/webapp/WEB-INF/working-director y/40 288618 [pool-1-thread-1] INFO org.apache.maven.continuum.execution.ContinuumBuildExecutor:maven2 - Exit code: 1 288753 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Performing action deploy-artifact 288863 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher: default - Error while trying to use the mailnotifier. org.codehaus.plexus.notification.NotificationException: Error while generating mail contents. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.build Complete(MailContinuumNotifier.java:335) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendN otification(MailContinuumNotifier.java:227) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:199) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.buildComplete(DefaultContinuumNotificationDispatcher.java:103) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBui ld(DefaultBuildController.java:219) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:173) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter .call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask .java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker .run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.apache.maven.continuum.installation.DefaultInstallationService.getJd kInformations(DefaultInstallationService.java:245) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getJa vaHomeInformations(MailContinuumNotifier.java:363) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.build Complete(MailContinuumNotifier.java:308) ... 13 more 288870
Assembly plugin question
Hey all, question about the assembly plugin. Is there a way to specify one assembly.xml descriptor within a POM that is global to all projects and to have it inherit down to all sub-projects? Right now when I run the execution phase the assembly is tied to from a sub-project of a parent project (that is in turn a child to the global POM) I get an error saying it can not locate the descriptor. I would like to only have one descriptor for all projects and have it in the master parent POM. That way I can specify a global execution phase so all sources get added into each project every time they are built but, I only want ZIP files, not TAR and tarball as in the default. Thanks in advance, Adam [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disable logins for continuum?
What is your version? Luke Matthews a écrit : Hi all, Quick question, is it possible to disable having to log in to continuum? Our CI server is well inside our firewall and it is a pain having to log in. I click the remember me but it seems to forget me! Cheers, Luke.
How to define as to which phase the goal is to be executed
Another quick question, Where to define/configure as to which phase the Mojo/goal is to be executed, so far with what I have read it seems that it's the Mojo class file which has this annotation for @phase (at class level) to tell MAVEN about the phase the goal is to be executed, just wanted to be sure if that's the only way. Farhan.
Re: How to define as to which phase the goal is to be executed
Farhan Sarwar [EMAIL PROTECTED] writes: Another quick question, Where to define/configure as to which phase the Mojo/goal is to be executed, so far with what I have read it seems that it's the Mojo class file which has this annotation for @phase (at class level) to tell MAVEN about the phase the goal is to be executed, just wanted to be sure if that's the only way. Farhan. No, that's not the only way, that's the default way to define when a mojo is run. You can also bind a mojo in a different phase, or even multiple phases, using the execution configuration in your POM (Note: the one that use the mojo, not the one that defines the mojo): plugins plugin artifactIdmyartifact-plugin groupId... executions execution idexe1/id goals goalmygoal/goal /goals configuration !-- config for this execution goes here -- /configuration /execution /executions HTH -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly plugin question
Hi, -- Beware: Untested Instructions -- :-) I. Create a new project, put the assembly descriptors you want to have available across projects in 'src/resources/assemblies' and install/deploy the artifact to your local/internal repository. II. In your projects configure the plugin like this: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId dependencies dependency !-- artifact containing the descriptors -- /dependency /dependencies configuration descriptorRefs descriptorRefname-of-your-descriptor/descriptorRef /descriptorRefs /configuration /plugin -Tim Adam schrieb: Hey all, question about the assembly plugin. Is there a way to specify one assembly.xml descriptor within a POM that is global to all projects and to have it inherit down to all sub-projects? Right now when I run the execution phase the assembly is tied to from a sub-project of a parent project (that is in turn a child to the global POM) I get an error saying it can not locate the descriptor. I would like to only have one descriptor for all projects and have it in the master parent POM. That way I can specify a global execution phase so all sources get added into each project every time they are built but, I only want ZIP files, not TAR and tarball as in the default. Thanks in advance, Adam [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 check for goals in each phase
Farhan Sarwar [EMAIL PROTECTED] writes: Hey guys, Wanted to know if there is a way to determine the goals configured to be executed in each of life-cycle phases? Hello, Maybe this link can answer your questions. Look also in sonatype's and devzuz's books: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html http://maven.apache.org/articles.html -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 documentation portion of the site is horribly broken
On 8/10/07, EJ Ciramella [EMAIL PROTECTED] wrote: Can someone please either enlighten me as to what I'm doing wrong or fix the site? Almost 90% of the links anywhere don't work. Considering this is the ONLY source for m2 documentation, this is a huge failure. http://maven.apache.org/plugins/index.html No idea yet what happened, but to work around it, edit the url to remove index.html#. For example: http://maven.apache.org/plugins/index.html#maven-compiler-plugin/ -- http://maven.apache.org/plugins/maven-compiler-plugin/ -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2 documentation portion of the site is horribly broken
Can someone please either enlighten me as to what I'm doing wrong or fix the site? Almost 90% of the links anywhere don't work. Considering this is the ONLY source for m2 documentation, this is a huge failure. http://maven.apache.org/plugins/index.html None of those links work anymore for me. I'm using the latest firefox for what its worth.
RE: Maven 2 documentation portion of the site is horribly broken
U - any of the jump-to-location-on-page links are similarly broken. Thanks for the workaround, I'm looking forward to the real fix. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 12:13 PM To: Maven Users List Subject: Re: Maven 2 documentation portion of the site is horribly broken Looks like the links are broken thanks to a recent update of the site. Fortunately, they are easy for you to fix in your browser until the site is updated again (hopefully *very* soon) with proper links. Let's take the jar plugin as an example: Current link is: http://maven.apache.org/plugins/index.html#maven-jar-plugin/ Correct link is: http://maven.apache.org/plugins/maven-jar-plugin/ Just cut out the index.html# and you'll get to the documentation for the jar plugin. Wayne On 8/10/07, EJ Ciramella [EMAIL PROTECTED] wrote: Can someone please either enlighten me as to what I'm doing wrong or fix the site? Almost 90% of the links anywhere don't work. Considering this is the ONLY source for m2 documentation, this is a huge failure. http://maven.apache.org/plugins/index.html None of those links work anymore for me. I'm using the latest firefox for what its worth. - 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: [m2] WHere can I find a list of all the standard maven properties?
If you want to reference resources from child builds you should make
a shared jar to include these files and reference them through the
classpath in child projects.
Andy
On 28 Jul 2007, at 23:25, Mick Knutson wrote:
I am actually looking for something like ${project.home} as I have
multiple
modules, and want to reference a file in the project root.
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trying to compile using jav 1.3 when I've 1.5
Hi,
When i try to user mvn compile I'm getting the following error, any
help
[INFO] [compiler:compile]
[INFO] Compiling 127 source files to F:\build\cougar_common\target
\classes
[INFO]
--
--
[ERROR] BUILD FAILURE
[INFO]
--
--
[INFO] Compilation failure
F:\build\path\file.java:[77, 19] generics are not supported in -
source 1.3
(try -source 1.5 to enable generics)
public ListObject getObjects(Class clazz, String
orderByField) {
I'm using maven 2.0.7 and I've Java 1.5 installed in my system. I'm
failed to understand why maven is trying to compile using 1.3 when
I've 1.5.
http://maven.apache.org/general.html#compiling-j2se-5
HTH
Thorsten
PGP.sig
Description: Signierter Teil der Nachricht
Re: Maven 2 documentation portion of the site is horribly broken
Looks like the links are broken thanks to a recent update of the site. Fortunately, they are easy for you to fix in your browser until the site is updated again (hopefully *very* soon) with proper links. Let's take the jar plugin as an example: Current link is: http://maven.apache.org/plugins/index.html#maven-jar-plugin/ Correct link is: http://maven.apache.org/plugins/maven-jar-plugin/ Just cut out the index.html# and you'll get to the documentation for the jar plugin. Wayne On 8/10/07, EJ Ciramella [EMAIL PROTECTED] wrote: Can someone please either enlighten me as to what I'm doing wrong or fix the site? Almost 90% of the links anywhere don't work. Considering this is the ONLY source for m2 documentation, this is a huge failure. http://maven.apache.org/plugins/index.html None of those links work anymore for me. I'm using the latest firefox for what its worth. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin index=true ignoring files in META-INF/
Zarick Lau wrote: Dear users and developers, I have a module with this files /src/main/resources/META-INF/persistence.xml /src/main/resources/log4j.xml In the pom, I have set indextrue/index for the maven-jar-plugin After package as a jar, the log4j.xml is listed but META-INF/persistence.xml is not listed in the META-INF/INDEX.LIST file. So, my question is, whether put the persistence.xml in the /src/main/resources/META-INF/ is a correct and supported way? Or I should put these files in some other place? You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10. Someone needs to update the maven-jar-plugin/maven-archiver to use a later version of plexus-archiver. Max. signature.asc Description: OpenPGP digital signature
maven-jar-plugin index=true ignoring files in META-INF/
Dear users and developers, I have a module with this files /src/main/resources/META-INF/persistence.xml /src/main/resources/log4j.xml In the pom, I have set indextrue/index for the maven-jar-plugin After package as a jar, the log4j.xml is listed but META-INF/persistence.xml is not listed in the META-INF/INDEX.LIST file. So, my question is, whether put the persistence.xml in the /src/main/resources/META-INF/ is a correct and supported way? Or I should put these files in some other place? Thanks in advance Best regards, Zarick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: properties
On 8/10/07, John Coleman [EMAIL PROTECTED] wrote:
Hi,
How do I return the value of the active profiles id as a property in my
pom.xml.
Add a property to each profile with a specific property name (eg:
Profile 'dev':
properties
active.profiledev/active.profile
/properties
Profile 'test':
properties
active.profiletest/active.profile
/properties
How do I override the property values in profiles.xml on a per
user basis?
Same way - you'll just have to manually create the custom profiles.xml.
Well, script it at least.
I thought I could put them in ${user.home}/build.properties,
but that seems not to work?!
No idea.
--
Eric Redmond
http://blog.propellors.net
TIA
John
Eurobase International Limited and its subsidiaries (Eurobase) are unable
to exercise control over the content of information in E-Mails. Any views
and opinions expressed may be personal to the sender and are not necessarily
those of Eurobase. Eurobase will not enter into any contractual obligations
in respect of any part of its business in any E-mail.
Privileged / confidential information may be contained in this message and
/or any attachments. This E-mail is intended for the use of the addressee(s)
only and may contain confidential information. If you are not the / an
intended recipient, you are hereby notified that any use or dissemination of
this communication is strictly prohibited. If you receive this transmission
in error, please notify us immediately, and then delete this E-mail.
Neither the sender nor Eurobase accepts any liability whatsoever for any
defects of any kind either in or arising from this E-mail transmission.
E-Mail transmission cannot be guaranteed to be secure or error-free, as
messages can be intercepted, lost, corrupted, destroyed, contain viruses, or
arrive late or incomplete. Eurobase does not accept any responsibility for
viruses and it is your responsibility to scan any attachments.
Eurobase Systems Limited is the main trading company in the Eurobase
International Group; registered in England and Wales as company number
02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex
CM2 0RE, UK.
RE: Continuum Emails
Thank you for your help. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 2:50 AM To: [EMAIL PROTECTED] Subject: Re: Continuum Emails No. In conf/plexus.xml, you must have something like that: resources !-- Mail Session -- resource namemail/Session/name typejavax.mail.Session/type properties property namemail.smtp.host/name valuelocalhost/value /property property namemail.smtp.port/name value25/value /property /properties /resource and in application.xml, you must keep the component declaration like it iwas when you installed Continuum: component roleorg.codehaus.plexus.mailsender.MailSender/role implementationorg.codehaus.plexus.mailsender.javamail.JndiJavamailMailSender/implementation configuration jndiSessionNamejava:comp/env/mail/Session/jndiSessionName /configuration /component Emmanuel LAMY Olivier a écrit : Yep. -Message d'origine- De : Morgovsky, Alexander (US - Glen Mills) [mailto:[EMAIL PROTECTED] Envoyé : vendredi 10 août 2007 00:36 À : [EMAIL PROTECTED] Objet : RE: Continuum Emails Does this mean that I should put the whole component node into plexus.xml? component roleorg.codehaus.plexus.mailsender.MailSender/role implementationorg.codehaus.plexus.mailsender.javamail.JndiJavamailMailSender/implementation configuration jndiSessionNamejava:comp/env/mail/Session/jndiSessionName smtp-host/smtp-host smtp-port/smtp-port /configuration /component -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, August 09, 2007 5:18 PM To: [EMAIL PROTECTED] Subject: Re: Continuum Emails the jndi conf must be done in conf/plexus.xml Morgovsky, Alexander (US - Glen Mills) a écrit : I am using Continuum 1.1-alpha-2. I have noticed that my Continuum instance is not sending out emails. In the logs I found the error: [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher: default - Error while trying to use the mailnotifier. org.codehaus.plexus.notification.NotificationException: Exception while sending message. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sen dM essage(MailContinuumNotifier.java:415) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.bui ld Complete(MailContinuumNotifier.java:319) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sen dN otification(MailContinuumNotifier.java:211) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDi sp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:198) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDi sp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:150) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDi sp atcher.buildComplete(DefaultContinuumNotificationDispatcher.java:103) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endB ui ld(DefaultBuildController.java:219) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.buil d( DefaultBuildController.java:173) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.ex ec uteTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exec ut orRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapt er .call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTa sk .java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Work er .runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Work er .run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:534) Caused by: org.codehaus.plexus.mailsender.MailSenderException: Error while sending the message. at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.sen d( AbstractJavamailMailSender.java:219) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sen dM essage(MailContinuumNotifier.java:411) ... 14 more I configured the continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\classes\META-INF\p le xus\application.xml with the following: component roleorg.codehaus.plexus.mailsender.MailSender/role
Documentation/Presentation Materials...
hi all, we've done an informal presentation on Maven to one of the development teams here at work. they liked what they saw and our manager wants a 'more polished' presentation that we can give to the other development teams and upper management. does anyone out there already have a presentation template, or free to use/modify presentation in Keynote, Impress, or PowerPoint? our initial presentation was on how/why it was best to change our project directory structure to match the Maven best practices directory structure, what the base commands were for Maven, using Maven to do complete, one click builds, and a very quick overview of Maven site. aside from the fancy presentation materials, is there anything i'm missing that i should include? thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin index=true ignoring files in META-INF/
On 8/10/07, Max Bowsher [EMAIL PROTECTED] wrote: Zarick Lau wrote: Dear users and developers, I have a module with this files /src/main/resources/META-INF/persistence.xml /src/main/resources/log4j.xml In the pom, I have set indextrue/index for the maven-jar-plugin After package as a jar, the log4j.xml is listed but META-INF/persistence.xml is not listed in the META-INF/INDEX.LIST file. So, my question is, whether put the persistence.xml in the /src/main/resources/META-INF/ is a correct and supported way? Or I should put these files in some other place? You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10. Thanks! I believe so !! Someone needs to update the maven-jar-plugin/maven-archiver to use a later version of plexus-archiver. Need to create an issue for this? Best regards, Zarick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] urgent issue with modules and sub-modules for initial builds
I'm having the same issue. Perhaps the cause is the same as whatever fixed http://jira.codehaus.org/browse/MNG-2434? Is anybody else experiencing this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [1.1-beta-1] How does the XML-RPC API work?
Hi Emmanuel, works great. Thanks! Emmanuel Venisse wrote: 1) the url is http://server:8080/continuum/xmlrpc 2) you use an old version of the client, the one to use is: dependency groupIdorg.apache.maven.continuum/groupId artifactIdcontinuum-xmlrpc-client/artifactId version1.1-beta-1/version /dependency and a sample client is available there: http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-client/src/main/java/org/apache/maven/continuum/xmlrpc/client/SampleClient.java Emmanuel Michael Meyer a écrit : Hi I'm using continuum-1.1-beta-1. And I would like to use the XML-RPC API to check the build state. When I run the following code I a get an exception stating that there were parsing errors: ProjectsReader pr = new ProjectsReader( new URL(http://server:8080/continuum) ); projects = pr.readProjects(); Am I doing something wrong or doesn't the XML-RPC api work for 1.1-beta-1 yet? In my pom.xml file I've added the following dependency: dependency groupIdorg.apache.maven.continuum/groupId artifactIdcontinuum-rpc-client/artifactId version1.0.3/version /dependency Cheers, michael -- Michael Meyer | [EMAIL PROTECTED] phone +41-44-247 79 12 | fax +41-44-247 70 75 Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch
Re: How to activate profile for certain packaging?
Hi
if you have access to the source code of the plugin you can do something
like this:
/**
* The packaging of this project.
*
* @parameter expression=${project.packaging}
* @required
* @readonly
*/
private String packaging;
public void execute() throws MojoExecutionException {
if (packaging.equals(war) {
...
}
}
Cheers, michael
Gisbert Amm wrote:
Michael Meyer schrieb:
Hi,
does this work?
activation
property
nameproject.packaging/name
valuewar/value
/property
/activation
Unfortunately not.
I'll describe my problem more generally instead of asking how to fix my
obviously wrong approach:
I need to execute a specific, home grown deployment preparation plugin
only for projects that produce a war (packagingwar/packaging). How
can I achieve that?
My first thought was to use a profile. However, that does not work
because a profile cannot be activated throught POM entries like
packagingwar/packaging. I don't want to set an extra property for
that either since all information I need is already covered in the
packaging element and doesn't need to be duplicated.
How do others implement conditional calls of certain plugins? How is the
Maven2 way to do that?
-Gisbert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Meyer | [EMAIL PROTECTED]
phone +41-44-247 79 12 | fax +41-44-247 70 75
Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to activate profile for certain packaging?
You could create a war specific parent pom with the plugin execution defined. -Tim Gisbert Amm schrieb: Michael Meyer schrieb: Hi, does this work? activation property nameproject.packaging/name valuewar/value /property /activation Unfortunately not. I'll describe my problem more generally instead of asking how to fix my obviously wrong approach: I need to execute a specific, home grown deployment preparation plugin only for projects that produce a war (packagingwar/packaging). How can I achieve that? My first thought was to use a profile. However, that does not work because a profile cannot be activated throught POM entries like packagingwar/packaging. I don't want to set an extra property for that either since all information I need is already covered in the packaging element and doesn't need to be duplicated. How do others implement conditional calls of certain plugins? How is the Maven2 way to do that? -Gisbert - 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: Assembly plugin question
Is there any way to do it with a configuration like this by adding the plugin abd descriptor to a super POM and to have it inherit down without having to specify the assembly in each project. Right now this is in the super POM: !-- Assembly Plugin configuration -- plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptorRefs descriptorRefsrc/descriptorRef /descriptorRefs /configuration executions execution phaseinstall/phase goals goalattached/goal /goals /execution /executions /plugin That keeps from having to update it across all projects. I'd like to be able to add a descriptor but, not have to add it to every project if at all possible. OR Is there any way with the above src descriptorRef to only get back one of the three source archives? Thanks, Adam On 8/10/07, Tim Kettler [EMAIL PROTECTED] wrote: Hi, -- Beware: Untested Instructions -- :-) I. Create a new project, put the assembly descriptors you want to have available across projects in 'src/resources/assemblies' and install/deploy the artifact to your local/internal repository. II. In your projects configure the plugin like this: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId dependencies dependency !-- artifact containing the descriptors -- /dependency /dependencies configuration descriptorRefs descriptorRefname-of-your-descriptor/descriptorRef /descriptorRefs /configuration /plugin -Tim Adam schrieb: Hey all, question about the assembly plugin. Is there a way to specify one assembly.xml descriptor within a POM that is global to all projects and to have it inherit down to all sub-projects? Right now when I run the execution phase the assembly is tied to from a sub-project of a parent project (that is in turn a child to the global POM) I get an error saying it can not locate the descriptor. I would like to only have one descriptor for all projects and have it in the master parent POM. That way I can specify a global execution phase so all sources get added into each project every time they are built but, I only want ZIP files, not TAR and tarball as in the default. Thanks in advance, Adam [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]
Trying to compile using jav 1.3 when I've 1.5
Hi all,
When i try to user mvn compile I'm getting the following error, any help
[INFO] [compiler:compile]
[INFO] Compiling 127 source files to F:\build\cougar_common\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
F:\build\path\file.java:[77, 19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListObject getObjects(Class clazz, String orderByField) {
I'm using maven 2.0.7 and I've Java 1.5 installed in my system. I'm
failed to understand why maven is trying to compile using 1.3 when I've 1.5.
Can anyone help me.
Thank you
Arun P Johny
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tests fail (class not found) when running against non-standard local repository location
I had a similar problem with maven-weblogic-plugin. Then I found out that it
was a problem with the white spaces in Documents and Settings so I added
something like this:
localRepository${HOMEDRIVE}/Docume~1/User/.m2/repository/localRepository
in the settings.xml and it worked perfectly.
Wayne Fay wrote:
I don't consider it to be a bug. Settings.xml is supposed to have
values that apply to all projects, so by definition, relative paths
should not be acceptable.
Wayne
On 8/8/07, Vihung Marathe [EMAIL PROTECTED] wrote:
The problem appears to be when the custom location is a relative path.
As soon as I change the localRepository value in my settings.xml to an
absolute path - in any form* - it seems to work.
Any ideas? Is this a bug - possibly with Surefire? All the other goals
work fine with a relative repository location.
-- Vihung
* I am on Windows, and all of the following values seem to work
- C:\workspace\myproject\repository
- \workspace\myproject\repository
- C:/workspace/myproject/repository
- /workspace/myproject/repository
However, assuming I am running maven from C:\workspace\myproject, none
of the following values work
- .\repository
- ./repository
- repository
-Original Message-
From: Vihung Marathe
Sent: Wednesday, August 01, 2007 5:56 PM
To: 'Maven Users List'
Subject: RE: Tests fail (class not found) when running against
non-standard local repository location
No.
Actually in the case that works, the command line is longer (because
the default repository location includes the Documents and Settings
directory on Windows).
-- Vihung
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 4:47 PM
To: Maven Users List
Subject: Re: Tests fail (class not found) when running against
non-standard local repository location
Off the top of my head, the only thing I could think would be if, by
redirecting the localRepo, you're running into max lengths of paths on
Windows, or maxing out the -classpath argument length.
It is certainly an odd problem, and I've never seen it myself, nor
seen it reported on this list. In fact, I know many people are using
localRepo setting to utilize a different location very successfully.
So I'd expect the problem is specific to your environment somehow.
Wayne
_
This e-mail may contain confidential information and/or copyright
material. This e-mail is intended for the use of the addressee only. Any
unauthorised use may be unlawful.
If you receive this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software.
The Friends Provident group of companies includes these Friends Provident
plc subsidiary companies:
Friends Provident Life and Pensions Limited. Registered number 4096141.
Friends Provident Life Assurance Limited. Registered number 782698.
Friends Provident Pensions Limited. Registered number 475201.
Friends Provident Marketing Limited. Registered number 5059179.
Each of the above subsidiary companies is authorised and regulated by the
Financial Services Authority.
Friends Provident Management Services Limited. Registered number 983330
The ultimate holding company is Friends Provident plc. Registered number
4113107.
All are incorporated companies limited by shares and registered in
England.
Registered and Head Office: Pixham End, Dorking, Surrey RH4 1QA.
www.friendsprovident.com
_
-
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]
--
View this message in context:
http://www.nabble.com/Tests-fail-%28class-not-found%29-when-running-against-non-standard-local-repository-location-tf4200745s177.html#a12091030
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to activate profile for certain packaging?
Michael Meyer schrieb: Hi, does this work? activation property nameproject.packaging/name valuewar/value /property /activation Unfortunately not. I'll describe my problem more generally instead of asking how to fix my obviously wrong approach: I need to execute a specific, home grown deployment preparation plugin only for projects that produce a war (packagingwar/packaging). How can I achieve that? My first thought was to use a profile. However, that does not work because a profile cannot be activated throught POM entries like packagingwar/packaging. I don't want to set an extra property for that either since all information I need is already covered in the packaging element and doesn't need to be duplicated. How do others implement conditional calls of certain plugins? How is the Maven2 way to do that? -Gisbert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disable logins for continuum?
if you are on the new 1.1 versions then just assign System Administrator to the Guest user and you should be good to go.. assign the Continuum Project Group Administrator to Guest as well jesse On 8/10/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: What is your version? Luke Matthews a écrit : Hi all, Quick question, is it possible to disable having to log in to continuum? Our CI server is well inside our firewall and it is a pain having to log in. I click the remember me but it seems to forget me! Cheers, Luke. -- jesse mcconnell [EMAIL PROTECTED]
RE: [m2] project.version in multiple modules
Hi Mick,
Mick Knutson wrote on Saturday, July 28, 2007 11:30 PM:
I have over 50 modules in my project and they all have headers like:
groupIdorg.delta.esp.dap.c2.services/groupId
version1.0.0.0/version
artifactIdc2-ear/artifactId
packagingear/packaging
parent
groupIdorg.delta.esp.dap/groupId
artifactIdc2/artifactId
version1.0.0.0/version
/parent
Now many of these modules I want to build independently from
one another
such as a grouping of org.delta.esp.dap.c2
When I do this, I can't use ${project.version} for the entries.
So what can I do as a best practice instead of doing a
site-wide search and
replace to go from:
version1.0.0.0/version
to
version1.0.0.1/version
Each time I want to increment the build number?
Use a master-pom (for your project) that contains all version numbers in a
dependencyManagement section. If we are about to release, we simply increase
the numbers in the master POM and release it before we release the individual
artifacts afterwards one by one. You only have to take care that they will
refer your new master-pom's version and that all deps in your POms are declared
without version. For the master POM itself we use by default version SNAPSHOT
only and have a real version umber for the release only (and turn it back toi
SNAPSHOT as the next version number). This way unreleased artifacts will
inherit the new version also if they're bleeding edge components or may refer
to a special version of the master POM with fixed versions at a certain time.
Works out quite well.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] project.version in multiple modules
Hi,
I have the same problem. If you use the Maven release plugin (mvn
release:prepare and mvn release:perform) it will ask you for each version
number for the release and for the version number after the release. That
makes it a bit easier, although he will ask you for each project, so you
will have to enter that 50 times * 2 (release version and new version for
trunk). To use this, you will have to follow the pattern of using
1.0-SNAPSHOT in trunk and then he will suggest a release version of 1.0 and
a new version number of 1.1-SNAPSHOT. But if you want to do it differently
from that, it gets difficult and you will have to manually modify the POMs.
Maven is simply not flexible: if you do not follow Maven's conventions you
won't get good results. The advantage of ant is that you can easily modify
and tweak things so that they work for you. I see two good points in Maven:
a) global repositories and automatic downloading of libraries, and b) all
Maven projects look the same, once you know it, you know all.
Well, back to the problem: What might be possible, and what I want to try
now, is to set a version number in the root pom only and remove the version
number declaration in all other poms. So there would be only one number (and
one file) you'd have to change for that. The open question is what to do
with dependencies: if you have 50 modules you probably have a lot of
cross-dependencies between your modules. Which version number should one
enter here? None as in the module declaration? I don't know if that works.
If not, one would have to set a global property like myproject.version and
reference it everywhere with version${myproject.version}/version.
I found similar things on the web but nothing that explains if that really
works.
Alex
Mick Knutson-4 wrote:
I have over 50 modules in my project and they all have headers like:
groupIdorg.delta.esp.dap.c2.services/groupId
version1.0.0.0/version
artifactIdc2-ear/artifactId
packagingear/packaging
parent
groupIdorg.delta.esp.dap/groupId
artifactIdc2/artifactId
version1.0.0.0/version
/parent
Now many of these modules I want to build independently from one another
such as a grouping of org.delta.esp.dap.c2
When I do this, I can't use ${project.version} for the entries.
So what can I do as a best practice instead of doing a site-wide search
and
replace to go from:
version1.0.0.0/version
to
version1.0.0.1/version
Each time I want to increment the build number?
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
--
View this message in context:
http://www.nabble.com/-m2--project.version-in-multiple-modules-tf4163642s177.html#a12089125
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-clean-plugin: does inheritedtrue/inherited work for you?
Barrie Treloar wrote: With mvn 2.0.7 and maven-clean-plugin:2.1.1 In my parent plugin build pluginManagement plugins plugin artifactIdmaven-clean-plugin/artifactId inheritedtrue/inherited configuration filesets fileset directorylogs/directory followSymlinksfalse/followSymlinks /fileset /filesets /configuration /plugin In my module plugin build plugins plugin artifactIdmaven-clean-plugin/artifactId inheritedtrue/inherited configuration filesets fileset directorylib/directory followSymlinksfalse/followSymlinks /fileset /filesets /configuration /plugin But mvn help:effective-pom produces: plugin artifactIdmaven-clean-plugin/artifactId version2.1.1/version inheritedtrue/inherited configuration filesets fileset directorylib/directory followSymlinksfalse/followSymlinks /fileset /filesets /configuration /plugin And running mvn clean only deletes the lib directory (the log directory is ignored) Am I configuring this wrong? First, inheritedtrue/inherited is the default! Second, the default behaviour is for configurations to be *merged* - hence configuration.filesets.fileset.directory=logs in the parent is overridden by configuration.filesets.fileset.directory=lib in the child. Try configuration combine.children=append - not tested, but I think that'll do what you want. Max. signature.asc Description: OpenPGP digital signature
Re: Building offline
Hi, I am having troubles with mvn ... -o (with maven 2.0.7) says not able to download (but, really, the file is in my local repo) The dependency is a -SNAPSHOT (for what's worth) Luckily, when traveling by train, I had maven 2.0.4 on my box as well. A change to use 2.0.4 works fine. So, is this an already know bug in 2.0.7 ? -Matthias On 6/22/07, Manuel J. Recena Soto [EMAIL PROTECTED] wrote: hi kjohnston: On Fri, 22 Jun 2007 10:45:25 -0700 (PDT), kjohnston wrote I'm having trouble getting Maven to build a project in offline mode. Is there a step-by-step procedure document for this? Here's what I'd like to do: - Set up a local file based repository with all the artifacts needed to build - Run Maven in offline mode, configured to use just a single, local repository Are you try this? *first option: mvn --help usage: mvn [options] [goal(s)] [phase(s)] Options: -o,--offline Work offline * second option: Config your setting.xml at $HOME/.m2/ or $MAVEN_DIR/bin/conf offlinetrue/offline regards, Thanks -- View this message in context: http://www.nabble.com/Building-offline- tf3966053s177.html#a11256959 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Manuel J. Recena Soto * www.manuelrecena.com[/blog] * [EMAIL PROTECTED] * +34 609710280 (ES) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] Archiva 1.0 Beta 1 Release
thanks for this :) its been a while
On 8/10/07, Maria Odea Ching [EMAIL PROTECTED] wrote:
Hi Everyone,
The Maven Archiva team is pleased to announce the release of Archiva 1.0Beta
1.
Archiva is a build artifact repository manager for use with build tools such
as Maven, Continuum and Ant.
It has features like repository search and browse, securing repositories,
identifying unknown artifacts and reporting of repository problems.
Aside from these, it can also act as a nearby (proxy) cache of popular
global repositories.
The latest release is now available here:
http://maven.apache.org/archiva/download.html
Below are the jira issues that were resolved for Archiva 1.0 Beta 1:
Release Notes - Archiva - Version 1.0-beta-1
** Sub-task
* [MRM-275] - add remove old snapshots Sheduler
** Bug
* [MRM-326] - Adding/Editing repositories doesn't have validation
* [MRM-329] - The Reports link gives an HTTP 500
* [MRM-347] - Undefined ${appserver.home} and ${appserver.base}
* [MRM-373] - Unable to delete the pre-configured example network proxy
* [MRM-425] - Search and Browse do not work for snapshots
* [MRM-426] - Search does not work for snapshots because of different
version values in index and database when the snapshot version is unique
* [MRM-429] - Find Artifact does not work when the applet is disabled
* [MRM-430] - Archiva always writes to ~/.m2/archiva.xml
* [MRM-447] - resolve jasper licensing issue by separating into a
profile
* [MRM-451] - regression: editing a repository on first creation of
~/.m2/archiva.xml doesn't call change listeners
** Improvement
* [MRM-143] - improve error reporting on corrupt jars, poms, etc
* [MRM-290] - Ability to pre-configure the Jetty port in conf/plexus.xml
* [MRM-412] - Add support for maven1 (legacy) request to access a maven2
(default layout) repo
* [MRM-446] - find artifact / search by checksum is not working
** New Feature
* [MRM-294] - Repository purge feature for snapshots
The Maven Archiva team will be pushing for a 1.0 release soon.
Thanks,
Deng
--
==
- alramirez
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
properties
Hi,
How do I return the value of the active profiles id as a property in my
pom.xml. How do I override the property values in profiles.xml on a per
user basis? I thought I could put them in ${user.home}/build.properties,
but that seems not to work?!
TIA
John
Eurobase International Limited and its subsidiaries (Eurobase) are unable to
exercise control over the content of information in E-Mails. Any views and
opinions expressed may be personal to the sender and are not necessarily those
of Eurobase. Eurobase will not enter into any contractual obligations in
respect of any part of its business in any E-mail.
Privileged / confidential information may be contained in this message and /or
any attachments. This E-mail is intended for the use of the addressee(s) only
and may contain confidential information. If you are not the / an intended
recipient, you are hereby notified that any use or dissemination of this
communication is strictly prohibited. If you receive this transmission in
error, please notify us immediately, and then delete this E-mail.
Neither the sender nor Eurobase accepts any liability whatsoever for any
defects of any kind either in or arising from this E-mail transmission. E-Mail
transmission cannot be guaranteed to be secure or error-free, as messages can
be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or
incomplete. Eurobase does not accept any responsibility for viruses and it is
your responsibility to scan any attachments.
Eurobase Systems Limited is the main trading company in the Eurobase
International Group; registered in England and Wales as company number
02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex
CM2 0RE, UK.
Re: [maven-antrun-plugin] How can we set the maven.plugin.classpath ?
Hi,
just tested with this pom:
project
modelVersion4.0.0/modelVersion
artifactIdmy-test-app/artifactId
groupIdmy-test-group/groupId
version1.0-SNAPSHOT/version
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
dependencies
dependency
groupIdorg.apache.ant/groupId
artifactIdant-junit/artifactId
version1.7.0/version
/dependency
/dependencies
executions
execution
idcompile/id
phasecompile/phase
configuration
tasks
property name=compile_classpath
refid=maven.compile.classpath/
property name=runtime_classpath
refid=maven.runtime.classpath/
property name=test_classpath
refid=maven.test.classpath/
property name=plugin_classpath
refid=maven.plugin.classpath/
echo message=compile classpath: ${compile_classpath}/
echo message=runtime classpath: ${runtime_classpath}/
echo message=test classpath:${test_classpath}/
echo message=plugin classpath: ${plugin_classpath}/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/project
ant-junit is on the plugin classpath as expected. So everything seems to
work as it should. Perhaps your problem has something to do with the
system scope of your dependency or the variables used?
-Tim
Gex Dev schrieb:
Hi,
I'm using maven-antrun-plugin in order to call specific ant targets
those ant targets needs a specific jar on the ant classpath. I don't
understand how works
the maven.plugin.classpath (
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html)
in this plugin :
- is it the classpath of the ant called by maven-antrun-plugin ?
- how can we set it ?
- and how maven-antrun-plugin call ant target ? I mean, which ant is call ?
Can we specify an ant version ?
A little example:
POM :
//
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idantrun_compile/id
phasecompile/phase
goals
goalrun/goal
/goals
configuration
tasks
property name=plugin_classpath refid=
maven.plugin.classpath/
echo message=plugin classpath:
${plugin_classpath}/
ant antfile=${basedir}/buildForMaven.xml
inheritRefs=true
target name=ant-compile/
/ant
/tasks
/configuration
/execution
/executions
dependencies
dependency !-- this dependency works well in the build
dependencies--
groupIdcom.bea.weblogic/groupId
artifactIdweblogic/artifactId
version${weblogic.version}/version
scopesystem/scope
systemPath${weblogic.serverPath
}\lib\weblogic.jar/systemPath
/dependency
/dependencies
/plugin
\\
buildForMaven.xml :
//
target name=ant-compile
echoAnt call.../echo
echo message=plugin classpath: ${plugin_classpath}/
ant target=appc / !-- Specific weblogic ant target--
/target
\\
mvn compile
=
//
[INFO] [antrun:run {execution: antrun_compile}]
[INFO] Executing tasks
[echo] plugin classpath: C:\...target of mvn compile but not
weblogic.jar
ant-compile:
[echo] Ant call...
[echo] plugin classpath: C:\...target of mvn compile but not
weblogic.jar
errors on appc ant target due to weblogic.jar not available
\\
Regards,
Gerald Reinhart
//
Thanks to markku : the build-helper-maven-plugin works well!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[maven-antrun-plugin] How can we set the maven.plugin.classpath ?
Hi,
I'm using maven-antrun-plugin in order to call specific ant targets
those ant targets needs a specific jar on the ant classpath. I don't
understand how works
the maven.plugin.classpath (
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html)
in this plugin :
- is it the classpath of the ant called by maven-antrun-plugin ?
- how can we set it ?
- and how maven-antrun-plugin call ant target ? I mean, which ant is call ?
Can we specify an ant version ?
A little example:
POM :
//
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idantrun_compile/id
phasecompile/phase
goals
goalrun/goal
/goals
configuration
tasks
property name=plugin_classpath refid=
maven.plugin.classpath/
echo message=plugin classpath:
${plugin_classpath}/
ant antfile=${basedir}/buildForMaven.xml
inheritRefs=true
target name=ant-compile/
/ant
/tasks
/configuration
/execution
/executions
dependencies
dependency !-- this dependency works well in the build
dependencies--
groupIdcom.bea.weblogic/groupId
artifactIdweblogic/artifactId
version${weblogic.version}/version
scopesystem/scope
systemPath${weblogic.serverPath
}\lib\weblogic.jar/systemPath
/dependency
/dependencies
/plugin
\\
buildForMaven.xml :
//
target name=ant-compile
echoAnt call.../echo
echo message=plugin classpath: ${plugin_classpath}/
ant target=appc / !-- Specific weblogic ant target--
/target
\\
mvn compile
=
//
[INFO] [antrun:run {execution: antrun_compile}]
[INFO] Executing tasks
[echo] plugin classpath: C:\...target of mvn compile but not
weblogic.jar
ant-compile:
[echo] Ant call...
[echo] plugin classpath: C:\...target of mvn compile but not
weblogic.jar
errors on appc ant target due to weblogic.jar not available
\\
Regards,
Gerald Reinhart
//
Thanks to markku : the build-helper-maven-plugin works well!
Re: Dependency project classes getting included in the resulting jar
Farhan Sarwar wrote: Hey Guys, Am experiencing a strange behavior, which I am not able to understand why.Basically I have got two projects A and B where project A has a dependency on the Project B, also I have a parent POM from which both these projects are being inherited, the compilation and everything works fine, but there is this behavior which I am not able to comprehend, i.e. when I build the project A (which has dependency on B) the binary jar is generated as I expected with only the classes of Project A, but when I do a build of both the projects at the parent pom level the jar generated of the Project A also contains the classes of project B which doesn't make sense to me, I mean why are there binaries of the dependent project (i.e. B) is getting included in it. Any feedback would be highly appreciated. Normally I would say no way, but you're in effect the second one I remember on this list who reported such a behavior. I am quite sure all devs would love to have a test case for this weird situation. BTW: Do you use the xdoclet plugin in your projects? Cheers, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly plugin question
I think this is *almost* right, and should work like a champ, though I haven't ever tried it either. What you'll need to do is have a project that looks like this: my-assembly-descriptor | +- pom.xml | +- src | +- main | +- resources | +- assemblies | +- my-assembly.xml The pom will look just like any other normal 'jar' packaging pom. The my-assembly.xml file will be a normal assembly descriptor. Now, to use it, you'll need to add this new artifact as a plugin- level dependency in your main prjoect's pom.xml, like this: project [...] build plugins [...] plugin artifactIdmaven-assembly-plugin/artifactId dependencies dependency groupIdorg.myproject.assemblies/groupId artifactIdmy-assembly-descriptor/artifactId version1.0/version /dependency /dependencies [...] /plugin /plugins /build /project I think you've got a good idea, Tim, and I think these minor tweaks will make it work. Good luck, Adam. -john On Aug 10, 2007, at 3:37 AM, Tim Kettler wrote: Hi, -- Beware: Untested Instructions -- :-) I. Create a new project, put the assembly descriptors you want to have available across projects in 'src/resources/assemblies' and install/ deploy the artifact to your local/internal repository. II. In your projects configure the plugin like this: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId dependencies dependency !-- artifact containing the descriptors -- /dependency /dependencies configuration descriptorRefs descriptorRefname-of-your-descriptor/descriptorRef /descriptorRefs /configuration /plugin -Tim Adam schrieb: Hey all, question about the assembly plugin. Is there a way to specify one assembly.xml descriptor within a POM that is global to all projects and to have it inherit down to all sub-projects? Right now when I run the execution phase the assembly is tied to from a sub-project of a parent project (that is in turn a child to the global POM) I get an error saying it can not locate the descriptor. I would like to only have one descriptor for all projects and have it in the master parent POM. That way I can specify a global execution phase so all sources get added into each project every time they are built but, I only want ZIP files, not TAR and tarball as in the default. Thanks in advance, Adam [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] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Re: Continuum Emails
No. In conf/plexus.xml, you must have something like that: resources !-- Mail Session -- resource namemail/Session/name typejavax.mail.Session/type properties property namemail.smtp.host/name valuelocalhost/value /property property namemail.smtp.port/name value25/value /property /properties /resource and in application.xml, you must keep the component declaration like it iwas when you installed Continuum: component roleorg.codehaus.plexus.mailsender.MailSender/role implementationorg.codehaus.plexus.mailsender.javamail.JndiJavamailMailSender/implementation configuration jndiSessionNamejava:comp/env/mail/Session/jndiSessionName /configuration /component Emmanuel LAMY Olivier a écrit : Yep. -Message d'origine- De : Morgovsky, Alexander (US - Glen Mills) [mailto:[EMAIL PROTECTED] Envoyé : vendredi 10 août 2007 00:36 À : [EMAIL PROTECTED] Objet : RE: Continuum Emails Does this mean that I should put the whole component node into plexus.xml? component roleorg.codehaus.plexus.mailsender.MailSender/role implementationorg.codehaus.plexus.mailsender.javamail.JndiJavamailMailSender/implementation configuration jndiSessionNamejava:comp/env/mail/Session/jndiSessionName smtp-host/smtp-host smtp-port/smtp-port /configuration /component -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, August 09, 2007 5:18 PM To: [EMAIL PROTECTED] Subject: Re: Continuum Emails the jndi conf must be done in conf/plexus.xml Morgovsky, Alexander (US - Glen Mills) a écrit : I am using Continuum 1.1-alpha-2. I have noticed that my Continuum instance is not sending out emails. In the logs I found the error: [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.ContinuumNotificationDispatcher: default - Error while trying to use the mailnotifier. org.codehaus.plexus.notification.NotificationException: Exception while sending message. at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sen dM essage(MailContinuumNotifier.java:415) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.bui ld Complete(MailContinuumNotifier.java:319) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sen dN otification(MailContinuumNotifier.java:211) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDi sp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:198) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDi sp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:150) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDi sp atcher.buildComplete(DefaultContinuumNotificationDispatcher.java:103) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endB ui ld(DefaultBuildController.java:219) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.buil d( DefaultBuildController.java:173) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.ex ec uteTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exec ut orRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapt er .call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTa sk .java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Work er .runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Work er .run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:534) Caused by: org.codehaus.plexus.mailsender.MailSenderException: Error while sending the message. at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.sen d( AbstractJavamailMailSender.java:219) at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sen dM essage(MailContinuumNotifier.java:411) ... 14 more I configured the continuum-1.1-alpha-2\apps\continuum\webapp\WEB-INF\classes\META-INF\p le xus\application.xml with the following: component roleorg.codehaus.plexus.mailsender.MailSender/role implementationorg.codehaus.plexus.mailsender.javamail.JndiJavamailMa il Sender/implementation configuration jndiSessionNamejava:comp/env/mail/Session/jndiSessionName smtp-hosta.b.c.d/smtp-host smtp-porte/smtp-port /configuration /component Could someone please explain
Re: How to activate profile for certain packaging?
Unfortunately, Maven 2.0.x doesn't support that particular type of profile activation. We're working on a feature in the trunk (2.1- SNAPSHOT, currently) that would allow you to bring in custom profile activators via build extensions, however. A custom activator could give you an avenue for this sort of profile activation...but it's still not available in a released version of Maven. Sorry, -john On Aug 10, 2007, at 9:08 AM, Gisbert Amm wrote: Michael Meyer schrieb: Hi, does this work? activation property nameproject.packaging/name valuewar/value /property /activation Unfortunately not. I'll describe my problem more generally instead of asking how to fix my obviously wrong approach: I need to execute a specific, home grown deployment preparation plugin only for projects that produce a war (packagingwar/ packaging). How can I achieve that? My first thought was to use a profile. However, that does not work because a profile cannot be activated throught POM entries like packagingwar/packaging. I don't want to set an extra property for that either since all information I need is already covered in the packaging element and doesn't need to be duplicated. How do others implement conditional calls of certain plugins? How is the Maven2 way to do that? -Gisbert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Re: What is the best way to consolidate the site from a multi-project project
yes you add this section in your root pom : loganalyzer.site Maven Project Website file:///C:\temp\site Maven nw knows where to deploy the site. after that, mvn site site:deploy and your site is fully operational see the doc : http://maven.apache.org/plugins/maven-site-plugin/usage.html http://maven.apache.org/plugins/maven-site-plugin/usage.html ChuckC wrote: I have my site generating for a multi-project project, but the top level pom report does not properly link into the sub-level pom reports. Ideally, I would like the site to be in a single destination. Is there a way to get the sites to link together as a single site. This is very similar to the earlier post about getting it to generate sites for a multi-projects project. -- View this message in context: http://www.nabble.com/What-is-the-best-way-to-consolidate-the-site-from-a-multi-project-project-tf4239560s177.html#a12088208 Sent from the Maven - Users mailing list archive at Nabble.com.
Re: What is the best way to consolidate the site from a multi-project project
Thanks. This works. dvicente wrote: yes you add this section in your root pom : distributionManagement site idloganalyzer.site/id nameMaven Project Website/name urlfile:///C:\temp\site/url /site /distributionManagement Maven nw knows where to deploy the site. after that, mvn site site:deploy and your site is fully operational see the doc : http://maven.apache.org/plugins/maven-site-plugin/usage.html http://maven.apache.org/plugins/maven-site-plugin/usage.html ChuckC wrote: I have my site generating for a multi-project project, but the top level pom report does not properly link into the sub-level pom reports. Ideally, I would like the site to be in a single destination. Is there a way to get the sites to link together as a single site. This is very similar to the earlier post about getting it to generate sites for a multi-projects project. -- View this message in context: http://www.nabble.com/What-is-the-best-way-to-consolidate-the-site-from-a-multi-project-project-tf4239560s177.html#a12098843 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trying to compile using jav 1.3 when I've 1.5
Try this in your pom.xml:
build
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
/configuration
/plugin
/plugins
/build
Regards,
Rodrigo
On 8/10/07, Arun P Johny [EMAIL PROTECTED] wrote:
Hi all,
When i try to user mvn compile I'm getting the following error, any help
[INFO] [compiler:compile]
[INFO] Compiling 127 source files to F:\build\cougar_common\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
F:\build\path\file.java:[77, 19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListObject getObjects(Class clazz, String orderByField) {
I'm using maven 2.0.7 and I've Java 1.5 installed in my system. I'm
failed to understand why maven is trying to compile using 1.3 when I've
1.5.
Can anyone help me.
Thank you
Arun P Johny
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven and Sun Java System Application Server
I used netbeans 5.5.1 and it gave me the same error message. now I am using glassfish v2 instead of sun application server and everything works fine. Thanks a lot Grog BISO Greg Morgan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 BISO wrote: Dears, I am trying to run maven 2 with Sun Java System Application Server on netbeans 5.5 and I got the following error: BISO my approach to these kinds of error messages is to use google with key messages. [INFO]Deploying on Sun Java System Application Server [INFO]debugMode=false [INFO]clientModuleuri=null [INFO]clientUrlPart= [INFO]forcedeploy=true no dd for=WEB-INF/webservices.xml The most promising error message was the no dd line. I copied and pasted this into the Firefox google search box. Google found this for me http://jira.codehaus.org/browse/MEVENIDE-441 . Even though some google links might have nothing to do with the tools that you are using, the bug report shows a successful conclusion by patching your tools: Fixed with NetBeans 5.5 Beta 2. Please try the instructions in this bug report and report back on this thread with success or failure. That way others may be helped with what you did. [INFO] [ERROR]BUILD FAILURE [INFO] [INFO]Failed Deployment:Deployment error: service-ref not found in the property list: WebApp If the other error message does not find a resolution, then I'd try this service-ref line in a google search. what should I do? Thanks a lot I hope this helps. Regards, Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGu9tYxyxe5L6mr7IRAhT/AJ9OlWTphSLt8jLa/eTFUcC4eXeUaQCfcTcq Qkc/HWVFyoT+1vPsvdLbWNo= =PrAq -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Maven-and-Sun-Java-System-Application-Server-tf4242720s177.html#a12090452 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCE] Archiva 1.0 Beta 1 Release
Hi Everyone,
The Maven Archiva team is pleased to announce the release of Archiva 1.0Beta 1.
Archiva is a build artifact repository manager for use with build tools such
as Maven, Continuum and Ant.
It has features like repository search and browse, securing repositories,
identifying unknown artifacts and reporting of repository problems.
Aside from these, it can also act as a nearby (proxy) cache of popular
global repositories.
The latest release is now available here:
http://maven.apache.org/archiva/download.html
Below are the jira issues that were resolved for Archiva 1.0 Beta 1:
Release Notes - Archiva - Version 1.0-beta-1
** Sub-task
* [MRM-275] - add remove old snapshots Sheduler
** Bug
* [MRM-326] - Adding/Editing repositories doesn't have validation
* [MRM-329] - The Reports link gives an HTTP 500
* [MRM-347] - Undefined ${appserver.home} and ${appserver.base}
* [MRM-373] - Unable to delete the pre-configured example network proxy
* [MRM-425] - Search and Browse do not work for snapshots
* [MRM-426] - Search does not work for snapshots because of different
version values in index and database when the snapshot version is unique
* [MRM-429] - Find Artifact does not work when the applet is disabled
* [MRM-430] - Archiva always writes to ~/.m2/archiva.xml
* [MRM-447] - resolve jasper licensing issue by separating into a
profile
* [MRM-451] - regression: editing a repository on first creation of
~/.m2/archiva.xml doesn't call change listeners
** Improvement
* [MRM-143] - improve error reporting on corrupt jars, poms, etc
* [MRM-290] - Ability to pre-configure the Jetty port in conf/plexus.xml
* [MRM-412] - Add support for maven1 (legacy) request to access a maven2
(default layout) repo
* [MRM-446] - find artifact / search by checksum is not working
** New Feature
* [MRM-294] - Repository purge feature for snapshots
The Maven Archiva team will be pushing for a 1.0 release soon.
Thanks,
Deng
Re: maven-ant-tasks-2.0.7 settings file read hangs at install-provider
Hi Mykel, Ok, I studied your case more deeply: you've just found a bug! :) For remote repositories defined in pom.xml, settings file is taken into account but not for remote repositories defined in build.xml... I filed a Jira issue, with a testcase and fix: http://jira.codehaus.org/browse/MANTTASKS-85 You'll find the modified tasks at http://codehaus.org/~hboutemy/maven-ant-tasks-2.0.7-MANTTASKS-85.jar Can you check that it fixes your problem? Then it should be released in 2.0.8. Hervé Le vendredi 10 août 2007, Mykel Alvis a écrit : Hervé, Sorry it took so long to get back to you about this. I've been out of the office and had trouble accessing the systems in question. Attached is my settings.xml that is used by 40+ developers daily with this. We do have a local firewall, but it definitely works with maven since we override central with our internal proximity instance. What appears to be the case is that the settings.xml isn't getting read prior to the attempt to acquire the provider, so it's trying (http://repo1.maven.org/maven2/) instead of (http://sirdsite/proximity/), but that's just a guess. Thanks again for your help, Mykel On 8/7/07, Hervé BOUTEMY [EMAIL PROTECTED] wrote: ok, settings.xml has been read, but the task is hanging when trying to download wagon-provider-api from central http://repo1.maven.org/maven2 Do you have direct internet access, or through a proxy? If through a proxy, how was it configured in settings.xml? Did you try your configuration with full Maven instead of Ant tasks? Le mardi 7 août 2007, Mykel Alvis a écrit : Hi Hervé, OK. I lied. It timed out after several minutes. I don't know why it would delay the 10 minutes it took before, but must recently it timed out in less than 4. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[1.1-beta-1] How does the XML-RPC API work?
Hi I'm using continuum-1.1-beta-1. And I would like to use the XML-RPC API to check the build state. When I run the following code I a get an exception stating that there were parsing errors: ProjectsReader pr = new ProjectsReader( new URL(http://server:8080/continuum) ); projects = pr.readProjects(); Am I doing something wrong or doesn't the XML-RPC api work for 1.1-beta-1 yet? In my pom.xml file I've added the following dependency: dependency groupIdorg.apache.maven.continuum/groupId artifactIdcontinuum-rpc-client/artifactId version1.0.3/version /dependency Cheers, michael
Maven in Zurich
For anyone in Zurich next week and interested in learning about Maven: http://blogs.sonatype.com/jvanzyl/2007/08/10/1186745448788.html Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependency project classes getting included in the resulting jar
Hey Guys, Am experiencing a strange behavior, which I am not able to understand why.Basically I have got two projects A and B where project A has a dependency on the Project B, also I have a parent POM from which both these projects are being inherited, the compilation and everything works fine, but there is this behavior which I am not able to comprehend, i.e. when I build the project A (which has dependency on B) the binary jar is generated as I expected with only the classes of Project A, but when I do a build of both the projects at the parent pom level the jar generated of the Project A also contains the classes of project B which doesn't make sense to me, I mean why are there binaries of the dependent project (i.e. B) is getting included in it. Any feedback would be highly appreciated. Thanks and Regards, Farhan.
Re: [1.1-beta-1] How does the XML-RPC API work?
1) the url is http://server:8080/continuum/xmlrpc 2) you use an old version of the client, the one to use is: dependency groupIdorg.apache.maven.continuum/groupId artifactIdcontinuum-xmlrpc-client/artifactId version1.1-beta-1/version /dependency and a sample client is available there: http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-client/src/main/java/org/apache/maven/continuum/xmlrpc/client/SampleClient.java Emmanuel Michael Meyer a écrit : Hi I'm using continuum-1.1-beta-1. And I would like to use the XML-RPC API to check the build state. When I run the following code I a get an exception stating that there were parsing errors: ProjectsReader pr = new ProjectsReader( new URL(http://server:8080/continuum) ); projects = pr.readProjects(); Am I doing something wrong or doesn't the XML-RPC api work for 1.1-beta-1 yet? In my pom.xml file I've added the following dependency: dependency groupIdorg.apache.maven.continuum/groupId artifactIdcontinuum-rpc-client/artifactId version1.0.3/version /dependency Cheers, michael
[m2] taglist question
I want to get a tag list of all the System.out.println(...) statements there are and I want it to show up as: System.out.println(some print statement); NOT: (some print statement); -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
Re: [m2] taglist question
Mick Knutson wrote: I want to get a tag list of all the System.out.println(...) statements there are and I want it to show up as: System.out.println(some print statement); NOT: (some print statement); What is the purpose of that? Do you want to avoid having System.out calls in your code? In that case you should be using Checkstyle instead. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] taglist question
I have checkstyle. How do I do it in Checkstyle? On 8/10/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Mick Knutson wrote: I want to get a tag list of all the System.out.println(...) statements there are and I want it to show up as: System.out.println(some print statement); NOT: (some print statement); What is the purpose of that? Do you want to avoid having System.out calls in your code? In that case you should be using Checkstyle instead. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
Re: [m2] taglist question
You can use the Regexp module [1] like this: module name=Regexp !-- . matches any character, so we need to escape it and use \. to match dots. -- property name=format value=System\.out\.println/ property name=illegalPattern value=true/ /module or the GenericIllegalRegexp [2] like this: module name=GenericIllegalRegexp !-- . matches any character, so we need to escape it and use \. to match dots. -- property name=format value=System\.out\.println/ /module Read more: [1] http://checkstyle.sourceforge.net/config_misc.html#Regexp [2] http://checkstyle.sourceforge.net/config_misc.html#GenericIllegalRegexp Mick Knutson wrote: I have checkstyle. How do I do it in Checkstyle? On 8/10/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Mick Knutson wrote: I want to get a tag list of all the System.out.println(...) statements there are and I want it to show up as: System.out.println(some print statement); NOT: (some print statement); What is the purpose of that? Do you want to avoid having System.out calls in your code? In that case you should be using Checkstyle instead. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCE] fitnesse-maven-plugin 1.0-beta-1
Hi everyone, The fitnesse plugin team is pleased to announce the release of the 1.0-beta-1. http://mojo.codehaus.org/fitnesse-maven-plugin/index.html http://fitnesse.org FitNesse is an acceptance testing framework and wiki. This plugin allows to run fitnesse during your build (remotly or locally) and aggregates a tests execution report into your site. ** Bug * [MFITNESSE-1] - Can't execute plugin * [MFITNESSE-2] - The FitNesse process is not killed when we stop the Maven build. * [MFITNESSE-3] - The plugin doesn't use properly the fitnesse conventions for page naming. It neiher use properly the type tags to override this conventions. * [MFITNESSE-4] - No picture in the result html page * [MFITNESSE-5] - Can't execute a single FitNesse Page Test * [MFITNESSE-6] - Can't use 'Expand All' or 'Collapse All' on a 'Command Line Test Results' html page * [MFITNESSE-7] - The Fitnesse plugin isn't compatible with JDK 1.4 * [MFITNESSE-8] - Error when creating report index * [MFITNESSE-10] - Can't execute Test twice ** Improvement * [MFITNESSE-13] - Add timestamp to the FitNesse result page ** Task * [MFITNESSE-11] - Mock FitnesseRunnerMojo logger in order to clean the tests execution log * [MFITNESSE-12] - Create a Jira project for Fitnesse mojo ** Wish * [MFITNESSE-14] - Have the output captured on the suite result page We'll publish a 1.0 soon. Thanks (specially to Arnaud), Philippe
