On 6/16/05, Brett Porter [EMAIL PROTECTED] wrote:
This will be something I have to document as a known issue. I think you
are running the Maven 1.0.2 script (check your path) against the Maven
1.1 MAVEN_HOME.
Yes, you are right.
Thank you for answer.
- Brett
Konstantin Shaposhnikov wrote
On 6/15/05, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
Please test these. I will release tomorrow if all is well.
I can't start it (some XML parse problems).
I have tried both on JDK 1.4 and JDK 1.5
Plugin cache will be regenerated
javax.xml.parsers.FactoryConfigurationError: Provider
am not very familiar with classloaders.
Konstatin.
ERic
-Original Message-
From: Konstantin Shaposhnikov [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 24, 2004 12:23 AM
To: Maven Developers List
Subject: Re: Hibernate plugin use Ant task instead of custom integration
On 18:15 Wed 23 Jun , Eric Pugh wrote:
Argh... You were right about classloader hell.. I was able quite quickly
to swap it to use the Hibernate SchemaExportTask with a .properties file.
However, attempting to get the right mix of classpath's etc to get
SchemaExportTask to work with
for
that?
As for xdoc/changes.xml file, what developer should I
specify in the action tag (dev attribute)?
Best regards,
Konstantin
On 22:31 Sat 29 Nov , Jason van Zyl wrote:
On Sat, 2003-11-29 at 18:59, Konstantin Shaposhnikov wrote:
Hello all,
I've created small patch for maven-hibernate
Hello all,
I've created small patch for maven-hibernate-plugin. It adds
delimiter property to the schema-export jelly tag.
This change required using newer version of the hibernate,
so I've change hibernate version used by plugin to 2.0.3.
Best regards,
Konstantin
? .classpath
? .project
Index:
Hi all.
What about placing this file in ${user.home}/.maven/ directory by
default and use ${user.home}/build.properties only if previous file
(${user.home}/.maven/build.properties) not found?
build.properties is only configuration file that is not hidden in my
linux home directory (i.e.
