plynch 078e8cfdfa o sometimes properties fetched using the ${some.property} notation don't always come through. in particular when I added a maven.webserver.port.http calue to my project.properties and ran the plugin, the plugin failed on the check for maven.webserver.test.socket because the ${maven.webserver.test.socket} notation was used. when I switched to context.getVariable('maven.webserver.test.socket') it found my project.properties specified value no problem. Amazing.... ...

o added maven.appserver properties to the filterset so that the two plugins can integrate better.


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113433 13f79535-47bb-0310-9956-ffa450edef68

2003-05-22 23:52:00 +00:00

..

src/plugin-resources

o leave it up to plugin.jelly to make the root dir since that is where the detection is and it is a required property

2003-05-05 03:06:51 +00:00

xdocs

o adding property docs for version 2.0

2003-05-02 18:40:56 +00:00

.cvsignore

Initial revision

2003-01-24 03:44:26 +00:00

plugin.jelly

o sometimes properties fetched using the ${some.property} notation don't always come through. in particular when I added a maven.webserver.port.http calue to my project.properties and ran the plugin, the plugin failed on the check for maven.webserver.test.socket because the ${maven.webserver.test.socket} notation was used. when I switched to context.getVariable('maven.webserver.test.socket') it found my project.properties specified value no problem. Amazing....

2003-05-22 23:52:00 +00:00

plugin.properties

o changing extra port names to A, B, C from one, two,three

2003-05-02 17:54:04 +00:00

project.properties

Added license property

2003-02-10 08:26:57 +00:00

project.xml

o adding back dependencies cause if you call the plugin from an attain goal it can

2003-05-15 17:12:47 +00:00