/openejb/geronimo-openejb/pom.xml
geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/main/
resources/META-INF/geronimo-dependency.xml
Modified: geronimo/server/trunk/plugins/openejb/geronimo-openejb/
pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/openejb
-d.xml file also get included (recursively).
I'm not longer sure this g-d.xml file is a wonderful idea. There
aren't that many of them and they seem to mostly cause confusion.
Yes, it's definitely confusing me :) Should we try to eliminating the
geronimo-dependency.xml files that we have right now
(recursively).
I'm not longer sure this g-d.xml file is a wonderful idea. There
aren't that many of them and they seem to mostly cause confusion.
Yes, it's definitely confusing me :) Should we try to eliminating the
geronimo-dependency.xml files that we have right now? I can take a
stab
=584194view=rev
Log:
openejb now needs commons-dbcp dependency (GERONIMO-3531)
Modified:
geronimo/server/trunk/modules/geronimo-openejb/src/main/
resources/META-INF/geronimo-dependency.xml
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk/modules/geronimo-openejb/src/main
-version.properties used for (in configs and in
2.0 assembly) ?
As noted above, to filter the maven repo to the versions specified in
the pom
2) what is the geronimo-dependency.xml used for ? (a handful of
modules contain it)
This is geronimo's transitive depenendency feature. When you
include a jar
is the geronimo-dependency.xml used for ? (a handful of
modules contain it)
Thanx
Prasad
On 10/12/07, Jarek Gawor [EMAIL PROTECTED] wrote:
Folks,
In trunk, I've noticed that dependencies specified in
geronimo-dependency.xml without an explicit version get resolved to an
incorrect version when
://svn.apache.org/viewvc?rev=584194view=rev
Log:
openejb now needs commons-dbcp dependency (GERONIMO-3531)
Modified:
geronimo/server/trunk/modules/geronimo-openejb/src/main/
resources/META-INF/geronimo-dependency.xml
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk
Folks,
In trunk, I've noticed that dependencies specified in
geronimo-dependency.xml without an explicit version get resolved to an
incorrect version when installed. For example, the root pom defines
geronimo-schema-j2ee_1.4 dependency with version 1.2. But in the final
javaee assembly only
-dependencies.xml, but these
principles should really be in a more accessible place than this jira
clean up geronimo-openejb geronimo-dependency.xml
-
Key: GERONIMO-2937
URL: https://issues.apache.org/jira/browse
clean up geronimo-openejb geronimo-dependency.xml
-
Key: GERONIMO-2937
URL: https://issues.apache.org/jira/browse/GERONIMO-2937
Project: Geronimo
Issue Type: Bug
Security Level: public
/geronimo-dependency.xml by AbstractRepository.getDependencies
--
Key: GERONIMO-2823
URL: https://issues.apache.org/jira/browse/GERONIMO-2823
class loader should not be searched for resource
META-INF/geronimo-dependency.xml by AbstractRepository.getDependencies
--
Key: GERONIMO-2823
META-INF/geronimo-dependency.xml by AbstractRepository.getDependencies
--
Key: GERONIMO-2823
URL: https://issues.apache.org/jira/browse
System class loader should not be searched for resource
META-INF/geronimo-dependency.xml by AbstractRepository.getDependencies
--
Key: GERONIMO-2823
loader should not be searched for resource
META-INF/geronimo-dependency.xml by AbstractRepository.getDependencies
--
Key: GERONIMO-2823
URL
Damour closed GERONIMO-2823.
---
Resolution: Fixed
Fix Version/s: 2.0-beta1
This is now fixed.
System class loader should not be searched for resource META-INF/
geronimo-dependency.xml by AbstractRepository.getDependencies
16 matches
Mail list logo
