On Jul 8, 2006, at 6:35 AM, anita kulshreshtha wrote:
inline..
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
If we don't use the <repository> in our assembly descriptor to copy
the modules from the local repo to geronimo repo, then we won't see
this problem of an invalid pom. Since installing the car will install
almost all of the modules into the geronimo repository for us,
Which modules did not get installed?
I haven't done a detailed search, but in principle the only jars we
ship that are not transitive dependencies of the installed
configurations (modules) are j2ee artifacts such as the tranql and
activemq rars that we ship as a convenience to those who wish to
deploy additional adapters.
thanks
david jencks
Thanks
Anita
we can
skip <repository> for now. Moreover, I have learnt that using the
<repository> to copy all modules into G repo was only a convenience
feature. It is not actually needed for the server to start.
So for now, we don't have to worry about moving to the latest apache
directory version. It doesn't affect our m2 migration work. But
eventually we will have to contend this issue and then we'll have to
map those 4 artifacts to their latest equivalents.
Thanx
Prasad
On 7/7/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Here's another idea. We could just fix the pom for
directory-protocols:ldap-protocol:0.9.2 and publish it to one of
our
repos. This will be a quick fix and we could get on with our
assembly
work. But we will be staying at whatever versions of the Apache
directory artifacts that we had in 1.1
I guess eventually we'll have to move to the latest version of
Apache
directory in our 1.2.
Cheers
Prasad
On 7/6/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Alex, Enrique,
The assembly of G in m2 is failing because we can't find valid
poms
for Apache directory artifacts. Our module geronimo-directory
depends
on apache directory artifacts. The Apache directory artifacts now
have
moved under the groupId "org.apache.directory"
http://www.ibiblio.org/maven2/org/apache/directory/
I have begun changing geronimo/directory/pom.xml to refelct the
new
groupId:artifactId of the Apache directory artifacts.
After those changes, the java code in geronimo-directory module
has to
be changed to reflect the new package names in the dependencies.
Below, you'll see an excerpt of the geronimo/directory/pom.xml
listing
the directory dependencies. I think I was able to map most of the
dependencies to the new groupId:artifactId. Please see comments
inline
and verify those.
I wasn't able to do so for the first 4 dependencies. Any help
there
would be appreciated.
<!-- unable to find a corresponding dependency in the new
groupdId:artifactId -->
<dependency>
<groupId>directory-asn1</groupId>
<artifactId>asn1-codec</artifactId>
<version>${asn1Version}</version>
</dependency>
<dependency>
<groupId>directory-asn1</groupId>
<artifactId>asn1-ber</artifactId>
<version>${asn1Version}</version>
</dependency>
<dependency>
<groupId>directory-asn1</groupId>
<artifactId>asn1-der</artifactId>
<version>${asn1Version}</version>
</dependency>
<dependency>
<groupId>directory-shared</groupId>
<artifactId>apache-ldapber-provider</artifactId>
<version>${apachedsVersion}</version>
</dependency>
<!-- mapped the following deps. Please verify --->
<dependency>
<groupId>org.apache.directory.server</groupId>
<artifactId>apacheds-core</artifactId>
<version>${apachedsVersion}</version>
</dependency>
<dependency>
<groupId>org.apache.directory.server</groupId>
<!-- artifactId>apacheds-shared</artifactId -->
<artifactId>apacheds-core-shared</artifactId>
<version>${apachedsVersion}</version>
</dependency>
<dependency>
<groupId>org.apache.directory.shared</groupId>
<!-- artifactId>ldap-common</artifactId -->
<artifactId>shared-ldap</artifactId>
<version>${apachedsVersion}</version>
</dependency>
<dependency>
<groupId>org.apache.directory.mina</groupId>
<!-- artifactId>mina</artifactId -->
<artifactId>mina-core</artifactId>
<version>${minaVersion}</version>
</dependency>
<dependency>
<groupId>org.apache.directory.server</groupId>
<!-- artifactId>kerberos-common</artifactId -->
<artifactId>apacheds-kerberos-shared</artifactId>
<version>${kerberosCommonVersion}</version>
</dependency>
<dependency>
<groupId>org.apache.directory.server</groupId>
<!-- artifactId>kerberos-protocol</artifactId -->
<artifactId>apacheds-protocol-kerberos</artifactId>
<version>${kerberosProtocolVersion}</version>
</dependency>
<dependency>
<groupId>org.apache.directory.server</groupId>
<!-- artifactId>ldap-protocol</artifactId -->
<artifactId>apacheds-protocol-ldap</artifactId>
<version>${ldapProtocolVersion}</version>
</dependency>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
