Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: Repository Support 2010
-
Component/s: Maven Builds
-
Labels:None
Description
There are a number of projects which have dependencies on non-jboss
maven repos (jboss-osgi is one of them)
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235779#4235779
I believe, this issue is general enough to have proper repo aggregation
setup somehow
Here is a link to some aggregators
http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix
Is this a way you want to move forward or should we stick with manually copying individual artefacts to the jboss repo?
Please note, that by doing so (i.e. mvn deploy-file) you loose the original pom and hence the information on transitive dependencies.
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
Gliffy Diagrams
Attachments
Issue Links
- is blocked by
-
ORG-237 Provide hardware for a maven proxy server which can be used by the project builds.
-
- Done
-