Re: [dash-dev] Maven (again)
Zitat von Denis Roy denis@eclipse.org: Alex, Block device performance is never spectacular on these virtualized machines -- that's why we use them for redundant front-ends. However, having a single CPU and 1G of RAM is certainly not helping. If I add a CPU and increase RAM to 3G can I restart the VM? Will Nexus start itself automatically? Yes, there is a script in init.d. A second CPU might help but I doubt that more RAM will help that much :-/ The main problem is disk space because someone decided to mirror Maven Central - which needs **much** more disk space than my original plan to host only the converted Maven artifacts on the system. So I suggest to either give the system 100GB more disk space or move the Maven Central mirror to a different host. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven Nexus server
Zitat von Jesse McConnell jesse.mcconn...@gmail.com: +1 for CBI, I know they are planning on looking into the orbit mess as well once SR1 is done orbit mess being how to reconcile orbit with maven central in a sane fashion Who is doing that? I already spent a lot of time in this area and I have a solution that works better than anything else I've encountered so far. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven Nexus server
Zitat von Andrew Ross andrew.r...@eclipse.org: I'm hoping that we can lean on you all a bit longer for your help to capture lessons learned from maven.eclipse.org to date, sort through bugs and requirements, and help figure out how we should implement the new system? If you feel like being part of this, please +1 to register your interest. +1 from me. I'm still actively developing mt4e but I'm also in a production team which has completely different goals, so I only have a couple of days every few months to enhance the tool set. My current status: All important features work and I do convert Eclipse releases in a couple of hours (mostly looking through the error reports that mt4e generates) but the tool needs the usual polishing (i.e. other people than me must try it and help improve the parts where I'm blind). Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] New nexus (maven) repositories
Am 27.07.2012 18:06, schrieb Andrew Ross: In the meantime, I'd like to attempt to leverage maven.eclipse.org. If nothing else, it'll help us learn more about what we need the official system to do. The biggest issue is disk space. I really don't understand why the server needs 18GB of disk space. How many packages do we have installed? When I start converting all the Eclipse bundles using mt4e, I'll probably need 2-3 GB and that's for about 3000 bundles. So 18GB of space should be plenty. I ran du over night and got this: 5,3Grepo1 186Mrepo2 4,6GSonatype Why are those repos so big and how can we make sure nexus doesn't fill the disk? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Fwd: [Bug 374052] Invalid plug-in descriptor of eclipse-signing-maven-plugin
Am 27.07.2012 19:34, schrieb Aaron Digulla: Zitat von Alex Blewitt alex.blew...@gmail.com: Can someone clean the caches for the maven site? I can't action this right now. The purge tasks are now running. I ran all the tasks but they aren't reclaiming any memory and I don't understand. At least deleting anything that hasn't been requested in the last 90 days should give some free space :-/ What is going on here? Along the same lines: I tried to purge old stuff from the timeline but nothing happens. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Fwd: [Bug 374052] Invalid plug-in descriptor of eclipse-signing-maven-plugin
Am 30.07.2012 22:25, schrieb David Carver: What version of Nexus are we running? I've lost track. 1.8.0.1 Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Nexus Timeline takes 1GB of disk space
Hi, I tried to purge it (just keep the last 90 days) but nothing happens :-/ This folder grows by 1-5MB every day. Any ideas? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Tycho build with eclipse-parent-pom cannot download external lib ?
Am 06.05.2012 08:52, schrieb Oberhuber, Martin: Hi all, We recently switched the TCF build to use the eclipse-parent-pom, and since that change the http://rxtx.qbang.org/eclipse p2 repo can not be accessed any more from Hudson.eclipse.org (see build log excerpt below). Seems like a network problem: java.net.ConnectException: Connection timed out That either means rxtx.qbang.org is under heavy load (so it doesn't answer in time) or there is a firewall between the two hosts that simply swallows all packets. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Am 24.04.2012 15:53, schrieb Wayne Beaton: Question is posted. Thanks a lot. Is there a way I can follow the discussion? The search doesn't show up anything :-/ https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advancedshort_desc_type=allwordssubstrshort_desc=long_desc_type=substringlong_desc=bug_file_loc_type=allwordssubstrbug_file_loc=keywords_type=allwordskeywords=emailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=chfieldfrom=2012-04-23chfieldto=Nowchfield=%5BBug+creation%5Dchfieldvalue=cmdtype=doitorder=Reuse+same+sort+as+last+timefield0-0-0=nooptype0-0-0=noopvalue0-0-0= Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Am 25.04.2012 21:45, schrieb Denis Roy: Sure, for CQs, but this is discussion involving licensing and copyright initiated by a member of our community (and a committer, no less). I don't understand why such discussion would need to happen behind closed doors, especially considering we advocate openness and transparency. +1 I could understand if comments were disabled for CQs to keep them clean but why completely hide them? Is that a legal matter (NDA or something) or a social matter (avoid bad blood, heated discussions, trolling)? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Zitat von Wayne Beaton wa...@eclipse.org: Right. That functionality is limited to Project Leads and PMC members. Sorry about that. What have we learned yesterday? open source isn't that open after all ;-) I guess that I'll have to pose the question. Thanks. Can you give me some words to start from? Sure: -- cut -- There was a request on the dash-dev mailing list how to handle the following situation: Copying code from public sources like Wikipedia, Stackoverflow or private blogs. To limit the scope of the discussion and kind of create a precedent, let's start with copying code from Stackoverflow. Stackoverflow.com is a site where all kinds of software developers share their knowledge. According to the rules of the site, all user contributions licensed under cc-wiki with attribution required (see the bottom of each page on http://stackoverflow.com/). cc-wiki means: You are free to share - to copy, distribute and transmit the work -, to remix - to adapt the work - and to make commercial use of the work (https://creativecommons.org/licenses/by-sa/3.0/) attribution required means You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Details can be found in this blog post: http://blog.stackoverflow.com/2009/06/attribution-required/ The four rules mentioned there apply if you copy (republish this content) the whole stackoverflow site - answers, questions, user data, everything. They don't make that much sense when just a piece of code is copied. For me, only the second rule makes sense in the context of using code from stackoverflow.com in Eclipse projects: Hyperlink directly to the original question I read that as: Add a comment with a link to the place where you found the code that you copied/used as a template. Can you please verify this for any code published on stackoverflow.com? My main goal is to get a single all-time approval for code so Eclipse developers can use this great resource without causing thousands of tiny CQ requests. If this works well, I'd like to file similar requests for other public developer resources like, for example, Wikipedia. -- cut -- Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] IP Cleanliness question
Hello, I've stumbled over one of these corner cases: I copied 7 lines of code from stackoverflow.com (http://stackoverflow.com/a/3758880/34088) The code isn't an OSS project, it's not under a specific license and I feel that it's not worth the effort to run this through the standard IP process. What are the rules when you copy a code example from a blog? I tried to find some guidelines in the committer rules and IP process, etc, but everything there is more suitable for we want to fork some big OSS project. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Am 23.04.2012 19:24, schrieb Wayne Beaton: Alternatively, I think we can make the case that Stack Overflow contributions are CC-licensed [1] and treat the code similar to a third-party library. However, I believe that license compatibility will be complicated. Here is some material to support this: http://blog.stackoverflow.com/2009/06/attribution-required/ The text is a bit complicated; the four rules apply if you make a copy of the site under a different domain. Since source code isn't HTML, the only rule that applies is probably #2 which boils down to add a link to the question/answer where you got that code from How about I open an IP request so the lawyers can give a nod to the rule? This would create a simple, safe solution for all Eclipse developers because I bet that I wasn't the first one to wonder - I was just the first one who dared to ask :-) Regards, [1] http://creativecommons.org/licenses/by-sa/3.0/ On 04/23/2012 09:25 AM, Aaron Digulla wrote: Hello, I've stumbled over one of these corner cases: I copied 7 lines of code from stackoverflow.com (http://stackoverflow.com/a/3758880/34088) The code isn't an OSS project, it's not under a specific license and I feel that it's not worth the effort to run this through the standard IP process. What are the rules when you copy a code example from a blog? I tried to find some guidelines in the committer rules and IP process, etc, but everything there is more suitable for we want to fork some big OSS project. Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Am 23.04.2012 20:08, schrieb Miles Parker: That's kind of perverse, given that one of the major points of Open Source is to be able to share code with one another... rant OSS is not about sharing code with just anyone; it's only with anyone you happen to like! The main difference to proprietary software is that OSS developers don't believe that you can buy love. And they especially hate you if you happen to use a different OSS license than the one which they painstakingly selected after a long time of suffering (reading legalese, trying to understand it, telling your shrink that you're not insane - the rest of the world is and you can prove it, ...) It's an ego problem: I spent a year to find the perfect license, so everyone else must be an idiot (proof: they use a different one). And who would want to share their hard work with fools? /rant Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Am 23.04.2012 19:59, schrieb Wayne Beaton: Sounds like a plan. Since this is my first attempt to do this: That means I should open a CQ request on ipzilla, right? What project should I select? eclipse.platform? How about I open an IP request so the lawyers can give a nod to the rule? This would create a simple, safe solution for all Eclipse developers because I bet that I wasn't the first one to wonder - I was just the first one who dared to ask :-) Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Am 23.04.2012 21:01, schrieb Wayne Beaton: Good question. Go to the portal, select any project (it doesn't matter) in the Eclipse Projects component. Click on the [pose] a question about general legal issue option. That'll take you to the right place. (or just go here: https://dev.eclipse.org/ipzilla/enter_bug.cgi?product=IPcomponent=IP_Discussion https://dev.eclipse.org/ipzilla/enter_bug.cgi?product=IPcomponent=IP_Discussion) Thanks a lot for your help! Only, I get nowhere... :-) When I click new in ipzilla, I get page has moved, go to the portal. I did but there is nothing obviously related to CQ or IP processes on https://dev.eclipse.org/portal/myfoundation/portal/portal.php. When I try your link, I get: Sorry, either the product IP does not exist or you aren't authorized to enter a CQ into it. ... :-P Regards, On 04/23/2012 02:40 PM, Aaron Digulla wrote: Am 23.04.2012 19:59, schrieb Wayne Beaton: Sounds like a plan. Since this is my first attempt to do this: That means I should open a CQ request on ipzilla, right? What project should I select? eclipse.platform? How about I open an IP request so the lawyers can give a nod to the rule? This would create a simple, safe solution for all Eclipse developers because I bet that I wasn't the first one to wonder - I was just the first one who dared to ask :-) Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] [cross-project-issues-dev] Corrupted Maven repository at Eclipse.org
Zitat von David Carver d_a_car...@yahoo.com: Alex, We may want to consider an upgrade to Nexus 1.9 or 2.0 as well. I think we are using 1.8.x which I know had some bugs. We didn't upgrade to 1.9 because of other bugs ;-) Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Missed some Dash issues in Bugzilla
Hello, It seems I missed a couple of Maven issues in Bugzilla. What is the official way to keep track of them? Can I get Bugzilla to send me a monthly reminder or something when a new bug is opened with Project = Dash AND Component = Maven? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] mt4e in Groovy
Hello, I finished converting the Python version to Groovy. Two questions: 1. What is the most efficient way to get a complete copy of the 3.7.0 Eclipse release (basically a mirror of the p2 repo)? Should I use the p2 mirror application to copy the data from the main site to our maven.eclipse.org host? Or would it be possible to get a read-only NFS mount of the folder? 2. The binary for the new tool is about 8MB. How do I get that onto one of the Eclipse download sites? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] mt4e in Groovy
Am 24.08.2011 17:05, schrieb Denis Roy: Thanks for the quick response. 1. What is the most efficient way to get a complete copy of the 3.7.0 Eclipse release (basically a mirror of the p2 repo)? Should I use the p2 mirror application to copy the data from the main site to our maven.eclipse.org host? Or would it be possible to get a read-only NFS mount of the folder? 1. rsync is likely your best bet. Simply rsync from download.eclipse.org::eclipseFullMirror Is that 3.7.0 or everything ever published? I'd rather download only 3.7.0. And I couldn't get it to work: nexus@maven:~/mt4e/3.7.0/downloads rsync download.eclipse.org::eclipseFullMirror eclipseFullMirror rsync: failed to connect to download.eclipse.org: Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(122) [receiver=3.0.4] Permissions or PEBKAC? 2. The binary for the new tool is about 8MB. How do I get that onto one of the Eclipse download sites? 2. rsync is likely your best bet. Simply rsync to commiter...@dev.eclipse.org:downloads/technology/dash Thanks, that works :-) If anyone has the same problem, here is the wiki page: http://wiki.eclipse.org/IT_Infrastructure_Doc#Downloads Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Need a couple of -devel packages
Am 08.05.2011 18:39, schrieb Aaron Digulla: Hi, For my new version of the (ill-named) m4e tools, I need to compile the Python module lxml which needs python-devel (or python-base-devel), libxml2-devel and libxslt-devel (at least). I couldn't find the devel packages in any of the active repositories on maven.eclipse.org. Where are they? Or do I really need to download and install each and every package? Can someone please add the devel repo on maven.eclipse.org? Fixed it myself; I simply downloaded all the source archives and compiled everything. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] SSH access to maven.eclipse.org is brittle
Zitat von Denis Roy denis@eclipse.org: The server itself has a local firewall which is triggered by too many bad login attempts. Your 212 IP was in there and I've cleared it. The command to clear the block is in the root user's command history. Thanks, it now works for me and I noted the command. David, what's your IP address? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven Git Repository
Zitat von David Carver d_a_car...@yahoo.com: I've created a Maven git repository for the maven signing plugin and the parent pom creation. Aaron let me know if you need a git repo for your conversion scripts. I do but I'm waiting for IP clearance (https://bugs.eclipse.org/bugs/show_bug.cgi?id=341956). Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] What happened to testing?
Hello, The M2 repo testing is gone. Who did it and why? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Fwd: Neuxs Snapshot Deployments
Zitat von David Carver d_a_car...@yahoo.com: I tried sending this to dash-dev yesterday but it got bounced, Original Message Subject:Neuxs Snapshot Deployments Date: Thu, 12 May 2011 17:55:18 -0400 From: David Carver d_a_car...@yahoo.com To: Tools for Committer Community dash-dev@eclipse.org There seems to be something configured wrong with our Nexus repository. For the life of me I can't figure out what is wrong. If a repository is set as release, and the appropriate deployment rights are set on a user, the Artifact Upload tab appears.However, if the repository is setup as a Snapshot profile, and the same user views the repository, there is no Artifact Upload rights. Uploading snapshots is complex: You need to update the metadata.xml with the correct version numbers, replace SNAPSHOT with the current date+time, etc. So it's not possible to upload snapshots via the web UI. You must use maven deploy. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Maven Tools for Eclipse RC1 ready
Hello, I've finished RC1 of my Maven Tools for Eclipse. All major features should be there. I'll try to create a new testing repo over the weekend, so we can get the patches wrapped up. Please read my announcement on http://blog.pdark.de/2011/05/13/maven-tools-for-eclipse-m2-repository-analysis-and-dependency-management/ Major pain points: 1. We probably need a tool to convert the M2 repo in tmp/ into the repo suitable for Nexus. This should either get Nexus to reload the cache or I'll have to add specific instructions how to do this. 2. The sample report shows the major problems with the current repo: catch all versions ([0,)), one missing dependency (org.eclipse.team:org.eclipse.team.cvs.ssh2:3.2.300), duplicates (javax.xml.bind:javax.xml.bind, javax.servlet:javax.servlet, org.apache.commons:org.apache.commons.logging, org.w3c.dom:org.w3c.dom.smil) Is it safe to replace [0,) with the version found in the repo? Or should I open roughly 500 bugs in bugzilla to get people to use a proper version range? Where is org.eclipse.team:org.eclipse.team.cvs.ssh2? Anything I'm missing? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] What happened to testing?
Am 13.05.2011 17:14, schrieb Alex Blewitt: Hello, The M2 repo testing is gone. Who did it and why? It was a while ago that I set them up though. It was deleted yesterday (Thursday). See the system feeds. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] SSH access to maven.eclipse.org is brittle
Am 05.05.2011 18:23, schrieb David Carver: I have never been able to get into the server. I always get time outs. From which server are you connecting? For me, it works from 80.242.196.73. It doesn't work from 212.126.163.137. Can a sysadmin please check this? I'd like to install the latest version of my tools and do another conversion of testing. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Dash Dev Repo Maven Release Tools
Am 11.05.2011 02:56, schrieb Jesse McConnell: I figured something like: org.eclipse.dash/ eclipse/ - for the eclipse tlp (top level pom) coordinates of org.eclipse:eclipse:1,2,3,4 dash-parent/ - for the dash tlp, inherits from eclipse tlp, coordinates of org.eclipse.dash:dash-parent:1,2,3,4 eclipse-signing-maven-plugin/ - inherits dash tlp, typical versioning.. minerva/ - inherits dash tlp etc/ etc/ Dave and I discussed on irc about the tlp for eclipse, that it should be on the scale of the apache tlp under org.apache:apache:9 for setting broad organizational metadata. We could put it under dash as the place that is currently aggregating maven bits and pieces for eclipse infrastructure as it relates to maven. I'm confused. Are you talking about GIT repos or Maven repos? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Need a couple of -devel packages
Hi, For my new version of the (ill-named) m4e tools, I need to compile the Python module lxml which needs python-devel (or python-base-devel), libxml2-devel and libxslt-devel (at least). I couldn't find the devel packages in any of the active repositories on maven.eclipse.org. Where are they? Or do I really need to download and install each and every package? Can someone please add the devel repo on maven.eclipse.org? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] SSH access to maven.eclipse.org is brittle
Hello, SSH access to maven.eclipse.org is brittle; in the beginning, it was sometimes slow (first connection attempt took 5-10 seconds) but over time, this deteriorated. When I tried a few weeks ago, the first attempt timed out, the second one got through. Today, I can't login at all. Despite that the web interface is quite snappy. Why is that? Is that a virtual machine and Nexus is eating all the CPU? Or is there a firewall issue? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] +1 for Chris Aniszczyk on technology.dash by Aaron Digulla
Aaron Digulla voted: +1 +1 for getting one step closer to build Eclipse without PDE Voting summary: http://portal.eclipse.org/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] +1 for Jesse McConnell on technology.dash by Aaron Digulla
Aaron Digulla voted: +1 +1 for more Tycho support Voting summary: http://portal.eclipse.org/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] +1 for Jesse McConnell on technology.dash by Aaron Digulla
Aaron Digulla voted: +1 +1 for more Tycho support Voting summary: http://portal.eclipse.org/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] +1 for David Carver on technology.dash by Aaron Digulla
Aaron Digulla voted: +1 +1 for more Tycho support Voting summary: http://portal.eclipse.org/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Bug 342046 - Invalid third party dependencies in Mavenized BIRT plugins
Hello, I'm working on this bug. To resolve it, two things need to be done: 1. We need to identify artifacts which are released under the EPL but which aren't below org.eclipse.*. Most prominent example: com.ibm.icu. 2. We need a tool to replace dependencies in POMs. Re #1: Simply ignoring everything besides org.eclipse when copying to the Nexus folder is not enough. We need more fine grained rules. Comments? We also need a mapping between Orbit and Maven Central. Re #2: I've completed a first version of the tool which can remove optionalfalse/optional from the generated POMs and which can replace dependencies. Currently, it has the following limitations: 1. It matches version by equals. More elaborate version matching could be problematic since there might be cases where I need to know if two version ranges *overlap*. My current plan is to modify the tool to match artifacts by group+name only (ignoring the version) and then check the version. If the version doesn't match, I'll log a warning so we can accumulate a report what versions are used. With that report, we can decide what to do next. 2. Currently, I replace the existing dependency with a new one. I'm wondering if I should create a profile section instead so users can select the original dependency or our patch. The problem with a profile section is that it's hard to make one the default (as in unless the user has selected a profile) because there can be any number of profiles and there is no way to say enable this profile if no profile of this set is enabled. That means users will generic errors if they import our POMs and they forget to specify a profile :-/ 3. There is currently no way to attach a condition to a patch (like apply it anywhere but for the POM X:Y:Z). Not sure if that's necessary, though. 4. There are generic patches (like the one which removes the optional=false elements) and special patches (like the one which replaces one dependency with another). Special patches are small Python scripts which the patch tool evaluates. The tool gets a directory and loads all the scripts in there. I'm uneasy how this will work out when the number of patches grows. Maybe it would be better to load a single patch which then includes others with the help of an include command. 5. Python vs. Java. Right now, I'm developing the tools in Python just because I'm about 10 times more productive with Python for tools like that. But looking at the big picture, is that the right decision? Should I stay with Python or convert the code to Java? PS: The new version sits on my harddisk but I can't push it to github right now; will do that tomorrow. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Paperwork
Hello, We're trying to make heads and tails of the individual committer agreement here. Won't take long ... maybe. One question that came up: What's the purpose of the enter date? Is it the same as the date at the end of the agreement or should it be some specific date? One reason I'm asking is the code sitting on github: I wrote that around mid March. Should the date be *before* that? Would that make it more simple to IP-clean the code? Or should that be the date of my committer application? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven repositories at Eclipse
Zitat von Alex Blewitt alex.blew...@gmail.com: I forgot indigo; I've created nightly, integration and milestone repositories for these and added them to the appropriate groups, and updated the wiki appropriately. Can you please try to import them (or part of them) and let me know your thoughts on my tools? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Version ranges or exact versions
Am 20.03.2011 16:20, schrieb Igor Fedorenko: I don't think it really matters, as dependencyManagement/ overrides all dependency versions. I think it is even possible to omit version/ element altogether, which will force all consumers to specify dependencyManagement/ via scope=import or explicitly. I didn't know about scope=import; that sounds really interesting. This explains the background: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies That would be a viable solution. The idea not to specify any version at all (forcing users to specify it) also sounds interesting but I think that will only work for top dependencies. People will not want to figure out version 3.1.100 of some core plugin which is pulled in by the 5th level of dependency resolution when they ask for x.y.z:3.6.2. I've posted a question on SO to get more ideas: http://stackoverflow.com/questions/5371174/importing-eclipse-bundles-into-maven-how-to-map-versions Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven repositories at Eclipse
Am 20.03.2011 15:13, schrieb Alex Blewitt:
I have put these repositories under /home/nexus/repositories with the
nightly/milestone/integration as parent directories. This should allow
us to roll forward with new releases as they come up, whilst
aggregating under the repository URL for the group.
Very good. I like it.
I have put {integration,milestone,nightly,release} as the defined set
for the public repositories. I'm unsure what to do for orbit. If we
include it in the public repositories, then it may prevent others from
consuming from there and central. On the other hand, there may be some
things in orbit which aren't available elsewhere that we need to
address. I suspect we can fix this subsequently.
How about another virtual repo which includes public and orbit? That
way, we can have both.
Lastly, this will be a little ugly as a URL:
http://maven.eclipse.org/nexus/content/groups/public
We may want to set up a rewrite rule so that (e.g.)
http://maven.eclipse.org/maven2/
- http://maven.eclipse.org/nexus/content/groups/public
which would then let us use http://maven.eclipse.org/maven2 as the
pubic facing URL for access to the outside world.
Agreed. But I'd map http://maven.eclipse.org/maven2/ to
http://maven.eclipse.org/nexus/content/groups/
http://maven.eclipse.org/nexus/content/groups/public (i.e. one level
above) so that all public groups appear under that URL.
Regards,
--
Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe
that's limited, it's our imagination. Follow me and I'll show you
something beyond the limits. http://blog.pdark.de/
___
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Orbit in Maven
Am 20.03.2011 16:28, schrieb Chris Aniszczyk: On Sun, Mar 20, 2011 at 9:40 AM, Alex Blewitt alex.blew...@gmail.com wrote: I have created a repository for hosting the Orbit repositories at Eclipse. http://maven.eclipse.org/nexus/content/repositories/orbit/ I'd like to populate this with the current set of approved Orbit releases. If so, where do we find these from? We can acquire these using Aaron's conversion script but would like to get at least the JARs from the valid upstream source rather than jus assuming that the set of non org.eclipse.* JARs are the current Orbit approved contents. http://download.eclipse.org/tools/orbit/downloads/ The latest Stable is generally what we want. I've downloaded the latest release (orbit-buildrepo-S20110304120314.zip) into /home/nexus/Downloads. Can someone please try to use my tools in /home/nexus/workspace/org.eclipse.dash.m4e.tools/src to convert the download into a new m2repo? I'd like to see whether I've missed something :-) Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] TODO List
Am 14.03.2011 21:38, schrieb Chris Aniszczyk: On Sun, Mar 13, 2011 at 3:28 PM, Aaron Digulla digu...@hepe.com wrote: Sorry, didn't get any work done. Taxes got me this weekend :-( I'll try again tomorrow. A newer version of Nexus came out... http://nexus.sonatype.org/download-nexus.html We should probably aim to use that one. Is there any feature which 1.9 brings that we really need? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven wiki page and suggested repository layout
Am 19.03.2011 12:36, schrieb Alex Blewitt: This would leave: * Releases * Maven central * Central m1 shadow Why mirror central? People should set up their own proxy. I'd vote that our public Nexus server only serves Eclipse stuff. If *we* need stuff, we should set up a second, internal Nexus server which isn't visible to the public. I'm tempted to agree with this. However, is it possible to restrict repository access in the open source nexus version to only allow access for some repositories based on (say) IP ranges? Failing that, a second instance on the same host but different port would probably suffice, and can be controlled on a build machine basis with an appropriate settings.xml file. Why restrict access? It only causes us more work and if people want a single hand serves all, they can add our thirdparty and releases to their POMs and they are done - everything we serve will work out of the box. Nexus is capable of segregating and aggregating individual repositories. To facilitate the management of artefacts hosted, it is proposed that the Nexus repository is configured with a number of subsidiary repositories which will hold different content, as follows: * |/orbit| - for holding Orbit approved external dependencies * |/release| - for storing final releases, e.g. Helios 3.6, 3.6.1, 3.6.2 Why separate /orbit and /release? I tend to agree; Orbit contains non-Eclipse stuff that is IP approved, so if you want to build Eclipse clean stuff, this is good. Mixing it with /release would mix code from Eclipse with non-Eclipse things which makes it more messy for people who don't want Orbit artifacts (for example more entries in the Add Dependency dialog). Other options? Btw, Maven uses artIfacts not artEfacts :-) * |/milestone| - for storing milestone releases (for the latest build only?) e.g. 3.7M1, 3.7M2 I'd support the current release train - since the next M1 doesn't start with the official release of the previous train, there is some overlap so people have several weeks(?) to update their POMs. * |/integration| - for storing -SNAPSHOT equivalents of integration (I) builds; to be purged frequently (weekly?) Weekly sounds pretty short. I'd keep the last 5 versions. What options does Nexus offer for purging? Can I purge on a count basis or only on a time basis? * |/nightly| - for storing -SNAPSHOT equivalents of nightly (N) builds; to be purged frequently (nightly?) Same here. It is proposed that the release entries are permanently available, whilst milestones may be cleared out after the final release, and nightly and integration builds are cleared out automatically. In addition, for testing: * |/testing| - for storing -SNAPSHOT equivalents for testing purposes; to be purged occasionally (monthly?) Yes, keep them around for voting for 30 days. To support automated builds at Eclipse, it may make sense to proxy publicly available repositories, although these should not be publicly available. * |/central| - for aggregating: o |/repo1| - mirror of http://repo1.maven.org http://repo1.maven.org/ o |/repo2| - mirror of http://repo1.maven.org http://repo1.maven.org/ Those two entries have the same URL - what's the difference between repo1 and repo2? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] TODO List
Am 11.03.2011 23:34, schrieb Aaron Digulla: My current TODO list: 1. Install Nexus and apache2 as service (auto start after reboot) Done. I've rebooted once to check that the scripts work. You can now start/stop Nexus as root (with service nexus start/stop) or as user nexus with nexus start/stop. 2. Finish the SMTP config (mailing/reset of passwords) Mail still doesn't work. If I do this on the command line: $ date | mailx -s test digu...@hepe.com there is no error but the mail never arrives. Same is true when I try inside of Nexus (with SMTP = localhost:25, no user, no password). 3. Create a testing/staging repo where newbies can deploy without corrupting the official repo. I'll leave that to Alex and Chris. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] First conversion of 3.6.2 projects
Am 18.03.2011 22:28, schrieb Aaron Digulla: Due to a bug, the repo is still polluted with non-Eclipse artifacts. I've fixed the problem; the result should now be ready for deeper inspection. /home/nexus/workspace/org.eclipse.dash.m4e.tools/tmp/m2repo/ When the testing repo is configured, please import this. I'll then post notices in my blog and on stackoverflow.com to get some more feedback. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] First conversion of 3.6.2 projects
Am 18.03.2011 23:56, schrieb Alex Blewitt: You can find the result in /home/nexus/workspace/org.eclipse.dash.m4e.tools/tmp/m2repo/ Looks good from what I've seen briefly. A couple of thoughts: dependency groupIdorg.eclipse.jface/groupId artifactIdorg.eclipse.jface/artifactId version[3.2.0,4.0.0)/version optionalfalse/optional /dependency We can probably optimise out the optionalfalse/optional if it's optional. Yes. Secondly, how does Maven handle the version range dependency? I know technically it should support it, but I am concerned it might not. Maven creates local metadata files which contain the available versions on a server and then tries to find a match. Unlike p2, this happens instantly, so it's not a performance issue. We *should* be able to find out what the release version is based on what we know is in the repository. For example, org/eclipse/jface/org.eclipse.jface/3.6.2 exists, so we could replace [3.2.0,4.0.0) with 3.6.2. This might make it easier for direct resolutions, as well as recording what was actually compiled against. I think there is a bit more to that. If you see a version range, then that version range was in the manifest. Without a version range, the conversion step selects what it can find in the plugins/ directory that is being converted. Examples: org.jdom:org.jdom:1.0.0 wants org.apache.xerces but no version was specified and this dependency is not available and it's optional. Result: dependency groupIdorg.apache.xerces/groupId artifactIdorg.apache.xerces/artifactId version[0,)/version optionaltrue/optional /dependency org.eclipse.pde.build-3.6.2.pom contains ranges and fixed versions. For example the dependency for org.eclipse.equinox.p2.publisher has no version range in the MANIFEST.MF but it is available during the conversion, so it's fixed to 1.1.0: dependency groupIdorg.eclipse.equinox/groupId artifactIdorg.eclipse.equinox.p2.publisher/artifactId version1.1.0/version optionaltrue/optional /dependency There are several goals here: - Preserve the original version range so people can see the minimum dependency which still satisfies the needs of an artifact - Stable builds - Automatic updates I see several solutions: - Use properties for versions so consumers can override them - Omit all versions and create one or more parent POMs with huge dependencyManagement elements to specify the default versions - Create profiles with the dependency versions. One profile uses the range, the other uses the version which is in the same conversion. Open issues: - How do we resolve conflicts? - How do we merge updates? Resolving conflicts: Imagine there is a.b.c:3.6.0 and e.f.g:3.6.0. a.b.c:3.6.0 wants x.y.z:3.5.0 while e.f.g:3.6.0 wants x.y.z:3.*6*.0. Example: org.apache.commons.logging comes as 1.0.4 and 1.1.1. For org.w3c.dom.smil, we have 1.0.0 and 1.0.1. javax.xml.bind comes as 2.0.0 and 2.2.0. Should we: - Notify the team behind a.b.c to update their dependencies? What if they refuse? - Update the dependency ourselves (probably without knowing what we're breaking)? - Keep two versions of x.y.z? Merging updates: Say we have imported 3.6.0 into Nexus. Now, SR1 is released which includes x.y.z_3.6.1. a.b.c:3.6.0 needs it but didn't specify a version range. There is no a.b.c:3.6.1. Should we - release a.b.c:3.6.0.1 and make it depend on x.y.z_3.6.1? - Update the parent POM and release everything in 3.6.0 as 3.6.0.1? - Release a a.b.c:3.6.*1* even though there wasn't one? - Create a report which lists such cases to consumers can make an educated decision themselves? - Leave it to the consumers to figure out? - Due to a bug, the repo is still polluted with non-Eclipse artifacts. No problem - we can probably just miss out anything that isn't in the org/eclipse tree. I cleaned the repo but there is still some artifacts outside of org/eclipse: ./com/ibm/icu/com.ibm.icu/4.2.1/com.ibm.icu-4.2.1.pom ./com/jcraft/jsch/com.jcraft.jsch/0.1.41/com.jcraft.jsch-0.1.41.pom ./com/lowagie/text/com.lowagie.text/2.1.7/com.lowagie.text-2.1.7.pom ./javax/xml/stream/javax.xml.stream/1.0.1/javax.xml.stream-1.0.1.pom ./javax/xml/bind/javax.xml.bind/2.0.0/javax.xml.bind-2.0.0.pom ./javax/xml/bind/javax.xml.bind/2.2.0/javax.xml.bind-2.2.0.pom ./javax/xml/soap/javax.xml.soap/1.2.0/javax.xml.soap-1.2.0.pom ./javax/xml/javax.xml/1.3.4/javax.xml-1.3.4.pom ./javax/xml/rpc/javax.xml.rpc/1.1.0/javax.xml.rpc-1.1.0.pom ./javax/transaction/javax.transaction/1.1.1/javax.transaction-1.1.1.pom ./javax/servlet/source/javax.servlet.source/2.5.0/javax.servlet.source-2.5.0.pom ./javax/servlet/javax.servlet/2.5.0/javax.servlet-2.5.0.pom ./javax/servlet/jsp/javax.servlet.jsp/2.0.0/javax.servlet.jsp-2.0.0.pom ./javax/persistence/javax.persistence/2.0.1/javax.persistence-2.0.1.pom ./javax/mail/javax.mail/1.4.0/javax.mail-1.4.0.pom ./javax/wsdl/javax.wsdl/1.5.1/javax.wsdl-1.5.1.pom
Re: [dash-dev] Git repo for m4e tools
Hello, To get things started, I've created a repo on github: https://github.com/digulla/org.eclipse.dash.m4e.tools Please have a look, especially to make sure the IP stuff is OK (license, copyright notice, etc). Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Project Dash m4e Tools
Hi, I've posted an explanation of the tools and an overview in my blog: http://blog.pdark.de/2011/03/18/project-dash-m4e-tools-create-maven-artifacts-from-eclipse-plug-ins/ Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Project Dash m4e Tools
Am 18.03.2011 17:45, schrieb Wayne Beaton: Can we make sure that this sort of information eventually finds a home in the wiki? Can I already access the wiki? I thought I need to wait for my committer accolade. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Naming the Maven effort
Am 18.03.2011 17:45, schrieb Wayne Beaton: I am concerned that naming your efforts m4e is potentially confusing for the community as it seems awfully close to m2e [1]. m2e comes from Maven 2 Plug-in for Eclipse and, apparently, some folks from the Maven community are already asking about m3e for Maven 3. Thoughts? I agree but naming is hard. Some suggestions: Eclipse Maven Tools - too long. Is that tools for Maven or Eclipse? Since we translate Eclipse bundles into Maven artifacts: translate in various languages: Catalan: traduir Croatian: prevesti Dutch: vertalen Filipino: isalin French: traduire Galician: traducir Or we use m2e tools because I'm building tools to use make Eclipse bundles usable in projects that use m2e to build. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] First conversion of 3.6.2 projects
Hello, I've converted the first batch of 3.6.2 archives from http://www.eclipse.org/downloads/, namely: eclipse-3.6.2-delta-pack.zip eclipse-modeling-helios-SR2-incubation-linux-gtk.tar.gz eclipse-rcp-helios-SR2-linux-gtk.tar.gz eclipse-reporting-helios-SR2-linux-gtk.tar.gz eclipse-SDK-3.6.2-win32.zip org.eclipse.rcp-3.6.2.zip org.eclipse.rcp.source-3.6.2.zip That's 1074 artifacts, 283 with sources. You can find the result in /home/nexus/workspace/org.eclipse.dash.m4e.tools/tmp/m2repo/ Due to a bug, the repo is still polluted with non-Eclipse artifacts. During the conversion, I had warnings like this one: WARNING ../tmp/m2repo/org/junit/org.junit/3.8.2/org.junit-3.8.2.jar differs from ../tmp/eclipse-SDK-3.6.2-win32_home/m2repo/org/junit/org.junit/3.8.2/org.junit-3.8.2.jar A quick search found four archives which contain this file: ./eclipse-reporting-helios-SR2-linux-gtk_home/m2repo/org/junit/org.junit/3.8.2/org.junit-3.8.2.jar ./eclipse-modeling-helios-SR2-incubation-linux-gtk_home/m2repo/org/junit/org.junit/3.8.2/org.junit-3.8.2.jar ./eclipse-rcp-helios-SR2-linux-gtk_home/m2repo/org/junit/org.junit/3.8.2/org.junit-3.8.2.jar ./eclipse-SDK-3.6.2-win32_home/m2repo/org/junit/org.junit/3.8.2/org.junit-3.8.2.jar Comparing the first two shows that JUnit 3.8.2 from eclipse-reporting-helios-SR2-linux-gtk.tar.gz and eclipse-modeling-helios-SR2-incubation-linux-gtk.tar.gz have differences near the beginning. In the file, it looks like this: 948 Defl:N 517 46% 03-18-11 17:09 7ce61aa8 META-INF/MANIFEST.MF 948 Defl:N 517 46% 03-18-11 17:15 7ce61aa8 META-INF/MANIFEST.MF So you can see the file date is different. How can that happen? I understand that Eclipse recreates the MANIFEST.MF when the JAR is signed but why are many plug-ins signed several times? Background: To make sure everything is ok, I check that all files are identical when I merge repositories. Only, they aren't... Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Git repo for m4e tools
Hi, I've started to write some tools to import downloads from eclipse.org into Maven repositories. The code sits in a git repo on my harddisk. The preliminary project name is org.eclipse.dash.m4e. Is the name OK? Can someone please create a git repo on eclipse.org where I can push my code? Or should I keep it somewhere else for the time being? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://www.pdark.de/ http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] New wiki pages (Was: Re: Nexus is ready)
Am 13.03.2011 19:13, schrieb Alex Blewitt: Before we do that ... are we happy with the five repositories that I proposed the other day? If so, I'll put them on the wiki so we're all working towards the same thing. Please put them in the Wiki so we can all have a look and give some comments to make sure we know what we agree on. While we're at it, everyone should probably have a look at http://wiki.eclipse.org/Development_Resources/New_Commmitter_Handbook for some gentle introduction into Eclipse's view of the world. Documentation: Don't forget to add some explanations *why* we want something. So: -- Repos: .../release Release repo .../release Nightly ... -- is bad. Users can see the repos on Nexus. Don't repeat boring stuff. People ask questions. Like Which one should I use? Why did they do it this way? Why didn't they put everything in a single repo? So try: -- Repos: .../release Release repo .../release Nightly ... Explanation: The release repo is for official releases only (like Helios a.k.a 3.6.0). If you want stable, go there. The milestone repo is a bit less stable. You can find the regular milestone builds here (link to timetable?). Use it if you need a pretty stable and pretty current version. ... -- Maybe link to a page which explains what a Nightly, ... build really is. Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven Repository at Eclipse
Am 11.03.2011 16:46, schrieb Alex Blewitt: On 11 Mar 2011, at 15:26, Aaron Digulla wrote: I was thinking in a similar way. Using snapshots for the milestones doesn't work. Creating a new repo for each milestone doesn't scale. My objection with M01...RELEASE is the sort order. the M01..RELEASE sort order works, provably so, since Virgo uses it at the moment. Good. Proof is better than hope. Why do you think it doesn't work for milestone and release artifacts? That's not what I said. I'm worried about I and N builds. That would give the order I M N REL which is probably wrong. Tools like the version tool of Maven should offer the latest version. If you run it today, I get 20030203.000129 as the latest version of commons-lang (instead of 2.6). Agreed, which is what we want to avoid. So M1..REL would work but mixing that with I and N builds wouldn't. So we don't use -I and -N. Both of these are really just -SNAPSHOT builds, which Maven already handles. I'm not sure whether we want those to be in the same repository anyway; or if we do, we want to be able to separate them out (c.f. snapshot.apache.org and repository.apache.org) I feel the same. Mixing snapshots and releases is bad. Which gives me an idea: How about we use the artifactId? org.eclipse.core - Releases wouldn't work for OSGi consumers of Maven bundles, like Felix. That's why Spring used -RELEASE. OK. org.eclipse.core-I - Integration builds org.eclipse.core-N - Nightly builds org.eclipse.core-M - Milestone builds Suggest -SNAPSHOT in both cases. If necessary, we can partition the repository in Nexus with 'nightly' and 'integration' to distinguish. Right now, I feel we should separate them. Any reason not to? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Installing Nexus 1.8.0.1
Hello, To get us started, I'm now installing Nexus 1.8.0.1. The update to 1.9 should be easy. Here is the full installation log: Installation protocol - I created the user nexus, group nexus # groupadd nexus # useradd -g nexus -m -c Nexus Service nexus - I copied the SSH keys from ~admin to ~nexus # cd ~nexus # cp -r /home/admin/.ssh . # chown nexus:nexus .ssh/ - Logging in as nexus works from remote. I'm using this in my ~/.ssh/config: Host nexus HostName maven.eclipse.org User nexus ForwardAgent yes - I created the scripts vi and vim for root. They create a backup of any edited file in /root/vibak/ That makes it much more simple to find the answer to these two questions: 1. Who changed something in the last three days? 2. What changed? 3. If I need to set up a new server, what do I have to change - As user nexus: I downloaded Nexus 1.8.0.1 wget http://nexus.sonatype.org/downloads/older/nexus-oss-webapp-1.8.0.1-bundle.tar.gz wget http://nexus.sonatype.org/downloads/older/nexus-oss-webapp-1.8.0.1-bundle.tar.gz.sha1 - Checked the SHA1 sum: sha1sum nexus-oss-webapp-1.8.0.1-bundle.tar.gz Unfortunately, the sha1-file isn't suitable as input for sha1sum. But the numbers seem to match. - Unpacking Nexus tar xzf nexus-oss-webapp-1.8.0.1-bundle.tar.gz - Creating a symbolic link to the current version of Nexus ln -s nexus-oss-webapp-1.8.0.1 nexus-current - Creating a symbolic link for the start script of Nexus ln -s $HOME/nexus-current/bin/jsw/linux-x86-64/nexus bin Checking Java version: java -version libnuma: Warning: /sys not mounted or no numa system. Assuming one node: Datei oder Verzeichnis nicht gefunden java version 1.6.0 Java(TM) SE Runtime Environment (build pxa6460sr8fp1-20100624_01(SR8 FP1)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr8ifx-20100609_59383 (JIT enabled, AOT enabled) J9VM - 20100609_059383 JIT - r9_20100401_15339ifx2 GC - 20100308_AA) JCL - 20100624_01 I'm not really happy with the libnuma warning but I'm not trying to fix this right now. - Installing Nexus (following the instruction at http://www.sonatype.com/books/nexus-book/reference/ch03s02.html) Done already with the links and stuff above. - Configuring Nexus I was thinking about changing the port from 8081 to 80 but then, we'd need to run Nexus as root. I think I'll install a web server that redirects the requests. - Starting nexus nexus start Starting worked. But I couldn't connect with http://maven.eclipse.org:8081/nexus/ The firewall doesn't let me in. - Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Can't install rdate and mail doesn't work
Am 11.03.2011 22:06, schrieb Denis Roy: On 03/11/2011 03:50 PM, Aaron Digulla wrote: Hello, Two more problems: rdate is missing. When I tried to install it with zypper, I can configure zypper to use a virtual cd as the source, but I'd need to restart your VM. Is that OK? I closed all connections, you can restart now. As for CD image: I'm worried about installing security patches. How will I be able to install them if I can't connect to an external repository? Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Nexus is ready
Am 11.03.2011 23:22, schrieb Aaron Digulla: Hello, I've installed apache2 instead of lighttpd (couldn't compile it). The proxy module is active and forwards all requests to /nexus. The server can be reached via http://maven.eclipse.org/nexus/index.html I haven't configure Nexus itself much except for changing the default password. The new ones are in the file /home/nexus/pw Forgot to mention: The installation log is in /home/nexus/install-apache2.txt Regards, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] TODO List
My current TODO list: 1. Install Nexus and apache2 as service (auto start after reboot) 2. Finish the SMTP config (mailing/reset of passwords) 3. Create a testing/staging repo where newbies can deploy without corrupting the official repo. I'll attack that tomorrow :-) Good night, -- Aaron Optimizer Digulla a.k.a. Philmann Dark It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits. http://blog.pdark.de/ ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
