Using Valang (startup and dependency problems) project, ejb, problems, central, website

amy

/nonav/repository)
Downloading: maven2/javax/...t-20060502.jar
[WARNING] Unable to get resource from repository central (maven2)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) javax.persistence:ejb:jar:3.0-public-draft-20060502
Try downloading the file manually from the project website.
Then, install it using the command:     mvn install:install-file -DgroupId=javax.persistence -DartifactId=ejb \         -Dversion=3.0-public-draft-20060502 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:       1) xxx:rmiapi:jar:1.4.0.0-SNAPSHOT       2) org.springmodules:spring-modules-validation:jar:0.6       3) org.hibernate:hibernate-annotations:jar:3.2.0.cr1       4) javax.persistence:ejb:jar:3.0-public-draft-20060502

How do I solve this issue?

I can make it compile by excluding javax.persistence:ejb, but I figure that it might not be a very good solution in the long run..

Also, our web application does not use  Spring or Acegi (yet) and we would like to limit the number of libraries used.
E.g. there is no reason (at least not to my knowledge) why Hibernate and Persistence is needed for validation...
Is it possible to cut down on the dependencies even more?

Regards,
Jimisola


Originally Posted by jimisolaMissing:
----------
1) javax.persistence:ejb:jar:3.0-public-draft-20060502

Hi,

the Persistence API dependency is a transitive one and in the IVY file seems to be disabled (even if this works only with IVY 1.4 or higher, if I'm not wrong).

I'll do the same with the POM file, hopefully tomorrow.

Cheers,

Sergio B.


Originally Posted by sbtouristHi,

the Persistence API dependency is a transitive one and in the IVY file seems to be disabled (even if this works only with IVY 1.4 or higher, if I'm not wrong).

I'll do the same with the POM file, hopefully tomorrow.

Cheers,

Sergio B.

Great. Thank you.

Is there actually an dependency on Hibernate as well? If not, I'd appreciate if that was excluded as well. Especially, since the Hibernate annotations causes some confusing as there are annotations for Hibernate and Valang and many of them with the same name (e.g. @Length).

Regards,
Jimisola


Originally Posted by jimisolaIs there actually an dependency on Hibernate as well? If not, I'd appreciate if that was excluded as well. Especially, since the Hibernate annotations causes some confusing as there are annotations for Hibernate and Valang and many of them with the same name (e.g. @Length).

I've set the Hibernate-Annotations dependency (and also OGNL and Joda-Time ones) as quot;providedquot;: this means that if you want to use it, you have to manually copy it in your lib dir.

The Hibernate-Annotations was the one causing transitive dependency towards EJB3 API and Hibernate, so that should solve the problem.

Just update to the 0.7 Spring Modules version and use the POM file in the CVS: s...dation/pom.xml

Let us know if everything is ok.

Thanks,
Cheers,

Sergio B.


Originally Posted by sbtouristJust update to the 0.7 Spring Modules version and use the POM file in the CVS: s...dation/pom.xml

Let us know if everything is ok.

Sergio,

What exactly do you mean by quot;update to the 0.7 Spring Modules version and use the POM file in the CVSquot;? Is 0.7 not deploy for usage by Maven? Perhaps not released at all?

If not, I would suggest that you deploy a SNAPSHOT/alfa/beta version that I can try instead.  We are are a team of developers and I don't want them to fiddle with 0.7 and a special POM.

Regards,
Jimisola


Originally Posted by jimisolaWhat exactly do you mean by quot;update to the 0.7 Spring Modules version and use the POM file in the CVSquot;? Is 0.7 not deploy for usage by Maven? Perhaps not released at all?

The 0.7 version has been released (node/388), but it is not in Maven2 repositories, yet.
So I mean just that: download the latest release and install in your maven repo theValidation module jar with the new POM checked out from the CVS.Originally Posted by jimisolaIf not, I would suggest that you deploy a SNAPSHOT/alfa/beta version that I can try instead.  We are are a team of developers and I don't want them to fiddle with 0.7 and a special POM.

I'm sorry, I understand your issue but at the moment we don't have an internal repository where to be able to deploy Maven2 bundles.
There's a somewhat related Jira issue: proj...browse/MOD-179
Vote for it and stay tuned

Cheers,

Sergio B.


Originally Posted by sbtouristThe 0.7 version has been released (node/388), but it is not in Maven2 repositories, yet.
So I mean just that: download the latest release and install in your maven repo theValidation module jar with the new POM checked out from the CVS.

Ok. I might wait for 0.7 to make it to the central repo then.
edit: How long do you think it will take for 0.7 to reach the central repo?Originally Posted by sbtouristI'm sorry, I understand your issue but at the moment we don't have an internal repository where to be able to deploy Maven2 bundles.
There's a somewhat related Jira issue: proj...browse/MOD-179
Vote for it and stay tuned

I've voted for it and also added minor comment. I'll add a new issue if it the original issue reporter or team developer feels that they're separate issues. I am very new to Spring and haven't gotten a clear view of it yet, but Spring and Spring Modules seem to hosted at different places. Who's responsible for the infrastructure of Spring Modules?

Regards,
Jimisola