I see. Well, I suppose you could keep a backup copy and just
overwrite the incorrectly gen'd one every time, but that would be
frustrating I'm sure.
I don't know if the current plugin supports this sort of specialized
build configuration or some way to inject fragments into the output
hi,
we are using subversion as scm and are in the middle of moving from ant 1.6
to maven2.
right now i am stuck with the following issue.
i would like to get information about the subversion copy that was used to
check-out the src directory and the repository revision of the src
directory into
That is what i thought. I should not a classpath. Most of my dependencies
are with compile scope and yes i have an ejb jar file that i'm trying to
compile. i cannot send u the exact snippet as i'm on a vacation :). Will get
in touch next week.
thanks.
Scott Ryan-2 wrote:
You should not
I'm trying to develop a Launch4j Maven2 plugin by reading this
tutorial:
http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html
Now I have a problem because launch4j uses a custom ant task so I need
to specify a classpath that indicates where to find launch4j.jar
(which I have
mvn clean would be a possibility ... but doing that always before
doing a backup? we'd prefer to run it independently.
but remy and max propositions help already a lot concerning verison
control. a few entries in the ignore is doable.
-solo
On 10/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
Hello Alex,
you can get the svn revision with
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
executions
execution
phasevalidate/phase
idgetting-scm.revision/id
I had this problem too and it seems we're not alone.
In my opinion an extra property should be added:
executeOnDatabase (but with a better name) which defaults on false
and outputFile should default on something like target/hibernate3/script.sql
so a defaulted hbm2dll run would create scripts.
Hi All,
How do you enable assertions for the jetty plugin?
Are they enabled by default?
Thanks!
,chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Jean-Michel.
Natively you can't update the project.properties .
But can certainly do it with Jelly and the propertyfile task :
http://ant.apache.org/manual/OptionalTasks/propertyfile.html
System Environment can't be edited. In fact before JDK 1.5 you wasn't able
to do it (easily) in Java.