[jira] Reopened: (GERONIMODEVTOOLS-648) Source release assembly contains temporary files generated in build process

["Han Hong Fang (JIRA)" <ji...@apache.org>]

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

Han Hong Fang reopened GERONIMODEVTOOLS-648:
--------------------------------------------


Verified with "mvn -DdryRun=true release:prepare" on branch 21, the problem still exist. So I reopen this JIRA.

> Source release assembly contains temporary files generated in build process
> ---------------------------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-648
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-648
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.1.6, 3.0_M1, 2.2.1, 3.0
>            Reporter: Delos Dai
>            Assignee: Delos Dai
>             Fix For: 2.1.6, 3.0_M1, 2.2.1, 3.0
>
>
> Currently, apache 5 is the parent of geronimo-eclipse-plugin.Besides, I added configuration to its pom.xml introduced here http://maven.apache.org/developers/release/apache-release.html. But the result is, after we complete release prepare and perform, the source assembly contains all the temporary files generated by maven, such as target directory and pom.releaseBackup. Seems the configuration doesn't work for GEP. 
> I found source assembly for Geronimo Server works fine because it uses a different source assembly dependency from apache 5 or 6, that is apache-source-release-assembly-descriptor in group org.apache.geronimo.genesis. So I did these changes to root pom.xml.
> 1) Update apache 5 to apache 6, which is also used by Geronimo server 3.0
> 2) copy apache-release profile snippet from genesis-2.0.pom 

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