brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From CMoH <...@git.apache.org>
Subject [GitHub] incubator-brooklyn pull request: Brooklyn OSGification - step 1 (b...
Date Tue, 27 Oct 2015 13:53:11 GMT
Github user CMoH commented on the pull request:

    https://github.com/apache/incubator-brooklyn/pull/962#issuecomment-151502990
  
    I'm trying to build right now on my machine using the same maven arguments as I have seen
in jenkins' console output. So far maven-3.3.3 built the project successfully. maven-3.0.4
failed the first build at the brooklyn-policy project, and a second run (again with a clean
repo) produced a successful build (including the karaf assembly, everything). Maybe it's a
non-deterministic failure? Has 
    
    Here is my test command: `mvn -B -f /home/cipi/src/incubator-brooklyn/pom.xml -Dmaven.repo.local=/home/cipi/.m2tmp/0
--also-make clean install`
    
    As far as I can see, the error can occur from two places, which can be seen in the log:
    
    1. brooklyn-features generates the features.xml using karaf-maven-plugin and install it
as an artifact in the maven repo as seen here in the log:
    
    ```
    [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ brooklyn-features ---
    [INFO] No primary artifact to install, installing attached artifacts instead.
    [INFO] Installing /jenkins/workspace/incubator-brooklyn-master-build/karaf/features/pom.xml
to /jenkins/maven-repositories/0/org/apache/brooklyn/brooklyn-features/0.9.0-SNAPSHOT/brooklyn-features-0.9.0-SNAPSHOT.pom
    [INFO] Installing /jenkins/workspace/incubator-brooklyn-master-build/karaf/features/target/feature/feature.xml
to /jenkins/maven-repositories/0/org/apache/brooklyn/brooklyn-features/0.9.0-SNAPSHOT/brooklyn-features-0.9.0-SNAPSHOT-features.xml
    ```
    
    2. The karaf assembly project "apache-brooklyn" tries to locate the above artifact through
karaf-maven-plugin, but fails to retrieve it from the maven repository:
    
    ```
    [WARNING] Error resolving artifactorg.apache.brooklyn:brooklyn-features:xml:features:0.9.0-SNAPSHOT:Could
not find artifact org.apache.brooklyn:brooklyn-features:xml:features:0.9.0-SNAPSHOT
    shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact
org.apache.brooklyn:brooklyn-features:xml:features:0.9.0-SNAPSHOT
    	at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
    ........
    Caused by: shaded.org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find
artifact org.apache.brooklyn:brooklyn-features:xml:features:0.9.0-SNAPSHOT
    ```
    
    I cannot spot any logical errors at this level, but I would like to look at the files
on the build machine and see if features.xml is actually installed in the repository, so we
can determine if the error occurs at step 1 or step 2. Can someone with access rights verify
this? If it is there, we need to determine why the installed artifact is not retrievable (NFS
mount? plugin bug? plugin bug on maven-3.0.4?)
    
    @ahgittin I'll start addressing your comments in the meantime.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message