Re: [paxweb] Update of Tomcat version

2017-09-09 Thread 'Achim Nierbeck' via OPS4J
Hi Stephan, actually I have no idea. But glad you managed to get around your issues. regards, Achim 2017-09-07 9:25 GMT+02:00 Stephan Siano : > Hi Achim, > > I did the release for tomcat-embed-websocket and here the release:perform > worked fine (in the correct repository). Do you have any ide

Re: [paxweb] Update of Tomcat version

2017-09-07 Thread Stephan Siano
Hi Achim, I did the release for tomcat-embed-websocket and here the release:perform worked fine (in the correct repository). Do you have any idea how the staging plugin selects the checkout directory? Best regards Stephan Am Donnerstag, 7. September 2017 09:16:12 UTC+2 schrieb Stephan Siano: >

Re: [paxweb] Update of Tomcat version

2017-09-07 Thread Stephan Siano
Hi Achim, I finally managed to release org.ops4j.pax.tipi.tomcat-embed-core with Linux. The "mvn release:prepare" worked fine, but the release:perform really went wrong: I ran the release:perform in directory tomcat-embed-core-8.0.46, but the release perform then created the staging repository

Re: [paxweb] Update of Tomcat version

2017-09-04 Thread 'Achim Nierbeck' via OPS4J
Hi Stephan, I'm not sure but you might have a valid point :) Most of the people here at ops4j do use anything besides Windows ;) for Pax Web the following is needed to run, this might also be possible for the Pax-Tipi release: mvn -Prelease -Darguments="-Prelease" release:prepare -DautoVersionSu

Re: [paxweb] Update of Tomcat version

2017-09-04 Thread Stephan Siano
Hi Achim, has anyone actually tried that under Windows? I have successfully created a sonatype account and got the access rights, but the mvn release:prepare fails for me with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on project or

Re: [paxweb] Update of Tomcat version

2017-08-31 Thread 'Achim Nierbeck' via OPS4J
Hi Stephan, actually anybody following this: https://ops4j1.jira.com/wiki/spaces/ops4j/pages/12060688/Releasing can do the releasing :) about pax tipi, take a look here: https://ops4j1.jira.com/wiki/spaces/PAXTIPI/pages/28540952/Creating+New+Bundles regards, Achim 2017-08-31 8:40 GMT+02:00 St

Re: [paxweb] Update of Tomcat version

2017-08-30 Thread Stephan Siano
Hi Achim, OK, thanks for your feedback. I have merged the pull request. What needs to be done next? Is there a build job that runs a SNAPSHOT build somewhere (so I can push a pull request to Pax-Web that references these SNAPSHOTS)? I actually don't understand how any consumable version of this

Re: [paxweb] Update of Tomcat version

2017-08-30 Thread 'Achim Nierbeck' via OPS4J
Hi looks good to me. regards, Achim 2017-08-30 12:01 GMT+02:00 Stephan Siano : > Hi Achim, > > OK, I created PAXTIPI-47 and > PAXWEB-1128 for the update. > Would you be willing to have a look into the pull

Re: [paxweb] Update of Tomcat version

2017-08-30 Thread Stephan Siano
Hi Achim, OK, I created PAXTIPI-47 and PAXWEB-1128 for the update. Would you be willing to have a look into the pull requests? Best regards Stephan Am Dienstag, 29. August 2017 23:23:23 UTC+2 schrieb Ach

Re: [paxweb] Update of Tomcat version

2017-08-29 Thread 'Achim Nierbeck' via OPS4J
Hi Stephan, Technically you are correct. Create the pax-tipi projects, a release is needed at lease the moment we release the pax-web project referencing that version. So you could also reference some snapshot versions from pax-web. Regarding Jira tasks, yes it's common to create a Jira task in th

Re: [paxweb] Update of Tomcat version

2017-08-28 Thread Stephan Siano
Hi Achim, No problem, I was also a but busy. I found out that SPDY support was removed from tomcat 8 in the meantime, which makes the tomcat-embed-core bundle easier to build. How does this work technically? I need to create two projects in pax-tipi, release it and then create the changes in p

Re: [paxweb] Update of Tomcat version

2017-08-25 Thread 'Achim Nierbeck' via OPS4J
Hi Stephan, sorry for taking me so long, but my day job actually eats up a lot of time right now. A new tomcat version does require a new folder in the pax-tipi project. Actually the main project is just a "container" holding a bunch of sub-projects. regarding the juli logger, what ever works bes

Re: [paxweb] Update of Tomcat version

2017-08-22 Thread Stephan Siano
Hi Achim, yes I was aware of the things done in pax-tipi. I will try this out and then create the required projects in there. As I understand a new tomcat version would require new folders in pax-tipi for the required bundles (next to the ones for version 8.0.14), is this correct? One more que

Re: [paxweb] Update of Tomcat version

2017-08-21 Thread 'Achim Nierbeck' via OPS4J
Hi, the 6.0.x branch should stay with 8.0 version but a newer one if available. A minor version bump is fine with a 6.1.x (or master branch). regards, Achim P.S. btw. since Tomcat isn't OSGi ready we did some "enhancements" in the Pax Tipi Project. 2017-08-21 15:07 GMT+02:00 Stephan Siano : >

[paxweb] Update of Tomcat version

2017-08-21 Thread Stephan Siano
Hi, currently the tomcat support in pax-web references tomcat 8.0.14, which is almost three years old. The current tomcat versions are 8.0.46 and 8.5.20. The end of life for tomcat 8.0 is announced for June 30th 2018. Would it make sense to upgrade the tomcat version in pax-web-6.0x branch to