Re: Sonatype-Aether Project on github.com
Hello Hervé, maven-aether-provider is in Maven-3 in github: http://github.com/bentmann/maven-3 it contains Maven-specific code, particularly everything to read Maven's pom.xml and maven-metadata.xml from remote repository. It is an intended dependency, since aether is a repository/dependency container with pluggable systems: AFAIK, only Maven-3 provider is done for the moment, but the intent is to have at least P2 too. If you don't give a provider to aether, you can't do anything concrete. And Maven support isn't hard-coded, like it would be a default system. Ah ...many thanks for the explanation...about that... I cloned Maven-3 from github and found out i have to compile aether first (mvn install) and then i'm able to mvn install (Maven 3) itself... Many thanks. Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Sonatype-Aether Project on github.com
maven-aether-provider is in Maven-3 in github: http://github.com/bentmann/maven-3 it contains Maven-specific code, particularly everything to read Maven's pom.xml and maven-metadata.xml from remote repository. It is an intended dependency, since aether is a repository/dependency container with pluggable systems: AFAIK, only Maven-3 provider is done for the moment, but the intent is to have at least P2 too. If you don't give a provider to aether, you can't do anything concrete. And Maven support isn't hard-coded, like it would be a default system. Regards, Hervé - Karl Heinz Marbaise khmarba...@gmx.de a écrit : Hi there, i have downloaded the sonatype-aether project (via git clone) and taken a deeper look into ...but i have faced with a little problem... The aether-demo contains a reference to dependency groupIdorg.apache.maven/groupId artifactIdmaven-aether-provider/artifactId version3.0-SNAPSHOT/version /dependency which is in my opinion not ok ? May be i misunderstand things... An other little issue is that if i try to compile the aether-demo via adding the demo into parent modules list it won't be compiled, cause there are references to internal classes: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project aether-demo: Compilation failure: Compilation failure: /Users/km/ws-git/sonatype-aether/aether-demo/src/main/java/demo/RepoSys.java:[18,43] package org.apache.maven.repository.internal does not exist /Users/km/ws-git/sonatype-aether/aether-demo/src/main/java/demo/RepoSys.java:[116,8] cannot find symbol symbol : class DefaultServiceLocator location: class demo.RepoSys /Users/km/ws-git/sonatype-aether/aether-demo/src/main/java/demo/RepoSys.java:[116,44] cannot find symbol symbol : class DefaultServiceLocator location: class demo.RepoSys - [Help 1] So i have two questions: Where can i put such issues ? Does an JIRA existing for the Aether project already ? Or did i oversight informations on the github site ? Was the aether-demo intended not to work at the moment ? (cause it's bleeding edge of Aether)... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Sonatype-Aether Project on github.com
Hi there, i have downloaded the sonatype-aether project (via git clone) and taken a deeper look into ...but i have faced with a little problem... The aether-demo contains a reference to dependency groupIdorg.apache.maven/groupId artifactIdmaven-aether-provider/artifactId version3.0-SNAPSHOT/version /dependency which is in my opinion not ok ? May be i misunderstand things... An other little issue is that if i try to compile the aether-demo via adding the demo into parent modules list it won't be compiled, cause there are references to internal classes: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project aether-demo: Compilation failure: Compilation failure: /Users/km/ws-git/sonatype-aether/aether-demo/src/main/java/demo/RepoSys.java:[18,43] package org.apache.maven.repository.internal does not exist /Users/km/ws-git/sonatype-aether/aether-demo/src/main/java/demo/RepoSys.java:[116,8] cannot find symbol symbol : class DefaultServiceLocator location: class demo.RepoSys /Users/km/ws-git/sonatype-aether/aether-demo/src/main/java/demo/RepoSys.java:[116,44] cannot find symbol symbol : class DefaultServiceLocator location: class demo.RepoSys - [Help 1] So i have two questions: Where can i put such issues ? Does an JIRA existing for the Aether project already ? Or did i oversight informations on the github site ? Was the aether-demo intended not to work at the moment ? (cause it's bleeding edge of Aether)... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
