Re: maven automation of webspher deployment
Have you looked at the plugins on http://maven-plugins.sourceforge.net/ On Wed, 24 Nov 2004 22:26:28 -0800 (PST), rajas kumar <[EMAIL PROTECTED]> wrote: > i need help for maven automation of webspher deployment > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven automation of webspher deployment
i need help for maven automation of webspher deployment __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
maven automation of webspher deployment
i need help for maven automation of webspher deployment - Do you Yahoo!? The all-new My Yahoo! Get yours free!
add generated tests to maven.test.compile.src.set
Hi all, I've created a plugin that generates code for my app. It generates test classes for generated classes too. /target/src/java <- generated classes /target/src/test <- generated test classes for generated classes I've found on the web a tip to force "maven test" to run my tests : (http://jroller.com/comments/dep4b/Weblog/maven_is_too_smart_for) I'd like to reduce pregoal to something like this to hide complexity : If I put previous code into a "myplugin:test" goal it doesn't workj any more. Is they're a way to do this ? I've tried to use without success. Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ant 1.6.2
is not the ant plugin, it is the ant target from ant itself. However, I believe this will use the Maven version of ant, not ant home (not sure - if there is a fork option for it then that'd work) You can always use ant:exec. - Brett On Wed, 24 Nov 2004 11:16:41 -0500, Jeff Yemin <[EMAIL PROTECTED]> wrote: > My impression from the docs is that the ant plugin generates an ant > build.xml file, but doesn't actually run anything. > > Jeff > > > > > > -Original Message- > > From: dan tran [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, November 24, 2004 11:01 AM > > To: Maven Users List; Felipe Vieira Silva > > Subject: Re: ant 1.6.2 > > > > so tag invokes any ant in $ANT_HOME?? > > > > -D > > > > > > On Wed, 24 Nov 2004 10:54:31 -0200, Felipe Vieira Silva > > <[EMAIL PROTECTED]> wrote: > > > > > > > target="junit"/> > > > > > > > > > It will call the ANT target from Maven. > > > > > > > > > > > > > > > On Mon, 22 Nov 2004 17:28:09 -0500, Jeff Yemin > > <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > There's a new feature in the ant 1.6.2 junit task (forkmode > > > > attribute) that I would really, really like to use. I tried > > > > modifiying the plugin.jelly file in the maven test plugin > > to support > > > > the new attributes, but quickly discovered that maven 1.0 > > is bound > > > > pretty tightly to ant 1.5.3. Is there any way to use new ant > > > > features without waiting for a new maven release that > > supports ant 1.6.2 directly? > > > > > > > > Thanks, > > > > Jeff Yemin > > > > > > > > > > > > > > > > - > > > 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: Dynamically modifing the ressources
No, it won't ever work. The project is loaded before maven.xml, and
all the values evaluated.
Don't you think you are making this build overly complicated?
- Brett
On Wed, 24 Nov 2004 18:24:57 +0100, Charles-Alexandre Sabourdin
<[EMAIL PROTECTED]> wrote:
> i is not working, it seem that the variable is not event modifiy :(
> Le mercredi 24 Novembre 2004 17:20, Steve Molloy a écrit :
>
>
> > Try adding scope="parent" to your j:set.
> >
> > Steve Molloy
> >
> > -Original Message-
> > From: Charles-Alexandre Sabourdin [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, November 24, 2004 10:56 AM
> > To: Maven Users List
> > Subject: Re: Dynamically modifing the ressources
> >
> > it it not woking correctly.
> > What I am tried was to set in
> > project.xml
> > src/conf${configDir}
> > in project.properties
> > configDir=/default
> > and in my maven.xml I creat the following goal :
> >
> >
> >
> >set configuration directory : ${configDir}
> >
> >
> >
> >
> > unfortunatly it does not works.
> >
> > Le mardi 23 Novembre 2004 20:30, Brett Porter a écrit :
> > > in the resources, set it to something like:
> > >
> > > src/conf/project${foo}, then set foo to A or B.
> > >
> > > - Brett
> > >
> > >
> > > On Tue, 23 Nov 2004 12:47:55 +0100, Charles-Alexandre Sabourdin
> > >
> > > <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > > I feel that this must have been discuss somewhere but I could not
> > > > figure it out.
> > > > The basic idea is to have 2 directory /src/conf/projetA
> > > > /src/conf/projetB. I would like to set maven goals to use a specific
> > > > directory.
> > > > I llok aroud and found :
> > > > [echo] $ {pom.build.resources}:
> > > > [[dir =
> > > > /home/sabourdin/Documents/projet/exemplebean/src/conf/projetA]] but I
> > > > did not find how to modify this propertie :(
> > > >
> > > > --
> > > > Charles-Alexandre
> > > > SABOURDIN
> > > > -
> > > >
> > > > -
> > > > 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]
>
> --
> Charles-Alexandre
> SABOURDIN
> -
>
> -
> 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: Maven site:sshdeploy hanging
>From what I know, you need to create a local key pair (using ssh-keygen) and add the public key it to the authorized_keys file on the remote machine. This will make ssh connect without prompting a password. []s Matheus On Wed, 24 Nov 2004 14:17:24 -0700, Chris Huisman <[EMAIL PROTECTED]> wrote: > Hello, when attempting to use maven site:sshdeploy things hang when it > gets to: > _ _ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0.1 > > build:start: > > xdoc:init: > > site:init: > > site:sshdeploy: >[echo] > siteAddress = hummer > siteDirectory = /home/httpd/html/QS/projects/hotdog > siteUser = chuisman > >[echo] >maven.homepage="/home/httpd/html/QS/projects/hotdog > >[tar] Building tar: > D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar >[gzip] Building: > D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar.gz >[delete] Deleting: D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar > > Nothing proceeds after this, however when I type ctrl^C I get the following: >[exec] [EMAIL PROTECTED]'s password: >[exec] [ERROR] Result: 1 > > how do I go about entering the password??? Why won't it ask me for the > password until I type ctrl^C? > > Thanks, > > Chris > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- Matheus Costa Leite [EMAIL PROTECTED] Minds at Work Tecnologia da Informação -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compile failure
That jdepend quit with an exit code of 9 :) You can try running with -X or -e, but it may not give any additional information. Sorry, but you might have to ask the jdepend project this. The class is jdepend.xmlui.JDepend and the JAR version 2.7. Cheers, Brett On Wed, 24 Nov 2004 16:11:37 -0500, STRAYER, JON (SBCSI) <[EMAIL PROTECTED]> wrote: > Does anyone know what this means: > > Unable to obtain goal [site] -- > /home/wfausers/wfaoper/.maven/cache/maven-jdepend-plugin-1.5/plugin.jell > y:57:26: Java returned: 9 > > - > 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: site:deploy
It requires the installation of ssh. On windows, you can get cygwin, or with some property changes you can use putty. http://maven.apache.org/reference/plugins/site/properties.html I notice you seem to have got this working and later get asked for a password from another email. You will need to use an SSH agent and private key auth, as ssh is run in batch mode. Sourceforge has some good documentation on this for their site: https://sourceforge.net/docman/display_doc.php?docid=6841&group_id=1 Regards, Brett On Wed, 24 Nov 2004 12:32:46 -0700, Chris Huisman <[EMAIL PROTECTED]> wrote: > I'm having problems deploying my generated site to the server. I get > the following error: > > BUILD FAILED > File.. C:\Documents and > Settings\chuisman\.maven\cache\maven-site-plugin-1.5 > .2\plugin.jelly > Element... exec > Line.. 137 > Column 56 > Execute failed: java.io.IOException: CreateProcess: ssh -l username > server "mkdir -p /home/httpd/QS/projects/projectname" error=2 > Total time: 38 seconds > Finished at: Wed Nov 24 12:03:25 MST 2004 > > Does the maven site plugin come with ssh? Is that the problem here? > > Thanks, > > Chris. > > - > 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: Maven site:sshdeploy hanging
I'm just guessing, so take it with a grain of salt. But you might need to setup key based logins so you don't need user interaction? Read this http://software.newsforge.com/software/04/03/15/211214.shtml Good luck, Alex Chris Huisman wrote: Hello, when attempting to use maven site:sshdeploy things hang when it gets to: _ _ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.1 build:start: xdoc:init: site:init: site:sshdeploy: [echo] siteAddress = hummer siteDirectory = /home/httpd/html/QS/projects/hotdog siteUser = chuisman [echo] maven.homepage="/home/httpd/html/QS/projects/hotdog [tar] Building tar: D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar [gzip] Building: D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar.gz [delete] Deleting: D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar Nothing proceeds after this, however when I type ctrl^C I get the following: [exec] [EMAIL PROTECTED]'s password: [exec] [ERROR] Result: 1 how do I go about entering the password??? Why won't it ask me for the password until I type ctrl^C? Thanks, Chris - 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]
Maven site:sshdeploy hanging
Hello, when attempting to use maven site:sshdeploy things hang when it gets to: _ _ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.1 build:start: xdoc:init: site:init: site:sshdeploy: [echo] siteAddress = hummer siteDirectory = /home/httpd/html/QS/projects/hotdog siteUser = chuisman [echo] maven.homepage="/home/httpd/html/QS/projects/hotdog [tar] Building tar: D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar [gzip] Building: D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar.gz [delete] Deleting: D:\chuisman\dev\hotdog\target\qsCommons-0.01-site.tar Nothing proceeds after this, however when I type ctrl^C I get the following: [exec] [EMAIL PROTECTED]'s password: [exec] [ERROR] Result: 1 how do I go about entering the password??? Why won't it ask me for the password until I type ctrl^C? Thanks, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Compile failure
Does anyone know what this means: Unable to obtain goal [site] -- /home/wfausers/wfaoper/.maven/cache/maven-jdepend-plugin-1.5/plugin.jell y:57:26: Java returned: 9 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Add dynamic dependiences
On Wed, 24 Nov 2004 11:20:05 -0500, Adrian Tarau ><[EMAIL PROTECTED]> wrote: > > >>Hi, >> >>I want to build an ear, and in the ear I want to put a war or jar which is >>not define in the dependences (it is build in this project). >> >> Why don't define one project per artifact type and use multiproject ? ;-) >>It is possible to add it in the dependences so the ear plugin will see it? Or >>I need to write Java code for this? >> >> Yes, if you are sure about the build order add the war / jar in the dependancies of the ear i think that the ear.bundle, war.bundle, ... will protect you to include them in the war lib. But the best is probably to have one project per artifact. Maybe you can use your base project as a multiproject one and have a directory per artifacts with a project.xml with theire own dependancies and point to ../src/??? for theres sources or resources files Nicolas, Nicolas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
site:deploy
I'm having problems deploying my generated site to the server. I get the following error: BUILD FAILED File.. C:\Documents and Settings\chuisman\.maven\cache\maven-site-plugin-1.5 .2\plugin.jelly Element... exec Line.. 137 Column 56 Execute failed: java.io.IOException: CreateProcess: ssh -l username server "mkdir -p /home/httpd/QS/projects/projectname" error=2 Total time: 38 seconds Finished at: Wed Nov 24 12:03:25 MST 2004 Does the maven site plugin come with ssh? Is that the problem here? Thanks, Chris. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Add dynamic dependiences
Adrian, I am not certain but you might like to try setting the maven.ear.src property to the directory that your generated files will be, or if you are using this property already, then you might want to use the jelly tag to get the files you want into a place where they can be picked up. I think this may be clear as mud!!! If it is please let me know and I will see if I can explain better Regards, Corey On Wed, 24 Nov 2004 11:20:05 -0500, Adrian Tarau <[EMAIL PROTECTED]> wrote: > Hi, > > I want to build an ear, and in the ear I want to put a war or jar which is > not define in the dependences (it is build in this project). > > It is possible to add it in the dependences so the ear plugin will see it? Or > I need to write Java code for this? > > Thanks. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven site:deploy --> download link empty ... [more]
Ok it works but now: How can I modify the generated download
webpage so that it does not link to jar files but rather to the zip and
gz files I created through the maven dist goal?
--mike
Michael Niemaz wrote:
Hi,
When deploying the generated site, the download section stays
desperately
empty or more exactly keep displaying the boring "This project has not
released any version yet."
message ...
Is this related to the tag 'versions' in project.xml? What if it's the
first version ...
Should I put in 'versions' what's in the 'currentVersion' tag???
Any ideas?
--mike
Charles-Alexandre Sabourdin wrote:
i is not working, it seem that the variable is not event modifiy :(
Le mercredi 24 Novembre 2004 17:20, Steve Molloy a écrit :
Try adding scope="parent" to your j:set.
Steve Molloy
-Original Message-
From: Charles-Alexandre Sabourdin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004 10:56 AM
To: Maven Users List
Subject: Re: Dynamically modifing the ressources
it it not woking correctly.
What I am tried was to set in
project.xml
src/conf${configDir}
in project.properties
configDir=/default
and in my maven.xml I creat the following goal :
set configuration directory : ${configDir}
unfortunatly it does not works.
Le mardi 23 Novembre 2004 20:30, Brett Porter a écrit :
in the resources, set it to something like:
src/conf/project${foo}, then set foo to A or B.
- Brett
On Tue, 23 Nov 2004 12:47:55 +0100, Charles-Alexandre Sabourdin
<[EMAIL PROTECTED]> wrote:
Hi,
I feel that this must have been discuss somewhere but I could not
figure it out.
The basic idea is to have 2 directory /src/conf/projetA
/src/conf/projetB. I would like to set maven goals to use a specific
directory.
I llok aroud and found :
[echo] $ {pom.build.resources}:
[[dir =
/home/sabourdin/Documents/projet/exemplebean/src/conf/projetA]] but I
did not find how to modify this propertie :(
--
Charles-Alexandre
SABOURDIN
-
-
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]
maven site:deploy --> download link empty ...
Hi,
When deploying the generated site, the download section stays
desperately
empty or more exactly keep displaying the boring "This project has not
released any version yet."
message ...
Is this related to the tag 'versions' in project.xml? What if it's the
first version ...
Should I put in 'versions' what's in the 'currentVersion' tag???
Any ideas?
--mike
Charles-Alexandre Sabourdin wrote:
i is not working, it seem that the variable is not event modifiy :(
Le mercredi 24 Novembre 2004 17:20, Steve Molloy a écrit :
Try adding scope="parent" to your j:set.
Steve Molloy
-Original Message-
From: Charles-Alexandre Sabourdin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004 10:56 AM
To: Maven Users List
Subject: Re: Dynamically modifing the ressources
it it not woking correctly.
What I am tried was to set in
project.xml
src/conf${configDir}
in project.properties
configDir=/default
and in my maven.xml I creat the following goal :
set configuration directory : ${configDir}
unfortunatly it does not works.
Le mardi 23 Novembre 2004 20:30, Brett Porter a écrit :
in the resources, set it to something like:
src/conf/project${foo}, then set foo to A or B.
- Brett
On Tue, 23 Nov 2004 12:47:55 +0100, Charles-Alexandre Sabourdin
<[EMAIL PROTECTED]> wrote:
Hi,
I feel that this must have been discuss somewhere but I could not
figure it out.
The basic idea is to have 2 directory /src/conf/projetA
/src/conf/projetB. I would like to set maven goals to use a specific
directory.
I llok aroud and found :
[echo] $ {pom.build.resources}:
[[dir =
/home/sabourdin/Documents/projet/exemplebean/src/conf/projetA]] but I
did not find how to modify this propertie :(
--
Charles-Alexandre
SABOURDIN
-
-
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: Dynamically modifing the ressources
i is not working, it seem that the variable is not event modifiy :(
Le mercredi 24 Novembre 2004 17:20, Steve Molloy a écrit :
> Try adding scope="parent" to your j:set.
>
> Steve Molloy
>
> -Original Message-
> From: Charles-Alexandre Sabourdin [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 24, 2004 10:56 AM
> To: Maven Users List
> Subject: Re: Dynamically modifing the ressources
>
> it it not woking correctly.
> What I am tried was to set in
> project.xml
> src/conf${configDir}
> in project.properties
> configDir=/default
> and in my maven.xml I creat the following goal :
>
>
>
>set configuration directory : ${configDir}
>
>
>
>
> unfortunatly it does not works.
>
> Le mardi 23 Novembre 2004 20:30, Brett Porter a écrit :
> > in the resources, set it to something like:
> >
> > src/conf/project${foo}, then set foo to A or B.
> >
> > - Brett
> >
> >
> > On Tue, 23 Nov 2004 12:47:55 +0100, Charles-Alexandre Sabourdin
> >
> > <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > > I feel that this must have been discuss somewhere but I could not
> > > figure it out.
> > > The basic idea is to have 2 directory /src/conf/projetA
> > > /src/conf/projetB. I would like to set maven goals to use a specific
> > > directory.
> > > I llok aroud and found :
> > > [echo] $ {pom.build.resources}:
> > > [[dir =
> > > /home/sabourdin/Documents/projet/exemplebean/src/conf/projetA]] but I
> > > did not find how to modify this propertie :(
> > >
> > > --
> > > Charles-Alexandre
> > > SABOURDIN
> > > -
> > >
> > > -
> > > 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]
--
Charles-Alexandre
SABOURDIN
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Réf. : RE: ant 1.6.2
sounds right Extranet [EMAIL PROTECTED] - 24/11/2004 17:16 Veuillez répondre à [EMAIL PROTECTED] Pour : users, dantran, fgaucho cc : Objet : RE: ant 1.6.2 My impression from the docs is that the ant plugin generates an ant build.xml file, but doesn't actually run anything. Jeff > -Original Message- > From: dan tran [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 24, 2004 11:01 AM > To: Maven Users List; Felipe Vieira Silva > Subject: Re: ant 1.6.2 > > so tag invokes any ant in $ANT_HOME?? > > -D > > > On Wed, 24 Nov 2004 10:54:31 -0200, Felipe Vieira Silva > <[EMAIL PROTECTED]> wrote: > > > > target="junit"/> > > > > > > It will call the ANT target from Maven. > > > > > > > > > > On Mon, 22 Nov 2004 17:28:09 -0500, Jeff Yemin > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > There's a new feature in the ant 1.6.2 junit task (forkmode > > > attribute) that I would really, really like to use. I tried > > > modifiying the plugin.jelly file in the maven test plugin > to support > > > the new attributes, but quickly discovered that maven 1.0 > is bound > > > pretty tightly to ant 1.5.3. Is there any way to use new ant > > > features without waiting for a new maven release that > supports ant 1.6.2 directly? > > > > > > Thanks, > > > Jeff Yemin > > > > > > > > > > > - > > 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] This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. - Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problem *not* forking unit tests
--- Ryan Sonnek <[EMAIL PROTECTED]> wrote: > spring apps should be inherintly more UNIT testable > meaning that each > service should be constructed with mock objects or > other lightweight > implementations and not rely at all on spring. > relying on spring to > construct and weave together your dependencies is > classified as an > integration test, which can be slower. I would say that relying on container is generally "a bad thing", and kind of violates IoC pattern... Well, Sometimes I use picocontainer inside test cases, but only when I'm really lazy to type all the initialisation manually. But then I cache parsed scripts, or use recording proxies... And for integration tests - it is sometimes better to rig up special project for those tests only, so system development ist not slowed down by it... regards, = [ Konstantin Pribluda ( ko5tik ) ] ... Sucht gerade nach neuen Projekt oder Festanstelung Plugins for xdoclet-2 are released. check it out at: http://www.sourceforge.net/projects/xdoclet-plugins/ [ http://www.pribluda.de ] __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problem *not* forking unit tests
I did something like this: http://jroller.com/page/dep4b/20040210#in_container_testing_makes_testing to help with the startup cost. Eric > -Original Message- > From: Micah Craig [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 24, 2004 5:29 PM > To: Maven Users List > Subject: Re: problem *not* forking unit tests > > > First, thanks for the quick reply, and a thousand apologies for the > duplicate post (more email addresses than I know what to do with.) > I appreciate that not forking is a somewhat fringe use case. The > problem that we are facing is that as a Spring based project, we face a > non-negligible initial startup cost (loading our Application Context), > which, in a non-forked environment, we can avoid repeating for each > test. When forking, the time to run all our tests balloons dramatically > (hours, not minutes). Can you provide any insight as to how we might > alleviate this burden (Test Suites seem a possible option, but we worry > about maintenance overhead)? Thanks very much, > > -micah > > Ryan Sonnek wrote: > > >this question comes up so frequently, and the answer is always, "Junit > >tests should be forked." Can someone PLEASE change the default behavior > >of the test plugin to fork unless it's overridden? It would save on the > >constent confusion in this area. > > > >-Original Message- > >From: Julien Kirch [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, November 23, 2004 3:21 PM > >To: Maven Users List > >Subject: Re: problem *not* forking unit tests > > > > > >Hi Micah > > > >I think the test forking law is "thou shall fork", not forking is a real > > > >classpath mess between maven and project classpath (and caused your > >problem), I don't think not forking is ever a good idea. > > > >Julien > > > > > >Micah Craig wrote: > > > > > > > >>Hi, > >> I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit > >>tests un-forked (maven.junit.fork=no). Failure output is below. > >> > >> > >Could > > > > > >>this be some sort of mangled classpath issue left over from the > >> > >> > >upgrade, > > > > > >>or is something more sinister afoot. Thanks, > >> > >> -micah > >> > >> > > > > > > > >- > >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: problem *not* forking unit tests
Try a TestSetup decorator. the suite can try to find all testcases based on
filename. I think there is such a testrunner/suite already for the junit
project (junit-addons).
I've found the TestSetup decorator to be quite useful in a development
environment like Eclipse. Running them naively from maven using the fork is
quite painful, and should not be done. Define 1 testcase whose only purpose
is to deliver a decorated suite.
I use the following pattern for this:
public class FooTest extends TestCase {
// test methods
public static Test suite() {
return new MyTestSetup(new TestSuite(FooTest.class));
}
}
public class BarTest extends TestCase {
// testmethods
public static Test suite() {
return new MyTestSetup(new
TestSuite(BarTest.class));
}
}
public class AllTests extens TestCase {
public static Test suite() {
TestSuite result = new TestSuite();
result.add(FooTest.class);
result.add(BarTest.class);
return new MyTestSetup(result);
}
}
The last testsuite can be replaced with more elegant methods of finding and
adding testcases.
Using this pattern, it is possible to just run the FooTest cases, or run all
testcases from within your IDE.
Martijn
-Oorspronkelijk bericht-
Van: Micah Craig [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 24 november 2004 17:29
Aan: Maven Users List
Onderwerp: Re: problem *not* forking unit tests
First, thanks for the quick reply, and a thousand apologies for the
duplicate post (more email addresses than I know what to do with.) I
appreciate that not forking is a somewhat fringe use case. The problem that
we are facing is that as a Spring based project, we face a non-negligible
initial startup cost (loading our Application Context), which, in a
non-forked environment, we can avoid repeating for each test. When forking,
the time to run all our tests balloons dramatically (hours, not minutes).
Can you provide any insight as to how we might alleviate this burden (Test
Suites seem a possible option, but we worry about maintenance overhead)?
Thanks very much,
-micah
Ryan Sonnek wrote:
>this question comes up so frequently, and the answer is always, "Junit
>tests should be forked." Can someone PLEASE change the default
>behavior of the test plugin to fork unless it's overridden? It would
>save on the constent confusion in this area.
>
>-Original Message-
>From: Julien Kirch [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, November 23, 2004 3:21 PM
>To: Maven Users List
>Subject: Re: problem *not* forking unit tests
>
>
>Hi Micah
>
>I think the test forking law is "thou shall fork", not forking is a
>real
>
>classpath mess between maven and project classpath (and caused your
>problem), I don't think not forking is ever a good idea.
>
>Julien
>
>
>Micah Craig wrote:
>
>
>
>>Hi,
>> I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit
>>tests un-forked (maven.junit.fork=no). Failure output is below.
>>
>>
>Could
>
>
>>this be some sort of mangled classpath issue left over from the
>>
>>
>upgrade,
>
>
>>or is something more sinister afoot. Thanks,
>>
>> -micah
>>
>>
>
>
>
>-
>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: problem *not* forking unit tests
spring apps should be inherintly more UNIT testable meaning that each service should be constructed with mock objects or other lightweight implementations and not rely at all on spring. relying on spring to construct and weave together your dependencies is classified as an integration test, which can be slower. -Original Message- From: Micah Craig [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 24, 2004 10:29 AM To: Maven Users List Subject: Re: problem *not* forking unit tests First, thanks for the quick reply, and a thousand apologies for the duplicate post (more email addresses than I know what to do with.) I appreciate that not forking is a somewhat fringe use case. The problem that we are facing is that as a Spring based project, we face a non-negligible initial startup cost (loading our Application Context), which, in a non-forked environment, we can avoid repeating for each test. When forking, the time to run all our tests balloons dramatically (hours, not minutes). Can you provide any insight as to how we might alleviate this burden (Test Suites seem a possible option, but we worry about maintenance overhead)? Thanks very much, -micah Ryan Sonnek wrote: >this question comes up so frequently, and the answer is always, "Junit >tests should be forked." Can someone PLEASE change the default behavior >of the test plugin to fork unless it's overridden? It would save on the >constent confusion in this area. > >-Original Message- >From: Julien Kirch [mailto:[EMAIL PROTECTED] >Sent: Tuesday, November 23, 2004 3:21 PM >To: Maven Users List >Subject: Re: problem *not* forking unit tests > > >Hi Micah > >I think the test forking law is "thou shall fork", not forking is a real > >classpath mess between maven and project classpath (and caused your >problem), I don't think not forking is ever a good idea. > >Julien > > >Micah Craig wrote: > > > >>Hi, >> I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit >>tests un-forked (maven.junit.fork=no). Failure output is below. >> >> >Could > > >>this be some sort of mangled classpath issue left over from the >> >> >upgrade, > > >>or is something more sinister afoot. Thanks, >> >> -micah >> >> > > > >- >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] smime.p7s Description: S/MIME cryptographic signature
RE: problem *not* forking unit tests
I had a similar problem. A workaround that worked for me was to set the MAVEN_OPTS like this setenv MAVEN_OPTS "-Xbootclasspath/a:$CLASSPATH" where CLASSPATH is the list of jars that you get a ClassDefNotFound exception for. -Original Message- From: Micah Craig [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 24, 2004 11:29 AM To: Maven Users List Subject: Re: problem *not* forking unit tests First, thanks for the quick reply, and a thousand apologies for the duplicate post (more email addresses than I know what to do with.) I appreciate that not forking is a somewhat fringe use case. The problem that we are facing is that as a Spring based project, we face a non-negligible initial startup cost (loading our Application Context), which, in a non-forked environment, we can avoid repeating for each test. When forking, the time to run all our tests balloons dramatically (hours, not minutes). Can you provide any insight as to how we might alleviate this burden (Test Suites seem a possible option, but we worry about maintenance overhead)? Thanks very much, -micah Ryan Sonnek wrote: >this question comes up so frequently, and the answer is always, "Junit >tests should be forked." Can someone PLEASE change the default >behavior of the test plugin to fork unless it's overridden? It would >save on the constent confusion in this area. > >-Original Message- >From: Julien Kirch [mailto:[EMAIL PROTECTED] >Sent: Tuesday, November 23, 2004 3:21 PM >To: Maven Users List >Subject: Re: problem *not* forking unit tests > > >Hi Micah > >I think the test forking law is "thou shall fork", not forking is a >real > >classpath mess between maven and project classpath (and caused your >problem), I don't think not forking is ever a good idea. > >Julien > > >Micah Craig wrote: > > > >>Hi, >> I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit >>tests un-forked (maven.junit.fork=no). Failure output is below. >> >> >Could > > >>this be some sort of mangled classpath issue left over from the >> >> >upgrade, > > >>or is something more sinister afoot. Thanks, >> >> -micah >> >> > > > >- >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: problem *not* forking unit tests
--- Micah Craig <[EMAIL PROTECTED]> wrote: > First, thanks for the quick reply, and a thousand > apologies for the > duplicate post (more email addresses than I know > what to do with.) > I appreciate that not forking is a somewhat fringe > use case. The > problem that we are facing is that as a Spring based > project, we face a > non-negligible initial startup cost (loading our > Application Context), > which, in a non-forked environment, we can avoid > repeating for each > test. When forking, the time to run all our tests > balloons dramatically > (hours, not minutes). Can you provide any insight > as to how we might > alleviate this burden (Test Suites seem a possible > option, but we worry > about maintenance overhead)? Thanks very much, > do you realy need to mount full application context for your unit tests? Normally I do not need this ( with pico/nano ) - I can come away even without a container at all ( during tests ) regards, = [ Konstantin Pribluda ( ko5tik ) ] ... Sucht gerade nach neuen Projekt oder Festanstelung Plugins for xdoclet-2 are released. check it out at: http://www.sourceforge.net/projects/xdoclet-plugins/ [ http://www.pribluda.de ] __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem *not* forking unit tests
First, thanks for the quick reply, and a thousand apologies for the duplicate post (more email addresses than I know what to do with.) I appreciate that not forking is a somewhat fringe use case. The problem that we are facing is that as a Spring based project, we face a non-negligible initial startup cost (loading our Application Context), which, in a non-forked environment, we can avoid repeating for each test. When forking, the time to run all our tests balloons dramatically (hours, not minutes). Can you provide any insight as to how we might alleviate this burden (Test Suites seem a possible option, but we worry about maintenance overhead)? Thanks very much, -micah Ryan Sonnek wrote: this question comes up so frequently, and the answer is always, "Junit tests should be forked." Can someone PLEASE change the default behavior of the test plugin to fork unless it's overridden? It would save on the constent confusion in this area. -Original Message- From: Julien Kirch [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 3:21 PM To: Maven Users List Subject: Re: problem *not* forking unit tests Hi Micah I think the test forking law is "thou shall fork", not forking is a real classpath mess between maven and project classpath (and caused your problem), I don't think not forking is ever a good idea. Julien Micah Craig wrote: Hi, I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit tests un-forked (maven.junit.fork=no). Failure output is below. Could this be some sort of mangled classpath issue left over from the upgrade, or is something more sinister afoot. Thanks, -micah - 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]
Add dynamic dependiences
Hi, I want to build an ear, and in the ear I want to put a war or jar which is not define in the dependences (it is build in this project). It is possible to add it in the dependences so the ear plugin will see it? Or I need to write Java code for this? Thanks.
RE: Dynamically modifing the ressources
Try adding scope="parent" to your j:set.
Steve Molloy
-Original Message-
From: Charles-Alexandre Sabourdin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 24, 2004 10:56 AM
To: Maven Users List
Subject: Re: Dynamically modifing the ressources
it it not woking correctly.
What I am tried was to set in
project.xml
src/conf${configDir}
in project.properties
configDir=/default
and in my maven.xml I creat the following goal :
set configuration directory : ${configDir}
unfortunatly it does not works.
Le mardi 23 Novembre 2004 20:30, Brett Porter a écrit :
> in the resources, set it to something like:
>
> src/conf/project${foo}, then set foo to A or B.
>
> - Brett
>
>
> On Tue, 23 Nov 2004 12:47:55 +0100, Charles-Alexandre Sabourdin
>
> <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I feel that this must have been discuss somewhere but I could not figure
> > it out.
> > The basic idea is to have 2 directory /src/conf/projetA
> > /src/conf/projetB. I would like to set maven goals to use a specific
> > directory.
> > I llok aroud and found :
> > [echo] $ {pom.build.resources}:
> > [[dir =
> > /home/sabourdin/Documents/projet/exemplebean/src/conf/projetA]] but I did
> > not find how to modify this propertie :(
> >
> > --
> > Charles-Alexandre
> > SABOURDIN
> > -
> >
> > -
> > 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]
--
Charles-Alexandre
SABOURDIN
-
-
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: ant 1.6.2
My impression from the docs is that the ant plugin generates an ant build.xml file, but doesn't actually run anything. Jeff > -Original Message- > From: dan tran [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 24, 2004 11:01 AM > To: Maven Users List; Felipe Vieira Silva > Subject: Re: ant 1.6.2 > > so tag invokes any ant in $ANT_HOME?? > > -D > > > On Wed, 24 Nov 2004 10:54:31 -0200, Felipe Vieira Silva > <[EMAIL PROTECTED]> wrote: > > > > target="junit"/> > > > > > > It will call the ANT target from Maven. > > > > > > > > > > On Mon, 22 Nov 2004 17:28:09 -0500, Jeff Yemin > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > There's a new feature in the ant 1.6.2 junit task (forkmode > > > attribute) that I would really, really like to use. I tried > > > modifiying the plugin.jelly file in the maven test plugin > to support > > > the new attributes, but quickly discovered that maven 1.0 > is bound > > > pretty tightly to ant 1.5.3. Is there any way to use new ant > > > features without waiting for a new maven release that > supports ant 1.6.2 directly? > > > > > > Thanks, > > > Jeff Yemin > > > > > > > > > > > - > > 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: Dynamically modifing the ressources
it it not woking correctly.
What I am tried was to set in
project.xml
src/conf${configDir}
in project.properties
configDir=/default
and in my maven.xml I creat the following goal :
set configuration directory : ${configDir}
unfortunatly it does not works.
Le mardi 23 Novembre 2004 20:30, Brett Porter a écrit :
> in the resources, set it to something like:
>
> src/conf/project${foo}, then set foo to A or B.
>
> - Brett
>
>
> On Tue, 23 Nov 2004 12:47:55 +0100, Charles-Alexandre Sabourdin
>
> <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I feel that this must have been discuss somewhere but I could not figure
> > it out.
> > The basic idea is to have 2 directory /src/conf/projetA
> > /src/conf/projetB. I would like to set maven goals to use a specific
> > directory.
> > I llok aroud and found :
> > [echo] $ {pom.build.resources}:
> > [[dir =
> > /home/sabourdin/Documents/projet/exemplebean/src/conf/projetA]] but I did
> > not find how to modify this propertie :(
> >
> > --
> > Charles-Alexandre
> > SABOURDIN
> > -
> >
> > -
> > 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]
--
Charles-Alexandre
SABOURDIN
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: ant 1.6.2
so tag invokes any ant in $ANT_HOME?? -D On Wed, 24 Nov 2004 10:54:31 -0200, Felipe Vieira Silva <[EMAIL PROTECTED]> wrote: > > > > > It will call the ANT target from Maven. > > > > > On Mon, 22 Nov 2004 17:28:09 -0500, Jeff Yemin <[EMAIL PROTECTED]> wrote: > > Hi, > > > > There's a new feature in the ant 1.6.2 junit task (forkmode attribute) > > that I would really, really like to use. I tried modifiying the > > plugin.jelly file in the maven test plugin to support the new > > attributes, but quickly discovered that maven 1.0 is bound pretty > > tightly to ant 1.5.3. Is there any way to use new ant features without > > waiting for a new maven release that supports ant 1.6.2 directly? > > > > Thanks, > > Jeff Yemin > > > > > > - > 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: ant 1.6.2
It will call the ANT target from Maven. On Mon, 22 Nov 2004 17:28:09 -0500, Jeff Yemin <[EMAIL PROTECTED]> wrote: > Hi, > > There's a new feature in the ant 1.6.2 junit task (forkmode attribute) > that I would really, really like to use. I tried modifiying the > plugin.jelly file in the maven test plugin to support the new > attributes, but quickly discovered that maven 1.0 is bound pretty > tightly to ant 1.5.3. Is there any way to use new ant features without > waiting for a new maven release that supports ant 1.6.2 directly? > > Thanks, > Jeff Yemin > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Benchmarking multiple implementations of an API using Maven?
Hello, I am interested in benchmarking multiple implementations of the same API, all of which are maven projects. The APIs are Java interfaces. I am interested in collecting statistics on performance under scale (size of the data models) and performance under concurrent operations. Ideally, I would like to see reports on the performance metrics per API implementation (aka maven project) and comparisons across multiple projects as well. The goal is both to understand the scaling problems within a given implementation and to understand how different implementations perform in comparison to one another for the same test data. Are there are integrated tools for doing this? Recommendations for tools that are not integrated? Thanks, -bryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Updating scripts according to artifacts [SOLVED}
Sorry guys for having bothered for such stupid mistakes.
was due to my namespaces declaration ;-(
xmlns:j="jelly" WRONG
xmlns:j="jelly:core" CORRECT
--mike
Michael Niemaz wrote:
Hi all,
I'd like to update my launchers when creating distribs but It does not
want to work ;-(
The problem here is that ${xxx.name} are always null.
${pom.artifacts} are valid though, I mean not empty:
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
I have this weird message when launching maven:
Tag library requested that is not present: 'jelly' in plugin: 'null'
Do you think it might be the cause? If so, why do I get it?
Any ideas?
Thanx,
--mike
-
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]
Deploying a site on Windows hangs indefinitely
I am running into a lot of trouble trying to deploy a site on a
Windows XP machine. The client machine is Windows XP as well. I am
using Maven 1.1 and Cygwin.
Basically the "site:deploy" goal hangs indefinitely almost at the end.
If I issue by hand each command the plugin uses to deploy the site,
everything works fine. But when Maven invokes them, bang. I've also
sorted out that Maven hangs exactly at when it tries to decompress the
.tar.gz file:
'${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz'
I tried to use a different version of gzip but the problem persists.
Please can anyone help me out? This has been a show stopper for me.
If anyone is successfully using Windows to deploy a site, could they
share their configuration?
Thank you
Matheus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Updating scripts according to artifacts
Hi all,
I'd like to update my launchers when creating distribs but It does not
want to work ;-(
The problem here is that ${xxx.name} are always null.
${pom.artifacts} are valid though, I mean not empty:
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
I have this weird message when launching maven:
Tag library requested that is not present: 'jelly' in plugin: 'null'
Do you think it might be the cause? If so, why do I get it?
Any ideas?
Thanx,
--mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
