Hi,
You can "dynamically" change the project object from jelly, so you should be able to add that
dependency with a maven goal. I tried to find the changes I made in a maven.xml, but since I don't
work there anymore (and it's been a while, could be that maven changed it's core and doesn't allow
anymore what I did), I don't have anything left on my system to get you going.
I know it took be about an hour to get working though.
Mvgr,
Martin
swebb wrote:
Hi there,
I am using maven 1 and using the jnlp goal to generate a jnlp file and sign
the associated jar files. The problem I have is that one of the jar files is
generated by the build as well as the normal project generated jar. Because
the jar is generated it isn't in the dependancy list so the jnlp plugin
doesn't know anything about it and doesn't put a reference to it in the jnlp
file. Also I should mention I don't want to use the repository for this
generated jar.
Is there anyway for me to add the details of the dependancy as a preGoal to
the jnlp goal ? I'm new to Maven so still finding my feet. From what I
understand the dependancy information is stored in the pom.artifacts is
there any way to add to this programatically within the build script ? I saw
some code that used something called system-scope to set another existing
variable could this be used ?
Thanks for any help.
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
