Now I am unable to complete the build because the juddi/uddi-ws SNAPSHOT was not
published.
-
Could not find artifact org.apache.juddi:uddi-ws:jar:3.1.0-20110610.165546-15 in
apache.snapshots (http://repository.apache.org/snapshots)
-
The pom's are there for 20110610.165546-15, but the jars are no
Yes it would seem that rev1133618 has resolved the build error I report
-
r1133618 | xuhaihong | 2011-06-08 20:42:31 -0400 (Wed, 08 Jun 2011) | 1 line
Changed paths:
M /geronimo/server/trunk/plugins/pom.xml
Update JAX-WS spec version number in the compile property
-
Thanks to xuhaihong for fixi
My checkout was 1.5 days old, as I was working on compiling all day yesterday
through to this morning.
I see xuhaihong updated the geronimo-jaxws_2.2_spec artifact dependency from 1.0
to 1.1 five hours after my last update.
I will try again to see if this resolves the matter.
Thanks.
-RG
On 06/
Is your code up-to-date? Especially check if plugins/pom.xml is
up-to-date. plugins/pom.xml should refer to 1.1-SNAPSHON of
geronimo-jaxws_2.2_spec which should be in your m2 repository already.
Jarek
On Fri, Jun 10, 2011 at 12:37 PM, Russell E Glaue wrote:
> Okay, the build has the "does not ex
Okay, the build has the "does not exist" error I remember.
-
[INFO]
[INFO] Building Geronimo Plugins, J2EE :: Builder 3.0-SNAPSHOT
[INFO]
[INFO]
[INFO]
Yes, I was able to reproduce the error.
After the last successful build that completed this morning, I then removed the
geronimo-jaxws_2.2_spec-1.0 artifact fron my local maven repository...
-
/bin/rm -r
~/.m2/repository/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/1.0
-
...and reexecuted the
Perhaps then, I am mistaken, it is not the uddi plugin that is the problem.
My build fails at this stage:
[INFO] Geronimo Plugins, J2EE :: Builder . FAILURE [18.237s]
The goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project geronimo-j2ee-b
Thanks for reporting this, I tried to remove the old jaxws spec 1.0 in my
local repo and then still can build uddi plugins without problems.
Anyway, something like this in root pom.xml to exclude jaxws spec
dependency from uddi-ws artifact would resolve this.
org.
G3.0 compiled!
That means, the issue I reported is the only problem.
This is the geronimo-jaxws_2.2_spec 1.0 maven bundle dependency.
I will go an create a JIRA for that.
The question is about the dependency on the 1.0 bundle, when Geronimo primarily
depends on 1.1-SNAPSHOT. It would seem the udd
I got a little further this time
I manually install the 1.0 jaxws spec file.
-
mvn install:install-file -DgroupId=org.apache.geronimo.specs
-DartifactId=geronimo-jaxws_2.2_spec -Dversion=1.0 -Dpackaging=jar
-Dfile=geronimo-jaxws_2.2_spec-1.0.jar
-
And I got past that problem spot.
So that does see
Okay,
I think I just put 2+2 together.
1. The build process complains of the missing geronimo-jaxws_2.2_spec 1.0
2. The error message received after only executing 'mvn clean install' is
complaining about javax.xml.ws.* class stuff
3. When issuing 'mvn compile' then 'mvn clean install', the pac
On Jun 7, 2011, at 6:51 PM, Russell E Glaue wrote:
>
>
> On 06/07/2011 05:08 PM, Kevan Miller wrote:
>>
>> On Jun 7, 2011, at 5:48 PM, Russell E Glaue wrote:
>>
>>> I had originally done the install 'mvn clean install' yesterday, and
>>> received a
>>> build error. I then did it in the two s
On 06/07/2011 05:08 PM, Kevan Miller wrote:
>
> On Jun 7, 2011, at 5:48 PM, Russell E Glaue wrote:
>
>> I had originally done the install 'mvn clean install' yesterday, and
>> received a
>> build error. I then did it in the two stages and got the same results.
>> That is why I ended up executi
On Jun 7, 2011, at 5:48 PM, Russell E Glaue wrote:
> I had originally done the install 'mvn clean install' yesterday, and received
> a
> build error. I then did it in the two stages and got the same results.
> That is why I ended up executing mvn compile and package separately so I could
> see i
I had originally done the install 'mvn clean install' yesterday, and received a
build error. I then did it in the two stages and got the same results.
That is why I ended up executing mvn compile and package separately so I could
see if the error was in the compiling stage or the packaging stage.
On Jun 6, 2011, at 2:15 PM, Russell E Glaue wrote:
> I am not sure what I need to do to get a successful maven packaging of G3.0.
>
> I am successfully compiling G3.0-SNAPSHOT with Maven without errors.
> However, during the packaging stage, I get this error:
>
> -
> ...
> [org.apache.geronimo.
I am not sure what I need to do to get a successful maven packaging of G3.0.
I am successfully compiling G3.0-SNAPSHOT with Maven without errors.
However, during the packaging stage, I get this error:
-
...
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState for:
org.apach
17 matches
Mail list logo