Re: Maven WinRunner Integration?!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could write your own Maven goal that runs the batch file then use the ant:echo file=.../ task upon completion. You would not be able to properly catch errors this way unless the batch file was written to return an error code and your Maven goal caught it and did something with it, but you would get your report inline. -Brian On Apr 29, 2004, at 3:17 AM, Göschl,Siegfried wrote: Hi folks, on the project I currently work on WinRunner is used for regression testing of the web application. I had a chat with one of the local WinRunner gurus and we set up a batch file for Windows to run the WinRunner scripts from the command line. Basically this is all I need to write a Maven WinRunner Plugin. What I actually miss is some form of reporting since WinRunner creates a proprietary text report. My colleague searched through the WWW and there is an addon available to create an XML report but this requieres modifying the existing WinRunner scripts. The following questions remain ... +) Is there a Maven Plugin available I can use - if yes it is possible to contribute it on maven-plugins.sourceforge.net +) Are there any other options to create a WinRunner report - preferable XML or HTML?! Regards Siegfried Goeschl -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFAkRra0dKNWt3rpSURAirdAKDtNsBmUammDx6IyM7wnLO3Moh0sACgo4uO em41iLV2W7jlxrzbFdjlLLo= =TAxg -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Problem with RC2's site goal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I ran into what I think was the same problem about a month ago (it's hard to tell because the original post in this thread did not include the error messages or line number). I guess there is something in RC2 that works in Windows does not work in Unix. At any rate, I have been told it has been fixed in cvs (which does not help me, considering I don't really want/need bleeding-edge cvs code), but you can fix it on your own system by tweaking that stylesheet line. Check out this message in the archive: http://nagoya.apache.org/eyebrowse/ReadMsg? [EMAIL PROTECTED]msgNo=11599 -Brian On Apr 19, 2004, at 10:30 AM, Mark R. Diggory wrote: I just upgraded as well and am getting this problem too. I deleted all my .maven repository contents and let it download everything again, but this doesn't help. There may have been previous discussion about this issue. We should review the list archives. -Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFAhBdN0dKNWt3rpSURAt/9AKC861OCRI0/dOia55REbJ+7pU6wagCgn9o0 um591eNGbDL85N5l3Z9C82c= =hoIm -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.0RC2 : error durint site:deploy and xdoc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I ran into that exact problem a few days ago. It seems the xdoc plugin in RC2 is broken and you will have to edit line 345 of the plugin.jelly file: http://nagoya.apache.org/eyebrowse/ReadMsg? [EMAIL PROTECTED]msgNo=11599 -Brian On Mar 28, 2004, at 11:17 PM, Herve AGNOUX wrote: Hello, During site:deploy, with maven 1.0RC2, I get this error : == (the end) [javadoc] 19 warnings [echo] Generating the Source Xref... maven-jxr-plugin:report: [echo] PackageManager - parsing... Test.java PackageManager - parsing... gros_machin.java ... PackageManager - parsing... biz/.../ConnectionListener.java BUILD FAILED File.. file:/home/ha/.maven/plugins/maven-jxr-plugin-1.3/plugin.jelly Element... jxr:jxr Line.. 95 Column 31 org/apache/oro/text/perl/Perl5Util Total time: 2 minutes 28 seconds Finished at: Mon Mar 29 08:50:21 CEST 2004 == On the same project, if I launch xdoc goal : == (...the end) Checking link http://checkstyle.sourceforge.net/ Validating cvs-usage.html Validating index.html Validating maven-reports.html Validating dependencies.html Validating issue-tracking.html Checking link http://nagoya.apache.org/scarab/servlet/scarab/ Validating mail-lists.html Validating project-info.html Validating team-list.html maven-linkcheck-plugin:report-real: [echo] Generating /home/ha/maven/target/docs/linkcheck.html from /home/ha/maven/target/linkcheck/docs/linkcheck.xml BUILD FAILED File.. file:/home/herve/.maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly Element... j:include Line.. 345 Column 54 null:-1:-1: null Could not parse Jelly script Total time: 6 minutes 31 seconds Finished at: Mon Mar 29 09:11:00 CEST 2004 == -- SARL diaam informatique - 04 50 44 26 54 Ingenierie, développements de systèmes d'information http://www.diaam-informatique.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFAaEiy0dKNWt3rpSURAsMWAKC/IQSp2rzHOopC88wPYmXj/8hg0QCgy2DO a828m+aZJgr2wZ2ca07fA6o= =scPE -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with scm:perform-release?
I am not sure if this is a problem with my usage or a bug, but I seem to be having difficulty with the scm:perform-release goal in both RC1 and RC2. The project has been properly tagged with prepare-release, as I can manually do a cvs export and grab all the correct files. Running a perform-release asks all the expected questions, but when it comes time to grab the files, Maven spits out the following messages: scm:cvs-checkout-project: [echo] Checking out macpackage; from CVSROOT: :ext:[EMAIL PROTECTED]:/cvsroot/macpackage; using tag: macpackage_0_5 [mkdir] Created dir: /Users/enigma/Code/java/macpackage/checkouts/macpackage [cvs] Using cvs passfile: /Users/enigma/.cvspass [cvs] cvs checkout: in directory macpackage: [cvs] cvs checkout: cannot open CVS/Entries for reading: No such file or directory [cvs] cvs [checkout aborted]: cannot open CVS/Tag: No such file or directory ...at which point, it hangs (utilizing no CPU or network resources) and I have to ^C to quit. As I understand it, CVS does not hold any files named Tag under its /CVS control folders, so I am not sure why this is being sought after. I am also a little confused as to why it would be using a .cvspass file when I have cvs and maven set up to use ssh and public/private key pairs (other Maven ssh-related operations work, like generating reports for the website). It appears that absolutely nothing gets checked out: the ./target/checkouts/macpackage folder ends up being empty. Am I doing something stupid? Is there a deficiency in the documentation? Should I write this up as a bug? -Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven RC2 and xdoc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I upgraded from RC1 to RC2 today, and I thought I did everything
correctly. I wiped out my ~/.maven/plugins folder (as per suggestions
of other messages on the list). I also use a /usr/local/maven symlink,
which used to point to the RC1 folder, and now the RC2, so paths should
be fine. Various other goals work perfectly (clean, jar, java:compile)
under RC2, but running maven clean xdoc generates the following
messages:
...normal messages...
Validating plugins.html
Validating project-info.html
Validating team-list.html
[echo] Generating
/Users/enigma/Code/java/MagicCodes/target/docs/linkcheck.html from
/Users/enigma/Code/java/MagicCodes/target/linkcheck/docs/linkcheck.xml
BUILD FAILED
File..
file:/Users/enigma/.maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly
Element... j:include
Line.. 345
Column 54
null:-1:-1: null Could not parse Jelly script
Total time: 20 seconds
Finished at: Sat Mar 27 16:23:39 PST 2004
The specific line in question looks to be trying to include the URI
${stylesheet.toString()}. Any suggestions?
-Brian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAZh0m0dKNWt3rpSURApY5AKCST2bX2a7x38KEopvVcvO+Ub3sygCeIE81
qCKlWwUyfq2DqWLbyyM6WrM=
=hBvs
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: ssh cvs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Out of the box, ssh supports both key files and passwords--using the key files if they exist, then falling back to passwords if they do not (or if the keys are incorrect). It is not an either/or configuration. Disabling key files takes a willful act of the system administrator. Have you tried using key files yet? If so, do they have all the correct permissions? (Ssh is picky about some files not being writable by group+other and other files not even being readable by group+other, and doesn't offer much as far as error messages for permission problems). -Brian On Mar 8, 2004, at 4:18 AM, Stefan Groschupf wrote: My cvs has only ssh2 access but use passwords instead of key files. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFATJs60dKNWt3rpSURAndDAJoDUm3sVSJdPju+0g8hSMq1w3SfLgCgoZqd pyGLmFcFqG+NkIWQ+oI0ScM= =wdpw -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie question
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A little more complex and slightly less straightforward, I would
assume you could do this using XML entity trickery. For instance:
!DOCTYPE project [
!ENTITY pomBaseUrl http://server.com;
]
project
...
urlpomBaseUrl;/adept-open/url
...
/project
-Brian
On Mar 8, 2004, at 5:04 PM, Hensley, Richard wrote:
I'm trying to use maven to build a master site with multiple
subprojects,
like db.apache.org
I've worked out all the kinks, except one. The machine that the site
lives
on is likely to move. So, I wanted to define the base url somewhere
globally
and then base the rest of my url's from there.
?xml version=1.0 encoding=ISO-8859-1?
project
pomVersion3/pomVersion
extend${basedir}/../project_defaults.xml/extend
url${pom.base-url}/adept-open/url
/project
As the experts already know, and I found out through expirementation,
this
doesn't work.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFATV2V0dKNWt3rpSURAsmgAJ9TxdXBpHv6k0I00sij2aH/hdjK5wCgqhyG
zDHICbMXmf9KecEtjNNysOE=
=LRhO
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding source in Java builds
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was kind of looking for a solution that didn't involve shuffling around stuff too much on the CVS server. We would probably drop Maven and continue using Ant if we had to break the single source folder into twelve separate ones. I hate to think about how awkward it would be, working with that many source folders in an Eclipse project. I'd rather have the tools work for me, than the other way around. It seems the sourceModifications element is there for a reason, perhaps this very reason. I was just hoping for some confirmation/denial that I am using it correctly. -Brian On Mar 5, 2004, at 10:58 AM, Emmanuel Venisse wrote: Why you don't explode your source repository into multiple directory? It's very much simple to show which classes are in wich projects. Emmanuel -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFASNDy0dKNWt3rpSURAj+oAKCt8P9/S+hSCYkPkeHyzMP6xIyH0gCfXiOf lb4xp52OI7gSkFJRlnssOGE= =GA/k -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding source in Java builds
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That is what I originally had, but got a parsing error when Maven starts up: $ maven -p project-util.xml java:compile __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT java:prepare-filesystem: java:compile: [echo] Compiling to /Users/brian/Projects/Tools/target/classes BUILD FAILED File.. file:.maven/plugins/maven-java-plugin-1.3/ Element... ant:available Line.. 46 Column 81 At least one of (classname|file|resource) is required Total time: 6 seconds Finished at: Fri Mar 05 11:22:27 PST 2004 It looked like it could not find my classname tag, so I thought I had nested it too deep. The project.xml file is a little sketchy when it comes to whether there is a difference between sourceModification and sourceModifications and whether they are nested. -Brian On Mar 5, 2004, at 11:17 AM, Gilles Dodinet wrote: Brian, if this is what you actually have in your pom, i think you're the outer sourceModification element : sourceModifications sourceModification !-- includes/excludes/classname -- /sourceModification /sourceModifications -- gd -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFASNTB0dKNWt3rpSURAqZ6AKDRj8TCBkXN6RHU5+k1TcatfxKX3QCg1b68 2g/G3OFFkv9PuopLHF5D/0w= =i7PP -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding source in Java builds
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Never mind. I solved it. The error message Maven spits out, as well as the reference for properties.xml show the tag as classname (all lower case). The maven-java-plugin-1.3/plugin.jelly file seems to want className (mixed case). Using nested sourceModifications with a slight change in capitalization fixed everything: sourceModifications sourceModification className ...etc Everyone: thanks for your help! -Brian On Mar 5, 2004, at 11:27 AM, Brian Enigma wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That is what I originally had, but got a parsing error when Maven starts up: At least one of (classname|file|resource) is required Total time: 6 seconds Finished at: Fri Mar 05 11:22:27 PST 2004 It looked like it could not find my classname tag, so I thought I had nested it too deep. The project.xml file is a little sketchy when it comes to whether there is a difference between sourceModification and sourceModifications and whether they are nested. -Brian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iD8DBQFASNbm0dKNWt3rpSURAqOHAKDjY8DrLpajMqMY1CMEFJ8YirLz5QCeIDm8 OEYtRYwBdxN9I4PiKAi6cD4= =DD96 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
