3:32 p.m.
Hi,
I thought it might be interesting to know that the trunk of the two
projects Annotations and EntityManager (including commons-annotations)
have moved into Core. The new svn url is
https://svn.jboss.org/repos/hibernate/core/trunk.
As part of the move the build switched as well from Ant to Maven. All
tests are working again and you can build the documentation via:
mvn clean package -P hsqldb,doc
The documentation build is a temporary solution. In the long run we are
aiming to combine the different documentations into one single
documentation,
but that's will take a while to happen. There is quite some editing to be
done.
There is also more work required in order to include Annotations and
EntityManager into the distribution package. The 'old' distribution
packages for Annoations and EntityManager cannot be build anymore.
In case you want to work on any of these projects it is probably time to
switch to a Core checkout.
--Hardy
P.S. Almost forgot - the import of Envers into Core is also in full swing.
So a lot is happening.
11:31 p.m.
Cool
On the other hand now I have to suffer Maven. So not so cool.
Here were the tasks I had access to that mattered to me
- clean
- runt the test suite
- check the log files from the test suite
- build the distro
- compile
- compile tests
- deploy to my local repo to test a to be released distribution
What are their new equivalent?
Also for EM, how do I built the test jars and pars to test them in my
IDE.
We also need to get the JPA javadoc in the distro.
Emmanuel
On Nov 3, 2008, at 15:32, Hardy Ferentschik wrote:
Hi,
I thought it might be interesting to know that the trunk of the two
projects Annotations and EntityManager (including commons-annotations)
have moved into Core. The new svn url is https://svn.jboss.org/repos/hibernate/core/trunk
.
As part of the move the build switched as well from Ant to Maven.
All tests are working again and you can build the documentation via:
mvn clean package -P hsqldb,doc
The documentation build is a temporary solution. In the long run we
are aiming to combine the different documentations into one single
documentation,
but that's will take a while to happen. There is quite some editing
to be done.
There is also more work required in order to include Annotations and
EntityManager into the distribution package. The 'old' distribution
packages for Annoations and EntityManager cannot be build anymore.
In case you want to work on any of these projects it is probably
time to switch to a Core checkout.
--Hardy
P.S. Almost forgot - the import of Envers into Core is also in full
swing. So a lot is happening.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
4:37 a.m.
On Tue, 04 Nov 2008 05:31:52 +0100, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
On the other hand now I have to suffer Maven. So not so cool.
:)
- clean
mvn clean
- runt the test suite
mvn test
mvn test -Dtest=MyTest (to run single test)
mvn install -DskipTests (tests will actually run per default, but can
be skipped)
- check the log files from the test suite
the log files
are under target/surefire-reports. Per test there are
three files
* org.hibernate.*.MyTest.txt - the actual junit report
* org.hibernate.*.MyTest-output.txt - the standard out log
* TEST-org.hibernate.*.MyTest-output.xml - the xml formatted Junit
report
- build the distro
Not sure about this one. There is a
distribution module in Core, but I
haven't used it yet.
I don't know what is still required to get Annotations and
EntityManager into this
distribution. The old dist packages are currently not available, even
though it would
be straight forward to build them. We could use a similar approach I
took in
hibernate-validator-legacy. However, if I understood Steve correctly
there won't be
any standalone releases of Annotations and EntityManager anymore.
Maybe we should discuss our plans in this regards a little more.
- compile
mvn compile
- compile tests
mvn test-compile
- deploy to my local repo to test a to be released distribution
mvn install
See also
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle...
for other available goals.
Also for EM, how do I built the test jars and pars to test them in my
IDE.
For this custom tests we are still using ant via the maven-antrun plugin.
In fact the code to generate these packages
is pretty much unchanged. The jars/pars get automatically build when you
run the tests. You can run:
mvn process-test-classes
to build just these artifacts.
We also need to get the JPA javadoc in the distro.
This goes
really together with the overall distribution discussion.
--Hardy
4:23 a.m.
----- "Emmanuel Bernard" <emmanuel(a)hibernate.org> escreveu:
Cool
On the other hand now I have to suffer Maven. So not so cool.
By the way, are we considering, even remotely, moving away from Maven? I mean, this is
probably not feasible in short term, but there are good options today that are worth an
evaluation.
- Juca.
5:07 a.m.
On Wed, 05 Nov 2008 10:23:00 +0100, Juraci Costa <jcosta(a)redhat.com> wrote:
----- "Emmanuel Bernard" <emmanuel(a)hibernate.org>
escreveu:
> Cool
> On the other hand now I have to suffer Maven. So not so cool.
By the way, are we considering, even remotely, moving away from Maven? I
mean, this is probably not feasible in short term, but there are good
options today that are worth an evaluation.
I don't think that a move from maven is on the table right now. For that it
just took too much effort to actually get there.
Personally, I doubt that there will ever be a built tool which will make
everyone
happy. There are as many opinions as tools. I think for now we have to
make the best
of what we have.
Knowing that I might open pandora's box now - what alternatives are you
talking about?
I assume you are not referring to ant/ivy.
--Hardy
5649
days inactive
5651
days old
4 comments
3 participants
participants (3)
-
Emmanuel Bernard -
Hardy Ferentschik -
Juraci Costa