You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by anita kulshreshtha <a_...@yahoo.com> on 2007/01/26 17:03:19 UTC
Openejb question
This is a fragment from openejb3/server's pom.xml. Could someone
please explain how this works?
Thanks
Anita
................................................................
<dependencies>
<!--
This dependency is here to ensure that absolutely nothing
under the container module section can be dependent on any
server modules.
-->
<dependency>
<groupId>org.apache.openejb</groupId>
<artifactId>container</artifactId>
<version>${pom.version}</version>
<type>pom</type>
<scope>compile</scope>
</dependency>
</dependencies>
____________________________________________________________________________________
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html
Re: Openejb question
Posted by Kevan Miller <ke...@gmail.com>.
On Jan 26, 2007, at 1:47 PM, David Jencks wrote:
> so whats the stacktrace with -X? is this geronimo or maven
> complaining? Is this pom in your local repo? If so is it
> timestamped or -SNAPSHOT?
>
> Maybe... just maybe.... we're getting closer :-)
>
Sorry, was on my way out the door...
This error seems to be just Maven. Here's the failure info w/ -X:
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT
Path to dependency:
1) org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
2) org.apache.openejb:openejb-ejbd:jar:3.0-incubating-SNAPSHOT
3) org.apache.openejb:container:pom:3.0-
incubating-20070126.103431-20
----------
1 required artifact is missing.
for artifact:
org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-
repository),
codehaus (http://repository.codehaus.org),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-
repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-
repository/),
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
NOTE: Maven is executing in offline mode. Any artifacts not already
in your local
repository will be inaccessible.
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
----------
1) org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT
Path to dependency:
1) org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
2) org.apache.openejb:openejb-ejbd:jar:3.0-incubating-SNAPSHOT
3) org.apache.openejb:container:pom:3.0-
incubating-20070126.103431-20
----------
1 required artifact is missing.
for artifact:
org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-
repository),
codehaus (http://repository.codehaus.org),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-
repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-
repository/),
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:551)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: M
issing:
----------
1) org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT
Path to dependency:
1) org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
2) org.apache.openejb:openejb-ejbd:jar:3.0-incubating-SNAPSHOT
3) org.apache.openejb:container:pom:3.0-
incubating-20070126.103431-20
----------
1 required artifact is missing.
for artifact:
org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-
repository),
codehaus (http://repository.codehaus.org),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-
repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-
repository/),
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
tively(DefaultArtifactResolver.java:244)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
tively(DefaultArtifactResolver.java:211)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
tively(DefaultArtifactResolver.java:182)
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependenci
es(DefaultPluginManager.java:1117)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:366)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:534)
... 16 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 30 seconds
[INFO] Finished at: Fri Jan 26 14:07:38 EST 2007
[INFO] Final Memory: 19M/35M
[INFO]
------------------------------------------------------------------------
Re: Openejb question
Posted by David Jencks <da...@yahoo.com>.
Now I've updated the openejb poms and attempted to deploy an openejb
snapshot.
The openejb deploy breaks when it gets to the samples but this is
apparently expected and means the deploy succeeded.
thanks
david jencks
On Jan 26, 2007, at 3:53 PM, David Jencks wrote:
> I've opened http://jira.codehaus.org/browse/MNG-2796 to describe my
> understanding of what's going on.
>
> There are at least 7 other maven issues that describe similar
> problems. I'd appreciate it if everyone affected by this problem
> could vote on this issue and maybe add comments.
>
> Now I'll work on updating the openejb poms.
>
> thanks
> david jencks
>
> On Jan 26, 2007, at 2:54 PM, David Jencks wrote:
>
>> Anita figured out that replacing ${pom.version} with 3.0-
>> incubating-SNAPSHOT in openejb server pom fixes this problem. It
>> turns out that jason dillon previously ran into this problem in
>> geronimo and replaced all ${pom.version} in our poms with our own
>> defined variable ${version}.
>>
>> I'm investigating maven jira to make this problem better known and
>> will update the openejb poms with the same workaround (${version}
>> not ${pom.version})
>>
>> thanks!
>>
>> david jencks
>>
>> On Jan 26, 2007, at 11:50 AM, Kevan Miller wrote:
>>
>>>
>>> Here's what seems to be the relevant section from the -X trace:
>>>
>>> [DEBUG] Artifact not found - using stub model: System is offline.
>>>
>>> org.apache.openejb:container:pom:3.0-incubating-20070126.103431-20
>>>
>>>
>>> [DEBUG] Using defaults for missing POM
>>> org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT:compile
>>> [DEBUG] org.apache.openejb:container:pom:3.0-
>>> incubating-20070126.103431-20:compile (selected for compile)
>>> [DEBUG] org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:
>>> 1.0-M1:compile (removed - nearer found: 1.0)
>>> [DEBUG] org.apache.openejb:container:pom:3.0-
>>> incubating-20070126.103431-20:compile (selected for compile)
>>>
>>>
>>> And here's the contents of the relevant directories in my repo:
>>>
>>>
>>> /Users/kevan/.m2/repository/org/apache/openejb/container/3.0-
>>> incubating-SNAPSHOT:
>>> total used in directory 80 available 3125712
>>> -rw-r--r-- 1 kevan kevan 371 Jan 26 14:07 maven-metadata-
>>> apache-snapshots.xml
>>> -rw-r--r-- 1 kevan kevan 405 Jan 26 14:07 maven-metadata-
>>> apache.snapshots.xml
>>> -rw-r--r-- 1 kevan kevan 182 Jan 26 14:07 maven-metadata-
>>> codehaus-snapshots.xml
>>> drwxr-xr-x 12 kevan kevan 408 Jan 26 12:36 .
>>> -rw-r--r-- 1 kevan kevan 1521 Jan 26 12:36 container-3.0-
>>> incubating-20070126.103431-21.pom
>>> -rw-r--r-- 1 kevan kevan 1521 Jan 26 12:35 container-3.0-
>>> incubating-SNAPSHOT.pom
>>> drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
>>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 container-3.0-
>>> incubating-20070126.103431-21.pom.sha1
>>> -rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
>>> incubating-20070126.103431-21.pom~
>>> -rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
>>> incubating-SNAPSHOT.pom~
>>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>>> apache-snapshots.xml.sha1
>>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>>> apache.snapshots.xml.sha1
>>>
>>> /Users/kevan/.m2/repository/org/apache/openejb/server/3.0-
>>> incubating-SNAPSHOT:
>>> total used in directory 80 available 3127440
>>> -rw-r--r-- 1 kevan kevan 368 Jan 26 12:38 maven-metadata-
>>> apache-snapshots.xml
>>> -rw-r--r-- 1 kevan kevan 402 Jan 26 12:38 maven-metadata-
>>> apache.snapshots.xml
>>> -rw-r--r-- 1 kevan kevan 179 Jan 26 12:38 maven-metadata-
>>> codehaus-snapshots.xml
>>> drwxr-xr-x 12 kevan kevan 408 Jan 26 12:30 .
>>> -rw-r--r-- 1 kevan kevan 2281 Jan 26 12:30 server-3.0-
>>> incubating-SNAPSHOT.pom
>>> -rw-r--r-- 1 kevan kevan 2281 Jan 26 12:29 server-3.0-
>>> incubating-20070126.103431-20.pom
>>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>>> apache.snapshots.xml.sha1
>>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 server-3.0-
>>> incubating-20070126.103431-20.pom.sha1
>>> -rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
>>> incubating-20070126.103431-20.pom~
>>> -rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
>>> incubating-SNAPSHOT.pom~
>>> drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
>>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>>> apache-snapshots.xml.sha1
>>>
>>> Ignore the *~ backup filesgenerated emacs files...
>>>
>>> Changing the dependencies in the SNAPSHOT and dated pom to the
>>> following fixes the problem. I can only guess that Geronimo is
>>> closing some loop that doesn't exist for pure OpenEJB...
>>>
>>> <dependencies>
>>> <!--
>>> This dependency is here to ensure that absolutely nothing
>>> under the container module section can be dependent on any
>>> server modules.
>>> -->
>>> <!-- <dependency> -->
>>> <!-- <groupId>org.apache.openejb</groupId> -->
>>> <!-- <artifactId>container</artifactId> -->
>>> <!-- <version>${pom.version}</version> -->
>>> <!-- <type>pom</type> -->
>>> <!-- <scope>compile</scope> -->
>>> <!-- </dependency> -->
>>> </dependencies>
>>>
>>> --kevan
>>>
>>>
>>>
>>
>
Re: Openejb question
Posted by David Jencks <da...@yahoo.com>.
I've opened http://jira.codehaus.org/browse/MNG-2796 to describe my
understanding of what's going on.
There are at least 7 other maven issues that describe similar
problems. I'd appreciate it if everyone affected by this problem
could vote on this issue and maybe add comments.
Now I'll work on updating the openejb poms.
thanks
david jencks
On Jan 26, 2007, at 2:54 PM, David Jencks wrote:
> Anita figured out that replacing ${pom.version} with 3.0-incubating-
> SNAPSHOT in openejb server pom fixes this problem. It turns out
> that jason dillon previously ran into this problem in geronimo and
> replaced all ${pom.version} in our poms with our own defined
> variable ${version}.
>
> I'm investigating maven jira to make this problem better known and
> will update the openejb poms with the same workaround (${version}
> not ${pom.version})
>
> thanks!
>
> david jencks
>
> On Jan 26, 2007, at 11:50 AM, Kevan Miller wrote:
>
>>
>> Here's what seems to be the relevant section from the -X trace:
>>
>> [DEBUG] Artifact not found - using stub model: System is offline.
>>
>> org.apache.openejb:container:pom:3.0-incubating-20070126.103431-20
>>
>>
>> [DEBUG] Using defaults for missing POM
>> org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT:compile
>> [DEBUG] org.apache.openejb:container:pom:3.0-
>> incubating-20070126.103431-20:compile (selected for compile)
>> [DEBUG] org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:
>> 1.0-M1:compile (removed - nearer found: 1.0)
>> [DEBUG] org.apache.openejb:container:pom:3.0-
>> incubating-20070126.103431-20:compile (selected for compile)
>>
>>
>> And here's the contents of the relevant directories in my repo:
>>
>>
>> /Users/kevan/.m2/repository/org/apache/openejb/container/3.0-
>> incubating-SNAPSHOT:
>> total used in directory 80 available 3125712
>> -rw-r--r-- 1 kevan kevan 371 Jan 26 14:07 maven-metadata-
>> apache-snapshots.xml
>> -rw-r--r-- 1 kevan kevan 405 Jan 26 14:07 maven-metadata-
>> apache.snapshots.xml
>> -rw-r--r-- 1 kevan kevan 182 Jan 26 14:07 maven-metadata-
>> codehaus-snapshots.xml
>> drwxr-xr-x 12 kevan kevan 408 Jan 26 12:36 .
>> -rw-r--r-- 1 kevan kevan 1521 Jan 26 12:36 container-3.0-
>> incubating-20070126.103431-21.pom
>> -rw-r--r-- 1 kevan kevan 1521 Jan 26 12:35 container-3.0-
>> incubating-SNAPSHOT.pom
>> drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 container-3.0-
>> incubating-20070126.103431-21.pom.sha1
>> -rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
>> incubating-20070126.103431-21.pom~
>> -rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
>> incubating-SNAPSHOT.pom~
>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>> apache-snapshots.xml.sha1
>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>> apache.snapshots.xml.sha1
>>
>> /Users/kevan/.m2/repository/org/apache/openejb/server/3.0-
>> incubating-SNAPSHOT:
>> total used in directory 80 available 3127440
>> -rw-r--r-- 1 kevan kevan 368 Jan 26 12:38 maven-metadata-
>> apache-snapshots.xml
>> -rw-r--r-- 1 kevan kevan 402 Jan 26 12:38 maven-metadata-
>> apache.snapshots.xml
>> -rw-r--r-- 1 kevan kevan 179 Jan 26 12:38 maven-metadata-
>> codehaus-snapshots.xml
>> drwxr-xr-x 12 kevan kevan 408 Jan 26 12:30 .
>> -rw-r--r-- 1 kevan kevan 2281 Jan 26 12:30 server-3.0-
>> incubating-SNAPSHOT.pom
>> -rw-r--r-- 1 kevan kevan 2281 Jan 26 12:29 server-3.0-
>> incubating-20070126.103431-20.pom
>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>> apache.snapshots.xml.sha1
>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 server-3.0-
>> incubating-20070126.103431-20.pom.sha1
>> -rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
>> incubating-20070126.103431-20.pom~
>> -rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
>> incubating-SNAPSHOT.pom~
>> drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
>> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
>> apache-snapshots.xml.sha1
>>
>> Ignore the *~ backup filesgenerated emacs files...
>>
>> Changing the dependencies in the SNAPSHOT and dated pom to the
>> following fixes the problem. I can only guess that Geronimo is
>> closing some loop that doesn't exist for pure OpenEJB...
>>
>> <dependencies>
>> <!--
>> This dependency is here to ensure that absolutely nothing
>> under the container module section can be dependent on any
>> server modules.
>> -->
>> <!-- <dependency> -->
>> <!-- <groupId>org.apache.openejb</groupId> -->
>> <!-- <artifactId>container</artifactId> -->
>> <!-- <version>${pom.version}</version> -->
>> <!-- <type>pom</type> -->
>> <!-- <scope>compile</scope> -->
>> <!-- </dependency> -->
>> </dependencies>
>>
>> --kevan
>>
>>
>>
>
Re: Openejb question
Posted by David Jencks <da...@yahoo.com>.
Anita figured out that replacing ${pom.version} with 3.0-incubating-
SNAPSHOT in openejb server pom fixes this problem. It turns out that
jason dillon previously ran into this problem in geronimo and
replaced all ${pom.version} in our poms with our own defined variable
${version}.
I'm investigating maven jira to make this problem better known and
will update the openejb poms with the same workaround (${version} not
${pom.version})
thanks!
david jencks
On Jan 26, 2007, at 11:50 AM, Kevan Miller wrote:
>
> Here's what seems to be the relevant section from the -X trace:
>
> [DEBUG] Artifact not found - using stub model: System is offline.
>
> org.apache.openejb:container:pom:3.0-incubating-20070126.103431-20
>
>
> [DEBUG] Using defaults for missing POM
> org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT:compile
> [DEBUG] org.apache.openejb:container:pom:3.0-
> incubating-20070126.103431-20:compile (selected for compile)
> [DEBUG] org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:1.0-
> M1:compile (removed - nearer found: 1.0)
> [DEBUG] org.apache.openejb:container:pom:3.0-
> incubating-20070126.103431-20:compile (selected for compile)
>
>
> And here's the contents of the relevant directories in my repo:
>
>
> /Users/kevan/.m2/repository/org/apache/openejb/container/3.0-
> incubating-SNAPSHOT:
> total used in directory 80 available 3125712
> -rw-r--r-- 1 kevan kevan 371 Jan 26 14:07 maven-metadata-
> apache-snapshots.xml
> -rw-r--r-- 1 kevan kevan 405 Jan 26 14:07 maven-metadata-
> apache.snapshots.xml
> -rw-r--r-- 1 kevan kevan 182 Jan 26 14:07 maven-metadata-
> codehaus-snapshots.xml
> drwxr-xr-x 12 kevan kevan 408 Jan 26 12:36 .
> -rw-r--r-- 1 kevan kevan 1521 Jan 26 12:36 container-3.0-
> incubating-20070126.103431-21.pom
> -rw-r--r-- 1 kevan kevan 1521 Jan 26 12:35 container-3.0-
> incubating-SNAPSHOT.pom
> drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 container-3.0-
> incubating-20070126.103431-21.pom.sha1
> -rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
> incubating-20070126.103431-21.pom~
> -rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
> incubating-SNAPSHOT.pom~
> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
> apache-snapshots.xml.sha1
> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
> apache.snapshots.xml.sha1
>
> /Users/kevan/.m2/repository/org/apache/openejb/server/3.0-
> incubating-SNAPSHOT:
> total used in directory 80 available 3127440
> -rw-r--r-- 1 kevan kevan 368 Jan 26 12:38 maven-metadata-
> apache-snapshots.xml
> -rw-r--r-- 1 kevan kevan 402 Jan 26 12:38 maven-metadata-
> apache.snapshots.xml
> -rw-r--r-- 1 kevan kevan 179 Jan 26 12:38 maven-metadata-
> codehaus-snapshots.xml
> drwxr-xr-x 12 kevan kevan 408 Jan 26 12:30 .
> -rw-r--r-- 1 kevan kevan 2281 Jan 26 12:30 server-3.0-
> incubating-SNAPSHOT.pom
> -rw-r--r-- 1 kevan kevan 2281 Jan 26 12:29 server-3.0-
> incubating-20070126.103431-20.pom
> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
> apache.snapshots.xml.sha1
> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 server-3.0-
> incubating-20070126.103431-20.pom.sha1
> -rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
> incubating-20070126.103431-20.pom~
> -rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
> incubating-SNAPSHOT.pom~
> drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
> -rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
> apache-snapshots.xml.sha1
>
> Ignore the *~ backup filesgenerated emacs files...
>
> Changing the dependencies in the SNAPSHOT and dated pom to the
> following fixes the problem. I can only guess that Geronimo is
> closing some loop that doesn't exist for pure OpenEJB...
>
> <dependencies>
> <!--
> This dependency is here to ensure that absolutely nothing
> under the container module section can be dependent on any
> server modules.
> -->
> <!-- <dependency> -->
> <!-- <groupId>org.apache.openejb</groupId> -->
> <!-- <artifactId>container</artifactId> -->
> <!-- <version>${pom.version}</version> -->
> <!-- <type>pom</type> -->
> <!-- <scope>compile</scope> -->
> <!-- </dependency> -->
> </dependencies>
>
> --kevan
>
>
>
Re: Openejb question
Posted by Kevan Miller <ke...@gmail.com>.
Here's what seems to be the relevant section from the -X trace:
[DEBUG] Artifact not found - using stub model: System is offline.
org.apache.openejb:container:pom:3.0-incubating-20070126.103431-20
[DEBUG] Using defaults for missing POM
org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT:compile
[DEBUG] org.apache.openejb:container:pom:3.0-
incubating-20070126.103431-20:compile (selected for compile)
[DEBUG] org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar:1.0-
M1:compile (removed - nearer found: 1.0)
[DEBUG] org.apache.openejb:container:pom:3.0-
incubating-20070126.103431-20:compile (selected for compile)
And here's the contents of the relevant directories in my repo:
/Users/kevan/.m2/repository/org/apache/openejb/container/3.0-
incubating-SNAPSHOT:
total used in directory 80 available 3125712
-rw-r--r-- 1 kevan kevan 371 Jan 26 14:07 maven-metadata-
apache-snapshots.xml
-rw-r--r-- 1 kevan kevan 405 Jan 26 14:07 maven-metadata-
apache.snapshots.xml
-rw-r--r-- 1 kevan kevan 182 Jan 26 14:07 maven-metadata-
codehaus-snapshots.xml
drwxr-xr-x 12 kevan kevan 408 Jan 26 12:36 .
-rw-r--r-- 1 kevan kevan 1521 Jan 26 12:36 container-3.0-
incubating-20070126.103431-21.pom
-rw-r--r-- 1 kevan kevan 1521 Jan 26 12:35 container-3.0-
incubating-SNAPSHOT.pom
drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
-rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 container-3.0-
incubating-20070126.103431-21.pom.sha1
-rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
incubating-20070126.103431-21.pom~
-rw-r--r-- 1 kevan kevan 1557 Jan 26 12:15 container-3.0-
incubating-SNAPSHOT.pom~
-rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
apache-snapshots.xml.sha1
-rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
apache.snapshots.xml.sha1
/Users/kevan/.m2/repository/org/apache/openejb/server/3.0-
incubating-SNAPSHOT:
total used in directory 80 available 3127440
-rw-r--r-- 1 kevan kevan 368 Jan 26 12:38 maven-metadata-
apache-snapshots.xml
-rw-r--r-- 1 kevan kevan 402 Jan 26 12:38 maven-metadata-
apache.snapshots.xml
-rw-r--r-- 1 kevan kevan 179 Jan 26 12:38 maven-metadata-
codehaus-snapshots.xml
drwxr-xr-x 12 kevan kevan 408 Jan 26 12:30 .
-rw-r--r-- 1 kevan kevan 2281 Jan 26 12:30 server-3.0-
incubating-SNAPSHOT.pom
-rw-r--r-- 1 kevan kevan 2281 Jan 26 12:29 server-3.0-
incubating-20070126.103431-20.pom
-rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
apache.snapshots.xml.sha1
-rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 server-3.0-
incubating-20070126.103431-20.pom.sha1
-rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
incubating-20070126.103431-20.pom~
-rw-r--r-- 1 kevan kevan 2276 Jan 26 12:15 server-3.0-
incubating-SNAPSHOT.pom~
drwxr-xr-x 3 kevan kevan 102 Jan 26 12:15 ..
-rw-r--r-- 1 kevan kevan 40 Jan 26 12:15 maven-metadata-
apache-snapshots.xml.sha1
Ignore the *~ backup filesgenerated emacs files...
Changing the dependencies in the SNAPSHOT and dated pom to the
following fixes the problem. I can only guess that Geronimo is
closing some loop that doesn't exist for pure OpenEJB...
<dependencies>
<!--
This dependency is here to ensure that absolutely nothing
under the container module section can be dependent on any
server modules.
-->
<!-- <dependency> -->
<!-- <groupId>org.apache.openejb</groupId> -->
<!-- <artifactId>container</artifactId> -->
<!-- <version>${pom.version}</version> -->
<!-- <type>pom</type> -->
<!-- <scope>compile</scope> -->
<!-- </dependency> -->
</dependencies>
--kevan
Re: Openejb question
Posted by David Jencks <da...@yahoo.com>.
so whats the stacktrace with -X? is this geronimo or maven
complaining? Is this pom in your local repo? If so is it timestamped
or -SNAPSHOT?
Maybe... just maybe.... we're getting closer :-)
thanks
david jencks
On Jan 26, 2007, at 9:56 AM, Kevan Miller wrote:
>
> On Jan 26, 2007, at 11:45 AM, David Jencks wrote:
>
>>
>> On Jan 26, 2007, at 8:03 AM, anita kulshreshtha wrote:
>>
>>> This is a fragment from openejb3/server's pom.xml. Could someone
>>> please explain how this works?
>>
>>
>> I haven't investigate thoroughly, but I believe that this is an
>> easy way to make sure that if any container module references any
>> server module as a dependency you will get a circular dependency
>> and maven will refuse to build.
>>
>
> Anita,
> Interesting. If I remove that dependency from the pom in my local
> repo, I can build modules/geronimo-openejb with mvn -o. With the
> dependency, I get the following error:
>
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT
> Path to dependency:
> 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
> 2) org.apache.openejb:openejb-ejbd:jar:3.0-incubating-SNAPSHOT
> 3) org.apache.openejb:container:pom:3.0-
> incubating-20070126.103431-20
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
>
> --kevan
>
>>
>>>
>>> Thanks
>>> Anita
>>> ................................................................
>>> <dependencies>
>>> <!--
>>> This dependency is here to ensure that absolutely nothing
>>> under the container module section can be dependent on any
>>> server modules.
>>> -->
>>> <dependency>
>>> <groupId>org.apache.openejb</groupId>
>>> <artifactId>container</artifactId>
>>> <version>${pom.version}</version>
>>> <type>pom</type>
>>> <scope>compile</scope>
>>> </dependency>
>>> </dependencies>
>
>
Re: Openejb question
Posted by Kevan Miller <ke...@gmail.com>.
On Jan 26, 2007, at 11:45 AM, David Jencks wrote:
>
> On Jan 26, 2007, at 8:03 AM, anita kulshreshtha wrote:
>
>> This is a fragment from openejb3/server's pom.xml. Could someone
>> please explain how this works?
>
>
> I haven't investigate thoroughly, but I believe that this is an
> easy way to make sure that if any container module references any
> server module as a dependency you will get a circular dependency
> and maven will refuse to build.
>
Anita,
Interesting. If I remove that dependency from the pom in my local
repo, I can build modules/geronimo-openejb with mvn -o. With the
dependency, I get the following error:
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.openejb:container:pom:3.0-incubating-SNAPSHOT
Path to dependency:
1) org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
2) org.apache.openejb:openejb-ejbd:jar:3.0-incubating-SNAPSHOT
3) org.apache.openejb:container:pom:3.0-
incubating-20070126.103431-20
----------
1 required artifact is missing.
for artifact:
org.apache.geronimo.modules:geronimo-openejb:jar:2.0-SNAPSHOT
--kevan
>
>>
>> Thanks
>> Anita
>> ................................................................
>> <dependencies>
>> <!--
>> This dependency is here to ensure that absolutely nothing
>> under the container module section can be dependent on any
>> server modules.
>> -->
>> <dependency>
>> <groupId>org.apache.openejb</groupId>
>> <artifactId>container</artifactId>
>> <version>${pom.version}</version>
>> <type>pom</type>
>> <scope>compile</scope>
>> </dependency>
>> </dependencies>
Re: Openejb question
Posted by anita kulshreshtha <a_...@yahoo.com>.
Thanks David! openejb-core still has dependency on
openejb-persistence:
<dependency>
<groupId>org.apache.openejb</groupId>
<artifactId>openejb-persistence</artifactId>
<version>${pom.version}</version>
</dependency>
The openejb-persistence module has been deleted from the source (rev
500244). Where has this been moved to?
Thanks
Anita
--- David Jencks <da...@yahoo.com> wrote:
>
> On Jan 26, 2007, at 8:03 AM, anita kulshreshtha wrote:
>
> > This is a fragment from openejb3/server's pom.xml. Could someone
> > please explain how this works?
>
>
> I haven't investigate thoroughly, but I believe that this is an easy
>
> way to make sure that if any container module references any server
> module as a dependency you will get a circular dependency and maven
> will refuse to build.
>
> thanks
> david jencks
>
> >
> > Thanks
> > Anita
> > ................................................................
> > <dependencies>
> > <!--
> > This dependency is here to ensure that absolutely nothing
> > under the container module section can be dependent on any
> > server modules.
> > -->
> > <dependency>
> > <groupId>org.apache.openejb</groupId>
> > <artifactId>container</artifactId>
> > <version>${pom.version}</version>
> > <type>pom</type>
> > <scope>compile</scope>
> > </dependency>
> > </dependencies>
> >
> >
> >
> >
> >
> >
> >
>
______________________________________________________________________
>
> > ______________
> > Don't pick lemons.
> > See all the new 2007 cars at Yahoo! Autos.
> > http://autos.yahoo.com/new_cars.html
>
>
____________________________________________________________________________________
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front
Re: Openejb question
Posted by David Jencks <da...@yahoo.com>.
On Jan 26, 2007, at 8:03 AM, anita kulshreshtha wrote:
> This is a fragment from openejb3/server's pom.xml. Could someone
> please explain how this works?
I haven't investigate thoroughly, but I believe that this is an easy
way to make sure that if any container module references any server
module as a dependency you will get a circular dependency and maven
will refuse to build.
thanks
david jencks
>
> Thanks
> Anita
> ................................................................
> <dependencies>
> <!--
> This dependency is here to ensure that absolutely nothing
> under the container module section can be dependent on any
> server modules.
> -->
> <dependency>
> <groupId>org.apache.openejb</groupId>
> <artifactId>container</artifactId>
> <version>${pom.version}</version>
> <type>pom</type>
> <scope>compile</scope>
> </dependency>
> </dependencies>
>
>
>
>
>
>
> ______________________________________________________________________
> ______________
> Don't pick lemons.
> See all the new 2007 cars at Yahoo! Autos.
> http://autos.yahoo.com/new_cars.html