Maven Plug-in about randoop

[GoogleCodeExporter]

Thanks for creating a Maven plug-in!  That's wonderful.

Is there any documentation for it?  The wiki at 
https://bitbucket.org/javydreamercsw/randoop-maven-plugin/wiki/Home still 
contains default content, but maybe the documentation appears elsewhere.

> 1) I would need Randoop in Maven repository. I can do it myself but I guess 
you would like to have control over that.

We should be able to do this.  (You might want to do so in the short term, 
until we get it done.)

> 2) I would like to add some of your guys to have to my bitbucket repo so they 
can contribute.

I'll have three people contact you with their bitbucket IDs.

> 3) Do you have a place to host the Maven site that I'll generate for it?

We could put it in http://types.cs.washington.edu/m2-repo, or you could find a 
site.  I have been told that some projects have a policy to only use Maven 
projects that are hosted at Maven Central.  Do you think this is a common 
concern?

Original comment by [email protected] on 29 Nov 2012 at 4:36

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Documentation is not up yet, I'm just getting the code to work first. I was 
able to do the first goal to generate tests for all files in the project. Need 
to do a couple more.

1) I would prefer to wait for yours. I can add a warning with instructions on 
how to work around this.

2) Good.

3) It is a common concern. I get my projects to Maven Central via Sonatype. 
This is what I do for my projects: 
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide

Probably I'll add the site to a Sourceforge project page as described here: 
http://docs.codehaus.org/display/MAVENUSER/MavenAndSourceforge

Original comment by [email protected] on 29 Nov 2012 at 5:05

[GoogleCodeExporter]

Maven site gets generated and posted here: 
http://randoopmplugin.sourceforge.net/

Original comment by [email protected] on 30 Nov 2012 at 5:55

[GoogleCodeExporter]

I'm Mavenizing the project on my clone so I can publish it. My only issue so 
far is figuring out the origin of the plume jar. Any hints?

Original comment by [email protected] on 4 Dec 2012 at 2:59

[GoogleCodeExporter]

plume.jar is from the plume-lib package: http://code.google.com/p/plume-lib/

Original comment by [email protected] on 4 Dec 2012 at 3:37

[GoogleCodeExporter]

I worked around plume by installing locally. Theirs is not published either. It 
is something you guys would need to address if you plan on Mavenization.

I just published the Randoop artifact. It should show in maven central repo 
within the next 2 hours. randoop:randoop:1.3.2.

See my clone for details. Mavenization is not complete, some of the test fails 
and such, but was enough to publish the artifact.

Original comment by [email protected] on 4 Dec 2012 at 4:04

[GoogleCodeExporter]

The artifact was not published. I'm sorting out the issue with Sonatype: 
https://issues.sonatype.org/browse/OSSRH-4847

Original comment by [email protected] on 4 Dec 2012 at 9:54

[GoogleCodeExporter]

Artifact published as net.sourceforge.javydreamercsw:randoop:1.3.2

Original comment by [email protected] on 5 Dec 2012 at 9:26

[GoogleCodeExporter]

Original comment by [email protected] on 17 Dec 2012 at 5:38

[mernst]

Thanks! I have added a link to this Maven plug-in from the Randoop manual.

[zaplatynski]

Hey, what is the status of the Maven plugin? Seems not active any more... I would like to contribute if it possible or rewite one since I have some experience in writing Maven plugins.

[bjkeller]

I don't know anything about it. It seems like it would need to be resurrected or replaced.

I added an empty repo https://github.com/randoop/randoop-maven-plugin. You could build your plugin and then do a PR to that repo.

[zaplatynski]

Ok, thanks. Is there any repository available from where l can create a Maven dependency?

[bjkeller]

Sorry, I don't know of one.

[zaplatynski]

Never mind. I try something. I will open a new a new issue if I have new issues to report.

[jeacott1]

@zaplatynski did you ever get to building a new maven plugin?

[zaplatynski]

Yes, I am waiting for the promised Maven dependency by Ben Keller since then because I made an awful hack to get the randdoop via command line to work. I did no want to create an pull request for that and waited since then. Now someone just deleted the upstream repository so I can not create any pull request. The plugin with the awful hack is still on my profile available: https://github.com/zaplatynski/randoop-maven-plugin Regards, Marian 2018-03-06 3:06 GMT+01:00 jeacott1 <[email protected]>:

…

@zaplatynski <https://github.com/zaplatynski> did you ever get to building a new maven plugin? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#40 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJX8GruUq3I0seSqxGpa8ZKkcyB9ncoUks5tbe8mgaJpZM4ExeZT> .

[mernst]

I have added a reference to your plugin to the Randoop manual, in commit cd50d2c.
If you could update your plugin to use Randoop version 4, that would be very helpful. Thanks!

[mernst]

@zaplatynski Could you enable the issue tracker in your repository https://github.com/zaplatynski/randoop-maven-plugin ? Also, it is still using Randoop 3.1.5 as noted above. Thanks.