Resolving Gump/Maven Artefact Identifiers (MX4J)

["Adam R. B. Jack" <aj...@trysybase.com>]

I am trying to get Geronimo to build on Gump using Maven. The issues is
dependencies (MX4J and Velocity) and artefact identifiers. I'd like to
gather information to generate a repeatable process by which issues like
these can be easily resolved.

Looking at:


http://brutus.apache.org:8080/gump/incubator-geronimo/incubator-geronimo/index.html

I see these missing dependencies.

    mx4j-jmx-2.0.1.jar (try downloading from http://mx4j.sourceforge.net)
    velocity-dep-1.4-rc1.jar (try downloading from
http://jakarta.apache.org/velocity/)

For MX4J I look here (to see what Maven knows these jars by).
    http://www.ibiblio.org/maven/mx4j/jars/

and I see mx4j/jmx/remote/tools.

[BTW: Is there a better way to view Maven's artefact ids? Something like
this? http://brutus.apache.org:8080/gump/gump_xref/output_id_project.html]

However when I look at what the Gump MX4J build produces, I see:

    http://cvs.apache.org/viewcvs.cgi/gump/project/mx4j.xml?view=markup

    <jar name="lib/mx4j-jmx.jar" id="mjmx"/>
    <jar name="lib/mx4j-impl.jar" id="impl"/>
    <jar name="lib/mx4j.jar" id="mx4j"/>
    <jar name="lib/mx4j-rjmx.jar" id="rjmx"/>
    <jar name="lib/mx4j-rimpl.jar" id="rimpl"/>
    <jar name="lib/mx4j-remote.jar" id="mx4j-remote"/>

and:

    <jar name="lib/mx4j-tools.jar"/>

So we have some differences. (Any insights into what/why would be
appreciated.)

1) I've removed the id="" here (and will cleanup what fallout I can) 'cos
Gump defaults id equal to jar basename, and Maven artefact ids are typically
the jar basename (it seems).

2) I'm not sure what do to about "impl" nor the "r*" jars. I don't know if
they are needed for runtime. How ought we deal with such differences? How
does Maven cope with artefact id change & addition (which I assume will
happen? Has it happened?)

I'd like to try to examine this case & see if we can learn what has to be
done in general, in the hope of making it repeatable.

regards,

Adam
--
Experience the Unwired Enterprise:
http://www.sybase.com/unwiredenterprise
Try Sybase: http://www.try.sybase.com


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Resolving Gump/Maven Artefact Identifiers (MX4J)

["Adam R. B. Jack" <aj...@trysybase.com>]

> On Thu, 3 Jun 2004, Adam R. B. Jack <aj...@trysybase.com> wrote:
>
> > 1) I've removed the id="" here (and will cleanup what fallout I can)
> > 'cos Gump defaults id equal to jar basename,
>
> This is not entirely correct - and we either kill all "traditional
> Gumps" now or get into a maintainence nightmare if you want to rely on
> this.

Oops. Yeah, I've heard of that Gump. Darn, that is what I get for cutting
down on caffeine.

> "Traditional" and "Python" Gump behave differently in absence of an id
> attribute - for the short term you may want to stick with explicit
> ids.

Agreed.

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Resolving Gump/Maven Artefact Identifiers (MX4J)

[Stefan Bodewig <bo...@apache.org>]

On Thu, 3 Jun 2004, Adam R. B. Jack <aj...@trysybase.com> wrote:

> 1) I've removed the id="" here (and will cleanup what fallout I can)
> 'cos Gump defaults id equal to jar basename,

This is not entirely correct - and we either kill all "traditional
Gumps" now or get into a maintainence nightmare if you want to rely on
this.

"Traditional" and "Python" Gump behave differently in absence of an id
attribute - for the short term you may want to stick with explicit
ids.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org