repository

I am receiving the following error: System.InvalidOperationException was unhandled Message=The type 'Judge' is not attributed with EdmEntityTypeAttribute but is contained in an assembly attributed with EdmSchemaAttribute. POCO entities that do not use EdmEntityTypeAttribute cannot be contained in the same assembly as non-POCO entities that use EdmEntityTypeAttribute. Source=EntityFramework StackTrace: at System.Data.Entity.Internal.InternalContext.UpdateEntitySetMappingsForType(Type entityType) at System.Data.Entity.Internal.InternalContext.GetEntitySetAndBaseTypeForType(Type entityType)....

In my project, there are a number of dependencies that are transitively included from other dependencies that do not have pom.xml files available in any of our corporate repositories. These are internal jar-only libraries supported by various teams which have been uploaded into repositories for convenience from non-Maven teams, however these repositories are unfortunately not mine to play with. For these dependencies, Maven insists on trying to retrieve the poms from each of my repository list every time I run a build, or mvn dependency:list . This means maven tries to retrieve 8x pom files

Why maven 3 depreciated false at Snapshot repository configuration at pom.xml? What is the motivation behind it? <snapshotRepository> <id>snapshots</id> <url>http://nexus.mycompany.local/content/repositories/snapshots</url> <uniqueVersion>false</uniqueVersion> </snapshotRepository> Thanks Raghuram As answered in your other question , the comments in this nexus bug says why uniqueVersion was present in the first place and why it is not available in maven3. Quoting from it, It's not recommended to use non-unique snapshots since they lead to non-reproducible builds. The main use case for these

I am aware that rollbacks can remove commits from the latest changeset in a local repository. However, is it possible to remove all the latest commits since the previous push without having to re-clone the share repository? You could make a new repo with hg clone : hg clone -r last_good_changeset localrepo newlocalrepo You can use the hg strip command, part of the mq extension: hg strip REV This will remove that revision + all its descendants. Before you try this, make a copy/clone of the repository to experiment in. If you are using mercurial eclipse, you can rollback once, then shelve those