Hi,
the vote on the release of the xml-maven-plugin went as follows:
+1 2+2Trygve, Jochen, Kostis (non-binding?), Kris (non-binding?)
=0 1Raphaël
-1 0
I haven't got sufficient experience with the Mojo policy. Is that
sufficient for a release? If so, what are my next steps? M
[ http://jira.codehaus.org/browse/MOJO-565?page=comments#action_80915 ]
Trygve Laugstol commented on MOJO-565:
--
The idea with the cd $BASEDIR was that the program always would know where to
get the files from, but after -Dbasedir was introdu
Hi Johann,
Thanks for the response :)
Johann Reyes wrote, On 2006-11-23 4:14 PM:
2) Actually it should find based on goal, because for example, if you don't
need to override any of the default values, you don't need to include a
element. If you need to override the implementation or
outputdire
Hello Geoffrey
1) Actually in the code is "ddl", not "dll" like I wrote in the email, sorry
for the confussion.
2) Actually it should find based on goal, because for example, if you don't
need to override any of the default values, you don't need to include a
element. If you need to override the
[ http://jira.codehaus.org/browse/MOJO-565?page=all ]
Mathieu Champlon updated MOJO-565:
--
Attachment: MOJO-565.patch
Here is a patch fixing this issue.
For the shell script I removed the cd because I honestly cannot understand what
it was for.
For th
Hi Johann,
I have some more feed-back :)
I still received the same error "Could not get ConfigurationTask.".
But for different reasons
configurationTasks contained 4 configurations, including the annotation
one I need.
1) The original mail with an example said hbm2dll,
that should be hbm2ddl
Hello Geoffrey
Thanks for pointing out the problem. Yep, that was the problem, the
component, through components.xml register itself to be available as a task
to the plugin, that way if there is a person that needs to use their "own"
ConfigurationTask implementation using their own Configuration
i
ConfigurationTasks is empty because the jdk5 configuration's
components.xml isn't updated I believe (not sure how this works with
plexus):
It's still using ConfigHibernate and ConfigOutputDirectory,
instead of DefaultConfigurationTask or something special for annotations
(not sure)
Take a lo
[appassembler] scripts change the current directory therefore relative pathes
become invalid
Key: MOJO-565
URL: http://jira.codehaus.org/browse/MOJO-565
Proj
[ http://jira.codehaus.org/browse/MEXEC-6?page=comments#action_80877 ]
Jerome Lacoste commented on MEXEC-6:
I have updated your patch to match the trunk.
I would like the upgrade to be as smooth as possible. With regard to
compatibility, wi
Classcast Exception in Cobertura
net.sourceforge.cobertura.coveragedata.PackageData
---
Key: MCOBERTURA-53
URL: http://jira.codehaus.org/browse/MCOBERTURA-53
Project: Mav
11 matches
Mail list logo
