[jboss-jira] [JBoss JIRA] Created: (JBBUILD-619) Build of JBPAPP branch is a pain and doesn't work in any documented way

[jaikiran pai (JIRA)]

Build of JBPAPP branch is a pain and doesn't work in any documented way
-----------------------------------------------------------------------

                 Key: JBBUILD-619
                 URL: https://jira.jboss.org/browse/JBBUILD-619
             Project: JBoss Build System
          Issue Type: Bug
            Reporter: jaikiran pai
            Assignee: Paul Gier


There's a discussion going on about the difficulties faced during the JBPAPP_5_1 branch build with the new maven nexus repo. Here's the initial part of the discussion:

<quote>
I was looking to reproduce an issue on JBPAPP_5_1 branch and did a fresh checkout and triggered a

./build.sh -Dbuild.unsecure=true

The build started downloading the entire internet (again), which was expected because EAP uses a separate local maven repo. After about 2 hours, when I thought it was almost done, I get 47 unresolved artifacts which aren't found in the repo! I digged around a bit and found this page https://docspace.corp.redhat.com/docs/DOC-28787. That wiki says, that in order to build EAP-5.1 branch with the new nexus repo I now additionally have to (again) change my local settings.xml to add a maven-brew repo. I am not sure why each  developer has to do that. Can't it be done in the JBPAPP_5_1/tools/maven/conf/settings.xml and committed to SVN, so that anyone who builds afresh doesn't have to change his local settings.xml?  Also, does anyone know how adding the maven-brew repo to my local settings.xml will affect the other projects (like JBoss AS) which share the same settings? I believe there are differences in the artifacts that are hosted in maven-brew and other publicly available repos?


For now, I have added maven-brew to my local settings.xml and triggered a build (hoping that it'll complete). After around 3-4 hours now, I haven't yet got a setup where I can actually do some work (of reproducing that bug). 
</quote>

<quote>
And down it goes again (after 20 mins) with the following error. Too late to try anything more tonight!


    [java] [INFO] ------------------------------------------------------------------------
    [java] [ERROR] BUILD ERROR
    [java] [INFO] ------------------------------------------------------------------------
    [java] [INFO] Failed to resolve artifact.
    [java]
    [java] Missing:
    [java] ----------
    [java] 1) wutka-dtdparser:dtdparser121:jar:1.2.1
    [java]
    [java]   Try downloading the file manually from the project website.
    [java]
    [java]   Then, install it using the command:
    [java]       mvn install:install-file -DgroupId=wutka-dtdparser -DartifactId=dtdparser121 -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file
    [java]
    [java]   Alternatively, if you host your own repository you can deploy the file there:
    [java]       mvn deploy:deploy-file -DgroupId=wutka-dtdparser -DartifactId=dtdparser121 -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
    [java]
    [java]   Path to dependency:
    [java]     1) org.jboss.jbossas:jboss-as-thirdparty:pom:5.1.0-SNAPSHOT
    [java]     2) org.jboss:jbossxb:jar:2.0.1.GA
    [java]     3) wutka-dtdparser:dtdparser121:jar:1.2.1
    [java]
    [java] ----------
    [java] 1 required artifact is missing.
    [java]
    [java] for artifact:
    [java]   org.jboss.jbossas:jboss-as-thirdparty:pom:5.1.0-SNAPSHOT
    [java]
    [java] from the specified remote repositories:
    [java]   jboss-maven2-brew (http://repository.jboss.org/maven2-brew/),
    [java]   jboss-developer-repository-group (https://repository.jboss.org/nexus/content/groups/developer/)
    [java]
    [java]
    [java] [INFO] ------------------------------------------------------------------------
    [java] [INFO] For more information, run Maven with the -e switch
    [java] [INFO] ------------------------------------------------------------------------
    [java] [INFO] Total time: 31 seconds
    [java] [INFO] Finished at: Sat May 22 00:18:09 IST 2010
    [java] [INFO] Final Memory: 36M/98M
    [java] [INFO] ------------------------------------------------------------------------
    [java] Java Result: 1 
</quote>

Thanks to Shelly, I was able to get the build working by *commenting out* the mirror section in the (common shared) local settings.xml file. However, this clearly is just a workaround and not a solution because:

1) It goes against the wiki document which asks you to use the mirror settings
2) With the mirror settings commented out, I can no longer build my other projects, because those projects share this same settings.xml
3) It's not practical to keep changing this file (or any other file) for each project/each build. 


Ideally, to get the build working, one should just be able to launch ./build.sh (or any single command) and get it working. The current way of changing  the local settings.xml isn't practical. 

Note that, as mentioned earlier, EAP SVN already consists of maven (and a settings.xml file) http://anonsvn.jboss.org/repos/jbossas/branches/JBPAPP_5_1/tools/maven/conf/ so that the build uses a separate maven repo for EAP builds. Why not just update that settings.xml file and commit it to SVN so that each developer will not have to change this local file(s)?
 



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira