Re: [Codenarc-developer] Release a CodeNarc test-jar please

[Clay M. <cod...@cl...>]

Either way would work for me.  Just having the one jar might be more
convenient if you can ensure that all the needed infrastructure for
writing tests will be visible. I'm mostly interested in what can be
done quickest so that I can ditch my homemade CodeNarc test-jar.
Thanks,
Clay

On Fri, Mar 30, 2012 at 4:51 AM,  <chr...@we...> wrote:
> Yes, thanks for feedback Clay.
>
> So, should we consider the other option as well -- just including the test classes in the regular jar?
>
> Chris
>
> -----Original Message-----
> From: Hamlet DArcy [mailto:ham...@ca...]
> Sent: Friday, March 30, 2012 1:14 AM
> To: Clay McCoy
> Cc: cod...@li...
> Subject: Re: [Codenarc-developer] Release a CodeNarc test-jar please
>
> This is great news Clay!
>
> I'm so happy to see other people writing rules, especially if you can share them with others.
>
> Chris is our Maven Master, so he will have to do the test-jar release.
>
> As for GitHub...
> In the end it is up to Chris. The only thing I am unhappy about with Sourceforge is the issue tracker. I feel like GitHub has a better issue tracker. But other than that, I don't see a move solving any of our active problems.
>
> So what are the state of your rules? I'd love to know even the names of the rules or any details. In the past with community rules, I have just merged them into CodeNarc itself. I'd definitely find time for this if you sent them over.
>
>
> ----- Original Message -----
>> I'm using CodeNarc on a large Grails app at Netflix.  We have created
>> some of our own rules.  Some of these are specific to us, some may be
>> useful to a broader audience and submitted back to CodeNarc.  It is
>> nice to write and run these rules in our own project as a sandbox.
>> Though this is possible, it is not as easy as it could be.  If I am
>> going to write my own rule, I will also write a test for it.  I'd
>> like
>> to use the infrastructure already in CodeNarc for the test (namely
>> AbstractRuleTestCase).  The problem is that it isn't available to me
>> with the regular jar since it is test code.  To overcome this I got
>> the source, modified the pom to release a test-jar, built locally,
>> and
>> released the test-jar to a local repo.
>> There are several easy ways that the CodeNarc project could make this
>> easier.  Perhaps release a test-jar and deploy it to the same repos
>> as
>> the regular CodeNarc jar.  Here are the minor pom modifications that
>> are needed
>> (http://maven.apache.org/guides/mini/guide-attached-tests.html).
>>  Or even simpler is to just move the test building blocks into the
>> main source.
>> BTW, the CodeNarc project might get more visibility and commits if it
>> were on Github.  Are there any plans for this?  If not would there be
>> an issue with a fan of the project maintaining a mirror on Github?
>> Thanks,
>> Clay
>>
>> ------------------------------------------------------------------------------
>> This SF email is sponsosred by:
>> Try Windows Azure free for 90 days Click Here
>> http://p.sf.net/sfu/sfd2d-msazure
>> _______________________________________________
>> Codenarc-developer mailing list
>> Cod...@li...
>> https://lists.sourceforge.net/lists/listinfo/codenarc-developer
>>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Codenarc-developer mailing list
> Cod...@li...
> https://lists.sourceforge.net/lists/listinfo/codenarc-developer