Hi guys,
The JBossIDE team is planning to do a release around the 20th.
This release will contain a alpha version of the toolset and plugins
that have been developed.
This release is dependent on code that was not present in Hibernate 3.0
beta,
so how do we handle this ?
The plugins will need th
Max Rydahl Andersen wrote:
Anyone objection to me just including a
hibernate3-.jar in this release
and document the fact mentioned above ?
Depends if we should have beta2 by this date or not. What are the open
and closed issues? We might almost be there.
--
Christian Bauer
+49 171 455 66 53
cal
So, does it make sense to do beta2 on the 20th?
It seems we've done a fair amount of work, but I'm not sure how much new
user-visible function we have.
Note that we would also need to do an alpha2 of the annotations package.
Max Rydahl Andersen wrote:
Hi guys,
The JBossIDE team is planning to do
Hi,
We are starting to use hibernate in
our applications, and I would like to know which is the best plugin for
hibernate in eclipse.
Some suggestion?
Thanks..
Leandro Silva Ferreira
Rigth now, the only way to map annotated classes is to
use the programmatic API
AnnotationConfiguration ac = new
AnnotationConfiguration();
ac.addPackage("my.package");
ac.addAnnotatedClass(MyClass.class);
...
Users ( and Max ;-) ) ask for declarative
configuration. The best way seems to enhance
We should sync the release dates, even if the features
on some packages are minors. It was a pain during the
hibernate-annotations release since I had to backport
some stuffs to make it work on beta1. It's easier/more
comfortable for users to play with released parts
rather than CVS snapshots.
-
On Wed, 12 Jan 2005 16:00:21 +0100 (CET), Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
Rigth now, the only way to map annotated classes is to
use the programmatic API
AnnotationConfiguration ac = new
AnnotationConfiguration();
ac.addPackage("my.package");
ac.addAnnotatedClass(MyClass.class);
...
Rigth now, the only way to map annotated classes is to
use the programmatic API
AnnotationConfiguration ac = new
AnnotationConfiguration();
ac.addPackage("my.package");
ac.addAnnotatedClass(MyClass.class);
...
Users ( and Max ;-) ) ask for declarative
configuration. The best way seems to enhance th
Max Rydahl Andersen wrote:
why not just:
To be consistent, see below.
-1 it breaks the actual semantic and prevents you from using cfg.xml on
annotated classes (you can switch afterall)
What does addPackage actually do ? Add package-level annotations such
as.. ?
Add package-info.class
It i
Oups, class and package are fine (I thought there were already a class
attribute in the current DTD).
Emmanuel Bernard wrote:
Max Rydahl Andersen wrote:
why not just:
To be consistent, see below.
-1 it breaks the actual semantic and prevents you from using cfg.xml
on annotated classes (yo
10 matches
Mail list logo
