Just for the record, I like having a "post-processed" module format.
I wouldn't mind if it had XML data instead of serialized objects, but
I am not really in favor of throwing it away and making a standard
("pre-processed") J2EE JAR+DD+deployment plan into our official module
format. So I'd rather find ways to make the CAR builds work right.
:)
But anyway, isn't there some way to get Maven to tell you why it's
chosen to download some particular module? It gives you that nice
little "dependency trace" when it fails to find something, but I would
hope there's some debug mode where it shows that for everything...
Thanks,
Aaron
On 10/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Ugh... well, I think there may be more problems... as I just started
to notice that builds of car modules downloads the deployed version
of the same module while building...
<snip>
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Geronimo Configs :: UDDI Jetty
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
...
[INFO] [car:package]
[INFO] Packaging module configuration: /home/gbuild/ws/server/configs/
uddi-jetty/target/plan/plan.xml
...
[INFO] snapshot org.apache.geronimo.configs:uddi-jetty:1.2-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.configs:uddi-jetty:1.2-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.configs:uddi-jetty:1.2-SNAPSHOT:
checking for updates from apache.snapshots
Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/
apache/geronimo/configs/uddi-jetty/1.2-SNAPSHOT/uddi-
jetty-1.2-20061027.030123-3.car
4403K downloaded
...
</snip>
This is really maddening...
The more I hack around CAR problems, the more that I find that CAR's
are just adding more and more extra unneeded complication to
Geronimo. In fact I believe that CAR are the reason why the G build
is so complicated... and convoluted.
At what point do we stop hacking around this and just toss CAR files
out the window?
Any simplicity we get from CARs when loading them in the server is
IMO completely negated by the complexity of the build required to
produce them.
I'd really love to see CARs go away... and leave in there place plain
xml files, which are easily editable and do not require and
additional build processing to massage them.
* * *
But, until then... anyone know why the build of a CAR is trying to
resolve itself as a dependency?
--jason
On Oct 28, 2006, at 2:17 PM, Jacek Laskowski wrote:
> On 10/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
>
>> But... in the meantime, I made a few changes which I think should
>> help reduce strange problems with SNAPSHOT resolution.
>
> Thanks Jason for your "passion" for conducting such a painstaking
> research and finally hunting it down. Much appreciated for such
> followers like me.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.jaceklaskowski.pl
