Hudson build is still unstable: Synapse - 1.3 - SNAPSHO T » Apache Synapse - Non-blocking HTTP/s Transport #113

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-nhttp-transport/113/ - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail:

Build failed in Hudson: Synapse - 1.3 - SNA PSHOT » Apache Synapse - PIPE Transport #113

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-pipe-transport/113/ -- [INFO] [INFO] Building Apache Synapse - PIPE Transport

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #113

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/113/ -- A timer trigger started this job Building on master Updating https://svn.apache.org/repos/asf/synapse/branches/1.3 At revision 889583 no change for

Re: [Transport] Incrementing version number of trunk

2009-12-11 Thread Ruwan Linton
Because OSGi versioning has a requirement that the bundle version has to be major.minor.micro.macro where as while macro can contain alpha characters all the other has to be numeric. Yes, we could keep the bundle version to that format and change the physical jar version name, but then again

Re: [Transport] Incrementing version number of trunk

2009-12-11 Thread Ruwan Linton
[missed commons-dev in the previous mail] Because OSGi versioning has a requirement that the bundle version has to be major.minor.micro.macro where as while macro can contain alpha characters all the other has to be numeric. Yes, we could keep the bundle version to that format and change the

Hudson build is still unstable: Synapse - 1.3 - SNAPSHO T » Apache Synapse - Non-blocking HTTP/s Transport #114

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-nhttp-transport/114/ - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail:

Build failed in Hudson: Synapse - 1.3 - SNA PSHOT » Apache Synapse - PIPE Transport #114

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-pipe-transport/114/ -- [INFO] [INFO] Building Apache Synapse - PIPE Transport

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #114

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/114/ -- [...truncated 43 lines...] [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean]

Re: [Transport] Incrementing version number of trunk

2009-12-11 Thread Andreas Veithen
Ruwan, Do you know if changing the version number is something that can be done using the maven-release-plugin, or do we have to do it manually? Andreas On Fri, Dec 11, 2009 at 16:47, Ruwan Linton ruwan.lin...@gmail.com wrote: [missed commons-dev in the previous mail] Because OSGi versioning

Hudson build is still unstable: Synapse - 1.3 - SNAPSHO T » Apache Synapse - Non-blocking HTTP/s Transport #115

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-nhttp-transport/115/ - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail:

Build failed in Hudson: Synapse - 1.3 - SNA PSHOT » Apache Synapse - PIPE Transport #115

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-pipe-transport/115/ -- [INFO] [INFO] Building Apache Synapse - PIPE Transport

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #115

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/115/ -- [...truncated 9 lines...] [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Synapse [INFO] Apache Synapse - Commons classes [INFO] Apache

Re: [Transport] Incrementing version number of trunk

2009-12-11 Thread Ruwan Linton
Andreas, AFAIK, there is no means of changing the versions with the release plugin, what I normally do is a search and replace. Since we shouldn't have any SNAPSHOT dependencies when releasing, hopefully that will not affect the other deps. A grep and sed, if you are on linux and on a terminal

Re: [Transport] Incrementing version number of trunk

2009-12-11 Thread Ruwan Linton
Well it seems we can :-) http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html [Disclaimer: I didn't try this] Thanks, Ruwan On Sat, Dec 12, 2009 at 10:16 AM, Ruwan Linton ruwan.lin...@gmail.comwrote: Andreas, AFAIK, there is no means of changing the versions

Hudson build is still unstable: Synapse - 1.3 - SNAPSHO T » Apache Synapse - Non-blocking HTTP/s Transport #116

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-nhttp-transport/116/ - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail:

Build failed in Hudson: Synapse - 1.3 - SNA PSHOT » Apache Synapse - PIPE Transport #116

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/org.apache.synapse$synapse-pipe-transport/116/ -- [INFO] [INFO] Building Apache Synapse - PIPE Transport

Build failed in Hudson: Synapse - 1.3 - SNAPSHOT #116

2009-12-11 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/116/ -- A timer trigger started this job Building on master Updating https://svn.apache.org/repos/asf/synapse/branches/1.3 At revision 889893 no change for