Note: I posted to users list and did not get a reply. So incase
developers know something. This is stopping me from submitting a patch
for SCM-261 as i cannot test it in linux environment. Will somebody be
able to give some clues.
Hi,
Platform OS: RHEL 5
Java: 1.6.0_17
Maven: 2.1.0
Maven SCM: 1
Issue Subscription
Filter: Design & Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Hi,
We solved 29 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&styleName=Html&version=14324
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11146&status=1
Staging repo:
https://repository.apache.org/co
I totally agree. Apart from saving you lots of bandwidth a repository manager
will also allow you to host artifacts that can not live on repo1 like
proprietary jdbc drivers and so on. You will also be able to release your
internal libraries to it and therefore share them better amongst your team an
Far better is just to run a maven repository manager at your site.
e.g. nexus, artifactory, etc
They are easy to set up (at least I find nexus trivial)
They will permanently cache all the artifacts that you use, which should
meet your requirements and save you from chasing the 70GB+ of rsync
-S
To whom it may concern,
I am currently working at National Cancer Institute. They have a policy
related to build processes that all resources used to build code at NCI need
to be hosted locally. Several months ago we started rsyncing the ibiblio
mirror site locally (rsync -v -t -l -r --exclu
