Quantcast

glassfish repo must die

classic Classic list List threaded Threaded
28 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: glassfish repo must die

Chris van Es
I don't see anything wrong with specifying a repo which is under developers control in the parent pom. It's a feature of maven and I use this feature regularly within my workplace to force our builds to use a repository manager for all dependencies and keep everything internal. I don't know Jenkins well enough but it might prove useful in future to limit the versions of core dependencies available to plugins.

Chris.

On 5 April 2012 17:43, Kohsuke Kawaguchi <[hidden email]> wrote:
On 04/05/2012 06:03 AM, Stephen Connolly wrote:
   As Nicolas wrote, repo.jenkins-ci.org <http://repo.jenkins-ci.org>

   is our domain that we control, so the same thing won't happen again.

   (There is a separate effort to make more of our artifacts available
   in central, which would eliminate this problem in a long run, but we
   shouldn't wait for that.)


Why not just hurry that effort along ;-)

Are you volunteering?


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: glassfish repo must die

Arnaud Héritier
It was detailled here : http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/

On Fri, Apr 6, 2012 at 12:39 AM, Chris van Es <[hidden email]> wrote:
I don't see anything wrong with specifying a repo which is under developers control in the parent pom. It's a feature of maven and I use this feature regularly within my workplace to force our builds to use a repository manager for all dependencies and keep everything internal. I don't know Jenkins well enough but it might prove useful in future to limit the versions of core dependencies available to plugins.

Chris.


On 5 April 2012 17:43, Kohsuke Kawaguchi <[hidden email]> wrote:
On 04/05/2012 06:03 AM, Stephen Connolly wrote:
   As Nicolas wrote, repo.jenkins-ci.org <http://repo.jenkins-ci.org>

   is our domain that we control, so the same thing won't happen again.

   (There is a separate effort to make more of our artifacts available
   in central, which would eliminate this problem in a long run, but we
   shouldn't wait for that.)


Why not just hurry that effort along ;-)

Are you volunteering?


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins




--
-----
Arnaud Héritier
06-89-76-64-24
Mail/GTalk: [hidden email]
Twitter/Skype : aheritier

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: glassfish repo must die

Chris van Es
Does the comment 

"If you are exposing your source and want to make it easy for others to build, then consider adding a repository entry to your POM, but don’t pick a URL lightly, think long-term, and use a URL that will always be under your control."

not agree with what the other guys have been saying?

Chris.

2012/4/5 Arnaud Héritier <[hidden email]>
It was detailled here : http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/


On Fri, Apr 6, 2012 at 12:39 AM, Chris van Es <[hidden email]> wrote:
I don't see anything wrong with specifying a repo which is under developers control in the parent pom. It's a feature of maven and I use this feature regularly within my workplace to force our builds to use a repository manager for all dependencies and keep everything internal. I don't know Jenkins well enough but it might prove useful in future to limit the versions of core dependencies available to plugins.

Chris.


On 5 April 2012 17:43, Kohsuke Kawaguchi <[hidden email]> wrote:
On 04/05/2012 06:03 AM, Stephen Connolly wrote:
   As Nicolas wrote, repo.jenkins-ci.org <http://repo.jenkins-ci.org>

   is our domain that we control, so the same thing won't happen again.

   (There is a separate effort to make more of our artifacts available
   in central, which would eliminate this problem in a long run, but we
   shouldn't wait for that.)


Why not just hurry that effort along ;-)

Are you volunteering?


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins




--
-----
Arnaud Héritier
06-89-76-64-24
Mail/GTalk: [hidden email]
Twitter/Skype : aheritier


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: glassfish repo must die

Chris van Es
I agree though, that maven central would be much better long term.

On 5 April 2012 23:47, Chris van Es <[hidden email]> wrote:
Does the comment 

"If you are exposing your source and want to make it easy for others to build, then consider adding a repository entry to your POM, but don’t pick a URL lightly, think long-term, and use a URL that will always be under your control."

not agree with what the other guys have been saying?

Chris.

2012/4/5 Arnaud Héritier <[hidden email]>
It was detailled here : http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/


On Fri, Apr 6, 2012 at 12:39 AM, Chris van Es <[hidden email]> wrote:
I don't see anything wrong with specifying a repo which is under developers control in the parent pom. It's a feature of maven and I use this feature regularly within my workplace to force our builds to use a repository manager for all dependencies and keep everything internal. I don't know Jenkins well enough but it might prove useful in future to limit the versions of core dependencies available to plugins.

Chris.


On 5 April 2012 17:43, Kohsuke Kawaguchi <[hidden email]> wrote:
On 04/05/2012 06:03 AM, Stephen Connolly wrote:
   As Nicolas wrote, repo.jenkins-ci.org <http://repo.jenkins-ci.org>

   is our domain that we control, so the same thing won't happen again.

   (There is a separate effort to make more of our artifacts available
   in central, which would eliminate this problem in a long run, but we
   shouldn't wait for that.)


Why not just hurry that effort along ;-)

Are you volunteering?


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins




--
-----
Arnaud Héritier
06-89-76-64-24
Mail/GTalk: [hidden email]
Twitter/Skype : aheritier



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: glassfish repo must die

nicolas de loof-2
I ran a groovy script to checkout plugins (from either git/svn) and fix glassfish vs jenkins-ci.org repositories

it also do a check for declared repositories, assuming we SHOULD not declare them but deploy on jenkins-ci.org or declare additional mirrors there :

--- accurev ---
--- active-directory ---
--- all-changes ---
--- analysis-collector ---
--- analysis-core ---
--- analysis-pom ---
--- analysis-regression-checker ---
--- analysis-suite ---
--- analysis-test ---
--- anchor-chain ---
--- android-emulator ---
--- android-lint ---
--- ansicolor ---
--- ant ---
--- antexec ---
--- any-buildstep ---
--- appaloosa ---
incorrect repository found : joel1di1-mvn-repo::https://github.com/joel1di1/joel1di1-mvn-repo/raw/master/releases/
--- artifactdeployer ---
--- artifactory ---
--- assembla ---
--- associated-files ---
incorrect repository found : kurtharriger-gmaven-snapshots::https://github.com/kurtharriger/gmaven/raw/maven/snapshots
--- audit-trail ---
--- avatar ---
--- backlog ---
incorrect repository found : sardine-google-svn-repo::http://sardine.googlecode.com/svn/maven/
--- backup ---
incorrect repository found : custom::file:///${basedir}/src/repository
--- bamboo-notifier ---
--- batch-task ---
--- bazaar ---
--- beer ---
--- bitkeeper ---
--- blame-upstream-commiters ---
--- BlameSubversion ---
--- brakeman ---
incorrect repository found : java.net2::http://download.java.net/maven/2/
--- browser-axis ---
--- bruceschneier ---
--- buckminster ---
--- bugzilla ---
--- build-flow ---
--- build-keeper ---
--- build-metrics ---
--- build-name-setter ---
--- build-node-column ---
--- build-publisher ---
--- build-timeout ---
--- build-user-vars ---
--- buildcontext-capture ---
--- buildresult-trigger ---
--- builton-column ---
--- bulk-builder ---
--- campfire ---
--- caroline ---
--- cas1 ---
--- cccc ---
--- ccm ---
--- changelog-history ---
--- checkstyle ---
--- chrome-frame ---
--- chromedriver ---
--- chucknorris ---
--- ci-game ---
--- cifs ---
--- claim ---
--- clamav ---
--- clang-scanbuild ---
--- clearcase ---
--- clearcase-release ---
--- clearcase-ucm-baseline ---
--- clearcase-ucm ---
incorrect repository found : praqma-repo::http://code.praqma.net/repo/maven/
--- cli-extras ---
incorrect repository found : ssh-slaves-plugin::https://github.com/hudson-plugins/ssh-slaves-plugin
--- cloudbees-deployer ---
incorrect repository found : oss.sonatype.snapshots::https://oss.sonatype.org/content/groups/public
--- clover ---
incorrect repository found : atlassian::https://maven.atlassian.com/public
--- cloverphp ---
incorrect repository found : powermock-repo::http://powermock.googlecode.com/svn/repo/
--- cmakebuilder ---
--- cmvc ---
--- cobertura ---
--- codecover ---
--- codeplex ---
--- codescanner ---
--- codeviation ---
incorrect repository found : codeviation-libs::file:${project.basedir}/lib
--- collabnet ---
incorrect repository found : collabnet-libs::file:${project.basedir}/lib
--- collapsing-console-sections ---
--- compact-columns ---
--- computer-queue ---
--- concordionpresenter ---
--- conditional-buildstep ---
--- conditional-upstream-trigger ---
--- config-autorefresh ---
--- config-file-provider ---
--- configurationslicing ---
--- confluence-publisher ---
--- console-column ---
--- copy-data-to-workspace-plugin ---
--- copy-project-link ---
--- copy-to-slave ---
--- copyarchiver ---
--- copyartifact ---
--- countjobs-viewstabbar ---
--- covcomplplot ---
incorrect repository found : powermock-repo::http://powermock.googlecode.com/svn/repo/
--- coverage ---
--- coverity ---
incorrect repository found : local::file:///${project.basedir}/repo
--- cppcheck ---
--- cppncss ---
--- cpptest ---
--- cppunit ---
--- crap4j ---
--- create-fingerprint ---
--- createjobadvanced ---
--- credentials ---
--- cron_column ---
--- crowd ---
incorrect repository found : atlassian::https://m2proxy.atlassian.com/repository/public
--- crowd2 ---
incorrect repository found : atlassian::https://m2proxy.atlassian.com/repository/public
--- culprit-report ---
--- customtools ---
--- cvs ---
--- cvs-tag ---
--- cygpath ---
--- darcs ---
--- dashboard-view ---
--- dbCharts ---
--- delta-cloud ---
--- dependency-analyzer ---
--- depgraph-view ---
--- deploy ---
incorrect repository found : glassfish::http://download.java.net/maven/glassfish
--- deploy-websphere ---
incorrect repository found : was-lib::file:${project.basedir}/lib/
--- description-column ---
--- description-setter ---
--- dev-mode ---
--- dimensions ---
--- dimensionsscm ---
incorrect repository found : serena-lib::file:${project.basedir}/lib/
--- disk-usage ---
--- display-upstream-changes ---
--- distfork ---
--- distTest ---
incorrect repository found : maven-repository::http://repo2.maven.org/maven2/
incorrect repository found : maven-repository::http://repo2.maven.org/maven2/
--- doclinks ---
--- dos-trigger ---
--- downstream-buildview ---
--- downstream-ext ---
--- doxygen ---
--- drmemory ---
incorrect repository found : praqma-repo::http://code.praqma.net/repo/maven/
--- drools ---
incorrect repository found : jboss::http://repository.jboss.com/maven2
--- dropdown-viewstabbar ---
--- dry ---
--- dry-run ---
--- dtkit ---
--- dumpinfo-buildwrapper ---
--- easyant ---
--- ec2 ---
--- eggplant ---
--- email-ext ---
incorrect repository found : powermock-repo::http://powermock.googlecode.com/svn/repo/
--- emma ---
--- emmacoveragecolumn ---
--- emotional-hudson ---
--- emotional-jenkins ---
--- envfile ---
--- envinject ---
--- escaped-markup ---
--- exclusion ---
--- exclusive-execution ---
--- extended-choice-parameter ---
--- extended-read-permission ---
--- extra-columns ---
--- ezwall ---
--- fail-the-build ---
--- favorite ---
--- favorite-view ---
--- file-leak-detector ---
--- files-found-trigger ---
--- filesystem_scm ---
--- findbugs ---
--- fit ---
--- fitnesse ---
--- flashlog ---
--- flexible-publish ---
--- flexteam ---
--- fogbugz ---
--- fortify360 ---
--- fstrigger ---
--- ftppublisher ---
--- gallio ---
--- gant ---
--- gcal ---
incorrect repository found : local::file:${project.basedir}/lib
--- gcrawler ---
--- gerrit-trigger ---
--- girls ---
--- git-parameter ---
incorrect repository found : jgit-repository::http://download.eclipse.org/jgit/maven
incorrect repository found : guice-maven::http://guice-maven.googlecode.com/svn/trunk
incorrect repository found : maven.jenkins-ci.org.git::http://maven.jenkins-ci.org/content/repositories/releases/
--- git ---
incorrect repository found : jgit-repository::http://download.eclipse.org/jgit/maven
incorrect repository found : guice-maven::http://guice-maven.googlecode.com/svn/trunk
--- github-api ---
--- github-oauth ---
--- github ---
incorrect repository found : jgit-repository::http://download.eclipse.org/jgit/maven
--- github-sqs ---
--- global-build-stats ---
--- gnat ---
--- google-desktop-gadget ---
--- googleanalytics ---
--- googlecode ---
--- gradle ---
--- grails ---
--- gravatar ---
--- graven ---
--- greenballs ---
--- grinder ---
--- groovy-choice-parameter ---
--- groovy ---
--- groovy-postbuild ---
--- groovyaxis ---
--- growl ---
--- hadoop ---
--- harvest ---
--- heavy-job ---
--- hello-world-groovy ---
--- hello-world-groovy-view ---
--- hello-world ---
--- hgca ---
--- hipchat ---
--- hsts-filter ---
--- html-audio-notifier ---
--- html5-notifier ---
--- htmlpublisher ---
--- hudson-clearcase ---
incorrect repository found : laughing-panda::http://www.laughingpanda.org/maven2/
--- hudson-notifo ---
--- hudsontrayapp ---
--- instant-messaging-parent ---
--- instant-messaging ---
--- integrity ---
--- intellij-jenkins-control ---
--- ion-deployer ---
--- iphoneview ---
incorrect repository found : bacons.ddo.jp repository::http://bacons.ddo.jp/maven2/
--- ipmsg ---
--- ircbot ---
incorrect repository found : jenkins-snapshots::http://maven.jenkins-ci.org:8081/content/repositories/snapshots
--- ivy ---
--- ivy-report ---
--- ivytrigger ---
--- jabber ---
--- japex ---
--- javadoc ---
--- javancss ---
--- javanet ---
--- javanet-realm ---
--- javanet-trigger-installer ---
--- javanet-uploader ---
--- javatest-report ---
--- jboss ---
incorrect repository found : jboss::http://repository.jboss.org/maven2/
--- jbpm ---
--- jcaptcha ---
--- jclouds ---
--- jdepend ---
--- jenkins-clone-workspace-scm ---
--- jenkins-cloudformation ---
--- jigomerge ---
--- jira-issue-updater ---
--- jira-issues-versioning ---
incorrect repository found : powermock-repo::http://powermock.googlecode.com/svn/repo/
--- jira ---
--- jmx-invoker ---
--- jmx ---
--- job-exporter ---
--- job-import ---
--- job-log-logger ---
--- job-poll-action ---
--- jobConfigHistory ---
--- jobinjector ---
--- jobrevision ---
--- jobtype-column ---
--- join ---
--- jprt ---
incorrect repository found : local::file:${project.basedir}/lib
--- jquery ---
--- jquery-ui ---
--- jsgames ---
--- jsunit ---
--- jswidgets ---
--- junit-attachments ---
--- jwsdp-sqe ---
--- jython ---
--- kagemai ---
--- karotz ---
--- kerberos-authenticator ---
--- keyboard-shortcuts ---
--- klaros-testmanagement ---
--- kundo ---
--- label-verifier ---
--- labeled-test-groups-publisher ---
--- labmanager ---
--- lastfailureversioncolumn ---
--- lastsuccessdescriptioncolumn ---
--- lastsuccessversioncolumn ---
--- lavalamp ---
--- ldapemail ---
--- libvirt-slave ---
--- lingr ---
--- list-command ---
--- liverebel-deploy ---
incorrect repository found : jmockit-svn::http://jmockit.googlecode.com/svn/maven-repo
--- local-groovy-cli ---
--- locale ---
--- localization ---
incorrect repository found : acoveo-snapshotrepo::http://acoveo.com/maven2/snapshots
incorrect repository found : acoveo-repo::http://acoveo.com/maven2/repo
--- locked-files-report ---
--- locks-and-latches ---
--- log-parser ---
--- logaction ---
--- m2-extra-steps ---
--- m2-repo-reaper ---
--- m2release ---
--- mail-commander ---
--- major-minor ---
incorrect repository found : jenkins-release-repo::http://maven.jenkins-ci.org:8081/content/groups/artifacts/
--- managed-scripts ---
--- mantis ---
incorrect repository found : jgit-repository::http://eclipse.ialto.org/jgit/maven/
--- mask-passwords ---
--- Matrix-sorter ---
--- matrixtieparent ---
--- maven-dependency-update-trigger ---
--- maven-deployment-linker ---
--- maven-dump-test-dependencies ---
--- maven-hpi ---
--- maven-hudson-dev ---
--- maven-info ---
--- maven-repo-cleaner ---
--- maven-scm ---
--- maven1-snapshot-plugin ---
incorrect repository found : java.net2::https://maven2-repository.dev.java.net/nonav/repository
--- maven3 ---
--- measurement-plots ---
--- memegen ---
--- mercurial ---
--- merge-queue ---
--- mibsr-m2 ---
--- mibsr ---
--- mongodb ---
--- monitoring ---
--- mozmill ---
--- msbuild ---
--- mstest ---
--- mstestrunner ---
--- multi-slave-config ---
incorrect repository found : powermock-repo::http://powermock.googlecode.com/svn/repo/
--- multiline-tabbar-plugin ---
--- multiple-scms ---
--- mysql-auth ---
--- nabaztag ---
--- naginator ---
--- nant ---
--- ncover ---
--- nested-view ---
--- network-monitor ---
--- next-build-number ---
--- next-executions ---
--- nodejs ---
--- nodelabelparameter ---
--- nodenamecolumn ---
--- notification ---
--- nsiqcollector ---
--- nsis ---
--- nunit ---
--- offlineonfailure ---
--- openid ---
--- openJDK-native ---
--- origo-issue-notifier ---
--- oslc-cm ---
--- parameter-defaults-options ---
--- parameterized-trigger ---
--- pegdown-formatter ---
--- people-redirector ---
--- perforce ---
--- performance ---
--- perfpublisher ---
incorrect repository found : java.net2::http://download.java.net/maven/2/
incorrect repository found : central::http://repo1.maven.org/maven2
incorrect repository found : java.net2::http://download.java.net/maven/2
--- periodicbackup ---
--- persistent-build-queue ---
--- persona ---
--- phing ---
--- piwikanalytics ---
--- plasticscm ---
--- platformlabeler ---
--- play ---
incorrect repository found : mavencentralrepo::http://repo1.maven.org/maven2/
incorrect repository found : infradna::http://download.java.net/maven/2/
--- plot ---
--- pmd ---
--- polarion ---
--- pollscm ---
--- pom-importer ---
--- port-allocator ---
--- postbuild-task ---
--- postbuildscript ---
--- powershell ---
--- pre-build ---
--- pre-scm-buildstep ---
--- priority-sorter ---
--- proc ---
--- progress-bar-column ---
--- project-description-setter ---
--- project-stats ---
--- promoted-builds ---
--- promoted-builds-simple ---
--- prqa ---
incorrect repository found : praqma-repo::http://code.praqma.net/repo/maven/
--- publish-over-cifs ---
--- publish-over-ftp ---
--- publish-over ---
--- publish-over-ssh ---
--- pucm ---
incorrect repository found : praqma-repo::http://code.praqma.net/repo/maven/
--- pure-coverage ---
incorrect repository found : central::http://repo1.maven.org/maven2
incorrect repository found : java.net2::http://download.java.net/maven/2
incorrect repository found : java.net::http://download.java.net/maven/1
incorrect repository found : central::http://repo1.maven.org/maven2
incorrect repository found : java.net2::http://download.java.net/maven/2
--- purge-build-queue ---
--- pvcs_scm ---
--- pview ---
--- pwauth ---
--- pxe ---
--- python ---
--- qc ---
--- qmakebuilder ---
--- rad-builder ---
--- radiatorview ---
--- rake ---
--- rebuild ---
--- redmine ---
--- refit ---
--- regexemail ---
--- release ---
--- remote-queue ---
--- repo ---
--- repository-connector ---
--- reverse-proxy-auth ---
--- reviewboard ---
--- rhapsodybuilder ---
incorrect repository found : central::http://repo1.maven.org/maven2
incorrect repository found : java.net2::http://download.java.net/maven/2
incorrect repository found : java.net::http://download.java.net/maven/1
incorrect repository found : central::http://repo1.maven.org/maven2
incorrect repository found : java.net2::http://download.java.net/maven/2
--- robot ---
--- role-strategy ---
--- root-cause ---
--- rotatews ---
--- rrod ---
--- rtc ---
--- ruby ---
--- ruby-runtime ---
incorrect repository found : codehaus::http://repository.codehaus.org/
--- rubymetrics ---
--- run-condition ---
--- rundeck ---
--- s3 ---
--- saferestart ---
--- sametime ---
incorrect repository found : sametime-libs::file:${project.basedir}/lib
--- sauce-ondemand ---
--- sbt ---
--- schedule-failed-builds ---
--- ScheduledTasksView ---
--- schmant ---
--- scis-ad ---
--- scm-sync-configuration ---
--- scons ---
--- scp ---
--- script-realm-extended ---
--- script-realm ---
--- script-scm ---
--- scriptler ---
--- scripttrigger ---
--- SCTMExecutor ---
--- secret ---
--- sectioned-view ---
--- security-no-captcha ---
--- selection-tasks-plugin ---
--- selenium-aes ---
--- selenium-grails ---
--- selenium ---
--- seleniumhq ---
--- seleniumrc-plugin ---
--- sep ---
--- serenitec ---
--- serenity ---
incorrect repository found : repo1.maven.org::http://repo1.maven.org/maven2
incorrect repository found : repo2.maven.org::http://repo2.maven.org/maven2
--- setenv ---
--- sfee ---
--- shared-objects ---
--- shell-script-scm ---
--- shelve-project-plugin ---
--- shiningpanda ---
--- sicci-for-xcode ---
--- sidebar-link ---
--- silktestsuite ---
--- simple-theme ---
--- simpleclearcase ---
--- simpleupdatesite ---
incorrect repository found : powermock-repo::http://powermock.googlecode.com/svn/repo/
--- sitemonitor ---
--- skip-certificate-check ---
--- skype-im ---
--- skype ---
incorrect repository found : internal::file:libs
--- skype-status ---
--- slave-prerequisites ---
--- slave-setup ---
--- slave-squatter ---
--- slave-status ---
--- sloccount ---
--- smart-jenkins ---
--- smartfrog ---
--- SmoothDashboardView ---
--- snsnotify ---
--- sonar ---
--- sounds ---
--- source-ip-realm ---
--- sourcemonitor ---
--- speaks ---
--- springbeandoc ---
--- ssh-cli ---
--- ssh-credentials ---
--- ssh ---
--- ssh-slaves ---
--- staf ---
--- staging ---
--- starteam ---
--- started-by-envvar ---
--- startup-trigger-plugin ---
--- status-view ---
--- statusmonitor ---
--- stepcounter ---
--- storable-configs-plugin ---
--- strawboss ---
--- subversion ---
incorrect repository found : mavenTMateSoftReleasesRepository::http://maven.tmatesoft.com/content/repositories/releases/
--- Surround-SCM ---
--- svn-release-mgr ---
--- svn-revert ---
--- svn-tag ---
--- svncompat13 ---
--- svncompat14 ---
--- svnimport ---
--- svnmerge ---
--- svnpublisher ---
--- swarm ---
--- synergy_scm ---
--- systemloadaverage-monitor ---
--- tap ---
--- tasks ---
--- template-project ---
--- tepco-epuw ---
--- tepco ---
--- terminal ---
--- testabilityexplorer ---
--- testflight ---
--- testingbot ---
--- testlink ---
--- testng-plugin ---
--- text-finder ---
--- tfs ---
--- thread-dump-action ---
--- throttle-concurrent-builds ---
--- tikal-multijob ---
--- timestamper ---
--- tmpcleaner ---
--- token-macro ---
--- toolenv ---
--- trac ---
--- trac-publisher ---
--- tracking-svn ---
--- translation ---
--- tusarnotifier ---
--- tuxdroid ---
incorrect repository found : local::file:${project.basedir}/lib
--- twilio-notifier ---
--- twitter ---
incorrect repository found : twitter4j.org::http://twitter4j.org/maven2
--- ucm4svn ---
--- unicorn ---
--- unity-asset-server ---
--- unity3d ---
--- url-change-trigger ---
--- URLSCM ---
--- urltrigger ---
--- utplsql ---
--- validating-string-parameter ---
--- versioncolumn ---
--- versionnumber ---
--- view-job-filters ---
--- viewVC ---
--- violations ---
--- virtualbox ---
--- virtualbox4 ---
--- virtualization ---
--- vmware ---
--- vsphere-cloud ---
--- vss ---
--- walldisplay ---
--- warnings ---
--- was-builder ---
--- websocket ---
--- WebSVN2 ---
--- webtestpresenter ---
--- windmill ---
--- ws-cleanup ---
--- ws7 ---
--- wsclean ---
--- xcode ---
--- xfpanel ---
--- xframe-filter ---
--- xpath-config-viewer ---
--- xshell ---
--- xtrigger ---
--- xunit ---
incorrect repository found : guice-maven::http://guice-maven.googlecode.com/svn/trunk
--- xvfb ---
--- xvnc ---
--- zentimestamp ---
--- zfs ---
incorrect repository found : java.net2::http://maven.dyndns.org/2/

2012/4/6 Chris van Es <[hidden email]>
I agree though, that maven central would be much better long term.


On 5 April 2012 23:47, Chris van Es <[hidden email]> wrote:
Does the comment 

"If you are exposing your source and want to make it easy for others to build, then consider adding a repository entry to your POM, but don’t pick a URL lightly, think long-term, and use a URL that will always be under your control."

not agree with what the other guys have been saying?

Chris.

2012/4/5 Arnaud Héritier <[hidden email]>
It was detailled here : http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/


On Fri, Apr 6, 2012 at 12:39 AM, Chris van Es <[hidden email]> wrote:
I don't see anything wrong with specifying a repo which is under developers control in the parent pom. It's a feature of maven and I use this feature regularly within my workplace to force our builds to use a repository manager for all dependencies and keep everything internal. I don't know Jenkins well enough but it might prove useful in future to limit the versions of core dependencies available to plugins.

Chris.


On 5 April 2012 17:43, Kohsuke Kawaguchi <[hidden email]> wrote:
On 04/05/2012 06:03 AM, Stephen Connolly wrote:
   As Nicolas wrote, repo.jenkins-ci.org <http://repo.jenkins-ci.org>

   is our domain that we control, so the same thing won't happen again.

   (There is a separate effort to make more of our artifacts available
   in central, which would eliminate this problem in a long run, but we
   shouldn't wait for that.)


Why not just hurry that effort along ;-)

Are you volunteering?


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins




--
-----
Arnaud Héritier
<a href="tel:06-89-76-64-24" value="+33689766424" target="_blank">06-89-76-64-24
Mail/GTalk: [hidden email]
Twitter/Skype : aheritier




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: glassfish repo must die

Nord, James
In reply to this post by nicolas de loof-2

My bad – I took an action a long time ago to investigate this and I did but never really got back to anyone or progressed it to its conclusion.

 

Getting an artifact that is not under our control whose project has no interest in pushing it isn’t a problem.

 

What’s more of a stumbling block – and what I have just asked the maven list is what we do with all the patched jars we have (svnkit/winstone)

 

 

/James

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of nicolas de loof
Sent: 05 April 2012 14:22
To: Stephen Connolly
Cc: [hidden email]
Subject: Re: glassfish repo must die

 

synch to central will fix dependency to jenkins artifacts (so most of plugins) 

but we still have some plugins to depend to artifacts that aren't available on central,

-> guice-2.0.1, or de.regnis.q.sequence:sequence-library (for svn-stuff) for sample 

 

2012/4/5 Stephen Connolly <[hidden email]>

On 4 April 2012 23:13, Kohsuke Kawaguchi <[hidden email]> wrote:

On 04/04/2012 01:38 PM, nicolas de loof wrote:

jenkins-ci.org <http://jenkins-ci.org> is under our control so we can


point it to whatever we like
also, plugin can't build without a repo declaration as jenkins artifacts
aren't available on central

I don't thing this to be a bad practice. Would you expect all developers
to configure settings with adequate repo to build your project ? This
*only* is a requirement for deployment on central
just my 2 cents :P


Yes, the goal here is to make it easier for people to check out plugins and build them, so that they can apply patches. Many of them are Maven newbies.

 

Then let's sync to central.

 

Every added step (like ~/.m2/settings.xml tweaking) is a hurdle. We should have <repository> definition in POM to avoid this.

 

Nope... we should just sync to central

 


As Nicolas wrote, repo.jenkins-ci.org is our domain that we control, so the same thing won't happen again.

(There is a separate effort to make more of our artifacts available in central, which would eliminate this problem in a long run, but we shouldn't wait for that.)

 

Why not just hurry that effort along ;-)

 

 


2012/4/4 Jeff MAURY <[hidden email]
<mailto:[hidden email]>>



   You should rather delete this repo definition as it is not a good
   Maven practice and may lead to the same problem in the future.

   Jeff



   On Wed, Apr 4, 2012 at 8:58 PM, nicolas de loof

   <[hidden email] <mailto:[hidden email]>> wrote:

       Hi folks,

       as you know, glassfish maven repo (aka m.g.o-public) is
       definitively off, but we depend on it for many plugins
       dependencies, and this is hardcoded in plugin parent pom (so, to
       get it fixed, plugin would need to upgrade to a recent
       jenkins-core dependency).

       some of you may already encounter dependency resolution issues
       trying to build a plugin form scratch

       I volunteer to migrate the 400+ plugins to replace <repository>
       pointing to m.g.o-public and replace/add
       repo.jenkins-ci.org/public

       <http://repo.jenkins-ci.org/public> where missing, so that each


       plugin explicitly defines repository to our infra (I plan to
       write a tool for that).

       We discussed this on governance meeting, but I wan't to ensure
       everybody agree here, so please let me know if you see any
       drawback or have another suggestion.

       Nicolas




   --
   Jeff MAURY

   "Legacy code" often differs from its suggested alternative by
   actually working and scaling.
     - Bjarne Stroustrup

   http://www.jeffmaury.com
   http://riadiscuss.jeffmaury.com
   http://www.twitter.com/jeffmaury

 


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

 

 




**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the [hidden email] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: glassfish repo must die

nicolas de loof-2


2012/4/12 Nord, James <[hidden email]>

My bad – I took an action a long time ago to investigate this and I did but never really got back to anyone or progressed it to its conclusion.

 

Getting an artifact that is not under our control whose project has no interest in pushing it isn’t a problem.

 

What’s more of a stumbling block – and what I have just asked the maven list is what we do with all the patched jars we have (svnkit/winstone)


afaik this is not a problem as long as we distribute it under our own groupId
 

 

 

/James

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of nicolas de loof
Sent: 05 April 2012 14:22
To: Stephen Connolly
Cc: [hidden email]


Subject: Re: glassfish repo must die

 

synch to central will fix dependency to jenkins artifacts (so most of plugins) 

but we still have some plugins to depend to artifacts that aren't available on central,

-> guice-2.0.1, or de.regnis.q.sequence:sequence-library (for svn-stuff) for sample 

 

2012/4/5 Stephen Connolly <[hidden email]>

On 4 April 2012 23:13, Kohsuke Kawaguchi <[hidden email]> wrote:

On 04/04/2012 01:38 PM, nicolas de loof wrote:

jenkins-ci.org <http://jenkins-ci.org> is under our control so we can


point it to whatever we like
also, plugin can't build without a repo declaration as jenkins artifacts
aren't available on central

I don't thing this to be a bad practice. Would you expect all developers
to configure settings with adequate repo to build your project ? This
*only* is a requirement for deployment on central
just my 2 cents :P


Yes, the goal here is to make it easier for people to check out plugins and build them, so that they can apply patches. Many of them are Maven newbies.

 

Then let's sync to central.

 

Every added step (like ~/.m2/settings.xml tweaking) is a hurdle. We should have <repository> definition in POM to avoid this.

 

Nope... we should just sync to central

 


As Nicolas wrote, repo.jenkins-ci.org is our domain that we control, so the same thing won't happen again.

(There is a separate effort to make more of our artifacts available in central, which would eliminate this problem in a long run, but we shouldn't wait for that.)

 

Why not just hurry that effort along ;-)

 

 


2012/4/4 Jeff MAURY <[hidden email]
<mailto:[hidden email]>>



   You should rather delete this repo definition as it is not a good
   Maven practice and may lead to the same problem in the future.

   Jeff



   On Wed, Apr 4, 2012 at 8:58 PM, nicolas de loof

   <[hidden email] <mailto:[hidden email]>> wrote:

       Hi folks,

       as you know, glassfish maven repo (aka m.g.o-public) is
       definitively off, but we depend on it for many plugins
       dependencies, and this is hardcoded in plugin parent pom (so, to
       get it fixed, plugin would need to upgrade to a recent
       jenkins-core dependency).

       some of you may already encounter dependency resolution issues
       trying to build a plugin form scratch

       I volunteer to migrate the 400+ plugins to replace <repository>
       pointing to m.g.o-public and replace/add
       repo.jenkins-ci.org/public

       <http://repo.jenkins-ci.org/public> where missing, so that each


       plugin explicitly defines repository to our infra (I plan to
       write a tool for that).

       We discussed this on governance meeting, but I wan't to ensure
       everybody agree here, so please let me know if you see any
       drawback or have another suggestion.

       Nicolas




   --
   Jeff MAURY

   "Legacy code" often differs from its suggested alternative by
   actually working and scaling.
     - Bjarne Stroustrup

   http://www.jeffmaury.com
   http://riadiscuss.jeffmaury.com
   http://www.twitter.com/jeffmaury

 


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

 

 




**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the [hidden email] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: glassfish repo must die

Nord, James

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of nicolas de loof
Sent: 12 April 2012 09:13
To: [hidden email]
Subject: Re: glassfish repo must die

 

 

2012/4/12 Nord, James <[hidden email]>

My bad – I took an action a long time ago to investigate this and I did but never really got back to anyone or progressed it to its conclusion.

 

Getting an artifact that is not under our control whose project has no interest in pushing it isn’t a problem.

 

What’s more of a stumbling block – and what I have just asked the maven list is what we do with all the patched jars we have (svnkit/winstone)

 

afaik this is not a problem as long as we distribute it under our own groupId

 

I hadn’t noticed that...

 




**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the [hidden email] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
12
Loading...