Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Drill, mail # user - mvn clean install is failing


Copy link to this message
-
Re: mvn clean install is failing
Timothy Chen 2013-08-05, 17:41
+1

I manually changed to 1.0.0 in my repo to get it to work too.

Tim
On Mon, Aug 5, 2013 at 10:39 AM, Jacques Nadeau <[EMAIL PROTECTED]> wrote:

> :D
>
> I guess that is what you get for relying on the bleeding edge of
> snapshot-land.  We'll get it pointed to the first 1.0.0 release soon.
>
> J
>
> On Mon, Aug 5, 2013 at 10:09 AM, Julien Le Dem <[EMAIL PROTECTED]> wrote:
> > Hi,
> > It looks like sonatype automatically deletes snapdhots when a release is
> made.
> > Good news is now you will be able to depend on fixed releases.
> > Julien
> >
> > On Mon, Aug 5, 2013 at 9:44 AM, Jacques Nadeau <[EMAIL PROTECTED]>
> wrote:
> >> Yeah, we need to fix that.  Apparently, the Parquet snapshot jar was
> >> deleted from the sonatype repository.
> >>
> >> If you modify the block:
> >>     <dependency>
> >>       <groupId>com.twitter</groupId>
> >>       <artifactId>parquet-column</artifactId>
> >>       <version>1.0.0-SNAPSHOT</version>
> >>     </dependency>
> >>
> >> To look like:
> >>     <dependency>
> >>       <groupId>com.twitter</groupId>
> >>       <artifactId>parquet-column</artifactId>
> >>       <version>1.0.0</version>
> >>     </dependency>
> >>
> >> In the file:
> >> sandbox/prototype/exec/java-exec/pom.xml
> >>
> >> And then retry, things should work.  Assuming protoc --version returns
> >> "libprotoc 2.5.0"
> >>
> >> J
> >>
> >>
> >>
> >> On Mon, Aug 5, 2013 at 9:35 AM, AnilKumar B <[EMAIL PROTECTED]>
> wrote:
> >>> Thanks Jason.
> >>>
> >>> I already installed protobuf.
> >>> user@ubuntu:~/Work/incubator-drill/sandbox/prototype$ protoc
> >>> Missing input file.
> >>>
> >>>
> >>> Even I tried with protobuf-2.5.0  & jdk-1.7, still I am getting
> following
> >>> error.
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] Building java-exec 1.0-SNAPSHOT
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [WARNING] The POM for com.twitter:parquet-column:jar:1.0.0-SNAPSHOT is
> >>> missing, no dependency information available
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] Reactor Summary:
> >>> [INFO]
> >>> [INFO] prototype-parent .................................. SUCCESS
> [1.184s]
> >>> [INFO] common ............................................ SUCCESS
> [3.319s]
> >>> [INFO] contrib-parent .................................... SUCCESS
> [0.087s]
> >>> [INFO] pom ............................................... SUCCESS
> [0.182s]
> >>> [INFO] Netty/Drill/Buffer ................................ SUCCESS
> [0.943s]
> >>> [INFO] exec .............................................. SUCCESS
> [0.124s]
> >>> [INFO] java-exec ......................................... FAILURE
> [0.229s]
> >>> [INFO] Logical Plan Execution Reference Implementation ... SKIPPED
> >>> [INFO] planner ........................................... SKIPPED
> >>> [INFO] sqlparser ......................................... SKIPPED
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] BUILD FAILURE
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] Total time: 6.300s
> >>> [INFO] Finished at: Mon Aug 05 12:34:54 EDT 2013
> >>> [INFO] Final Memory: 26M/62M
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [ERROR] Failed to execute goal on project java-exec: Could not resolve
> >>> dependencies for project
> org.apache.drill.exec:java-exec:jar:1.0-SNAPSHOT:
> >>> Failure to find com.twitter:parquet-column:jar:1.0.0-SNAPSHOT in
> >>> http://conjars.org/repo was cached in the local repository,
> resolution will
> >>> not be reattempted until the update interval of conjars has elapsed or
> >>> updates are forced -> [Help 1]
> >>> [ERROR]
> >>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e
> >>> switch.
> >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.