Thanks for the feedback Andreas. We'll fix these in an upcoming release. Since we've breathed some new life into the project, we'll hopefully have another release soon.
On 4 January 2017 at 11:04, Andreas Veithen <andreas.veit...@gmail.com> wrote: > The repository location definitely needs to be updated because it is > no longer correct. Not sure why one would need a profile. The way the > repository is configured means that Maven will only check it for > snapshots. Anyway, it looks like projects created by the archetype > will work unless the user later changes to a snapshot, so this isn't > release blocking. > > I think from a policy perspective the release looks good, so here is my +1. > > Two other minor technical issues I found while inspecting the > distributions: > - The lib directory contains slf4j-api and jul-to-slf4j (which I think > isn't actually used unless one changes the java.util.logging > properties), but no SLF4J implementation, so I would expect that some > code in dependencies will not produce logs. > - The binary distribution contains lots of unnecessary JARs, in > particular the plexus-* JARs. These appear to be transitive > dependencies of quickfixj, which itself is excluded from the > distribution. > > Andreas > > On Tue, Jan 3, 2017 at 11:45 PM, Ravi Undupitiya > <ravi.undupit...@gmail.com> wrote: > > Andreas, that seems to be set in a maven profile - it activates a > snapshot > > repository located in http://people.apache.org/repo/ > m2-snapshot-repository/. > > Correct me if I'm wrong but shouldn't that remain snapshot? Would you > happen > > to know why it's done like that? This is the only occurrence of snapshot > - > > not sure how it got away as I did grep the entire directory, maybe it was > > mix up when we had to switch between 3.0.0 and 3.0.1 a few times between > > take 1 and take 2. > > > > > > Thanks, > > Ravi > > > > On 4 January 2017 at 10:08, Andreas Veithen <andreas.veit...@gmail.com> > > wrote: > >> > >> There is at least one file that still contains a SNAPSHOT version: > >> > >> > >> modules/packaging/package-archetype/src/main/resources/arche > type-resources/pom.xml > >> > >> Andreas > >> > >> > >> On Tue, Jan 3, 2017 at 10:27 PM, Ravi Undupitiya <r...@apache.org> > wrote: > >> > > >> > We have now had the voting open for more than 72 hours. There are 9 +1 > >> > (>3 binding and 4 community) and no -1. I am calling this vote > complete and > >> > passed. > >> > > >> > > >> > Thanks, > >> > Ravi > >> > > >> > > >> > > >> > On 3 January 2017 at 16:46, Buddhima Wijeweera > >> > <buddhimawijewe...@gmail.com> wrote: > >> >> > >> >> Hi, > >> >> > >> >> I did some smoke testing on; > >> >> 1. CBR > >> >> 2. Proxy-Services > >> >> 3. APIs > >> >> 4. Store & Forward (In memory) > >> >> > >> >> Works fine. Here's my +1 > >> >> > >> >> Thank you, > >> >> > >> >> On Sun, Jan 1, 2017 at 11:08 AM, Vanjikumaran Sivajothy > >> >> <vanjikuma...@gmail.com> wrote: > >> >>> > >> >>> Based on the series of functional tests and load tests[1] covered by > >> >>> myself on Apache Synapse 3.0.0 RC2 [2]; I am casting my vote as +1. > >> >>> > >> >>> [1] > >> >>> 1) VFS to HTTP. > >> >>> 2) HTTP to VFS. > >> >>> 3) VFS Transport Load test for more than 12 hours. > >> >>> 4) VFS Transpot on FTP protocol. > >> >>> 5) VFS use-cases on different OS(Linux, Windows). > >> >>> 6) XML to JSON message transformation. > >> >>> 7) JSON to XML message transformation. > >> >>> > >> >>> [2] > >> >>> https://dist.apache.org/repos/dist/dev/synapse/3.0.0/RC2/ > >> >>> > >> >>> > >> >>> On Sat, Dec 31, 2016 at 4:10 AM, Ravi Undupitiya <r...@apache.org> > >> >>> wrote: > >> >>>> > >> >>>> This is a call for votes to release Apache Synapse 3.0.0 (Take 2) > >> >>>> > >> >>>> Please review the distribution artifacts: > >> >>>> https://dist.apache.org/repos/dist/dev/synapse/3.0.0/RC2/ > >> >>>> > >> >>>> The nexus staging repository is available at: > >> >>>> > >> >>>> https://repository.apache.org/content/repositories/orgapache > synapse-1004 > >> >>>> > >> >>>> Updated site for this release is available at: > >> >>>> http://people.apache.org/~ravi/synapse/3.0.0/RC2/site/ > >> >>>> > >> >>>> SVN Tag (r1776723): > >> >>>> https://svn.apache.org/repos/asf/synapse/tags/3.0.0/ > >> >>>> > >> >>>> Public key: > >> >>>> http://pgp.mit.edu/pks/lookup?op=get&search=0xAE1FFE87ABBB3CC4 > >> >>>> > >> >>>> Issues Fixed: > >> >>>> https://goo.gl/RfzoCK (Apache Synapse JIRA Link) > >> >>>> > >> >>>> Instructions on how to validate distribution artifacts before > voting: > >> >>>> http://www.apache.org/dev/release.html#approving-a-release > >> >>>> > >> >>>> > >> >>>> Thanks, > >> >>>> Ravi > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> Best Regards, > >> >>> Vanji > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> Buddhima Wijeweera, > >> >> Postgraduate Student, > >> >> Department Of Computer Science and Engineering, > >> >> University Of Moratuwa, > >> >> Sri Lanka. > >> >> > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > >> For additional commands, e-mail: dev-h...@synapse.apache.org > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > For additional commands, e-mail: dev-h...@synapse.apache.org > > On 4 January 2017 at 11:04, Andreas Veithen <andreas.veit...@gmail.com> wrote: > The repository location definitely needs to be updated because it is > no longer correct. Not sure why one would need a profile. The way the > repository is configured means that Maven will only check it for > snapshots. Anyway, it looks like projects created by the archetype > will work unless the user later changes to a snapshot, so this isn't > release blocking. > > I think from a policy perspective the release looks good, so here is my +1. > > Two other minor technical issues I found while inspecting the > distributions: > - The lib directory contains slf4j-api and jul-to-slf4j (which I think > isn't actually used unless one changes the java.util.logging > properties), but no SLF4J implementation, so I would expect that some > code in dependencies will not produce logs. > - The binary distribution contains lots of unnecessary JARs, in > particular the plexus-* JARs. These appear to be transitive > dependencies of quickfixj, which itself is excluded from the > distribution. > > Andreas > > On Tue, Jan 3, 2017 at 11:45 PM, Ravi Undupitiya > <ravi.undupit...@gmail.com> wrote: > > Andreas, that seems to be set in a maven profile - it activates a > snapshot > > repository located in http://people.apache.org/repo/ > m2-snapshot-repository/. > > Correct me if I'm wrong but shouldn't that remain snapshot? Would you > happen > > to know why it's done like that? This is the only occurrence of snapshot > - > > not sure how it got away as I did grep the entire directory, maybe it was > > mix up when we had to switch between 3.0.0 and 3.0.1 a few times between > > take 1 and take 2. > > > > > > Thanks, > > Ravi > > > > On 4 January 2017 at 10:08, Andreas Veithen <andreas.veit...@gmail.com> > > wrote: > >> > >> There is at least one file that still contains a SNAPSHOT version: > >> > >> > >> modules/packaging/package-archetype/src/main/resources/ > archetype-resources/pom.xml > >> > >> Andreas > >> > >> > >> On Tue, Jan 3, 2017 at 10:27 PM, Ravi Undupitiya <r...@apache.org> > wrote: > >> > > >> > We have now had the voting open for more than 72 hours. There are 9 +1 > >> > (>3 binding and 4 community) and no -1. I am calling this vote > complete and > >> > passed. > >> > > >> > > >> > Thanks, > >> > Ravi > >> > > >> > > >> > > >> > On 3 January 2017 at 16:46, Buddhima Wijeweera > >> > <buddhimawijewe...@gmail.com> wrote: > >> >> > >> >> Hi, > >> >> > >> >> I did some smoke testing on; > >> >> 1. CBR > >> >> 2. Proxy-Services > >> >> 3. APIs > >> >> 4. Store & Forward (In memory) > >> >> > >> >> Works fine. Here's my +1 > >> >> > >> >> Thank you, > >> >> > >> >> On Sun, Jan 1, 2017 at 11:08 AM, Vanjikumaran Sivajothy > >> >> <vanjikuma...@gmail.com> wrote: > >> >>> > >> >>> Based on the series of functional tests and load tests[1] covered by > >> >>> myself on Apache Synapse 3.0.0 RC2 [2]; I am casting my vote as +1. > >> >>> > >> >>> [1] > >> >>> 1) VFS to HTTP. > >> >>> 2) HTTP to VFS. > >> >>> 3) VFS Transport Load test for more than 12 hours. > >> >>> 4) VFS Transpot on FTP protocol. > >> >>> 5) VFS use-cases on different OS(Linux, Windows). > >> >>> 6) XML to JSON message transformation. > >> >>> 7) JSON to XML message transformation. > >> >>> > >> >>> [2] > >> >>> https://dist.apache.org/repos/dist/dev/synapse/3.0.0/RC2/ > >> >>> > >> >>> > >> >>> On Sat, Dec 31, 2016 at 4:10 AM, Ravi Undupitiya <r...@apache.org> > >> >>> wrote: > >> >>>> > >> >>>> This is a call for votes to release Apache Synapse 3.0.0 (Take 2) > >> >>>> > >> >>>> Please review the distribution artifacts: > >> >>>> https://dist.apache.org/repos/dist/dev/synapse/3.0.0/RC2/ > >> >>>> > >> >>>> The nexus staging repository is available at: > >> >>>> > >> >>>> https://repository.apache.org/content/repositories/ > orgapachesynapse-1004 > >> >>>> > >> >>>> Updated site for this release is available at: > >> >>>> http://people.apache.org/~ravi/synapse/3.0.0/RC2/site/ > >> >>>> > >> >>>> SVN Tag (r1776723): > >> >>>> https://svn.apache.org/repos/asf/synapse/tags/3.0.0/ > >> >>>> > >> >>>> Public key: > >> >>>> http://pgp.mit.edu/pks/lookup?op=get&search=0xAE1FFE87ABBB3CC4 > >> >>>> > >> >>>> Issues Fixed: > >> >>>> https://goo.gl/RfzoCK (Apache Synapse JIRA Link) > >> >>>> > >> >>>> Instructions on how to validate distribution artifacts before > voting: > >> >>>> http://www.apache.org/dev/release.html#approving-a-release > >> >>>> > >> >>>> > >> >>>> Thanks, > >> >>>> Ravi > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> Best Regards, > >> >>> Vanji > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> Buddhima Wijeweera, > >> >> Postgraduate Student, > >> >> Department Of Computer Science and Engineering, > >> >> University Of Moratuwa, > >> >> Sri Lanka. > >> >> > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > >> For additional commands, e-mail: dev-h...@synapse.apache.org > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > For additional commands, e-mail: dev-h...@synapse.apache.org > >
