Build error

[Priya S]

Hi,

Suddenly while running mvn package, the following error has occurred. (It was absolutely fine till friday) Could you please tell me how to solve this?.

Thanks
P

[INFO] ------------------------------------------------------------------------
[INFO] Building Dryad :: Customized API and Implementation
[INFO]    task-segment: [package]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] snapshot com.atmire:atmire-workflow:1.6.2-SNAPSHOT: checking for updates from maven.dspace.org-snapshot
[WARNING] repository metadata for: 'snapshot com.atmire:atmire-workflow:1.6.2-SNAPSHOT' could not be retrieved from repository: maven.dspace.org-snapshot due to an error: Error transferring file: maven.dspace.org
[INFO] Repository 'maven.dspace.org-snapshot' will be blacklisted
[INFO] snapshot com.atmire:atmire-workflow:1.6.2-SNAPSHOT: checking for updates from atmire.com-releases
[WARNING] repository metadata for: 'snapshot com.atmire:atmire-workflow:1.6.2-SNAPSHOT' could not be retrieved from repository: atmire.com-releases due to an error: Authorization failed: Access denied to: https://atmire.com/artifactory/atmire.com-releases/com/atmire/atmire-workflow/1.6.2-SNAPSHOT/maven-metadata.xml
[INFO] Repository 'atmire.com-releases' will be blacklisted
Downloading: http://maven.dspace.org/snapshot/org/dspace/discovery/discovery-modules/0.9.4-SNAPSHOT/discovery-modules-0.9.4-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: org.dspace.discovery:discovery-solr-provider:jar:0.9.4-SNAPSHOT

Reason: Cannot find parent: org.dspace.discovery:discovery-modules for project: org.dspace.discovery:discovery-solr-provider:jar:0.9.4-SNAPSHOT for project org.dspace.discovery:discovery-solr-provider:jar:0.9.4-SNAPSHOT


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Mon May 07 14:14:09 CEST 2012
[INFO] Final Memory: 30M/72M
[INFO] ------------------------------------------------------------------------

[Priya S]

Hi, Could you please tell me if there is any workaround for the below, like, tell maven to skip the download and build,deploy with existing files?.  (The site https://atmire.com/artifactory/atmire.com-releases/com/atmire/atmire-workflow/1.6.2-SNAPSHOT/maven-metadata.xml is expecting the login credentials now)

Thanks
P

[Ryan Scherle]

If you are using the -U switch for maven, try omitting it. 

-- Ryan

--
You received this message because you are subscribed to the Google Groups "dryad-dev" group.
To post to this group, send email to drya...@googlegroups.com.
To unsubscribe from this group, send email to dryad-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dryad-dev?hl=en.

[Priya S]

Hi Ryan,

I am just running "mvn package".

-P

[Priya S]

Hi,

Any idea how to solve this?. I was running mvn package , without -U switch.

-P

[Priya S]

Looks like atmire.com add on modules are now commercialised, thats what I understood from the website. would be great if anyone could tell me how to solve this.

rgds
P

[Mark Diggory]

Ryan and Priya

Actually, the Workflow was contributed to the Community and all source for any customizations used in Dryad are in its project directories.  There is no private source present there.  The use of the atmire repository was to enable distribution of the addons until this contribution was completed initially to assure the same version of the module was being used across all our projects.

Dryad code should not require accessing the atmire.com repositories as a copy of the workflow codebase is also distributed within the modules of Dryad.

Note, peppered throughout the Dryad poms are references to the old maven snapshot repository which is no longer in use.

<repositories>

<repository>

<id>maven.dspace.org-snapshot</id>

<name>DSpace Maven Snapshot Repository</name>

<url>http://maven.dspace.org/snapshot</url>

<releases>

<enabled>false</enabled>

<checksumPolicy>fail</checksumPolicy>

</releases>

<snapshots>

<enabled>true</enabled>

<checksumPolicy>fail</checksumPolicy>

</snapshots>

</repository>

as well as one reference to the atmire maven repository

<repository>

<id>atmire-open-repo</id>

<name>Atmire Open Maven Snapshot Repository</name>

<url>http://atmire.com/maven-repo</url>

<releases>

<enabled>true</enabled>

<checksumPolicy>warn</checksumPolicy>

</releases>

<snapshots>

<enabled>true</enabled>

<updatePolicy>never</updatePolicy>

<checksumPolicy>warn</checksumPolicy>

</snapshots>

</repository>

</repositories>

We will want to strip all these out of the existing poms.  This has slipped through in the past for the Dryad case because we configured maven internally to support access to the atmire repo during build processes, something that external users are not going to be able to access.

Mark

Mark Diggory (Schedule a Meeting) 2888 Loker Avenue East, Suite 305, Carlsbad, CA. 92010 Esperantolaan 4, Heverlee 3001, Belgium http://www.atmire.com

[Priya S]

Hi,

Thank you for the reply. I am very much new to this project, whenever I modify the code, I used to run mvn package...As its stuck with build error, now I have no clue on how to proceed further.

>Dryad code should not require accessing the atmire.com repositories as a copy of the >workflow codebase is also distributed within the modules of Dryad.

In this case, how to make the build process successful...Could you please help me out??

Your help is greatly appreciated.

Thanks and regards
Priya

[Ryan Scherle]

Hi Priya,

As Mark mentioned, these dependencies are in place due to the way the workflow system was developed. Now that the workflow has been integrated into the core DSpace, we will be removing the dependencies from the Dryad codebase. This process may take a bit of time, though.

One thing you can try: go through all of the pom files, and remove the dependencies for this snapshot file. Since presumably you already have the associated jar file available, maven may compile everything properly. (Though I'm not an expert on maven; it doesn't always do what I want.)

You may also want to verify your pom files against the current files in the Dryad codebase. It is likely that there have been changes since you made your snapshot of the Dryad code.

--- Ryan