validator
lib (empty)
compile depends on jpa-api, commons-annotations, core
compiletest depends on annotations //DDL integration, will depend on
jpa //JPA integration
annotations
lib (empty)
compile depends on jpa-api, validator, commons-annotations, core
//want to add a
Same cycle exists for search and annotations.
Alternative workaround for me is to remove the test's from the classpath
(but that's even worse)
/max
validator
lib (empty)
compile depends on jpa-api, commons-annotations, core
compiletest depends on annotations //DDL integration,
It actually works perfectly with ant. IntelliJ works nice to with
cross module dependency. Doesn't eclipse support cross module
dependencies?
On 15 févr. 07, at 06:33, Max Rydahl Andersen wrote:
validator
lib (empty)
compile depends on jpa-api, commons-annotations, core
It actually works perfectly with ant.
Well sure - here you don't specify the project dependencies. You specify
the dependencies
for each compile.
IntelliJ works nice to with cross module dependency. Doesn't eclipse
support cross module dependencies?
It supports project dependencies;
On 15 févr. 07, at 09:47, Max Rydahl Andersen wrote:
It actually works perfectly with ant.
Well sure - here you don't specify the project dependencies. You
specify the dependencies
for each compile.
IntelliJ works nice to with cross module dependency. Doesn't
eclipse support cross
IntelliJ works nice to with cross module dependency. Doesn't eclipse
support cross module dependencies?
It supports project dependencies; but not cyclic ones. (I don't know of
any IDE that
supports that (without having to build the annotations.jar by hand and
then not let the project
be
With the help of Paolo on commons-annotations refactoring, I came up
with a decent prototype, here is the structure
jpa-api
lib (empty)
compile depends on nothing
compiletest depends on nothing
commons-annotations
lib (empty)
compile depends on commons logging, log4j
compiletest
I plan to apply that sometimes this week (tomorrow hopefully). Once I'm
done we'll be able to think about the website changes.
Comments welcome before I commit that work.
you keep these things in hibernateext, correct ?
..and how much do i need to do to have the same dependency check for
yes
round 10 lines of ant script in your build.xml file. here is my
comment on that
!-- To add a dependency:
defines the dependency.jar property that points to the expected
jar file
in init, add an available dependency.jar and populate
dependency.jar.available
create a target
