Re: using Local repository while building jenkins using maven
Benson Margulies
that is online to collect all the pieces you need offline.
running dependency:go-offline on such a machine will haul everything
into the local repo, which you can then copy to the 'inside'.
In general, disconnected building of maven projects is a large and
costly undertaking.
On Wed, Aug 3, 2011 at 9:15 AM, Dileep mankada <pdile...@gmail.com> wrote:
> Hi all,
>
> Am buikding jenkins in offline mode.. but it is showing error stating
> that It cannot find parent... How to point to local repository in
> pom.xml and settings.xml? and where i will get all the dependencies to
> store in local repository.
>
>
> Please help me.. am in big truoble.. trying for the last two days
>
> Any help will be greatly appreciated
>
> Am copying my files below.........
>
> POM.xml in jenkins source folder
> ..................................................
> <?xml version="1.0" encoding="UTF-8"?>
> <!--
> The MIT License
>
> Copyright (c) 2004-2011, Sun Microsystems, Inc., Kohsuke Kawaguchi,
> id:sorokh
>
> Permission is hereby granted, free of charge, to any person obtaining
> a copy
> of this software and associated documentation files (the "Software"),
> to deal
> in the Software without restriction, including without limitation the
> rights
> to use, copy, modify, merge, publish, distribute, sublicense, and/or
> sell
> copies of the Software, and to permit persons to whom the Software is
> furnished to do so, subject to the following conditions:
>
> The above copyright notice and this permission notice shall be
> included in
> all copies or substantial portions of the Software.
>
> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> EXPRESS OR
> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY,
> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
> SHALL THE
> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
> ARISING FROM,
> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
> IN
> THE SOFTWARE.
> -->
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://
> www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://
> maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
>
> <parent>
> <groupId>org.jenkins-ci</groupId>
> <artifactId>jenkins</artifactId>
> <version>1.22</version>
> </parent>
>
> <groupId>org.jenkins-ci.main</groupId>
> <artifactId>pom</artifactId>
> <version>1.426-SNAPSHOT</version>
> <packaging>pom</packaging>
>
> <name>Jenkins main module</name>
> <description>The module that constitutes the main jenkins.war</
> description>
> <licenses>
> <license>
> <name>The MIT license</name>
> <url>http://www.opensource.org/licenses/mit-license.php</url>
> <distribution>repo</distribution>
> </license>
> </licenses>
>
> <modules>
> <module>core</module>
> <module>maven-plugin</module>
> <module>ui-samples-plugin</module>
> <module>war</module>
> <module>test</module>
> <module>cli</module>
> </modules>
>
> <scm>
> <connection>scm:git:git://github.com/jenkinsci/jenkins.git</
> connection>
> <developerConnection>scm:git:ssh://g...@github.com/jenkinsci/
> jenkins.git</developerConnection>
> <url>https://github.com/jenkinsci/jenkins</url>
> </scm>
> <distributionManagement>
> <site>
> <id>hudson-www</id>
> <url>scp://jenkins-ci.org/home/kohsuke/www/hudson-labs.org/maven-
> site/</url>
> </site>
> <snapshotRepository>
> <id>maven.jenkins-ci.org</id>
> <url>http://maven.jenkins-ci.org:8081/content/repositories/
> snapshots</url>
> </snapshotRepository>
> </distributionManagement>
>
> <properties>
> <!-- *.html files are in UTF-8, and *.properties are in
> iso-8859-1, so this configuration is acturally incorrect,
> but this suppresses a warning from Maven, and as long as we don't
> do filtering we should be OK. -->
> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> <build.type>private</build.type>
> </properties>
>
> <repositories>
> <repository>
> <id>my-local-repository</id>
> <url>c:/Dileep/LocalRepo</url>
> </repository>
> </repositories>
> <pluginRepositories>
> <pluginRepository>
> <id>m.g.o-public</id>
> <url>http://maven.glassfish.org/content/groups/public</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>false</enabled>
> </snapshots>
> </pluginRepository>
> </pluginRepositories>
>
> <dependencyManagement>
> <dependencies>
>
> <dependency>
> <groupId>org.apache.ant</groupId>
> <artifactId>ant</artifactId>
> <version>1.8.0</version>
> </dependency>
>
> <dependency>
> <groupId>commons-io</groupId>
> <artifactId>commons-io</artifactId>
> <version>1.4</version>
> </dependency>
>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.8.1</version>
> </dependency>
>
> <dependency>
> <groupId>commons-httpclient</groupId>
> <artifactId>commons-httpclient</artifactId>
> <version>3.1</version>
> </dependency>
>
> <dependency>
> <groupId>org.jenkins-ci.main</groupId>
> <artifactId>remoting</artifactId>
> <version>2.4</version>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> <dependency>
> <!-- for JRE requirement check annotation -->
> <groupId>org.jvnet</groupId>
> <artifactId>animal-sniffer-annotation</artifactId>
> <version>1.0</version>
> <optional>true</optional><!-- no need to have this at runtime --
>>
> </dependency>
> <dependency>
> <groupId>org.jvnet.hudson</groupId>
> <artifactId>test-annotations</artifactId>
> <version>1.0</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
>
> <build>
> <defaultGoal>install</defaultGoal>
> <resources>
> <resource>
> <directory>${basedir}/src/main/resources</directory>
> <filtering>false</filtering>
> </resource>
> <resource>
> <directory>${basedir}/src/filter/resources</directory>
> <filtering>true</filtering>
> </resource>
> </resources>
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>build-helper-maven-plugin</artifactId>
> <version>1.7</version>
> <executions>
> <execution>
> <id>timestamp-property</id>
> <goals>
> <goal>timestamp-property</goal>
> </goals>
> <configuration>
> <name>now</name>
> <pattern>MM/dd/yyyy HH:mm z</pattern>
> <locale>en_US</locale>
> </configuration>
> </execution>
> <execution>
> <id>version-property</id>
> <goals>
> <goal>regex-property</goal>
> </goals>
> <configuration>
> <name>build.version</name>
> <value>${project.version}</value>
> <regex>-SNAPSHOT</regex>
> <replacement>-SNAPSHOT (${build.type}-${now}-$
> {user.name})</replacement>
> <failIfNoMatch>false</failIfNoMatch>
> </configuration>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <groupId>org.kohsuke.gmaven</groupId>
> <artifactId>gmaven-plugin</artifactId>
> <version>1.0-rc-5-patch-2</version>
> <dependencies>
> <dependency><!-- this needs to be visible to Ant inside
> GMaven, so has to be a plugin dependency -->
> <groupId>org.apache.ant</groupId>
> <artifactId>ant-junit</artifactId>
> <version>1.7.0</version>
> </dependency>
> <dependency>
> <groupId>net.sourceforge.cobertura</groupId>
> <artifactId>cobertura</artifactId>
> <version>1.9</version>
> </dependency>
> <dependency>
> <!-- this provided scope dependency doesn't get added to
> GMaven unless explicitly added here -->
> <groupId>javax.servlet</groupId>
> <artifactId>servlet-api</artifactId>
> <version>2.4</version>
> </dependency>
> </dependencies>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-deploy-plugin</artifactId>
> <version>2.6</version>
> </plugin>
> <plugin>
> <artifactId>maven-gpg-plugin</artifactId>
> <version>1.2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-install-plugin</artifactId>
> <version>2.3.1</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-javadoc-plugin</artifactId>
> <version>2.8</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.3.1</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.1.1</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.8.1</version>
> <configuration>
> <systemPropertyVariables>
> <java.io.tmpdir>${project.build.directory}</
> java.io.tmpdir>
> <forkedProcessTimeoutInSeconds>3600</
> forkedProcessTimeoutInSeconds>
> </systemPropertyVariables>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <version>2.3</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <version>2.2.1</version>
> </plugin>
> <plugin>
> <artifactId>maven-jarsigner-plugin</artifactId>
> <version>1.2</version>
> <configuration>
> <!--
> during the development, debug profile will cause
> the jars to be signed by a self-certified dummy public
> key.
>
> For release, you should define the real values in ~/.m2/
> settings.xml
> -->
> <alias>${hudson.sign.alias}</alias>
> <storepass>${hudson.sign.storepass}</storepass>
> <keystore>${hudson.sign.keystore}</keystore>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-resources-plugin</artifactId>
> <version>2.5</version>
> </plugin>
> <plugin>
> <!--
> Both test harness and core uses stapler as an extension,
> and apparently without having extension preloaded at the
> parent, the main artifact of the 'test' module
> ends up installed with 'stapler-jar' extension (which
> normally is an indication that the ArtifactTypeHandler
> defined in this extension is not getting picked up.)
>
> To avoid this problem, I'm defining an extension here. Not
> sure if the nested <dependencies> is necessary.
> It's also possible that I misdiagnosed the problem and the
> root cause is something entirely different.
>
> To test if you can remove this work around, do a rebuild
> from main and see if the test harness
> is installed with the right extension into the local
> repository.
> -->
> <groupId>org.kohsuke.stapler</groupId>
> <artifactId>maven-stapler-plugin</artifactId>
> <version>1.16</version>
> <extensions>true</extensions>
> <dependencies>
> <dependency>
> <groupId>org.jvnet.maven-jellydoc-plugin</groupId>
> <artifactId>maven-jellydoc-plugin</artifactId>
> <version>1.4</version>
> </dependency>
> </dependencies>
> </plugin>
> <plugin>
> <groupId>org.kohsuke</groupId>
> <artifactId>access-modifier-checker</artifactId>
> <version>1.0</version>
> </plugin>
> <plugin>
> <groupId>com.cloudbees</groupId>
> <artifactId>maven-license-plugin</artifactId>
> <version>1.3</version>
> <executions>
> <execution>
> <goals>
> <goal>process</goal>
> </goals>
> <phase>compile</phase>
> <configuration>
> <requireCompleteLicenseInfo>true</
> requireCompleteLicenseInfo>
> <script>../licenseCompleter.groovy</script>
> </configuration>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <!-- see http://maven-junit-plugin.kenai.com/ for more info
> -->
> <groupId>org.kohsuke</groupId>
> <artifactId>maven-junit-plugin</artifactId>
> <version>1.9</version>
> </plugin>
> <plugin>
> <groupId>org.jvnet.localizer</groupId>
> <artifactId>maven-localizer-plugin</artifactId>
> <version>1.12</version>
> </plugin>
> <plugin>
> <groupId>org.jvnet.hudson.tools</groupId>
> <artifactId>maven-encoding-plugin</artifactId>
> <version>1.1</version>
> </plugin>
> <plugin>
> <groupId>com.infradna.tool</groupId>
> <artifactId>bridge-method-injector</artifactId>
> <version>1.4</version>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>antlr-maven-plugin</artifactId>
> <version>2.1</version>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>apt-maven-plugin</artifactId>
> <version>1.0-alpha-4</version>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>cobertura-maven-plugin</artifactId>
> <version>2.5</version>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> <version>2.3.2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-pmd-plugin</artifactId>
> <version>2.5</version>
> </plugin>
> <plugin>
> <!-- this is really just a patched version of maven-jetty-
> plugin to workaround issue #932 -->
> <groupId>org.jenkins-ci.tools</groupId>
> <artifactId>maven-jenkins-dev-plugin</artifactId>
> <version>6.1.26-jenkins-2</version>
> </plugin>
> <plugin>
> <groupId>org.jvnet.updatecenter2</groupId>
> <artifactId>maven-makepkgs-plugin</artifactId>
> <version>0.5.1</version>
> </plugin>
> <plugin>
> <groupId>org.jenkins-ci.tools</groupId>
> <artifactId>maven-hpi-plugin</artifactId>
> <version>1.74</version>
> </plugin>
> </plugins>
> </pluginManagement>
>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>build-helper-maven-plugin</artifactId>
> </plugin>
> <plugin>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.1</version>
> <configuration>
> <!-- enable release profile during the release, create IPS
> package, and sign bits. -->
> <prepareVerifyArgs>-P release,sign</prepareVerifyArgs>
> <!-- work around for a bug in javadoc plugin that causes the
> release to fail. see MRELEASE-271 -->
> <preparationGoals>clean install</preparationGoals>
> <goals>-DskipTests javadoc:javadoc animal-sniffer:check
> deploy javadoc:aggregate</goals>
> <pushChanges>false</pushChanges>
> <localCheckout>true</localCheckout>
> <tagNameFormat>jenkins-@{project.version}</tagNameFormat>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-remote-resources-plugin</artifactId>
> <version>1.2</version>
> <executions>
> <execution>
> <goals>
> <goal>process</goal>
> </goals>
> <configuration>
> <resourceBundles>
> <resourceBundle>org.jvnet.hudson:license:1.0</
> resourceBundle>
> </resourceBundles>
> </configuration>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <!-- make sure our code doesn't have 1.6 dependencies except
> where we know it -->
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>animal-sniffer-maven-plugin</artifactId>
> <version>1.7</version>
> <configuration>
> <signature>
> <groupId>org.codehaus.mojo.signature</groupId>
> <artifactId>java15</artifactId>
> <version>1.0</version>
> </signature>
> </configuration>
> </plugin>
>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.3.2</version>
> <configuration><!-- we specify this in the parent POM, so this
> is redundant, but otherwise IntelliJ is unhappy -->
> <source>1.5</source>
> <target>1.5</target>
> </configuration>
> </plugin>
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-enforcer-plugin</artifactId>
> <version>1.0</version>
> <executions>
> <execution>
> <goals>
> <goal>enforce</goal>
> </goals>
> <configuration>
> <rules>
> <!-- There is a bug in JDK 1.5's compiler therefore
> need to compile with 1.6 -->
> <requireJavaVersion>
> <version>[1.6.0,]</version>
> </requireJavaVersion>
> </rules>
> </configuration>
> </execution>
> </executions>
> </plugin>
>
> <plugin>
> <!--
> Since some developers try to run hudson-dev:run from main,
> define it here so that at least the plugin resolves.
> This enables us to report a better error message.
> -->
> <groupId>org.jenkins-ci.tools</groupId>
> <artifactId>maven-jenkins-dev-plugin</artifactId>
> <version>6.1.26-jenkins-2</version>
> </plugin>
>
> <!--<plugin>
> <groupId>org.jvnet.fix1600</groupId>
> <artifactId>fix1600</artifactId>
> <executions>
> <execution>
> <goals>
> <goal>fix</goal>
> </goals>
> </execution>
> </executions>
> </plugin>-->
> </plugins>
>
> </build>
>
> <profiles>
> <profile>
> <id>rc</id>
> <properties>
> <build.type>rc</build.type>
> </properties>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>build-helper-maven-plugin</artifactId>
> <executions>
> <execution>
> <id>version-property</id>
> <configuration>
> <replacement>-RC (${now})</replacement>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </profile>
> <profile>
> <id>metrics</id>
> <reporting>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <threshold>High</threshold>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-pmd-plugin</artifactId>
> <version>2.5</version>
> <configuration>
> <!--rulesets>
> <ruleset>ruleset.xml</ruleset>
> </rulesets-->
> <targetJdk>1.5</targetJdk>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <version>2.6</version>
> </plugin>
> </plugins>
> </reporting>
> </profile>
> <profile>
> <id>debug</id>
> <activation>
> <activeByDefault>true</activeByDefault>
> </activation>
> <properties>
> <hudson.sign.alias>jenkins</hudson.sign.alias>
> <hudson.sign.keystore>../dummy.keystore</hudson.sign.keystore>
> <hudson.sign.storepass>jenkins</hudson.sign.storepass>
> </properties>
> </profile>
> <profile>
> <id>sorcerer</id>
> <reporting>
> <plugins>
> <plugin>
> <groupId>org.jvnet.sorcerer</groupId>
> <artifactId>maven-sorcerer-plugin</artifactId>
> <version>0.8</version>
> </plugin>
> </plugins>
> </reporting>
> <build>
> <plugins>
> <plugin>
> <groupId>org.jvnet.sorcerer</groupId>
> <artifactId>maven-sorcerer-plugin</artifactId>
> <version>0.8</version>
> </plugin>
> </plugins>
> </build>
> </profile>
> <profile>
> <id>release</id>
> <build>
> <plugins>
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <inherited>false</inherited>
> <executions>
> <execution>
> <goals>
> <goal>attached</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <finalName>jenkins-${project.version}</finalName>
> <descriptors>
> <descriptor>assembly-src.xml</descriptor>
> </descriptors>
> </configuration>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <artifactId>maven-gpg-plugin</artifactId>
> <executions>
> <execution>
> <id>sign-artifacts</id>
> <phase>verify</phase>
> <goals>
> <goal>sign</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> </profile>
> <profile>
> <id>m2e</id>
> <properties>
> <m2BuildDirectory>target</m2BuildDirectory>
> </properties>
> <activation>
> <property>
> <name>m2e.version</name>
> </property>
> </activation>
> <build>
> <directory>${m2BuildDirectory}</directory>
> <plugins>
> <plugin>
> <groupId>org.maven.ide.eclipse</groupId>
> <artifactId>lifecycle-mapping</artifactId>
> <version>0.12.0</version>
> <configuration>
> <mappingId>customizable</mappingId>
> <configurators>
> <configurator
> id="org.maven.ide.eclipse.jdt.javaConfigurator" />
> <configurator
> id="org.maven.ide.eclipse.plexus.annotations.plexusConfigurator" />
> </configurators>
> <mojoExecutions>
> <mojoExecution>org.apache.maven.plugins:maven-
> resources-plugin::</mojoExecution>
> </mojoExecutions>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> </profiles>
> </project>
> .......................................
> settings.xml in Maven folder
> .........................................
> <?xml version="1.0" encoding="UTF-8"?>
>
> <!--
> Licensed to the Apache Software Foundation (ASF) under one
> or more contributor license agreements. See the NOTICE file
> distributed with this work for additional information
> regarding copyright ownership. The ASF licenses this file
> to you under the Apache License, Version 2.0 (the
> "License"); you may not use this file except in compliance
> with the License. You may obtain a copy of the License at
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing,
> software distributed under the License is distributed on an
> "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> KIND, either express or implied. See the License for the
> specific language governing permissions and limitations
> under the License.
> -->
>
> <!--
> | This is the configuration file for Maven. It can be specified at
> two levels:
> |
> | 1. User Level. This settings.xml file provides configuration for a
> single user,
> | and is normally provided in ${user.home}/.m2/
> settings.xml.
> |
> | NOTE: This location can be overridden with the CLI
> option:
> |
> | -s /path/to/user/settings.xml
> |
> | 2. Global Level. This settings.xml file provides configuration for
> all Maven
> | users on a machine (assuming they're all using the
> same Maven
> | installation). It's normally provided in
> | ${maven.home}/conf/settings.xml.
> |
> | NOTE: This location can be overridden with the CLI
> option:
> |
> | -gs /path/to/global/settings.xml
> |
> | The sections in this sample file are intended to give you a running
> start at
> | getting the most out of your Maven installation. Where appropriate,
> the default
> | values (values used when the setting is not specified) are
> provided.
> |
> |-->
> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> http://maven.apache.org/xsd/settings-1.0.0.xsd">
> <!-- localRepository-->
>
> <localRepository>my-local-repository</localRepository>
>
> <!-- interactiveMode
> | This will determine whether maven prompts you when it needs
> input. If set to false,
> | maven will use a sensible default value, perhaps based on some
> other setting, for
> | the parameter in question.
> |
> | Default: true
> <interactiveMode>true</interactiveMode>
> -->
>
> <!-- offline
> | Determines whether maven should attempt to connect to the network
> when executing a build.
> | This will have an effect on artifact downloads, artifact
> deployment, and others.
> |
> | Default: false
> -->
>
> <offline>true</offline>
>
>
> <!-- pluginGroups
> | This is a list of additional group identifiers that will be
> searched when resolving plugins by their prefix, i.e.
> | when invoking a command line like "mvn prefix:goal". Maven will
> automatically add the group identifiers
> | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are
> not already contained in the list.
> |-->
> <pluginGroups>
> <!-- pluginGroup
> | Specifies a further group identifier to use for plugin lookup.
> <pluginGroup>com.your.plugins</pluginGroup>
> -->
> </pluginGroups>
>
> <!-- proxies
> | This is a list of proxies which can be used on this machine to
> connect to the network.
> | Unless otherwise specified (by system property or command-line
> switch), the first proxy
> | specification in this list marked as active will be used.
> |-->
> <proxies>
> <!-- proxy
> | Specification for one proxy, to be used in connecting to the
> network.
> |
> <proxy>
> <id>optional</id>
> <active>true</active>
> <protocol>http</protocol>
> <username>proxyuser</username>
> <password>proxypass</password>
> <host>proxy.host.net</host>
> <port>80</port>
> <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
> </proxy>
> -->
> </proxies>
>
> <!-- servers
> | This is a list of authentication profiles, keyed by the server-id
> used within the system.
> | Authentication profiles can be used whenever maven must make a
> connection to a remote server.
> |-->
> <servers>
> <!-- server
> | Specifies the authentication information to use when connecting
> to a particular server, identified by
> | a unique name within the system (referred to by the 'id'
> attribute below).
> |
> | NOTE: You should either specify username/password OR privateKey/
> passphrase, since these pairings are
> | used together.
> |
> <server>
> <id>deploymentRepo</id>
> <username>repouser</username>
> <password>repopwd</password>
> </server>
> -->
>
> <!-- Another sample, using keys to authenticate.
> <server>
> <id>siteServer</id>
> <privateKey>/path/to/private/key</privateKey>
> <passphrase>optional; leave empty if not used.</passphrase>
> </server>
> -->
> </servers>
>
> <!-- mirrors
> | This is a list of mirrors to be used in downloading artifacts
> from remote repositories.
> |
> | It works like this: a POM may declare a repository to use in
> resolving certain artifacts.
> | However, this repository may have problems with heavy traffic at
> times, so people have mirrored
> | it to several places.
> |
> | That repository definition will have a unique id, so we can
> create a mirror reference for that
> | repository, to be used as an alternate download site. The mirror
> site will be the preferred
> | server for that repository.
> |-->
> <mirrors>
> <!-- mirror
> | Specifies a repository mirror site to use instead of a given
> repository. The repository that
> | this mirror serves has an ID that matches the mirrorOf element
> of this mirror. IDs are used
> | for inheritance and direct lookup purposes, and must be unique
> across the set of mirrors.
> |
> <mirror>
> <id>mirrorId</id>
> <mirrorOf>repositoryId</mirrorOf>
> <name>Human Readable Name for this Mirror.</name>
> <url>http://my.repository.com/repo/path</url>
> </mirror>
> -->
> </mirrors>
>
> <!-- profiles
> | This is a list of profiles which can be activated in a variety of
> ways, and which can modify
> | the build process. Profiles provided in the settings.xml are
> intended to provide local machine-
> | specific paths and repository locations which allow the build to
> work in the local environment.
> |
> | For example, if you have an integration testing plugin - like
> cactus - that needs to know where
> | your Tomcat instance is installed, you can provide a variable
> here such that the variable is
> | dereferenced during the build process to configure the cactus
> plugin.
> |
> | As noted above, profiles can be activated in a variety of ways.
> One way - the activeProfiles
> | section of this document (settings.xml) - will be discussed
> later. Another way essentially
> | relies on the detection of a system property, either matching a
> particular value for the property,
> | or merely testing its existence. Profiles can also be activated
> by JDK version prefix, where a
> | value of '1.4' might activate a profile when the build is
> executed on a JDK version of '1.4.2_07'.
> | Finally, the list of active profiles can be specified directly
> from the command line.
> |
> | NOTE: For profiles defined in the settings.xml, you are
> restricted to specifying only artifact
> | repositories, plugin repositories, and free-form properties
> to be used as configuration
> | variables for plugins in the POM.
> |
> |-->
> <profiles>
> <!-- profile
> | Specifies a set of introductions to the build process, to be
> activated using one or more of the
> | mechanisms described above. For inheritance purposes, and to
> activate profiles via <activatedProfiles/>
> | or the command line, profiles have to have an ID that is
> unique.
> |
> | An encouraged best practice for profile identification is to
> use a consistent naming convention
> | for profiles, such as 'env-dev', 'env-test', 'env-production',
> 'user-jdcasey', 'user-brett', etc.
> | This will make it more intuitive to understand what the set of
> introduced profiles is attempting
> | to accomplish, particularly when you only have a list of
> profile id's for debug.
> |
> | This profile example uses the JDK version to trigger
> activation, and provides a JDK-specific repo.
> <profile>
> <id>jdk-1.4</id>
>
> <activation>
> <jdk>1.4</jdk>
> </activation>
>
> <repositories>
> <repository>
> <id>jdk14</id>
> <name>Repository for JDK 1.4 builds</name>
> <url>http://www.myhost.com/maven/jdk14</url>
> <layout>default</layout>
> <snapshotPolicy>always</snapshotPolicy>
> </repository>
> </repositories>
> </profile>
> -->
>
> <!--
> | Here is another profile, activated by the system property
> 'target-env' with a value of 'dev',
> | which provides a specific path to the Tomcat instance. To use
> this, your plugin configuration
> | might hypothetically look like:
> |
> | ...
> | <plugin>
> | <groupId>org.myco.myplugins</groupId>
> | <artifactId>myplugin</artifactId>
> |
> | <configuration>
> | <tomcatLocation>${tomcatPath}</tomcatLocation>
> | </configuration>
> | </plugin>
> | ...
> |
> | NOTE: If you just wanted to inject this configuration whenever
> someone set 'target-env' to
> | anything, you could just leave off the <value/> inside
> the activation-property.
> |
> <profile>
> <id>env-dev</id>
>
> <activation>
> <property>
> <name>target-env</name>
> <value>dev</value>
> </property>
> </activation>
>
> <properties>
> <tomcatPath>/path/to/tomcat/instance</tomcatPath>
> </properties>
> </profile>
> -->
> </profiles>
>
> <!-- activeProfiles
> | List of profiles that are active for all builds.
> |
> <activeProfiles>
> <activeProfile>alwaysActiveProfile</activeProfile>
> <activeProfile>anotherAlwaysActiveProfile</activeProfile>
> </activeProfiles>
> -->
>
>
>
>
>
>
>
>
> </settings>
>
>
> Error showing.......
>
> [INFO]
> NOTE: Maven is executing in offline mode. Any artifacts not already in
> your loca
> l
> repository will be inaccessible.
>
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: org.jenkins-ci.main:pom:pom:1.426-SNAPSHOT
>
> Reason: Cannot find parent: org.jenkins-ci:jenkins for project:
> org.jenkins-ci.m
> ain:pom:pom:1.426-SNAPSHOT for project org.jenkins-ci.main:pom:pom:
> 1.426-SNAPSHO
> T
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> org.jenkin
> s-ci:jenkins for project: org.jenkins-ci.main:pom:pom:1.426-SNAPSHOT
> for project
> org.jenkins-ci.main:pom:pom:1.426-SNAPSHOT
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:
> 404)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
> 272)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
> 138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> 0)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot
> find parent: org.jenkins-ci:jenkins for project: org.jenkins-
> ci.main:pom:pom:1.426-SNAPSHOT for project org.jenkins-ci.main:pom:pom:
> 1.426-SNAPSHOT
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:
> 1396)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:
> 823)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:
> 508)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:
> 200)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:
> 604)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:
> 391)
> ... 12 more
> Caused by: org.apache.maven.project.ProjectBuildingException: POM
> 'org.jenkins-ci:jenkins' not found in repository: System is offline.
> org.jenkins-ci:jenkins:pom:1.22
>
>
> for project org.jenkins-ci:jenkins
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:
> 605)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:
> 1392)
> ... 18 more
> Caused by:
> org.apache.maven.artifact.resolver.ArtifactNotFoundException: System
> is offline.
>
> org.jenkins-ci:jenkins:pom:1.22
>
>
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
> 203)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
> 90)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:
> 558)
> ... 19 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Wed Aug 03 18:40:15 IST 2011
> [INFO] Final Memory: 1M/15M
> [INFO]
> ------------------------------------------------------------------------
> C:\Dileep\Jenkins\jenkinsci-jenkins-3e52131>
>
>
>
>