Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Renato Athaydes
Hi! Just wanted to announce the release of version 1.2.6 of Spock-Reports.

It now supports parallel builds (before, the summary report would get messed up).

An important note to users of template reports: the "forEach" method of the "features" object had to be renamed to "eachFeature". This is a breaking change!
Please update your templates. The change was necessary as "forEach" was conflicting with Java 8's method of the same name.

Regards!

Renato Athaydes

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Renato Athaydes
Just an update. Release 1.2.6 missed support for some doc annotations! This has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL Spock documentation annotations!

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Kostis Kapelonis
Very nice!

Finally a reporting tool that honours @Title and @Issue.

You might want to write in the README that the @Issue value is
expected to be a link. If I write for example @Issue("JIRA-5585") the
report contains a broken link that goes nowhere.

Any chance we will see this in Maven central as well?

Kostis

On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <[hidden email]> wrote:

> Just an update. Release 1.2.6 missed support for some doc annotations! This
> has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL Spock
> documentation annotations!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> To post to this group, send email to [hidden email].
> Visit this group at http://groups.google.com/group/spockframework.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Renato Athaydes
Hello,

For now, @Issue and @See are expected to be links.

I was planning to add a "smart" decider for whether to make that a link or not but that will be for a future release.

I only publish SpockReports on JCenter, currently. Haven't had requests to add it to Maven Central also (I guess most people have no problem using JCenter instead, any reason why you would prefer Maven Central?).

Em sábado, 15 de agosto de 2015 17:56:03 UTC+2, Kostis Kapelonis escreveu:
Very nice!

Finally a reporting tool that honours @Title and @Issue.

You might want to write in the README that the @Issue value is
expected to be a link. If I write for example @Issue("JIRA-5585") the
report contains a broken link that goes nowhere.

Any chance we will see this in Maven central as well?

Kostis

On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="5oq6qiqxAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ren...@...> wrote:

> Just an update. Release 1.2.6 missed support for some doc annotations! This
> has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL Spock
> documentation annotations!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="5oq6qiqxAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">spockframewor...@googlegroups.com.
> To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="5oq6qiqxAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">spockfr...@googlegroups.com.
> Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;">http://groups.google.com/group/spockframework.
> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Marcin Grzejszczak
I use JCenter but there is plenty of people who don't know that it even exists :)

I went through the same stuff with my Gradle Plugin. You can take a look here - https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle at how I'm using Nexus Staging plugin to deploy to Maven Central.

W dniu niedziela, 16 sierpnia 2015 00:05:47 UTC+2 użytkownik Renato Athaydes napisał:
Hello,

For now, @Issue and @See are expected to be links.

I was planning to add a "smart" decider for whether to make that a link or not but that will be for a future release.

I only publish SpockReports on JCenter, currently. Haven't had requests to add it to Maven Central also (I guess most people have no problem using JCenter instead, any reason why you would prefer Maven Central?).

Em sábado, 15 de agosto de 2015 17:56:03 UTC+2, Kostis Kapelonis escreveu:
Very nice!

Finally a reporting tool that honours @Title and @Issue.

You might want to write in the README that the @Issue value is
expected to be a link. If I write for example @Issue("JIRA-5585") the
report contains a broken link that goes nowhere.

Any chance we will see this in Maven central as well?

Kostis

On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <[hidden email]> wrote:

> Just an update. Release 1.2.6 missed support for some doc annotations! This
> has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL Spock
> documentation annotations!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to spockframewor...@googlegroups.com.
> To post to this group, send email to [hidden email].
> Visit this group at <a href="http://groups.google.com/group/spockframework" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;">http://groups.google.com/group/spockframework.
> For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Kostis Kapelonis
Well I personally have no problem with JCenter.

Unfortunately there are organizations with very strict policies (due
to software licencing and political issues) that force all company
projects to use only the internal repo (i.e. Nexus or Artifactory)
which in turn just mirrors Maven central (and nothing else). When I
say "force" I mean via network fire-walling.

In such organizations, your pom file of the project you develop cannot
contain any other repos and all libraries that you use come from Maven
central (because apparently Maven central is the safest option as far
as security/licencing matter - go figure)

I find the @Issue/@Title combo very useful and these organizations
will benefit from it as well. It would be a shame if they cannot use
the spock-reports extension, because of internal network constraints.

As I said, this does not block me personally. I think that a release
in Maven central will help the exposure of the project.

Regarding the links in @See and @Issue, I can wait for the next version then :-)

Kostis

On Sun, Aug 16, 2015 at 1:52 PM, Marcin Grzejszczak
<[hidden email]> wrote:

> I use JCenter but there is plenty of people who don't know that it even
> exists :)
>
> I went through the same stuff with my Gradle Plugin. You can take a look
> here -
> https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle
> at how I'm using Nexus Staging plugin to deploy to Maven Central.
>
>
> W dniu niedziela, 16 sierpnia 2015 00:05:47 UTC+2 użytkownik Renato Athaydes
> napisał:
>>
>> Hello,
>>
>> For now, @Issue and @See are expected to be links.
>>
>> I was planning to add a "smart" decider for whether to make that a link or
>> not but that will be for a future release.
>>
>> I only publish SpockReports on JCenter, currently. Haven't had requests to
>> add it to Maven Central also (I guess most people have no problem using
>> JCenter instead, any reason why you would prefer Maven Central?).
>>
>> Em sábado, 15 de agosto de 2015 17:56:03 UTC+2, Kostis Kapelonis escreveu:
>>>
>>> Very nice!
>>>
>>> Finally a reporting tool that honours @Title and @Issue.
>>>
>>> You might want to write in the README that the @Issue value is
>>> expected to be a link. If I write for example @Issue("JIRA-5585") the
>>> report contains a broken link that goes nowhere.
>>>
>>> Any chance we will see this in Maven central as well?
>>>
>>> Kostis
>>>
>>> On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <[hidden email]>
>>> wrote:
>>> > Just an update. Release 1.2.6 missed support for some doc annotations!
>>> > This
>>> > has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL
>>> > Spock
>>> > documentation annotations!
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Spock Framework - User" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> > an
>>> > email to [hidden email].
>>> > To post to this group, send email to [hidden email].
>>> > Visit this group at http://groups.google.com/group/spockframework.
>>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> To post to this group, send email to [hidden email].
> Visit this group at http://groups.google.com/group/spockframework.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Renato Athaydes
I agree, having the project in Maven Central is nice... if nothing else because then nobody needs to add a new repository to their poms just to use Spock Reports.

It's unfortunate that companies still have these restrictions on using only Maven Central, which until recently favoured HTTP over HTTPS, and think that that's safer....

Anyway, Thanks @Marcin for the pointers, I will have a look... I've heard that getting a project on Maven Central is a hassle.... but I will give it a go for the next release... hoping I have time...

And I will definitely "fix" @Issue and @See to not require only links... have you created a issue for that?

Em domingo, 16 de agosto de 2015 20:41:39 UTC+2, Kostis Kapelonis escreveu:
Well I personally have no problem with JCenter.

Unfortunately there are organizations with very strict policies (due
to software licencing and political issues) that force all company
projects to use only the internal repo (i.e. Nexus or Artifactory)
which in turn just mirrors Maven central (and nothing else). When I
say "force" I mean via network fire-walling.

In such organizations, your pom file of the project you develop cannot
contain any other repos and all libraries that you use come from Maven
central (because apparently Maven central is the safest option as far
as security/licencing matter - go figure)

I find the @Issue/@Title combo very useful and these organizations
will benefit from it as well. It would be a shame if they cannot use
the spock-reports extension, because of internal network constraints.

As I said, this does not block me personally. I think that a release
in Maven central will help the exposure of the project.

Regarding the links in @See and @Issue, I can wait for the next version then :-)

Kostis

On Sun, Aug 16, 2015 at 1:52 PM, Marcin Grzejszczak
<<a href="javascript:" target="_blank" gdf-obfuscated-mailto="HefXxMgIAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marcin.gr...@...> wrote:

> I use JCenter but there is plenty of people who don't know that it even
> exists :)
>
> I went through the same stuff with my Gradle Plugin. You can take a look
> here -
> <a href="https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw&#39;;return true;">https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle
> at how I'm using Nexus Staging plugin to deploy to Maven Central.
>
>
> W dniu niedziela, 16 sierpnia 2015 00:05:47 UTC+2 użytkownik Renato Athaydes
> napisał:
>>
>> Hello,
>>
>> For now, @Issue and @See are expected to be links.
>>
>> I was planning to add a "smart" decider for whether to make that a link or
>> not but that will be for a future release.
>>
>> I only publish SpockReports on JCenter, currently. Haven't had requests to
>> add it to Maven Central also (I guess most people have no problem using
>> JCenter instead, any reason why you would prefer Maven Central?).
>>
>> Em sábado, 15 de agosto de 2015 17:56:03 UTC+2, Kostis Kapelonis escreveu:
>>>
>>> Very nice!
>>>
>>> Finally a reporting tool that honours @Title and @Issue.
>>>
>>> You might want to write in the README that the @Issue value is
>>> expected to be a link. If I write for example @Issue("JIRA-5585") the
>>> report contains a broken link that goes nowhere.
>>>
>>> Any chance we will see this in Maven central as well?
>>>
>>> Kostis
>>>
>>> On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <[hidden email]>
>>> wrote:
>>> > Just an update. Release 1.2.6 missed support for some doc annotations!
>>> > This
>>> > has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL
>>> > Spock
>>> > documentation annotations!
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Spock Framework - User" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> > an
>>> > email to spockframewor...@googlegroups.com.
>>> > To post to this group, send email to [hidden email].
>>> > Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;">http://groups.google.com/group/spockframework.
>>> > For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="HefXxMgIAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">spockframewor...@googlegroups.com.
> To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="HefXxMgIAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">spockfr...@googlegroups.com.
> Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;">http://groups.google.com/group/spockframework.
> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Marcin Zajączkowski
In reply to this post by Renato Athaydes

Dnia Poniedziałek, 17 Sierpnia 2015 09:16 Renato Athaydes <[hidden email]> napisał(a)

I agree, having the project in Maven Central is nice... if nothing else because then nobody needs to add a new repository to their poms just to use Spock Reports.
 
It's unfortunate that companies still have these restrictions on using only Maven Central, which until recently favoured HTTP over HTTPS, and think that that's safer....
 
Anyway, Thanks @Marcin for the pointers, I will have a look... I've heard that getting a project on Maven Central is a hassle.... but I will give it a go for the next release... hoping I have time...
 
Yes, it is a little bit cumbersome, but only for the first time when you need to manually request permissions for your porject(s). Later using Gradle it is a matter of using gradle-nexus-plugin by Benjamin Muschko [1] to generate artifact and put them to Sonatype staging repository and my gradle-nexus-staging-plugin [2] to promote to to Maven Central. All from a command line with minimum configuration - see that [3] for inspiration and a template to reuse.
 
[1] - https://github.com/bmuschko/gradle-nexus-plugin
[2] - https://github.com/Codearte/gradle-nexus-staging-plugin
[3] - https://github.com/Codearte/gradle-nexus-staging-plugin/blob/a4593a0239a4ddd311b9f536e7c4ee0612a202fa/build.gradle#L60-L99
 
Marcin
 
 
 
 
And I will definitely "fix" @Issue and @See to not require only links... have you created a issue for that?

Em domingo, 16 de agosto de 2015 20:41:39 UTC+2, Kostis Kapelonis escreveu:
Well I personally have no problem with JCenter.

Unfortunately there are organizations with very strict policies (due
to software licencing and political issues) that force all company
projects to use only the internal repo (i.e. Nexus or Artifactory)
which in turn just mirrors Maven central (and nothing else). When I
say "force" I mean via network fire-walling.

In such organizations, your pom file of the project you develop cannot
contain any other repos and all libraries that you use come from Maven
central (because apparently Maven central is the safest option as far
as security/licencing matter - go figure)

I find the @Issue/@Title combo very useful and these organizations
will benefit from it as well. It would be a shame if they cannot use
the spock-reports extension, because of internal network constraints.

As I said, this does not block me personally. I think that a release
in Maven central will help the exposure of the project.

Regarding the links in @See and @Issue, I can wait for the next version then :-)

Kostis

On Sun, Aug 16, 2015 at 1:52 PM, Marcin Grzejszczak
<<a onclick="this.href='javascript:';return true;" onmousedown="this.href='javascript:';return true;" href="javascript:" rel="nofollow" target="_blank">marcin.gr...@...> wrote:

> I use JCenter but there is plenty of people who don't know that it even
> exists :)
>
> I went through the same stuff with my Gradle Plugin. You can take a look
> here -
> <a onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw';return true;" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw';return true;" href="https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle" rel="nofollow" target="_blank">https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle
> at how I'm using Nexus Staging plugin to deploy to Maven Central.
>
>
> W dniu niedziela, 16 sierpnia 2015 00:05:47 UTC+2 użytkownik Renato Athaydes
> napisał:
>>
>> Hello,
>>
>> For now, @Issue and @See are expected to be links.
>>
>> I was planning to add a "smart" decider for whether to make that a link or
>> not but that will be for a future release.
>>
>> I only publish SpockReports on JCenter, currently. Haven't had requests to
>> add it to Maven Central also (I guess most people have no problem using
>> JCenter instead, any reason why you would prefer Maven Central?).
>>
>> Em sábado, 15 de agosto de 2015 17:56:03 UTC+2, Kostis Kapelonis escreveu:
>>>
>>> Very nice!
>>>
>>> Finally a reporting tool that honours @Title and @Issue.
>>>
>>> You might want to write in the README that the @Issue value is
>>> expected to be a link. If I write for example @Issue("JIRA-5585") the
>>> report contains a broken link that goes nowhere.
>>>
>>> Any chance we will see this in Maven central as well?
>>>
>>> Kostis
>>>
>>> On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <[hidden email]>
>>> wrote:
>>> > Just an update. Release 1.2.6 missed support for some doc annotations!
>>> > This
>>> > has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL
>>> > Spock
>>> > documentation annotations!
>>> >

 

--

http://blog.solidsoft.info/ - Solid Soft - Working code is not enough

 

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Peter Niederwieser
Administrator
In reply to this post by Renato Athaydes
From what I’ve heard, it's straightforward to publish to Maven Central through JCenter. See e.g. https://medium.com/@vyarus/the-hard-way-to-maven-central-c9e16d163acc

-Peter

On 17 Aug 2015, at 09:16, Renato Athaydes <[hidden email]> wrote:

I agree, having the project in Maven Central is nice... if nothing else because then nobody needs to add a new repository to their poms just to use Spock Reports.

It's unfortunate that companies still have these restrictions on using only Maven Central, which until recently favoured HTTP over HTTPS, and think that that's safer....

Anyway, Thanks @Marcin for the pointers, I will have a look... I've heard that getting a project on Maven Central is a hassle.... but I will give it a go for the next release... hoping I have time...

And I will definitely "fix" @Issue and @See to not require only links... have you created a issue for that?

Em domingo, 16 de agosto de 2015 20:41:39 UTC+2, Kostis Kapelonis escreveu:
Well I personally have no problem with JCenter.

Unfortunately there are organizations with very strict policies (due
to software licencing and political issues) that force all company
projects to use only the internal repo (i.e. Nexus or Artifactory)
which in turn just mirrors Maven central (and nothing else). When I
say "force" I mean via network fire-walling.

In such organizations, your pom file of the project you develop cannot
contain any other repos and all libraries that you use come from Maven
central (because apparently Maven central is the safest option as far
as security/licencing matter - go figure)

I find the @Issue/@Title combo very useful and these organizations
will benefit from it as well. It would be a shame if they cannot use
the spock-reports extension, because of internal network constraints.

As I said, this does not block me personally. I think that a release
in Maven central will help the exposure of the project.

Regarding the links in @See and @Issue, I can wait for the next version then :-)

Kostis

On Sun, Aug 16, 2015 at 1:52 PM, Marcin Grzejszczak
<<a href="javascript:" target="_blank" gdf-obfuscated-mailto="HefXxMgIAwAJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;" class="">marcin.gr...@...> wrote:

> I use JCenter but there is plenty of people who don't know that it even
> exists :)
>
> I went through the same stuff with my Gradle Plugin. You can take a look
> here -
> <a href="https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw';return true;" class="">https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle
> at how I'm using Nexus Staging plugin to deploy to Maven Central.
>
>
> W dniu niedziela, 16 sierpnia 2015 00:05:47 UTC+2 użytkownik Renato Athaydes
> napisał:
>>
>> Hello,
>>
>> For now, @Issue and @See are expected to be links.
>>
>> I was planning to add a "smart" decider for whether to make that a link or
>> not but that will be for a future release.
>>
>> I only publish SpockReports on JCenter, currently. Haven't had requests to
>> add it to Maven Central also (I guess most people have no problem using
>> JCenter instead, any reason why you would prefer Maven Central?).
>>
>> Em sábado, 15 de agosto de 2015 17:56:03 UTC+2, Kostis Kapelonis escreveu:
>>>
>>> Very nice!
>>>
>>> Finally a reporting tool that honours @Title and @Issue.
>>>
>>> You might want to write in the README that the @Issue value is
>>> expected to be a link. If I write for example @Issue("JIRA-5585") the
>>> report contains a broken link that goes nowhere.
>>>
>>> Any chance we will see this in Maven central as well?
>>>
>>> Kostis
>>>
>>> On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <[hidden email]>
>>> wrote:
>>> > Just an update. Release 1.2.6 missed support for some doc annotations!
>>> > This
>>> > has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL
>>> > Spock
>>> > documentation annotations!
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Spock Framework - User" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> > an
>>> > email to spockframewor...@googlegroups.com.
>>> > To post to this group, send email to [hidden email].
>>> > Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" rel="nofollow" onmousedown="this.href='http://groups.google.com/group/spockframework';return true;" onclick="this.href='http://groups.google.com/group/spockframework';return true;" class="">http://groups.google.com/group/spockframework.
>>> > For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/optout';return true;" onclick="this.href='https://groups.google.com/d/optout';return true;" class="">https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="HefXxMgIAwAJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;" class="">spockframewor...@googlegroups.com.
> To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="HefXxMgIAwAJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;" class="">spockfr...@googlegroups.com.
> Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" rel="nofollow" onmousedown="this.href='http://groups.google.com/group/spockframework';return true;" onclick="this.href='http://groups.google.com/group/spockframework';return true;" class="">http://groups.google.com/group/spockframework.
> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/optout';return true;" onclick="this.href='https://groups.google.com/d/optout';return true;" class="">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.

signature.asc (859 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Athaydes Spock-Reports 1.2.6 released! Now works fine with parallel builds.

Marcin Grzejszczak
Yeah but you would have to give them your key :) If you don't want to do that then @Marcin Zajaczkowski's approach is very cool :)

W dniu poniedziałek, 17 sierpnia 2015 19:34:51 UTC+2 użytkownik Peter Niederwieser napisał:
From what I’ve heard, it's straightforward to publish to Maven Central through JCenter. See e.g. <a href="https://medium.com/@vyarus/the-hard-way-to-maven-central-c9e16d163acc" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fmedium.com%2F%40vyarus%2Fthe-hard-way-to-maven-central-c9e16d163acc\46sa\75D\46sntz\0751\46usg\75AFQjCNGatAN9ywqCKpiBEQUg5YjTnYcvTQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fmedium.com%2F%40vyarus%2Fthe-hard-way-to-maven-central-c9e16d163acc\46sa\75D\46sntz\0751\46usg\75AFQjCNGatAN9ywqCKpiBEQUg5YjTnYcvTQ&#39;;return true;">https://medium.com/@vyarus/the-hard-way-to-maven-central-c9e16d163acc

-Peter

On 17 Aug 2015, at 09:16, Renato Athaydes <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="XmS0FLhTAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ren...@...> wrote:

I agree, having the project in Maven Central is nice... if nothing else because then nobody needs to add a new repository to their poms just to use Spock Reports.

It's unfortunate that companies still have these restrictions on using only Maven Central, which until recently favoured HTTP over HTTPS, and think that that's safer....

Anyway, Thanks @Marcin for the pointers, I will have a look... I've heard that getting a project on Maven Central is a hassle.... but I will give it a go for the next release... hoping I have time...

And I will definitely "fix" @Issue and @See to not require only links... have you created a issue for that?

Em domingo, 16 de agosto de 2015 20:41:39 UTC+2, Kostis Kapelonis escreveu:
Well I personally have no problem with JCenter.

Unfortunately there are organizations with very strict policies (due
to software licencing and political issues) that force all company
projects to use only the internal repo (i.e. Nexus or Artifactory)
which in turn just mirrors Maven central (and nothing else). When I
say "force" I mean via network fire-walling.

In such organizations, your pom file of the project you develop cannot
contain any other repos and all libraries that you use come from Maven
central (because apparently Maven central is the safest option as far
as security/licencing matter - go figure)

I find the @Issue/@Title combo very useful and these organizations
will benefit from it as well. It would be a shame if they cannot use
the spock-reports extension, because of internal network constraints.

As I said, this does not block me personally. I think that a release
in Maven central will help the exposure of the project.

Regarding the links in @See and @Issue, I can wait for the next version then :-)

Kostis

On Sun, Aug 16, 2015 at 1:52 PM, Marcin Grzejszczak
<[hidden email]> wrote:

> I use JCenter but there is plenty of people who don't know that it even
> exists :)
>
> I went through the same stuff with my Gradle Plugin. You can take a look
> here -
> <a href="https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fmarcingrzejszczak%2Fspock-subjects-collaborators-extension%2Fblob%2Fmaster%2Fgradle%2Frelease.gradle\46sa\75D\46sntz\0751\46usg\75AFQjCNESbVGGVflgmkpmPQ6LPmdb02MCxw&#39;;return true;">https://github.com/marcingrzejszczak/spock-subjects-collaborators-extension/blob/master/gradle/release.gradle
> at how I'm using Nexus Staging plugin to deploy to Maven Central.
>
>
> W dniu niedziela, 16 sierpnia 2015 00:05:47 UTC+2 użytkownik Renato Athaydes
> napisał:
>>
>> Hello,
>>
>> For now, @Issue and @See are expected to be links.
>>
>> I was planning to add a "smart" decider for whether to make that a link or
>> not but that will be for a future release.
>>
>> I only publish SpockReports on JCenter, currently. Haven't had requests to
>> add it to Maven Central also (I guess most people have no problem using
>> JCenter instead, any reason why you would prefer Maven Central?).
>>
>> Em sábado, 15 de agosto de 2015 17:56:03 UTC+2, Kostis Kapelonis escreveu:
>>>
>>> Very nice!
>>>
>>> Finally a reporting tool that honours @Title and @Issue.
>>>
>>> You might want to write in the README that the @Issue value is
>>> expected to be a link. If I write for example @Issue("JIRA-5585") the
>>> report contains a broken link that goes nowhere.
>>>
>>> Any chance we will see this in Maven central as well?
>>>
>>> Kostis
>>>
>>> On Sat, Aug 15, 2015 at 12:44 PM, Renato Athaydes <[hidden email]>
>>> wrote:
>>> > Just an update. Release 1.2.6 missed support for some doc annotations!
>>> > This
>>> > has been fixed in 1.2.7 and I believe now Spock-Reports supports ALL
>>> > Spock
>>> > documentation annotations!
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Spock Framework - User" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> > an
>>> > email to spockframewor...@googlegroups.com.
>>> > To post to this group, send email to [hidden email].
>>> > Visit this group at <a href="http://groups.google.com/group/spockframework" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;">http://groups.google.com/group/spockframework.
>>> > For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Spock Framework - User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to spockframewor...@googlegroups.com.
> To post to this group, send email to [hidden email].
> Visit this group at <a href="http://groups.google.com/group/spockframework" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;">http://groups.google.com/group/spockframework.
> For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="XmS0FLhTAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">spockframewor...@googlegroups.com.
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="XmS0FLhTAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">spockfr...@googlegroups.com.
Visit this group at <a href="http://groups.google.com/group/spockframework" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/spockframework&#39;;return true;">http://groups.google.com/group/spockframework.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.
Loading...