SCM APIs cause "ref HEAD is not a symbolic ref"

Hi all mates, I've been happily using the Maven SCM APIs to perform few operations "under the hood" for my users, everything was working fine until stumbled in the SCMException "Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref" The scenario is: I am using the libraries

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

Yeah, that could work as well. On Tue, 14 Jun 2016, 21:05 Christian Schulte, wrote: > http://git-wip-us.apache.org/repos/asf/maven/commit/ded1379e > > > - > To unsubscribe, e-mail:

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

http://git-wip-us.apache.org/repos/asf/maven/commit/ded1379e - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven and Eclipse

Hi Michael, > Failure to find org.apache.maven:maven-plugin-api:jar:2.0.9 in > https://swimrepo.faa.gov/nexus/content/repositories/Repo-jboss-fuse-06-02-01-Releases > was cached in the local repository, resolution will not be reattempted > until the update interval of SwimRepo has elapsed or

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

Yes, exactly. To be able to show markers at correct locations in an editor, we need to know if a particular problem is sourced at this particular file. Since early 2.x versions of this source was exactly one path to a file and now it has changed. So it would be really helpful to know what the new

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

Am 06/14/16 um 18:46 schrieb Anton Tanasenko: > Christian? Anyone? > > 2016-06-13 1:19 GMT+03:00 Anton Tanasenko : > >> I've tried running m2eclipse tests with 3.4.0-SNAPSHOT maven. There are >> several failures. >> >> 1. src/x/resources-filtered addition, which we will

RE: Maven and Eclipse

And one last thing on this. So now that I have resolved the Maven Dependencies problem, which it appears I created myself, I am back to the original problem which is when I compile from Eclipse (regardless of whether I upgraded to Mars 2 from Luna as in my Windows environment or fresh

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

You need to build the snapshot version of maven-findbugs-plugin. 2016-06-14 19:46 GMT+03:00 Anton Tanasenko : > Christian? Anyone? > > 2016-06-13 1:19 GMT+03:00 Anton Tanasenko : > > > I've tried running m2eclipse tests with 3.4.0-SNAPSHOT maven.

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

Christian? Anyone? 2016-06-13 1:19 GMT+03:00 Anton Tanasenko : > I've tried running m2eclipse tests with 3.4.0-SNAPSHOT maven. There are > several failures. > > 1. src/x/resources-filtered addition, which we will need to adhere to when > 3.4.0 gets released. > > 2. >

RE: Maven and Eclipse

Curtis, Thank you for your reply. It actually gave me an idea that solved my problem. To get Eclipse and Maven recreate the Maven Dependencies in my Java Build Path I ran Maven -> Update Projects. first without a settings.xml file which did recreate the entry, but with the errors because

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

Hi Karl-Heinz, I found another project I can't build with the latest snapshot of Maven. Building it with Maven 3.4.0-SNAPSHOT results in the following message [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs (findbugs) on project tamaya-code: Unable to

Re: Maven and Eclipse

Hi Michael, > I removed the Maven Dependencies entry from the Java Build Bath > Libraries tab I don't understand why you are doing this step. It should never be necessary in my experience, and my intuition is that it could hose things up. The Maven > Update Project... command in the Package

RE: Maven and Eclipse

Further information on this issue: I earlier reported that my fresh install of Eclipse Mars 2 in a Linux environment did create a Maven Directories entry when executing Maven -> Update Project, but that I noticed a problem with the actual jar files this entry was pointing to and that they were

RE: Maven and Eclipse

> From: michael.ctr.taru...@faa.gov > To: users@maven.apache.org > Subject: RE: Maven and Eclipse > Date: Tue, 14 Jun 2016 14:33:31 + > > This is a partial update to this issue, which I am posting as requested by > Barrie Treloar. > > I encountered this problem on a Windows install of

RE: Maven and Eclipse

This is a partial update to this issue, which I am posting as requested by Barrie Treloar. I encountered this problem on a Windows install of Eclipse. For the project I am working on I also needed a Linux Eclipse environment. So I asked our Linux Sys Admin to install a fresh download of