Hi  Tim,
This is my settings.xml.
Please help to to check is there any problem? Because i had follow the website 
that u gave me but i still can't fix this problem.
Thanks

> Date: Tue, 8 Jun 2010 10:48:53 -0500
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: [Dspace-tech] dspace -mvn package
> 
> Hi,
> 
> It still looks like to me that you may need to modify your proxy 
> settings.  If you look at the first "WARNING" message, it initially has 
> trouble downloading this file:
> 
> http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-11/doxia-1.0-alpha-11.pom
> 
> That file downloads fine for me (both via Maven or just by using a web 
> browser).  Are you able to access that file via your web browser?  You 
> could also try and see if you can access that file from your 
> command-line, by running:
> 
> curl 
> http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-11/doxia-1.0-alpha-11.pom
> 
> (NOTE: I recommend using 'curl', as the Maven repository specifically 
> blocks all 'wget' requests.  If you have 'curl' installed, you should be 
> able to see the XML contents of that file.)
> 
> If you are unable to access this file, then that means you likely have a 
> local firewall which is blocking your requests.  The only way to get 
> around your local firewall is to either (a) disable the firewall (if you 
> are allowed to), or (b) setup a proxy (recommended).
> 
> Take a closer look at your Maven "settings.xml" file (usually at 
> ~/.m2/settings.xml).  You may need to setup a proxy in that file, 
> similar to the instructions here:
> http://www.dspace.org/1_6_1Documentation/ch03.html#N106E6
> 
> If you are still having issues, you could also try to run Maven with the 
> "-e" switch (as it suggests below the error messages).  Doing that will 
> cause maven to report more information about the specific error.  You'd 
> just run this as follows:
> 
> mvn -e package
> 
> 
> - Tim
> 
> 
> On 6/8/2010 9:30 AM, see choon wrote:
> >
> > Hi all,
> >
> > May i know what is this problem here? I'm still having problem on
> > $ mvn package
> >
> > This is the output that i get [as shown below]
> >
> > ubu...@ubuntu-desktop:/usr/local/dspace/dspace-1.6.1-release/dspace$ mvn
> > package[INFO] Scanning for projects...
> > [INFO] Reactor build order:
> > [INFO] DSpace Addon Modules
> > [INFO] DSpace XML-UI (Manakin) :: Web Application
> > [INFO] DSpace LNI :: Web Application
> > [INFO] DSpace OAI :: Web Application
> > [INFO] DSpace JSP-UI :: Web Application
> > [INFO] DSpace SWORD :: Web Application
> > [INFO] DSpace SOLR :: Web Application
> > [INFO] DSpace Assembly and Configuration
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Building DSpace Addon Modules
> > [INFO] task-segment: [package]
> > [INFO]
> > ------------------------------------------------------------------------
> > Downloading:
> > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-11/doxia-1.0-alpha-11.pom
> > [WARNING] Unable to get resource
> > 'org.apache.maven.doxia:doxia:pom:1.0-alpha-11' from repository central
> > (http://repo1.maven.org/maven2): Error transferring file: repo1.maven.org
> > Downloading:
> > http://download.java.net/maven/2/org/apache/maven/doxia/doxia/1.0-alpha-11/doxia-1.0-alpha-11.pom
> > [WARNING] Unable to get resource
> > 'org.apache.maven.doxia:doxia:pom:1.0-alpha-11' from repository java.net
> > (http://download.java.net/maven/2): Error transferring file:
> > download.java.net
> > Downloading:
> > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-11/doxia-1.0-alpha-11.pom
> > [WARNING] Unable to get resource
> > 'org.apache.maven.doxia:doxia:pom:1.0-alpha-11' from repository central
> > (http://repo1.maven.org/maven2): Error transferring file: repo1.maven.org
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Error building POM (may not be this project's POM).
> >
> >
> > Project ID: null:doxia-modules:pom:null
> >
> > Reason: Cannot find parent: org.apache.maven.doxia:doxia for project:
> > null:doxia-modules:pom:null for project null:doxia-modules:pom:null
> >
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 2 seconds
> > [INFO] Finished at: Tue Jun 08 22:22:19 MYT 2010
> > [INFO] Final Memory: 7M/17M
> > [INFO]
> > ------------------------------------------------------------------------
> > ------------------------------------------------------------------------
> > From: [email protected]
> > To: [email protected]
> > CC: [email protected]
> > Date: Sat, 5 Jun 2010 00:38:32 -0400
> > Subject: Re: [Dspace-tech] dspace -mvn package
> >
> > See,
> >
> > What is the end of the output from the mvn package command? Typically
> > there are a number of messages saying that the artifact can't be found
> > because all defined repositories are checked for dependencies.
> >
> > The end of the output after these lines should provide hints as to why
> > the build stopped.
> >
> >
> >
> > --
> > sands fish
> > Software Engineer
> > MIT Libraries
> > Technology Research & Development
> > [email protected] <mailto:[email protected]>
> > E25-131
> >
> >
> >
> >
> > On Jun 5, 2010, at 12:23 AM, see choon wrote:
> >
> >     Hi,
> >
> >     I would use DSpace to build a digital library.However,after i finish
> >     install all the prerequisite,and install DSpace.
> >     I facing problem in installing DSpace.
> >
> >     Below is the prerequisite i had installed:
> >
> >     operating system that used : Ubuntu 9.10
> >     Java version : jdk1.6.0_20
> >     maven used : apache-maven-2.2.1
> >     ant version : apache-ant-1.8.1
> >     tomcat version : apache-tomcat-5.5.29
> >     DSpace version : dspace-1.6.1-release
> >
> >     When i had done step and reach command
> >     $ mvn package
> >     It will download a lot of packages. After a few minutes,it will stop
> >     here [shown below]
> >
> >     Downloading:
> >     
> > http://download.java.net/maven/2/org/apache/maven/doxia/doxia-module-fml/1.0-alpha-11/doxia-module-fml-1.0-alpha-11.jar
> >     [INFO] Unable to find resource
> >     'org.apache.maven.doxia:doxia-module-fml:jar:1.0-alpha-11' in
> >     repository java.net <http://java.net> (http://download.java.net/maven/2)
> >     Downloading:
> >     
> > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-module-fml/1.0-alpha-11/doxia-module-fml-1.0-alpha-11.jar
> >
> >     Downloading:
> >     
> > http://download.java.net/maven/2/org/apache/maven/doxia/doxia-module-xdoc/1.0-alpha-11/doxia-module-xdoc-1.0-alpha-11.jar
> >     [INFO] Unable to find resource
> >     'org.apache.maven.doxia:doxia-module-xdoc:jar:1.0-alpha-11' in
> >     repository java.net <http://java.net> (http://download.java.net/maven/2)
> >     Downloading:
> >     
> > http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-module-xdoc/1.0-alpha-11/doxia-module-xdoc-1.0-alpha-11.jar
> >
> >
> >     I had tried for many time and even formating my desktop to reinstall
> >     all the prerequisite, but i still having problem in this step. Is it
> >     the website having problem to let my terminal to download those
> >     packages or any other problem?
> >
> >     ps: i found that many others package also fail to downloaded
> >
> >     Hope you can help.Urgent
> >     Thanks
> >     ------------------------------------------------------------------------
> >     Hotmail: Powerful Free email with security by Microsoft. Get it now.
> >     <https://signup.live.com/signup.aspx?id=60969>
> >     <ATT00001.c><ATT00002.c>
> >
> >
> >
> > ------------------------------------------------------------------------
> > Hotmail: Free, trusted and rich email service. Get it now.
> > <https://signup.live.com/signup.aspx?id=60969>
> >
> >
> >
> > ------------------------------------------------------------------------------
> > ThinkGeek and WIRED's GeekDad team up for the Ultimate
> > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> > lucky parental unit.  See the prize list and enter to win:
> > http://p.sf.net/sfu/thinkgeek-promo
> >
> >
> >
> > _______________________________________________
> > DSpace-tech mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/dspace-tech
                                          
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
https://signup.live.com/signup.aspx?id=60969
<?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
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ~/.m2/repository
  <localRepository>/path/to/local/repo</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>false</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>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>dspace</username>
      <password>88050831</password>
      <host>www.unimas.my</host>
      <port>8080</port>
      <nonProxyHosts>www.google.com|some.host.com</nonProxyHosts>
    </proxy>
 </proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
     -->

  <!-- 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>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to