[mojo-dev] Re: selenium-maven-plugin

2011-05-27 Thread Greg Akins
OK.. I looked around a bit more and found MSELENIUM-65-selenium-2 Does anyone have an idea what Selenium plugin release this is targeted for, if any? On Fri, May 27, 2011 at 11:37 AM, Greg Akins wrote: > Is there anyone on the list working on selenium-maven-plugin? > > I'd like to find out  like

[mojo-dev] selenium-maven-plugin

2011-05-27 Thread Greg Akins
Is there anyone on the list working on selenium-maven-plugin? I'd like to find out likelihood of moving to Selenium 2. Anybody know? -- Greg Akins http://twitter.com/akinsgre - To unsubscribe from this list, please visit:

[mojo-dev] [jira] Closed: (MOJO-1680) Add ability to pass JVM system properties to jmeter execution

2011-05-27 Thread Daniel Hopper (JIRA)
[ http://jira.codehaus.org/browse/MOJO-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Hopper closed MOJO-1680. --- Resolution: Won't Fix Fix Version/s: chronos-maven-plugin-1.0 Scratch that, I just noticed this is al

[mojo-dev] [jira] Created: (MOJO-1680) Add ability to pass JVM system properties to jmeter execution

2011-05-27 Thread Daniel Hopper (JIRA)
Add ability to pass JVM system properties to jmeter execution - Key: MOJO-1680 URL: http://jira.codehaus.org/browse/MOJO-1680 Project: Mojo Issue Type: New Feature Compone

Re: [mojo-dev] Alternative idea about site publication

2011-05-27 Thread Benson Margulies
If Ben turns on rewrite rules in .htaccess, we can push a .htaccess with an antrun as part of the release profile. On Fri, May 27, 2011 at 3:48 AM, Markus Mahlberg wrote: > Thw hole point is that relying on symlinks is simply not a portable way to do > it. > Neither do all operating systems supp

AW: [mojo-dev] Alternative idea about site publication

2011-05-27 Thread Markus Mahlberg
Thw hole point is that relying on symlinks is simply not a portable way to do it. Neither do all operating systems support symbolic links nor does even the Apache httpd necessarily follow them. And the idea should be to solve that issue once and for all, shouldn't it? I'll post a modified pom.x