[
https://issues.apache.org/jira/browse/DRILL-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283497#comment-14283497
]
Daniel Barclay (Drill/MapR) commented on DRILL-2024:
----------------------------------------------------
Yes, doing {{mvn clean}} and then {{mvn install -DskipContrib -DskipJdbcAll
-DskipInterpreter}} does run without errors.
What's going on? Is it that running the {{mvn clean install -D...}} version
skips cleaning of those three modules, so any previous build ({{target/}})
directories still exist for those modules, and if they exist, the "Packaging
and Distribution Assembly" subproject tries to copy and package them?
If so:
How does it end up thinking that {{exec/jdbc/target/classes}} doesn't exist or
should be a file?
Is there any easy way for that copying and packaging to be controlled by those
{{skipXxx}} flags?
(If so, it would be nice to eliminate this apparently non-intuitive behavior.
If not, we should at least add something about it to {{INSTALL.md}}.)
> ".../exec/jdbc/target/classes isn't a file" error
> -------------------------------------------------
>
> Key: DRILL-2024
> URL: https://issues.apache.org/jira/browse/DRILL-2024
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Reporter: Daniel Barclay (Drill/MapR)
> Assignee: Patrick Wong
> Priority: Minor
>
> Building with "mvn clean install -DskipContrib -DskipJdbcAll
> -DskipInterpreter" has (at least twice) yielded errors like:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single (distro-assembly)
> on project distribution: Failed to create assembly: Error adding file
> 'org.apache.drill.exec:drill-jdbc:jar:0.8.0-SNAPSHOT' to archive:
> /home/xxxxx/exec/jdbc/target/classes isn't a file. -> [Help 1]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
