You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Blevins <da...@visi.com> on 2010/10/07 07:50:08 UTC
Re: Time for a 3.1.3 release?
I'm repeatedly getting HTTP 502 errors while uploading the assemblies to nexus....
Going to keep retrying. If anyone has any tips, they would be very welcome.
I seem to remember encountering this before and eventually it just worked. Seems like something here is in dire need of improvement.
-David
Re: Time for a 3.1.3 release?
Posted by Shawn Jiang <ge...@gmail.com>.
Geronimo 2.2 branch 100% passed tck with this staging openejb 3.1.3
artifacts. It's time to start the vote.
On Fri, Oct 8, 2010 at 8:17 PM, Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:
> Just ran this. I ran into one problem which was the Tomcat bundle trying to
> use the openejb-webapp 3.1.3-SNAPSHOT and not 3.1.3 - I guess the prepare
> goal for the release plugin didn't pick this one up. I've updated the
> version string and committed the change to the branch.
>
> Other than that, I've done the deployment, and it has just finished without
> any errors. I've checked Nexus, and it looks like stuff is there. The
> repository is here:
> https://repository.apache.org/content/repositories/orgapacheopenejb-009/
>
> Let me know if there's anything else I can do, but hopefully this
> deployment
> will be good.
>
> Jon
>
> On Fri, Oct 8, 2010 at 1:08 AM, David Blevins <david.blevins@visi.com
> >wrote:
>
> >
> > On Oct 7, 2010, at 4:10 PM, Jonathan Gallimore wrote:
> >
> > > Do you think this is a Nexus / Central problem? I don't mind giving it
> a
> > go
> > > from here if you think its worth a shot.
> >
> > Starting to wonder that.
> >
> > I tried going around the httpd proxy by hitting
> repository.apache.org:8081and hacking my apache parent pom to use that as
> the repo. Still died while
> > uploading the standalone tar.gz. So that rules out the httpd proxy as
> the
> > cause.
> >
> > To rule out anything in the middle, I setup a tunnel between me and
> > repository.a.o through people.apache.org (via ssh -L 8081:
> > repository.apache.org:8081 people.apache.org). Double verified that
> > everything worked through the tunnel by killing the tunnel to make sure
> that
> > the upload would immediately fail. Still no luck. So that would
> indicate
> > no one in the middle is hanging up on me.
> >
> > So at this point it's either me or Nexus.
> >
> > Here's the command do upload:
> >
> > $ svn co https://svn.apache.org/repos/asf/openejb/branches/openejb-3.1.3
> > $ cd openejb-3.1.3
> > $ mvn install -Dassemble -Dmaven.test.skip=true
> > $ mvn clean deploy -Dassemble -Prelease -Dgpg.passphrase=xxxxxx
> >
> > Something is messed up in our poms that the build fails unless you've
> built
> > at least once. So I added that 'mvn install -Dassemble
> > -Dmaven.test.skip=true'.
> >
> > Anyway, anxious to see what kind of results you get.
> >
> > -David
> >
> >
> > > On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <david.blevins@visi.com
> > >wrote:
> > >
> > >> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
> > >>
> > >>> I'm repeatedly getting HTTP 502 errors while uploading the assemblies
> > to
> > >> nexus....
> > >>>
> > >>> Going to keep retrying. If anyone has any tips, they would be very
> > >> welcome.
> > >>>
> > >>> I seem to remember encountering this before and eventually it just
> > >> worked. Seems like something here is in dire need of improvement.
> > >>
> > >> Unfortunately I seem to be at an impasse with uploading the binaries.
> > I'm
> > >> getting bit by this:
> > >>
> > >> https://issues.sonatype.org/browse/NEXUS-2879
> > >>
> > >> Been working with infra to try and tweak the proxy, but at this point
> we
> > >> still have no idea what's going wrong.
> > >>
> > >> Will keep trying and post more details later.
> > >>
> > >> -David
> > >>
> > >>
> >
> >
>
--
Shawn
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 11, 2010, at 11:06 AM, David Blevins wrote:
> Going to try an upload from the mac mini and see if I can't get it to work. If not, I may need you to do another upload.
Things worked fine from my mini. Not sure why maven doesn't like my laptop -- oh well.
Staging repo is here:
https://repository.apache.org/content/repositories/orgapacheopenejb-017/
Uploading the "dist" directory now. Vote coming shortly....
-David
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 8, 2010, at 5:17 AM, Jonathan Gallimore wrote:
> Just ran this. I ran into one problem which was the Tomcat bundle trying to
> use the openejb-webapp 3.1.3-SNAPSHOT and not 3.1.3 - I guess the prepare
> goal for the release plugin didn't pick this one up. I've updated the
> version string and committed the change to the branch.
>
> Other than that, I've done the deployment, and it has just finished without
> any errors. I've checked Nexus, and it looks like stuff is there. The
> repository is here:
> https://repository.apache.org/content/repositories/orgapacheopenejb-009/
>
> Let me know if there's anything else I can do, but hopefully this deployment
> will be good.
>
That's great. Noticed our tomcat bundle didn't have the intended 6.0.26.313 version number and just had 313. As fixing that would mean attempting to get another upload to work, I switched over to my mac mini to see if I could get the build to go from there. Then I noticed that we don't compile under java 1.5. We get this compilation failure:
[INFO] ------------------------------------------------------------------------
[INFO] Building OpenEJB :: Server :: CXF
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting file set: /Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/target (included: [**], excluded: [])
[INFO] [remote-resources:process {execution: default}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not a valid reference.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 23 source files to /Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
/Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/src/main/java/org/apache/openejb/server/cxf/ejb/EjbMessageContext.java:[22,33] cannot find symbol
symbol : class W3CEndpointReferenceBuilder
location: package javax.xml.ws.wsaddressing
/Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/src/main/java/org/apache/openejb/server/cxf/ejb/EjbMessageContext.java:[40,8] cannot find symbol
symbol : class W3CEndpointReferenceBuilder
location: class org.apache.openejb.server.cxf.ejb.EjbMessageContext
/Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/src/main/java/org/apache/openejb/server/cxf/ejb/EjbMessageContext.java:[40,50] cannot find symbol
symbol : class W3CEndpointReferenceBuilder
location: class org.apache.openejb.server.cxf.ejb.EjbMessageContext
I sifted through and was able to fix it by updating our javaee-api jar. Seems I cut things too thin when trimming down the cxf dependencies. The jaxws api is in the Java 6 vm so it went unnoticed.
Going to try an upload from the mac mini and see if I can't get it to work. If not, I may need you to do another upload.
-David
Re: Time for a 3.1.3 release?
Posted by Jonathan Gallimore <jo...@gmail.com>.
Just ran this. I ran into one problem which was the Tomcat bundle trying to
use the openejb-webapp 3.1.3-SNAPSHOT and not 3.1.3 - I guess the prepare
goal for the release plugin didn't pick this one up. I've updated the
version string and committed the change to the branch.
Other than that, I've done the deployment, and it has just finished without
any errors. I've checked Nexus, and it looks like stuff is there. The
repository is here:
https://repository.apache.org/content/repositories/orgapacheopenejb-009/
Let me know if there's anything else I can do, but hopefully this deployment
will be good.
Jon
On Fri, Oct 8, 2010 at 1:08 AM, David Blevins <da...@visi.com>wrote:
>
> On Oct 7, 2010, at 4:10 PM, Jonathan Gallimore wrote:
>
> > Do you think this is a Nexus / Central problem? I don't mind giving it a
> go
> > from here if you think its worth a shot.
>
> Starting to wonder that.
>
> I tried going around the httpd proxy by hitting repository.apache.org:8081and hacking my apache parent pom to use that as the repo. Still died while
> uploading the standalone tar.gz. So that rules out the httpd proxy as the
> cause.
>
> To rule out anything in the middle, I setup a tunnel between me and
> repository.a.o through people.apache.org (via ssh -L 8081:
> repository.apache.org:8081 people.apache.org). Double verified that
> everything worked through the tunnel by killing the tunnel to make sure that
> the upload would immediately fail. Still no luck. So that would indicate
> no one in the middle is hanging up on me.
>
> So at this point it's either me or Nexus.
>
> Here's the command do upload:
>
> $ svn co https://svn.apache.org/repos/asf/openejb/branches/openejb-3.1.3
> $ cd openejb-3.1.3
> $ mvn install -Dassemble -Dmaven.test.skip=true
> $ mvn clean deploy -Dassemble -Prelease -Dgpg.passphrase=xxxxxx
>
> Something is messed up in our poms that the build fails unless you've built
> at least once. So I added that 'mvn install -Dassemble
> -Dmaven.test.skip=true'.
>
> Anyway, anxious to see what kind of results you get.
>
> -David
>
>
> > On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <david.blevins@visi.com
> >wrote:
> >
> >> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
> >>
> >>> I'm repeatedly getting HTTP 502 errors while uploading the assemblies
> to
> >> nexus....
> >>>
> >>> Going to keep retrying. If anyone has any tips, they would be very
> >> welcome.
> >>>
> >>> I seem to remember encountering this before and eventually it just
> >> worked. Seems like something here is in dire need of improvement.
> >>
> >> Unfortunately I seem to be at an impasse with uploading the binaries.
> I'm
> >> getting bit by this:
> >>
> >> https://issues.sonatype.org/browse/NEXUS-2879
> >>
> >> Been working with infra to try and tweak the proxy, but at this point we
> >> still have no idea what's going wrong.
> >>
> >> Will keep trying and post more details later.
> >>
> >> -David
> >>
> >>
>
>
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 7, 2010, at 4:10 PM, Jonathan Gallimore wrote:
> Do you think this is a Nexus / Central problem? I don't mind giving it a go
> from here if you think its worth a shot.
Starting to wonder that.
I tried going around the httpd proxy by hitting repository.apache.org:8081 and hacking my apache parent pom to use that as the repo. Still died while uploading the standalone tar.gz. So that rules out the httpd proxy as the cause.
To rule out anything in the middle, I setup a tunnel between me and repository.a.o through people.apache.org (via ssh -L 8081:repository.apache.org:8081 people.apache.org). Double verified that everything worked through the tunnel by killing the tunnel to make sure that the upload would immediately fail. Still no luck. So that would indicate no one in the middle is hanging up on me.
So at this point it's either me or Nexus.
Here's the command do upload:
$ svn co https://svn.apache.org/repos/asf/openejb/branches/openejb-3.1.3
$ cd openejb-3.1.3
$ mvn install -Dassemble -Dmaven.test.skip=true
$ mvn clean deploy -Dassemble -Prelease -Dgpg.passphrase=xxxxxx
Something is messed up in our poms that the build fails unless you've built at least once. So I added that 'mvn install -Dassemble -Dmaven.test.skip=true'.
Anyway, anxious to see what kind of results you get.
-David
> On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <da...@visi.com>wrote:
>
>> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
>>
>>> I'm repeatedly getting HTTP 502 errors while uploading the assemblies to
>> nexus....
>>>
>>> Going to keep retrying. If anyone has any tips, they would be very
>> welcome.
>>>
>>> I seem to remember encountering this before and eventually it just
>> worked. Seems like something here is in dire need of improvement.
>>
>> Unfortunately I seem to be at an impasse with uploading the binaries. I'm
>> getting bit by this:
>>
>> https://issues.sonatype.org/browse/NEXUS-2879
>>
>> Been working with infra to try and tweak the proxy, but at this point we
>> still have no idea what's going wrong.
>>
>> Will keep trying and post more details later.
>>
>> -David
>>
>>
Re: Time for a 3.1.3 release?
Posted by Jonathan Gallimore <jo...@gmail.com>.
Do you think this is a Nexus / Central problem? I don't mind giving it a go
from here if you think its worth a shot.
Jon
On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <da...@visi.com>wrote:
> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
>
> > I'm repeatedly getting HTTP 502 errors while uploading the assemblies to
> nexus....
> >
> > Going to keep retrying. If anyone has any tips, they would be very
> welcome.
> >
> > I seem to remember encountering this before and eventually it just
> worked. Seems like something here is in dire need of improvement.
>
> Unfortunately I seem to be at an impasse with uploading the binaries. I'm
> getting bit by this:
>
> https://issues.sonatype.org/browse/NEXUS-2879
>
> Been working with infra to try and tweak the proxy, but at this point we
> still have no idea what's going wrong.
>
> Will keep trying and post more details later.
>
> -David
>
>
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
> I'm repeatedly getting HTTP 502 errors while uploading the assemblies to nexus....
>
> Going to keep retrying. If anyone has any tips, they would be very welcome.
>
> I seem to remember encountering this before and eventually it just worked. Seems like something here is in dire need of improvement.
Unfortunately I seem to be at an impasse with uploading the binaries. I'm getting bit by this:
https://issues.sonatype.org/browse/NEXUS-2879
Been working with infra to try and tweak the proxy, but at this point we still have no idea what's going wrong.
Will keep trying and post more details later.
-David