Looking for org.apache.poi 3.10-FINAL

Hi, I'm new to maven thought I'd try it out on the recently checked-in: org.apache.poi3.10-FINAL I'm using m2eclipse standard config with Eclipse Kepler. Repo defaults to: http://repo.maven.apache.org/maven2 The Problem: m2eclipse does not know the org.apache.poi 3.10-FINAL artifact.

Re: Looking for org.apache.poi 3.10-FINAL

David, just guessing: - indexing takes it's time, there are only two hours difference between the commit (??l and end of indexing. - commit (tag creation), artifact creation (jar build), deployment (upload to staging), promotion (move of staged to released) and synchronization from

Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute

Op Sun, 16 Feb 2014 08:15:25 +0100 schreef Henrik Skriver Rasmussen skrive...@gmail.com: Thanks for the advice on how to restructure. Could you have a look at the deploy-plugin project and the file org.apache.maven.plugin.deploy.DeployFileMojo execute method line 376 in version 2.8.1 ? I

Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute

Hi Robert Thank you for your answer. I would like to figure out how to simple skip the generation of the given extra zip file because I do not know how now. Any way to see during debug which goal will result in which artifact? Any help on finding out when running my build will be appreciated. I

Re: Looking for org.apache.poi 3.10-FINAL

Hi Mirko, I think though 6 days!!! should be adequate for that. In fact, I think 6 minutes should be adequate. So I really need someone to explain how I can move forward with this issue. All the best, DaveLaw On 16.02.2014 10:49, Mirko Friedenhagen wrote: David, just guessing: - indexing

Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute

Hi Henrik, IMHO deploy-file (just like install-file) should *never* be a part of a lifecycle, but should be run standalone and should only be used for unavailable third party artifacts. Looking back at your pom-fragment, you should do the following: * if deploymentfile is being created by

RE: Possible build collision between CI snapshot build and Release build

From: bmat...@batmat.net Date: Sat, 15 Feb 2014 22:07:26 +0100 Subject: Re: Possible build collision between CI snapshot build and Release build To: users@maven.apache.org OK, so this has to be CVCS (svn and so on) specific? I didn't check if the release-plugin commits + push each

Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute

Hi Robert Thanks - that sounds interesting and I will look into that Monday. But what is the right way to deploy a zip file build in the project to the artifactory repository then? Is it to only use deploy? Regards Henrik Skriver Rasmussen On Feb 16, 2014, at 14:47, Robert Scholte

Re: Looking for org.apache.poi 3.10-FINAL

On 16 February 2014 10:31, David Law m2ecli...@apconsult.de wrote: Hi Mirko, I think though 6 days!!! should be adequate for that. In fact, I think 6 minutes should be adequate. So I really need someone to explain how I can move forward with this issue. FWIW, I did a search today for

RE: Looking for org.apache.poi 3.10-FINAL

Date: Sun, 16 Feb 2014 10:49:48 +0100 Subject: Re: Looking for org.apache.poi 3.10-FINAL From: mfriedenha...@gmail.com To: users@maven.apache.org David, just guessing: - indexing takes it's time, there are only two hours difference between the commit (??l and end of indexing.

Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute

Yes. Use a pom project and bind the assembly plugin to the build lifecycle. Did you take a look at the project I linked to earlier? Just copy that solution. /Anders (mobile) Den 16 feb 2014 14:37 skrev Henrik Skriver Rasmussen skrive...@gmail.com : Hi Robert Thanks - that sounds interesting

Re: Looking for org.apache.poi 3.10-FINAL

Hi Stuart, thanks for that very useful information. Are you using the default repo? (http://repo.maven.apache.org/maven2) All the best, DaveLaw On 16.02.2014 14:36, Stuart McCulloch wrote: On 16 February 2014 10:31, David Law m2ecli...@apconsult.de wrote: Hi Mirko, I think though 6

Re: Why does Maven fail to compile my project occasionally?

Thanks for your suggestion. But I don't think it's the Jenkins fault because: I've written a Windows batch file to invoke Maven to build the project before I choose Jenkins as my daily build system. And at that time I got the same Maven error as I described in this thread. I'll post some other

Re: Looking for org.apache.poi 3.10-FINAL

On 16 February 2014 14:36, David Law m2ecli...@apconsult.de wrote: Hi Stuart, thanks for that very useful information. Are you using the default repo? (http://repo.maven.apache.org/maven2) I switch depending what workspace I'm using, as I have a corporate repo as well as a local nexus

Re: Why does Maven fail to compile my project occasionally?

I've written a Windows batch file to invoke Maven to build the project before I choose Jenkins as my daily build system. And at that time I got the same Maven error as I described in this thread. Maven calls out to your system JDK to do the compilation step. With the [ERROR] lines you provided

Re: Why does Maven fail to compile my project occasionally?

Is it possible that you have more than 1 version of Java installed? I use Eclipse/STS, have all the Maven tools that I need to build with Maven so I may suggest some things that you may not have, with m2 installed separately. 1) Look in the project properties and make sure that you have

Re: Looking for org.apache.poi 3.10-FINAL

Hi Stuart, thanks once again! The only person to supply useful information. I checked the Nexus Index Timestamp from the repo this morning 05:39 CET and: nexus.index.timestamp=20140209134945.568 + Over 6 days old!! Just checked it again and: nexus.index.timestamp=20140216125157.106

Re: Looking for org.apache.poi 3.10-FINAL

On Sunday, 16 February 2014, David Law m2ecli...@apconsult.de wrote: Hi Stuart, thanks once again! The only person to supply useful information. I checked the Nexus Index Timestamp from the repo this morning 05:39 CET and: nexus.index.timestamp=20140209134945.568 + Over 6 days old!!

Re: Looking for org.apache.poi 3.10-FINAL

thanks once again! The only person to supply useful information. ... Over 6 days old!! ... So that means maven central took over 6 days to index this content. That is quite incredible! ... This is in my opinion a bug, or at least a fundamental design error. Also before completely blaming

Re: Looking for org.apache.poi 3.10-FINAL

And it's just an index. You can always download the artifact without it. And as far as I know, the downloadable central index has always only been updated once a week. Have a look here: http://repo1.maven.org/maven2/.index/ /Anders On Sun, Feb 16, 2014 at 9:52 PM, Wayne Fay wayne...@gmail.com

Re: Looking for org.apache.poi 3.10-FINAL

Anders, Tack för det. Dave On 16.02.2014 22:03, Anders Hammar wrote: And it's just an index. You can always download the artifact without it. And as far as I know, the downloadable central index has always only been updated once a week. Have a look here: http://repo1.maven.org/maven2/.index/

Re: Looking for org.apache.poi 3.10-FINAL

Hi Wayne, I would suggest someone documents the behaviour in the FAQ with a tip that a not-yet-indexed artifact can be proactively retrieved by entering its Group Id, Artifact Id Version. That way we all save time. All the best, DaveLaw On 16.02.2014 21:52, Wayne Fay wrote: thanks once

[ANN] Apache Maven Plugin Testing 3.1.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Plugin Testing, version 3.1.0 The Maven Plugin Testing contains the necessary tools to be able to test Maven Plugins. http://maven.apache.org/plugin-testing/ You should specify the version in your project's dependency

adding repository url

Hi there , I have this dependency present in my pom.xml . dependency groupIdorg.apache.solr/groupId artifactIdsolr-cell/artifactId version4.0/version /dependency However , while trying to mvn install results

Re: adding repository url

On 15 February 2014 11:13, 454329 abhi454...@gmail.com wrote: Hi there , I have this dependency present in my pom.xml . dependency groupIdorg.apache.solr/groupId artifactIdsolr-cell/artifactId version4.0/version Did

Re: Looking for org.apache.poi 3.10-FINAL

Sure, but which FAQ should this go in - a generic Maven faq, a faq specific to m2eclipse (bear in mind, this group has zero control over m2e), or a FAQ related to Central? Or all of those places? Where did you look (in the Maven website docs) for such information, prior to posting your email to

Re: Looking for org.apache.poi 3.10-FINAL

http://stackoverflow.com/questions/10600576/nexus-index-of-maven-central-is-not-up-to-date-new-installation The problem appears to be well known but is not something that one expects and it will be hard to know where people are most likely to look. It is not really a Maven problem and as I

Re: Why does Maven fail to compile my project occasionally?

Robert Scholte-4 wrote My code is correct because I could successfully build the whole project in Eclipse again and again. This is 100% true. Within Eclipse you can manually add libraries. Actually, if you create your first JUnit test, Eclipse will ask if the JUnit4 library should be

Re: Looking for org.apache.poi 3.10-FINAL

Ron, Wayne, this wasted several days (elapsed) of my time: I spent ages trying out options trying to figure out what I'd done wrong... ...rebuilding updating indices, hacking through to workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration, to set logging to ALL, but even ALL was