collection.
Is JDK5 allowed in writing a plugin? If so, any idea what I might be doing
wrong?
--
Steve Ebersole
Hibernate Project Lead
http://hibernate.org
Principal Software Engineer
http://redhat.com
http://jboss.org
with a classpath similar to
src/main/test:src/main/java:../moduleA/src/main/test/:
I'd like some comments about if this is possible/desirable or not.
--
Steve Ebersole
Hibernate Project Lead
http://hibernate.org
Principal Software Engineer
http://redhat.com
http://jboss.org
really it just comes down to
personal choice. The usual (productive) middle ground between theory and
pragmatism in this realm is to use an in memory database (I actually prefer
H2 over HSQLDB)
--
Steve Ebersole
Hibernate Project Lead
http://hibernate.org
Principal Software Engineer
http
]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Steve Ebersole
Hibernate Project Lead
http://hibernate.org
Principal Software Engineer
http://redhat.com
http://jboss.org
this using a custom suite.
--
Steve Ebersole
Hibernate Project Lead
http://hibernate.org
Principal Software Engineer
http://redhat.com
http://jboss.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
I think you mean sp1, not spl
thats a 1 (one) ...
On Thursday 19 July 2007 08:57:14 pm Wayne Fay wrote:
As you can see here:
http://repo1.maven.org/maven2/hibernate/hibernate/
3.2.4.spl is not a valid hibernate version.
Where did you get this version number?
Wayne
On 7/19/07, pinky88
I am having a problem getting multi-module builds to work right.
All this stuff is publicly accessible, if someone was willing to take a look
and try to help me figure it out. There are a couple of piece of information
you'd need:
1) First, you'd need to define the jboss repo in addition to
Ahh, the moving modules into profiles approach is nice. Good thought.
Tim Kettler wrote:
Hi,
you have a few options to achieve what you want:
1.
I suppose you currently use the top level pom for two things:
subproject aggregation (modules/ tag) and the definition of default
values for you
Don't know if this is the correct answer, but I have the same issue
and here is how I plan on getting around it. Basically, split the top
poms into one for inheritance (used in the parent/ definition) and one
for reactor/aggregation (defining the modules/). This is based on the
observation
I asked this before, but I don't think I understood the problem well
enough to voice it properly nor had I sat down and implemented the
alternatives.
This is in regards to my DocBook plugin which works completely off the
Maven dependency mechanism. So every aspect of the DocBook
environment
Sure. The JBoss repo (http://repository.jboss.com/maven2/) does exactly
this. If the SVN repo is enabled for http access, then its no different
from accessing any other Maven repository.
Raphaël Piéroni wrote:
Hi,
i have googled for an answer on the question whether
it is possible to store
.
Btw, the docbkx project moved from agilejava.com to
http://code.google.com/p/docbkx-tools/
Cheers,
~t~
On 6/4/07, Steve Ebersole [EMAIL PROTECTED] wrote:
As part of migrating Hibernate to use Maven, one of the big issues I ran
into was the current state of DocBook plugins
Sure. What we do is we package the styles in a zip file using a
standard maven project and the build-helper-mojo from codehaus. The
zip file contains not only the CSS, the XSLT parameters but also the
images linked to the style.
Next, in a doc project, we depend on the zip above and we use
On Tue, 2007-06-05 at 09:18 +0200, Stephane Nicoll wrote:
I am currently migration our doc on docbook+M2 and I ran in the same
issues. Is your plugin freely available?
Sure, as of now it is in Hibernate SVN and published to the JBoss Maven repo.
Regarding styles, we also use them as
I wanted to throw a comment into this discussion...
Please keep in mind that this level of build reproducibility is not
*necessarily* a good thing. The particular issue I have with the
reproducibility is actually the testing side of it
(functional/integration testing). I would love to use
As part of migrating Hibernate to use Maven, one of the big issues I ran
into was the current state of DocBook plugins for Maven. The current
mojo-codehaus hosted plugin is insufficient. There is another more
widely used one done by one Wilfred Springer as part of something called
agilejava.
Mark and I already discussed this. But its a different discussion,
since he does not deal with pre-packaged styles...
On Mon, 2007-06-04 at 21:38 +0200, Max Rydahl Andersen wrote:
one thing is for sure, the current image location in our docbook is
annoying ;(
It is not relative to where
jdbc.version5.0.4/jdbc.version
jdbc.driverClassNamecom.mysql.jdbc.Driver/jdbc.driverClassName
/properties
/profile
On 23/05/07, Steve Ebersole [EMAIL PROTECTED] wrote:
I am looking to migrate Hibernate to use Maven for building. I am
I am looking to migrate Hibernate to use Maven for building. I am
currently running into a problem porting the Hibernate testsuite. The
Hibernate testsuite is mainly a bunch of functional and integration
tests and not really unit tests per-se. But it is built on top of
Junit.
Anyway, the
19 matches
Mail list logo
