So, my questions for you all:
We will need to move fairly fast to avoid delaying 2.4.0 too much, so please post your thoughts asap.
Simon
Many people have asked me when we are going to migrate to GitHub, but I've resisted due to the disruption it will cause.
However we are rapidly running out of space on the main zaproxy Google Code repo and I've had no answers to my requests to increase our quota :(
So I think we'll have to migrate ZAP away from Google Code, and GitHub seems to be the obvious choice.
We're also probably going to have to do this _before_ 2.4.0 can be released.
We could migrate the repos as they are now. but I think it makes sense to reassess them to see if we could do anything better.
Some suggestions that have been mentioned before include:
- Using maven to manage the jars
- Having one repo for each add-on
So, my questions for you all:
- Is GitHub the best place to migrate ZAP to?
- What changes should we make?
- Any other thoughts or suggestions??
We will need to move fairly fast to avoid delaying 2.4.0 too much, so please post your thoughts asap.
Simon
Those kind of things :)
So right now I'm playing with Gradle scripts and investigating Maven Central.
Advice and guidance from anyone who knows about these things much appreciated :)
Cheers,
Simon
Simon,
Have you been in touch with Max Gelman <max.gelman@contrastsecurity.com>?
> email to zaproxy-develop+unsubscribe@googlegroups.com.
I got some replies back from Max. Sends like they didn't have to deal we large binaries the same way ZAP is setup. Also got some feedback from a github staff that we can remove large binaries this way:
https://help.github.com/articles/remove-sensitive-data/
He also used a modified version of:
https://github.com/arthur-debert/google-code-issues-migrator
--
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
Wish the article actually linked to it:
"Exporting to GitHub is probably easiest, as Google has an export-to-GitHub tool"
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-devel...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OWASP ZAP Developer Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to zaproxy-develop+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OWASP ZAP Developer Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to zaproxy-devel...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Blog: http://off-the-wall-security.blogspot.com/
NSA: All your crypto bit are belong to us.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-devel...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OWASP ZAP Developer Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to zaproxy-develop+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Blog: http://off-the-wall-security.blogspot.com/
NSA: All your crypto bit are belong to us.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OWASP ZAP Developer Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to zaproxy-devel...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Blog: http://off-the-wall-security.blogspot.com/
NSA: All your crypto bit are belong to us.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-devel...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-devel...@googlegroups.com.
Gradle provides nice functionality to call ant tasks. I would say gradle is to prefer over maven.
Best regards,
Niklas
--
For an Ant-heavy project like ZAP Gradle definitely has the easier migration path. Maven will also do its best to prevent future scripting in the build process - which you can either love or hate it for... I'd go for Gradle.
For an Ant-heavy project like ZAP Gradle definitely has the easier migration path. Maven will also do its best to prevent future scripting in the build process - which you can either love or hate it for... I'd go for Gradle.
Am 12.05.2015 12:08 schrieb Niklas Volcz <niklas...@gmail.com>:
Gradle provides nice functionality to call ant tasks. I would say gradle is to prefer over maven.
Best regards,
Niklas
On May 12, 2015 10:11, "java bean" <java.dev...@gmail.com> wrote:
Could we migrate the Ant build to a more modern Maven build ? Let me know if i can help here.--
I havel already updated the Maven plugin for ZAP to the latest Maven and jdk version and ZAP client api : https://github.com/javabeanz/zap-maven-plugin2
Cheers,
javabean.
Op donderdag 7 mei 2015 17:43:20 UTC+2 schreef kingthorin+owaspzap:I've been trying for a long time to cleanup our issue tracker and I've made some progress. Unfortunately due to work and life I kind of only get to tackle it about 30mins to and hour at a time and once a month (or every other month). With the pace things come in and giving requesters a reasonable chance to provide further details, it's really hard to get ahead.
We currently have ~350 open issues. Which to me doesn't seem like too much, do we expect/want to move all the closed/historic issues as well?
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
I haven't any experience in both Maven and Gradle. But I red about a Gradle daemon with a 1Gb heap that run in execution under the hood consuming lot of resources... is that true?
Besides that I saw that lots of Environment support Maven directly (e.g. Netbeans that is the IDE I use support it without any plugin). This was very useful for me, because when I migrated from SVN to Git I benefit by the native implementation of Git inside Netbeans and I'd only to solve issues related to project automation respect to IDE plugin compatibility...
Il giorno martedì 12 maggio 2015 16:05:02 UTC+2, Björn Kimminich ha scritto:
For an Ant-heavy project like ZAP Gradle definitely has the easier migration path. Maven will also do its best to prevent future scripting in the build process - which you can either love or hate it for... I'd go for Gradle.
Am 12.05.2015 12:08 schrieb Niklas Volcz <niklas...@gmail.com>:
Gradle provides nice functionality to call ant tasks. I would say gradle is to prefer over maven.
Best regards,
Niklas
On May 12, 2015 10:11, "java bean" <java.dev...@gmail.com> wrote:
Could we migrate the Ant build to a more modern Maven build ? Let me know if i can help here.--
I havel already updated the Maven plugin for ZAP to the latest Maven and jdk version and ZAP client api : https://github.com/javabeanz/zap-maven-plugin2
Cheers,
javabean.
Op donderdag 7 mei 2015 17:43:20 UTC+2 schreef kingthorin+owaspzap:I've been trying for a long time to cleanup our issue tracker and I've made some progress. Unfortunately due to work and life I kind of only get to tackle it about 30mins to and hour at a time and once a month (or every other month). With the pace things come in and giving requesters a reasonable chance to provide further details, it's really hard to get ahead.
We currently have ~350 open issues. Which to me doesn't seem like too much, do we expect/want to move all the closed/historic issues as well?
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
>>>> To unsubscribe from this group and all its topics, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
>>>> To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/zaproxy-develop/H3GzoTf9MEI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to zaproxy-devel...@googlegroups.com.
I would like to migrate the history to github, but thats proving very hard.
However it looks like the automated migration process to Source Forge works well. Before you all get too upset, no I'm not suggesting we move the source code there, but we could use it as the history archive and then just migrate the zaproxy trunk and 2.4 branch to github without any history.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-devel...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-develop+unsubscribe@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-devel...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-devel...@googlegroups.com.
Martin is right, it is the remains of the unit/integration tests that could not yet be moved into the core project under /src/test. The project should be obsolete in the long run.
Cheers,
Björn