[jira] Updated: (ARIES-353) SPI-Fly needs changes in project structure, so that itests and other subprojects can be added there

["Bartosz Kowalewski (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARIES-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Kowalewski updated ARIES-353:
-------------------------------------

    Attachment: spi-fly-poms.zip

> SPI-Fly needs changes in project structure, so that itests and other subprojects can be added there
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-353
>                 URL: https://issues.apache.org/jira/browse/ARIES-353
>             Project: Aries
>          Issue Type: Improvement
>    Affects Versions: 0.2
>         Environment: SPI-Fly
>            Reporter: Bartosz Kowalewski
>         Attachments: spi-fly-poms.zip
>
>
> I'd like to propose a change to the spi-fly project structure that would enable me to start contributing SPI-Fly itests and other bits and pieces. I think that the current spi-fly folder should contain a parent (pom) project, while its current contents should be used to create a new subproject (i.e. to spi-fly-core).
> Unfortunately, the standard 'diff' command does not support such changes as the ones generated by 'svn move'. I think that git diff supports that, but I've never used git and I don't want to experiment now :). As I'm unable to create a diff for 'svn move' that would contain all the necessary data (i.e. keep history), I'm wondering if you could do it? This would be a set of simple actions:
> 1) Create/add a directory for the new child - 'aries\spi-fly\spi-fly-core' (or some other name)
> 2) 'svn move' from 'aries\spi-fly\src' to 'aries\spi-fly\spi-fly-core\'
> 3) Changes also need to be applied to pom.xml files. Modified versions of these files will be attached in a moment.
> I'll send an e-mail with a link to this JIRA to the e-mail thread 'SPI-Fly and provider-configuration file names that are different than the abstract service class' that was started some time ago on aries-dev by David Bosschaert and me.
> Once these changes are available I'll start contributing some patches - first an itests project, then a sandbox with mavenified versions of David's AspectJ-based samples.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.