Write a java bean. You can then use the jelly:bean tag to wrap it as a
jelly tag, and as long as the method name is execute, I believe Ant will
run it too.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nathan Coast [EMAIL PROTECTED] wrote on 25/09/2003
cheers Dion,
figured there would be an easy answer. does jelly:bean supported nested
path structures?
e.g.
if my bean has a method
setSrc(Path srcPath)
{.
can I declare
mytag ..
src path=${src}/
src path=${src2}/
/mytag
[EMAIL PROTECTED] wrote:
Write a java bean. You can then
Hallo,
the project descriptor resources can be used if you want the additional files
to end up inside the artifact produced for your project. If you want the
additional files to be in the tar ball you might want to do something like this
in your maven.xml:
postGoal
OK this is what's in my jelly
.
xmlns:bean=jelly:bean
bean:beandef
className=com.codeczar.maven.plugins.ejbgen.EjbgenBean
methodName=execute
name=ejbgentag/
ejbgentag outputDir=${maven.ejbgen.java.dir}
descriptorDir=${maven.build.dest}\META-INF
.
Sorry for spamming. Just didn't see that there was a reply already.
Dominik
On Thu, 2003-09-25 at 12:16, Dominik Dahlem wrote:
Hi Skip,
I think you can do this one:
j:set var=your.web.app.dir
value=${pom.getPluginContext('maven-war-plugin').getVariable('maven.war.webapp.dir')}/
Hi,
Having got my tag working, I've now broken it again by adding nested
tags to it. I'd like to add src tags the same as for the
ant:javac
ant:src
ant:path refid=maven.compile.src.set/
/ant:src
so my tag is:
ejbgen:ejbgen
Hi Maveners,
The console plugin is a nice speed-up... would it be possible to set
properties with it as well ?
Using the reactor it looks possible to actually perform other builds
with all plugin-classes loaded.
Paul
-
To
FWIW I have also observed this behavior with Win2K and XP and have noted that it
usually coincides with bad XML content.
Usually a short between the keyboard and chair on my part. :)
Perhaps something within the Javadoc tags is causing the problem.
Have a closer look a possible entity
I'm trying to run the cactus:report goal and I keep getting the
following error:
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-10
BUILD FAILED
File.. file:/C:/Documents and
I write this mail with my day job hat on, rather than my Jakarta Commons
hat.
I have spent a little while trying to get Maven integrated as the build and
deploy system for one of our products at my day job. The product is fairly
simple and small, so I thought it wouldn't be too bad to achieve. I
I have spent a little while trying to get Maven integrated as
the build and deploy system for one of our products at my day
job.
A lot of people here have done this. I agree it could be easier, especially
in terms of doco, but I'm sure that will improve as we go towards 1.0.
Feedback and
I'm not sure what you are trying to achieve. ${basedir} should always be set
to the executing project's directory.
- Brett
-Original Message-
From: Jamie McCrindle [mailto:[EMAIL PROTECTED]
Sent: Thursday, 25 September 2003 7:29 PM
To: Maven Users List
Subject: properties
hi,
I think 3.1 only works with the latest release.
Vincent??
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Gaffney, Michael [EMAIL PROTECTED] wrote on 26/09/2003
02:58:42 AM:
I'm trying to run the cactus:report goal and I keep getting the
following
Little comments...
Stephen Colebourne [EMAIL PROTECTED] wrote on 26/09/2003
07:09:02 AM:
1) Project xml and Project properties.
Maven sells itself as 'wite a project xml and you are done'. But in
reality
this is not the case. Many parameters are controlled in the project
properties, and
14 matches
Mail list logo
