[
https://issues.apache.org/jira/browse/DROIDS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996932#comment-12996932
]
Eugen Paraschiv commented on DROIDS-89:
---------------------------------------
Hi,
I've been having some trouble with this one - the addition of a new module
requires that the module is already committed to svn so that the build will
succeed. This is because the parent pom uses the buildnumber-maven-plugin which
adds the SVN revision to the jar MANIFEST.
I'm not sure how I can go about providing a patch without the droids-examples
project already committed. Perhaps a solution is for someone with commit rights
to create an empty droids-examples project and commit it and then for me to
provide the patch based on that work. If however I'm missing something, any
help is appreciated. Thanks.
> Move droid classes from src/test/java to src/main/java
> ------------------------------------------------------
>
> Key: DROIDS-89
> URL: https://issues.apache.org/jira/browse/DROIDS-89
> Project: Droids
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.0.1, 0.0.2
> Reporter: Eugen Paraschiv
> Priority: Minor
> Fix For: 0.0.2
>
>
> There are functionality classes in the test source directory (src/test/java):
> - FileRenameDroid
> - ExceptionCrawlingDroid
> - ReportCrawlingDroid
> - SysoutCrawlingDroid
> - DroidsFactory
> These should all be moved into the sources directory (src/main/java)
> These can all be moved in either:
> - org.apache.droids.robot.various
> or
> - org.apache.droids.droid
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
