Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318144 - transformRepos target in genericTargets.xml doesn't transform if directory contains non-repository files
Summary: transformRepos target in genericTargets.xml doesn't transform if directory co...
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.6.1   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-28 05:18 EDT by Alfred Schmid CLA
Modified: 2010-08-10 16:31 EDT (History)
2 users (show)

See Also:
darin.eclipse: review+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alfred Schmid CLA 2010-06-28 05:18:16 EDT
Build Identifier: Eclipse basebuilder r36x_20100623

Our repository contains some control files from version control system. These are hidden files like .copyarea.db or .svn. This can't be avoided. The problem is that headless build tries to transform this files and stops with a failure like the following:

....\org.eclipse.releng.basebuilder-r36x_20100623\plugins\org.eclipse.pde.build_3.6.0.v20100603\scripts\genericTargets.xml:210: Error occurred while transforming repository: No repository found at file:/Z:/zCCRCz/zccrcz_view_targetplatform/pegbin/target.platform/eclipseBaseRepos/.copyarea.db..

From my point of view the transForm target shouldn't look into hidden files. I changed line 211 in genericTargets.xml from basebuilder like this:

<source dir="${repoBaseLocation}/" includes="*" excludes=".*" />

Now the build works without any problems :)

Reproducible: Always

Steps to Reproduce:
1. Setup a headless build which uses repositories
2. Use a repoBaseLocation which contains other files then repositories (like version control system hidden files)
3. Start the build an you will get the error
Comment 1 Andrew Niefer CLA 2010-07-05 16:27:09 EDT
Sounds reasonable to me, I did this:

<property name="repoBaseLocation.excludes" value=".*" />
<p2.repo2runnable destination="${transformedRepoLocation}">
  <source dir="${repoBaseLocation}/" includes="*"
                                     excludes="${repoBaseLocation.excludes}"/>
</p2.repo2runnable>


Which allows the user to exclude other things too.

This is in 3.7 head and 3.6.1
Comment 2 Alfred Schmid CLA 2010-07-06 04:04:40 EDT
Thanx Andrew, this solution fits exact to my needs.