As a test, I've ran $ mvn deploy on our rave-master-pom project, which now is
available here:
https://repository.apache.org/snapshots/org/apache/rave/rave-master/0.1-incubating-SNAPSHOT/
This means, you no longer need to separately build the rave-master-pom first
before being able to build the rave-project itself as long as the deployed
SNAPSHOT is up to date.
I don't think its very useful to enable automatic SNAPSHOT deployment to Nexus
until someone actually wants to build on top or integrate with rave-project, so
for the time being I think occasional manual deployment is good enough.
But at least we now can, and flipping the switch on the Jenkins jobs to also do
a SNAPSHOT deployment is trivial to do when so desired.
Ate
-------- Original Message --------
Subject: [jira] [Closed] (INFRA-3572) Enable Nexus Access For Rave (Incubating)
Date: Tue, 26 Apr 2011 15:01:04 +0000 (UTC)
From: Brian Demers (JIRA) <[email protected]>
Reply-To: [email protected]
To: [email protected]
[
https://issues.apache.org/jira/browse/INFRA-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Demers closed INFRA-3572.
-------------------------------
Resolution: Fixed
Assignee: Brian Demers (was: Brian Fox)
See: http://www.apache.org/dev/publishing-maven-artifacts.html
Enable Nexus Access For Rave (Incubating)
-----------------------------------------
Key: INFRA-3572
URL: https://issues.apache.org/jira/browse/INFRA-3572
Project: Infrastructure
Issue Type: Task
Security Level: public(Regular issues)
Components: Nexus
Reporter: Ate Douma
Assignee: Brian Demers
Priority: Blocker
Project URL: http://incubator.apache.org/rave
SVN URL: http://svn.apache.org/repos/asf/incubator/rave
Maven Group Ids: org.apache.rave
Managed By This TLP Project: Incubator
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
