[jira] Created: (MPTEST-47) It should be possible to add additional elements to the test classpath
It should be possible to add additional elements to the test classpath
--
Key: MPTEST-47
URL: http://jira.codehaus.org/browse/MPTEST-47
Project: maven-test-plugin
Type: Improvement
Environment: Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.2_07-b05)
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)
Reporter: Henning Schmiedehausen
Attachments: maven-test.patch
(this is basically a rehash of MPTEST-16)
For porting unit tests from ant to maven, it was necessary to add certain
pre-produced jars to the test classpath. This is not possible with the 1.6.2
plugin. My solution was (as the solution of some other users), to add a
property which can
be assigned and is then added to the classpath. This allows me to do e.g.
maven.test.classpath=
${basedir}/test/cpload/test1.jar;${basedir}/test/cpload/test2.jar
where test1.jar and test2.jar are jars that must not be present in the build
phase but need to present in the test phase.
There have different solution been discussed. However:
- adding something to the resources part of the POM makes it impossible to
automatically download such a jar
through maven.
- adding a property to the dependencies makes it impossible to ship such a test
jar with the distribution and reference
it locally.
and still we currently have no solution at all. I'd therefore propose the
attached patch which allows all three test goals in maven-test-plugin
(test:single, test:test and test:match) to evaluate a property variable called
maven.test.classpath. This
variable (if nonempty) is transferred to a pathelement path=.../ element
and can therefore contain multiple elements (separated by e.g. ;).
The attached patch is IMHO the easiest fix for this problem with seems to
affect a lot of maven users.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[cruisecontrol] 1.7-SNAPSHOT not using correct ${url} for CVS
Vincent,
I think that the change you made fro using the computed ${url} from
maven-scm-plugin isn't quite right, but I thought I would run it by you.
At least for CVS, I find that the ${url} property is only used to define
the cvsroot. Therefore it should be ${url} should equal ${root}, and
not have the module appended.
I haven't committed the change as I thought I would run it by you'all
first.. Am I just attempting to use 1.7-SNAPSHOT in the middle of your
efforts?
If your changes are done, I'd like to move to releasing 1.7 soon, as it
does match to CC 2.2.1 much better.
Eric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r156562 - maven/maven-1/plugins/trunk/cruisecontrol/plugin.jelly
Author: epugh
Date: Tue Mar 8 12:01:26 2005
New Revision: 156562
URL: http://svn.apache.org/viewcvs?view=revrev=156562
Log:
url property for CVS is used as CVSROOT and should not
have the module attached to it.
Modified:
maven/maven-1/plugins/trunk/cruisecontrol/plugin.jelly
Modified: maven/maven-1/plugins/trunk/cruisecontrol/plugin.jelly
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/cruisecontrol/plugin.jelly?view=diffr1=156561r2=156562
==
--- maven/maven-1/plugins/trunk/cruisecontrol/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/cruisecontrol/plugin.jelly Tue Mar 8 12:01:26
2005
@@ -54,12 +54,14 @@
j:if test=${method == 'cvs'}
maven:pluginVar var=root plugin=maven-scm-plugin
property=maven.scm.cvs.root/
maven:pluginVar var=module plugin=maven-scm-plugin
property=maven.scm.cvs.module/
+ j:set var=url value=${root}/
/j:if
j:if test=${method == 'svn'}
maven:pluginVar var=root plugin=maven-scm-plugin
property=maven.scm.svn.root/
maven:pluginVar var=module plugin=maven-scm-plugin
property=maven.scm.svn.module/
+ j:set var=url value=${root}/${module}/
/j:if
-j:set var=url value=${root}/${module}/
+
!-- Compute the merge directory automatically if not specified by the
user --
maven:makeRelativePath var=relativeMavenBuildDir basedir=${basedir}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Releasing CruiseControl plugin v1.7?
-1
Plugin tests are failing! I know we don't run them much, but I noticed
that Brett commented out the cruisecontrol plugin:test from being run as
part of the main Maven build, and that feels like a real mark of
shame.
Would it be possible to hold on till the end of this week? I just fixed
a bug with setting up CVSROOT's and would like a day or two to test it
on my production systems. I am also working on a small tweak to make
creating your own cruisecontrol.jsl a bit easier. Right now I jump
through odd hoops to get my own cruisecontrol.jsl to load, and would
like to simplify and document it a bit more.
If you really need the 1.7 release this week, then my tweak can wait for
1.8, if you can just review my bugfix for the CVSROOT and ${url}
property, and we agree that plugin:test doesn't have to pass, then I'll
change my -1 to a -0. Otherwise, I hope to get done in the next two
days fixing the plugin tests.
ERic
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 06, 2005 5:10 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
+1
Arnaud
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoyé : dimanche 6 mars 2005 22:02
À : 'Maven Developers List'
Objet : [VOTE] Releasing CruiseControl plugin v1.7?
Hi,
I'd like to release the CC plugin v1.7. Here are the changes
brought since
v1.6:
action dev=vmassol type=update
Removed all dependencies on the SCM module and
instead replace all
occurrences with code${pom.artifactId}/code.
/action
action dev=vmassol type=add
Added new codecruisecontrol:configure-war/code
goal that generates
a configured CruiseControl webapp WAR.
/action
action dev=vmassol type=update
Use the same default value for the
codemaven.cruisecontrol.mail.buildresultsurl/code property
than the one for
codemaven.cruisecontrol.buildresults.url/code.
/action
action dev=vmassol type=update
Modified default value of
codemaven.cruisecontrol.logs.mergedirectory/code
so that CC can aggregate JUnit test reports both for
single project and
multiproject setups.
/action
action dev=vmassol type=update
Compute automatically the merge directory automatically (the
value of codemaven.cruisecontrol.logs.mergedirectory/code
if not specified by the user. The computation uses the
codemaven.build.dir/code property to guess the output
directory for JUnit test results.
/action
action dev=vmassol type=add
Added a new
codemaven.cruisecontrol.logs.pattern/code property
to specify the report files that will be merged by
CC. Defaults to
code*.xml/code.
/action
action dev=vmassol type=add
Added a new codecruisecontrol:install-local/code goal
to install the generated CC config to a target location on
the same machine (it uses a file copy). In the future we could
provide other installation mechanisms like ssh, scp, etc.
/action
action dev=vmassol type=update
Changed the default build status file name to be
codestatus.txt/code which is the default value
expected by the CC Webapp.
/action
action dev=vmassol type=update
New codemaven.cruisecontrol.work.dir/code
property that specifies
what CC work directory to use for the project.
Default values of
codemaven.cruisecontrol.checkout.dir/code and
codemaven.cruisecontrol.logs.dir/code have been
modified to be
relative to it.
/action
action dev=vmassol type=fix
Fixed default property values for
codemaven.cruisecontrol.mail.xlsdir/code
and codemaven.cruisecontrol.mail.css/code so that
the plugin works by default
with the latest CC version (2.2.1).
/action
action dev=vmassol type=fix issue=MPCRUISECONTROL-19
Fix order in which the CruiseControl's
codelt;projectgt;/code
elements are generated. They must be in the order of the less
dependent project first.
/action
Here's my +1
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [cruisecontrol] 1.7-SNAPSHOT not using correct ${url} for CVS
Hi Eric,
Thanks for the patch you've just committed. You're right, it should be
tested more before committing (I have tested it well with SVN but I have not
tested it with CVS - I had forgotten about this part when I proposed to
release it).
And you're also right that I've not run the plugin tests as they were not
running before I initially started modifying the plugin. I should have spent
time fixing them.
Anyway, let's fix them now.
Thanks
-Vincent
-Original Message-
From: Eric Pugh [mailto:[EMAIL PROTECTED]
Sent: mardi 8 mars 2005 18:19
To: Maven-Dev
Subject: [cruisecontrol] 1.7-SNAPSHOT not using correct ${url} for CVS
Vincent,
I think that the change you made fro using the computed ${url} from
maven-scm-plugin isn't quite right, but I thought I would run it by you.
At least for CVS, I find that the ${url} property is only used to define
the cvsroot. Therefore it should be ${url} should equal ${root}, and
not have the module appended.
I haven't committed the change as I thought I would run it by you'all
first.. Am I just attempting to use 1.7-SNAPSHOT in the middle of your
efforts?
If your changes are done, I'd like to move to releasing 1.7 soon, as it
does match to CC 2.2.1 much better.
Eric
-
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: [VOTE] Releasing CruiseControl plugin v1.7?
I completely agree. Thanks for pointing the problems out! :-)
There's absolutely no urgency so let's get it in good shape before we
release it.
Thanks
-Vincent
-Original Message-
From: Eric Pugh [mailto:[EMAIL PROTECTED]
Sent: mardi 8 mars 2005 21:06
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
-1
Plugin tests are failing! I know we don't run them much, but I noticed
that Brett commented out the cruisecontrol plugin:test from being run as
part of the main Maven build, and that feels like a real mark of
shame.
Would it be possible to hold on till the end of this week? I just fixed
a bug with setting up CVSROOT's and would like a day or two to test it
on my production systems. I am also working on a small tweak to make
creating your own cruisecontrol.jsl a bit easier. Right now I jump
through odd hoops to get my own cruisecontrol.jsl to load, and would
like to simplify and document it a bit more.
If you really need the 1.7 release this week, then my tweak can wait for
1.8, if you can just review my bugfix for the CVSROOT and ${url}
property, and we agree that plugin:test doesn't have to pass, then I'll
change my -1 to a -0. Otherwise, I hope to get done in the next two
days fixing the plugin tests.
ERic
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 06, 2005 5:10 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
+1
Arnaud
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoyé : dimanche 6 mars 2005 22:02
À : 'Maven Developers List'
Objet : [VOTE] Releasing CruiseControl plugin v1.7?
Hi,
I'd like to release the CC plugin v1.7. Here are the changes
brought since
v1.6:
action dev=vmassol type=update
Removed all dependencies on the SCM module and
instead replace all
occurrences with code${pom.artifactId}/code.
/action
action dev=vmassol type=add
Added new codecruisecontrol:configure-war/code
goal that generates
a configured CruiseControl webapp WAR.
/action
action dev=vmassol type=update
Use the same default value for the
codemaven.cruisecontrol.mail.buildresultsurl/code property
than the one for
codemaven.cruisecontrol.buildresults.url/code.
/action
action dev=vmassol type=update
Modified default value of
codemaven.cruisecontrol.logs.mergedirectory/code
so that CC can aggregate JUnit test reports both for
single project and
multiproject setups.
/action
action dev=vmassol type=update
Compute automatically the merge directory automatically (the
value of codemaven.cruisecontrol.logs.mergedirectory/code
if not specified by the user. The computation uses the
codemaven.build.dir/code property to guess the output
directory for JUnit test results.
/action
action dev=vmassol type=add
Added a new
codemaven.cruisecontrol.logs.pattern/code property
to specify the report files that will be merged by
CC. Defaults to
code*.xml/code.
/action
action dev=vmassol type=add
Added a new codecruisecontrol:install-local/code goal
to install the generated CC config to a target location on
the same machine (it uses a file copy). In the future we could
provide other installation mechanisms like ssh, scp, etc.
/action
action dev=vmassol type=update
Changed the default build status file name to be
codestatus.txt/code which is the default value
expected by the CC Webapp.
/action
action dev=vmassol type=update
New codemaven.cruisecontrol.work.dir/code
property that specifies
what CC work directory to use for the project.
Default values of
codemaven.cruisecontrol.checkout.dir/code and
codemaven.cruisecontrol.logs.dir/code have been
modified to be
relative to it.
/action
action dev=vmassol type=fix
Fixed default property values for
codemaven.cruisecontrol.mail.xlsdir/code
and codemaven.cruisecontrol.mail.css/code so that
the plugin works by default
with the latest CC version (2.2.1).
/action
action dev=vmassol type=fix issue=MPCRUISECONTROL-19
Fix order in which the CruiseControl's
codelt;projectgt;/code
elements are generated. They must be in the order of the less
dependent project first.
/action
Here's my +1
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Releasing CruiseControl plugin v1.7?
My previous email about CC and CVSROOT went out today, I wrote it a
couple days ago, not sure why it didn't send. At any rate, I just
committed my fix, based on someone else finding the same issue, and I'll
work on the failing plugin tests tonight.
Eric
-Original Message-
From: Eric Pugh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 08, 2005 3:06 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
-1
Plugin tests are failing! I know we don't run them much, but I noticed
that Brett commented out the cruisecontrol plugin:test from being run as
part of the main Maven build, and that feels like a real mark of
shame.
Would it be possible to hold on till the end of this week? I just fixed
a bug with setting up CVSROOT's and would like a day or two to test it
on my production systems. I am also working on a small tweak to make
creating your own cruisecontrol.jsl a bit easier. Right now I jump
through odd hoops to get my own cruisecontrol.jsl to load, and would
like to simplify and document it a bit more.
If you really need the 1.7 release this week, then my tweak can wait for
1.8, if you can just review my bugfix for the CVSROOT and ${url}
property, and we agree that plugin:test doesn't have to pass, then I'll
change my -1 to a -0. Otherwise, I hope to get done in the next two
days fixing the plugin tests.
ERic
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 06, 2005 5:10 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
+1
Arnaud
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoyé : dimanche 6 mars 2005 22:02
À : 'Maven Developers List'
Objet : [VOTE] Releasing CruiseControl plugin v1.7?
Hi,
I'd like to release the CC plugin v1.7. Here are the changes brought
since
v1.6:
action dev=vmassol type=update
Removed all dependencies on the SCM module and instead replace
all
occurrences with code${pom.artifactId}/code.
/action
action dev=vmassol type=add
Added new codecruisecontrol:configure-war/code
goal that generates
a configured CruiseControl webapp WAR.
/action
action dev=vmassol type=update
Use the same default value for the
codemaven.cruisecontrol.mail.buildresultsurl/code property
than the one for
codemaven.cruisecontrol.buildresults.url/code.
/action
action dev=vmassol type=update
Modified default value of
codemaven.cruisecontrol.logs.mergedirectory/code
so that CC can aggregate JUnit test reports both for
single project and
multiproject setups.
/action
action dev=vmassol type=update
Compute automatically the merge directory automatically (the
value of codemaven.cruisecontrol.logs.mergedirectory/code
if not specified by the user. The computation uses the
codemaven.build.dir/code property to guess the output
directory for JUnit test results.
/action
action dev=vmassol type=add
Added a new
codemaven.cruisecontrol.logs.pattern/code property
to specify the report files that will be merged by
CC. Defaults to
code*.xml/code.
/action
action dev=vmassol type=add
Added a new codecruisecontrol:install-local/code goal
to install the generated CC config to a target location on
the same machine (it uses a file copy). In the future we could
provide other installation mechanisms like ssh, scp, etc.
/action
action dev=vmassol type=update
Changed the default build status file name to be
codestatus.txt/code which is the default value
expected by the CC Webapp.
/action
action dev=vmassol type=update
New codemaven.cruisecontrol.work.dir/code
property that specifies
what CC work directory to use for the project.
Default values of
codemaven.cruisecontrol.checkout.dir/code and
codemaven.cruisecontrol.logs.dir/code have been
modified to be
relative to it.
/action
action dev=vmassol type=fix
Fixed default property values for
codemaven.cruisecontrol.mail.xlsdir/code
and codemaven.cruisecontrol.mail.css/code so that
the plugin works by default
with the latest CC version (2.2.1).
/action
action dev=vmassol type=fix issue=MPCRUISECONTROL-19
Fix order in which the CruiseControl's
codelt;projectgt;/code
elements are generated. They must be in the order of the less
dependent project first.
/action
Here's my +1
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Releasing CruiseControl plugin v1.7? (KMM158504026V22743L0KM)
Hello,
Thank you for writing to eBay. My name is Fenton.
I have now received seven emails regarding this 'CruiseControl' issue. I
would like to inform you that you are writing to eBay's Trust Safety
department. If you have an issue with an eBay transaction, I ask that
you clearly state your issue, otherwise I would ask that you remove us
from your mailing list regarding this software development.
This is for both your security and privacy for the software, as well as
my time that has been spent reading your communication.
Thanks again for writing, and thank you for being part of the eBay
community.
Kind Regards
Fenton
Fraud Prevention Group
_
Original Message Follows:
-
My previous email about CC and CVSROOT went out today, I wrote it a
couple days ago, not sure why it didn't send. At any rate, I just
committed my fix, based on someone else finding the same issue, and I'll
work on the failing plugin tests tonight.
Eric
-Original Message-
From: Eric Pugh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 08, 2005 3:06 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
-1
Plugin tests are failing! I know we don't run them much, but I noticed
that Brett commented out the cruisecontrol plugin:test from being run as
part of the main Maven build, and that feels like a real mark of
shame.
Would it be possible to hold on till the end of this week? I just fixed
a bug with setting up CVSROOT's and would like a day or two to test it
on my production systems. I am also working on a small tweak to make
creating your own cruisecontrol.jsl a bit easier. Right now I jump
through odd hoops to get my own cruisecontrol.jsl to load, and would
like to simplify and document it a bit more.
If you really need the 1.7 release this week, then my tweak can wait for
1.8, if you can just review my bugfix for the CVSROOT and ${url}
property, and we agree that plugin:test doesn't have to pass, then I'll
change my -1 to a -0. Otherwise, I hope to get done in the next two
days fixing the plugin tests.
ERic
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 06, 2005 5:10 PM
To: 'Maven Developers List'
Subject: RE: [VOTE] Releasing CruiseControl plugin v1.7?
+1
Arnaud
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoyé : dimanche 6 mars 2005 22:02
À : 'Maven Developers List'
Objet : [VOTE] Releasing CruiseControl plugin v1.7?
Hi,
I'd like to release the CC plugin v1.7. Here are the changes brought
since
v1.6:
action dev=vmassol type=update
Removed all dependencies on the SCM module and instead replace
all
occurrences with code${pom.artifactId}/code.
/action
action dev=vmassol type=add
Added new codecruisecontrol:configure-war/code
goal that generates
a configured CruiseControl webapp WAR.
/action
action dev=vmassol type=update
Use the same default value for the
codemaven.cruisecontrol.mail.buildresultsurl/code property
than the one for
codemaven.cruisecontrol.buildresults.url/code.
/action
action dev=vmassol type=update
Modified default value of
codemaven.cruisecontrol.logs.mergedirectory/code
so that CC can aggregate JUnit test reports both for
single project and
multiproject setups.
/action
action dev=vmassol type=update
Compute automatically the merge directory automatically (the
value of codemaven.cruisecontrol.logs.mergedirectory/code
if not specified by the user. The computation uses the
codemaven.build.dir/code property to guess the output
directory for JUnit test results.
/action
action dev=vmassol type=add
Added a new
codemaven.cruisecontrol.logs.pattern/code property
to specify the report files that will be merged by
CC. Defaults to
code*.xml/code.
/action
action dev=vmassol type=add
Added a new codecruisecontrol:install-local/code goal
to install the generated CC config to a target location on
the same machine (it uses a file copy). In the future we could
provide other installation mechanisms like ssh, scp, etc.
/action
action dev=vmassol type=update
Changed the default build status file name to be
codestatus.txt/code which is the default value
expected by the CC Webapp.
/action
action dev=vmassol type=update
New codemaven.cruisecontrol.work.dir/code
property that specifies
what CC work directory to use for the project.
Default values of
codemaven.cruisecontrol.checkout.dir/code and
codemaven.cruisecontrol.logs.dir/code have been
modified to be
relative to it.
/action
action dev=vmassol type=fix
[jira] Commented: (MPJAVADOC-34) Javadoc links don't work behind a proxy
[ http://jira.codehaus.org/browse/MPJAVADOC-34?page=comments#action_30613 ] Wim Deblauwe commented on MPJAVADOC-34: --- Why doesn't the plugin take the values you already need to define to get to the remote repository? I have for instance the following build.properties in my home folder: # Properties file for maven maven.proxy.host = proxy.mycompany.com maven.proxy.port = 80 maven.proxy.ntlm.domain = MYDOMAIN maven.proxy.username = myusername maven.proxy.password = mypassword The javadoc plugin should be able to read out these values, so I don't have to specify them somewhere else again. Javadoc links don't work behind a proxy --- Key: MPJAVADOC-34 URL: http://jira.codehaus.org/browse/MPJAVADOC-34 Project: maven-javadoc-plugin Type: Improvement Versions: 1.1, 1.2, 1.3, 1.4, 1.5 Reporter: Carlos Sanchez Assignee: Arnaud HERITIER Priority: Minor Links doesn't work behind a proxy javadoc: Error fetching URL: http://java.sun.com/j2se/1.4.2/docs/api/package-list I've found some information in the net: It is possible to pass proxy information to javadoc. Try: javadoc -J-DproxyHost=myproxyhost.com -J-DproxyPort=8080 -link http://java.sun.com/products/jdk/1.3/docs/api *.java You have to pass http.proxyhost and http.proxyport properties to the JVM. -Dhttp.proxyhost=proxy -Dhttp.proxyport=3128 The problem is that javadoc ant task starts in another jvm (as stated in ant docs) Also I've tried the setProxy ant task and it doesn't work either. ant:setproxy proxyhost=proxy proxyport=3128/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
