Sign existing artifacts in repository
Hi, we have an existing repository which I want to batch sign all the artifacts within. I do have file system access. Is there any tool available that will go though our existing repository and allow me to sign the artifacts (all of which have been created by me in the past)? thanks, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Amazon EC2 EBS Volume for Maven central repository
Ok, so, from the EBS web page...we can speculate... As an example, a medium sized website database might be 100 GB in size and expect to average 100 I/Os per second over the course of a month. This would translate to $10 per month in storage costs (100 GB x $0.10/month), and approximately $26 per month in request costs (~2.6 million seconds/month x 100 I/O per second * $0.10 per million I/O). We might seek out the Freebase folks and inquire for the what their costs are like to provide an EBS dataset. Mark On Mon, Dec 21, 2009 at 12:43 AM, Wayne Fay wayne...@gmail.com wrote: What's the current storage requirements for the central repository at this time? Per Jarvana, Central is around 100gb, as of mid October 2009: http://www.jarvana.com/jarvana/info/repository_statistics Wayne On Sun, Dec 20, 2009 at 9:09 PM, Mark Diggory mdigg...@gmail.com wrote: I imagine there have to be a number of projects/companies out there using Maven artifacts and incurring bandwidth costs to build systems. Atlassian seems to be recommending the practice to its Bamboo users... http://confluence.atlassian.com/display/BAMBOO/Populating+your+EBS+volume#PopulatingyourEBSvolume-UploadingMaven2repositorydata I know its not much, but on large builds and continuous integration projects would benefit. What's the current storage requirements for the central repository at this time? I wonder if the maven central repo could qualify as a public dataset? http://aws.amazon.com/publicdatasets/ http://developer.amazonwebservices.com/connect/forum.jspa?forumID=55 Mark On Sun, Dec 20, 2009 at 8:28 PM, Carlos Sanchez car...@apache.org wrote: there was some talk about it during ApacheCON but there are some costs associated - S3 storage of the EBS snapshot - bandwidth to upload the repo and keep it up to date - an EC2 machine to do the rsync and scheduled snapshots of the EBS volume There's an option to sell it so users end paying the fees On Sun, Dec 20, 2009 at 8:18 PM, Mark Diggory mdigg...@gmail.com wrote: Cheers, After experimenting a bit with EC2, It seems it would be ideal if there were an EBS volume that had all the Maven central repository within it. Does anyone know of such a thing? thanks, Mark
Re: Amazon EC2 EBS Volume for Maven central repository
FYI Initiating a thread here to see its effect. http://developer.amazonwebservices.com/connect/thread.jspa?messageID=158762#158762 Cheers, Mark On Mon, Dec 21, 2009 at 10:19 AM, Carlos Sanchez car...@apache.org wrote: you can set s3 buckets where requester pays http://developer.amazonwebservices.com/connect/message.jspa?messageID=123715 On Mon, Dec 21, 2009 at 9:30 AM, Brian Fox bri...@infinity.nu wrote: On Mon, Dec 21, 2009 at 12:09 AM, Mark Diggory mdigg...@gmail.com wrote: I imagine there have to be a number of projects/companies out there using Maven artifacts and incurring bandwidth costs to build systems. Atlassian seems to be recommending the practice to its Bamboo users... They should just have a repo manager running in their ec2 grid anyway to reduce bandwidth. We looked into putting central into s3 but then you loose all control over the access and we would get killed by the scrapers constantly downloading everything because it's free.
Amazon EC2 EBS Volume for Maven central repository
Cheers, After experimenting a bit with EC2, It seems it would be ideal if there were an EBS volume that had all the Maven central repository within it. Does anyone know of such a thing? thanks, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Amazon EC2 EBS Volume for Maven central repository
I imagine there have to be a number of projects/companies out there using Maven artifacts and incurring bandwidth costs to build systems. Atlassian seems to be recommending the practice to its Bamboo users... http://confluence.atlassian.com/display/BAMBOO/Populating+your+EBS+volume#PopulatingyourEBSvolume-UploadingMaven2repositorydata I know its not much, but on large builds and continuous integration projects would benefit. What's the current storage requirements for the central repository at this time? I wonder if the maven central repo could qualify as a public dataset? http://aws.amazon.com/publicdatasets/ http://developer.amazonwebservices.com/connect/forum.jspa?forumID=55 Mark On Sun, Dec 20, 2009 at 8:28 PM, Carlos Sanchez car...@apache.org wrote: there was some talk about it during ApacheCON but there are some costs associated - S3 storage of the EBS snapshot - bandwidth to upload the repo and keep it up to date - an EC2 machine to do the rsync and scheduled snapshots of the EBS volume There's an option to sell it so users end paying the fees On Sun, Dec 20, 2009 at 8:18 PM, Mark Diggory mdigg...@gmail.com wrote: Cheers, After experimenting a bit with EC2, It seems it would be ideal if there were an EBS volume that had all the Maven central repository within it. Does anyone know of such a thing? thanks, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Assembly Plugin 2.2-beta-2 Released
We are having problems with mavenn 2.0.8 and maven-assebly-plugin-2.2-beta-2
we can't seem to resolve the new ${modules.artifactId} properties...
for instance...
moduleSets
moduleSet
includes
include*:war:*/include
/includes
excludes
excludeorg.dspace:dspace-oai-webapp/exclude
/excludes
binaries
includeDependenciesfalse/includeDependencies
outputDirectorywebapps/outputDirectory
outputFileNameMapping${module.artifactId
}/outputFileNameMapping
fails to return the name of the current module being processed. This is with
a fresh download of maven 2.0.8 and a fresh recreation of my local
repository that I tested today. All the modules get dumped over top of
eachother and are not separated by their artifactId. If I remove the
outputFileNameMapping, they do get separated and the documented default
${module.artifactId}-${module.version}${dashClassifier?}.${module.extension
}.
gets used appropriately.
thanks for any advice,
-Mark
On Fri, Feb 29, 2008 at 4:04 PM, John Casey [EMAIL PROTECTED] wrote:
The Maven team is pleased to announce the release of the Maven
Assembly Plugin, version 2.2-beta-2
This plugin is used to build custom archives, such as those used to
distribute project releases.
http://maven.apache.org/plugins/maven-assembly-plugin/
You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration (recommended):
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-2/version
/plugin
Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-2
(See: http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=11126styleName=Textversion=14027)
** Bug
* [MASSEMBLY-121] - Custom manifest attributres are ignored.
* [MASSEMBLY-129] - BaseDirectory Ignored When Including a
Repository
* [MASSEMBLY-156] - appendAssemblyId cannot be false
* [MASSEMBLY-162] - In a multiproject environment, assembly
takes wrong dependencies
* [MASSEMBLY-163] - In a multiproject environment Assembly
causes many unneded rebuilds
* [MASSEMBLY-178] - filtering doesn't read filter files
* [MASSEMBLY-179] - Assembled jar includes artifact names in path
* [MASSEMBLY-180] - A bug in artifact filtering ( maven-common-
artifact-filters )
* [MASSEMBLY-183] - assembly:attached does not work with filter-
ERROR: Cannot override read-only parameter
* [MASSEMBLY-184] - components are not interpolated - i.e., $
{params} are not substituted
* [MASSEMBLY-188] - manifestEntries are not set in resulting jar
* [MASSEMBLY-189] - plugin not correctly interpolating POM
variables like project.build.directory
* [MASSEMBLY-194] - unnecessary dependency expansion regression
* [MASSEMBLY-195] - unpackOptions ignored
* [MASSEMBLY-197] - 2.2-beta-1 regression, project artifact no
longer included in
* [MASSEMBLY-208] - Assembly plugin does not resolve version
ranges correctly
* [MASSEMBLY-210] - repository does not include the parent pom
* [MASSEMBLY-212] - Assembly Descriptor Schemas (XSD) have wrong
targetNamespace
* [MASSEMBLY-214] - java.lang.NullPointerException: version was
null for junit:junit
* [MASSEMBLY-221] - Filtering doesn't work when a file matches
both a fileSet and a file
* [MASSEMBLY-222] - 2.2-beta-1 regression in assembly descriptor
interpolation
* [MASSEMBLY-223] - 2-nd exclude element of
dependencySets:excludes doesn't work
* [MASSEMBLY-225] - Not a v4.0.0 POM
* [MASSEMBLY-226] - Filters as read-only parameter can break the
assembly build of a multi-module project
* [MASSEMBLY-232] - NPE - MASSEMBLY-222 fix broken?
* [MASSEMBLY-233] - Custom ContainerDescriptorHandler
integration tests don't work in Maven 2.0.7
* [MASSEMBLY-234] - Artifacts not deployed
* [MASSEMBLY-235] - dependencySet ignores dependency management
* [MASSEMBLY-250] - Trunk of assembly plugin broken and not in
synch with deployed 2.2-beta2-SNAPSHOT ?
* [MASSEMBLY-254] - Not a v4.0.0 POM Still an Issue
* [MASSEMBLY-257] - OutOfMemoryError when assembling large
binary file
* [MASSEMBLY-262] - unit fail in trunk on windows (need upgrade
of plexus-utils)
* [MASSEMBLY-266] - Property expansion does not work for $
{project.build.finalName} in descriptor file
* [MASSEMBLY-277] - NullPointerException
* [MASSEMBLY-282] - Fix failing IT no-appendAssemblyId-no-
classifier
** Improvement
* [MASSEMBLY-136] - outputDirectory to support absolute paths
* [MASSEMBLY-142] - Should be able to use artifact version as
variable in outputDirectory
* [MASSEMBLY-152] - Support Ant token
* [MASSEMBLY-154] - FileSet does not support filtering
* [MASSEMBLY-182] -
create:archetype won't work on my installed archetype... can't test my development.
So, I'm trying to author an archetype for our project and have it located here in source: https://dspace-sandbox.googlecode.com/svn/team/maven/plugins/dspace-addon-archetype/trunk My problem is that if I check this out and run mvn package install I expect that it will be installed into my local repository and accessible via: mvn archetype:create -DarchetypeGroupId=org.dspace.maven.plugins -DarchetypeArtifactId=dspace-addon-archetype -DarchetypeVersion=1.5-beta1 -DgroupId=org.my.groupid-DartifactId=my-module-name but archetype:create can't seem to find it? Did the usual Google research... But don't understand the new maven archetype plugin logic. thanks, Mark Diggory
Re: create:archetype won't work on my installed archetype... can't test my development.
I'll add that the website for the 2.0-alpha1 is horribly broken... http://maven.apache.org/plugins/index.html http://maven.apache.org/plugins/maven-archetype-plugin/ click on any navigation otpions and they send back 404's On Fri, Feb 15, 2008 at 3:08 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Fri, Feb 15, 2008 at 3:56 PM, Mark Diggory [EMAIL PROTECTED] wrote: I'm trying to author an archetype for our project and have it located here in source: https://dspace-sandbox.googlecode.com/svn/team/maven/plugins/dspace-addon-archetype/trunk My problem is that if I check this out and run mvn package install (Unrelated, but just 'mvn install' will work. It will run through all the phases up to and including install, which already includes package.) I expect that it will be installed into my local repository and accessible via: mvn archetype:create -DarchetypeGroupId=org.dspace.maven.plugins -DarchetypeArtifactId=dspace-addon-archetype -DarchetypeVersion= 1.5-beta1 -DgroupId=org.my.groupid-DartifactId=my-module-name but archetype:create can't seem to find it? What is the error you're seeing? mark-diggorys-computer-2:~/workspace-bbp-1.5/dspace-1_5-beta1/dspace/modules mdiggory$ mvn archetype:create -DarchetypeGroupId=org.dspace.maven.plugins -DarchetypeArtifactId=dspace-addon-archetype -DarchetypeVersion=1.5-beta1 -DgroupId=org.your.groupid-DartifactId=your-module-name -U -N [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking for updates from central [INFO] [INFO] Building DSpace Addon Modules [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Preparing archetype:create [INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-assembly-plugin: checking for updates from central [INFO] No goals needed for project - skipping Downloading: http://repo1.maven.org/maven2/org/your/groupid/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom Downloading: http://repo1.maven.org/maven2/org/your/groupid/wagon-http-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom [INFO] Setting property: classpath.resource.loader.class = ' org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:create] [WARNING] No archetype repository found. [WARNING] Specified archetype not found. Choose archetype: 1: internal - appfuse-basic-jsf (AppFuse archetype for creating a web application with Hibernate, Spring and JSF) 2: internal - appfuse-basic-spring (AppFuse archetype for creating a web application with Hibernate, Spring and Spring MVC) 3: internal - appfuse-basic-struts (AppFuse archetype for creating a web application with Hibernate, Spring and Struts 2) yada yada yada Did the usual Google research... But don't understand the new maven archetype plugin logic. It may just be a bug/different behavior in the new archetype plugin. There should be a new release soon that makes it behave more like the old version. You can check JIRA or the discussion on the dev list for more info. Does it work if you use the 1.0 archetype plugin? Start with: mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create ... That results in the following error [DEBUG] Configuring mojo ' org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create' -- [DEBUG] (f) archetypeArtifactId = dspace-addon-archetype [DEBUG] (f) archetypeGroupId = org.dspace.maven.plugins [DEBUG] (f) archetypeVersion = 1.5-beta1 [DEBUG] (f) artifactId = your-module-name [DEBUG] (f) basedir = /Users/mdiggory/workspace-bbp-1.5 /dspace-1_5-beta1/dspace/modules [DEBUG] (f) groupId = org.your.groupid [DEBUG] (f) localRepository = [local] - file:///Users/mdiggory/.m2/repository [DEBUG] (f) pomRemoteRepositories = [[maven.dspace.org-snapshot] - http://maven.dspace.org/snapshot, [maven.dspace.org/snapshot] - http://maven.dspace.org/snapshot, [central] - http://repo1.maven.org/maven2 ] [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) version = 1.0-SNAPSHOT [DEBUG] -- end configuration -- [INFO] [archetype:create] [INFO] Defaulting package to group ID: org.your.groupid [INFO] [INFO] Using following parameters for creating Archetype: dspace-addon-archetype:1.5-beta1 [INFO
Re: assembly project properties
I see this is still the case, even with the 2.2.-beta-2 version. Only a few
properties are available (artifactId, version) otherslike
project.build.directory, or the configuration properties from the pom are
not available.
thanks,
Mark
Stefano Fornari wrote:
Hi All,
I am interested to know if there is any documentation that specifies
which exact project properties will be filtered when filtering is
used. I searched the list and the assembly and resources plugins
documentation but I could not find a proper list.
I am particularly interested into accessing the dependency version
number (or even artifactId). for example, if my projects depends on
foo:artifact-1.0, how can I have a text file with any ${} expansion
rule that will expand in the mentioned dependency?
Many thanks in advance.
Stefano
--
Stefano Fornari - Funambol Chief Architect / Funambol CTO
===
Home:
http://www.funambol.org
Documents:
http://www.funambol.org/documentation/documents.html
FAQ:
http://www.funambol.org/support/faq.html
WIKI:
https://wiki.objectweb.org/sync4j/
Mailinglist archives:
http://groups.yahoo.com/group/Sync4j (login required)
http://sourceforge.net/mailarchive/forum.php?forum_id=215 (sync4j-users)
http://sourceforge.net/mailarchive/forum.php?forum_id=48877
(funambol-dev)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/assembly-project-properties-tf4341762s177.html#a13661098
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: setting up rsync remote repo and release questions
Sorry, thats an error, yes some of the Apache stuff we are working with did not have latest versions in the central repo, I see Lucene 2.2.0 was placed in there earlier this summer and I'll switch us to that. We'll also ask about getting the latest bouncycastle jars added as well. -Mark On Oct 2, 2007, at 11:06 PM, Dan Tran wrote: just curious, why repackage lucene? -D On 10/2/07, Carlos Sanchez [EMAIL PROTECTED] wrote: 1) yes 2) yes On 10/3/07, Mark Diggory [EMAIL PROTECTED] wrote: I'm following the guidelines located here and trying to prepare our repository to be rsynced into the central repo. http://maven.dspace.org/release http://maven.dspace.org/snapshot I have a few questions. 1.) by release do you mean that only true versioned releases (not snapshots) can be rsynced to the central repo? 2.) We have our own compilations of apache cocoon, lucene and other various jars (bouncy-castle, jena (hp) which we need to maintain slightly customized for our project. we keep these under our org.dspace groupId, is it ok to place releases of these third party jars in our groupId space? dependency groupIdorg.dspace/groupId artifactIdjena/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdhandle/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdjargon/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdmets/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdbcprov-jdk15/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdbcmail-jdk15/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdlucene/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdtm-extractors/artifactId /dependency thanks, Mark ~ Mark R. Diggory - DSpace Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bouncycastle Jars
Is Bouncycastle responsible for publishing their jars under ( http:// repo1.maven.org/maven2/bouncycastle/ )or is someone else doing it? There are a few additions we are hoping to see in the repository. thanks, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
setting up rsync remote repo and release questions
I'm following the guidelines located here and trying to prepare our repository to be rsynced into the central repo. http://maven.dspace.org/release http://maven.dspace.org/snapshot I have a few questions. 1.) by release do you mean that only true versioned releases (not snapshots) can be rsynced to the central repo? 2.) We have our own compilations of apache cocoon, lucene and other various jars (bouncy-castle, jena (hp) which we need to maintain slightly customized for our project. we keep these under our org.dspace groupId, is it ok to place releases of these third party jars in our groupId space? dependency groupIdorg.dspace/groupId artifactIdjena/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdhandle/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdjargon/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdmets/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdbcprov-jdk15/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdbcmail-jdk15/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdlucene/artifactId /dependency dependency groupIdorg.dspace/groupId artifactIdtm-extractors/artifactId /dependency thanks, Mark ~ Mark R. Diggory - DSpace Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology
Re: Snapshot access to maven-assembly-plugin-2.2-beta-2-SNAPSHOT
Yes, it appears to be working now. I'm unsure why it wasn't working earlier, I was using the proper settings for the repository location and proper groupId and artifactID dependency groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-2-SNAPSHOT/version /dependency /dependencies repository idpeople.apache.org-m2-snapshot-repository/id nameApache Snapshot Maven Repository/name urlhttp://people.apache.org/repo/m2-snapshot-repository/url releases updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /releases snapshots updatePolicyalways/updatePolicy checksumPolicyfail/checksumPolicy /snapshots /repository Thanks again, Mark In article [EMAIL PROTECTED] Tim Kettler [EMAIL PROTECTED]wrote: Hi, this works for me without problems: [...] plugin artifactIdmaven-assembly-plugin/artifactId version2.2-beta-2-SNAPSHOT/version plugin [...] What exactly is your problem? Have you configured the the Apache snapshot repository [1]? -Tim [1] http://maven.apache.org/guides/development/guide-plugin-snapshot-repos itories.html Mark Diggory schrieb: I'm having difficulty getting Maven to detect the maven-assembly-plugin snapshots at http://people.apache.org/repo/m2-snapshot-repository. While I can download maven-assembly-plugin-2.2-SNAPSHOT the wierd beta-N numbering scheme seems to be confusing Maven. Is there any way we can get a new SNAPSHOT under 2.2-SNAPSHOT or lose the number on the beta in people? thanks, Mark Diggory ~ Mark R. Diggory - DSpace Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I'm trying a new usenet client for Mac, Nemo OS X. You can download it at http://www.malcom-mac.com/nemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Merge assemblies across projects?
Hello List, I have a couple projects (each with their own assemblies) as modules of a current project. Is there a way I can have their generated assemblies merged when I call assembly:assembly? thanks, Mark ~ Mark R. Diggory - DSpace Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repo down?
You can't if its the first time you've run maven, anyone trying to use maven for the first time can't get the proper plugins because its looking for Snapshots on codehaus. Seems if your going to do a full release of maven it would be wise to base it on full releases of the plugins in the mirrors, or at least a full release of maven and/or any plugin maintained and required by maven should be full released and often, then this sort of thing wouldn't happen. Look at Eclipse and the way they organize thier updates into integration, stable and release builds. For instance, EMF has a interim and stable update sites. This is one of the reasons I really pushed to have separate snapshot and release repositories at Apache, product stability. -Mark p.s. there was a comment I should set up a mirror or something crazy like that, it assumes I have some extensive knowledge of maven, which at this point with maven 2 I don't. While I understand you guys do allot of development and are focused on new features and bug fixes, it makes your product look bad to have single points of failure like this, I'm evaluating maven 2 for a project I'm now working on, this doesn't bode well in my evaluation. On May 16, 2006, at 8:25 AM, javed mandary wrote: You can use the -o flag , e.g mvn -o install this will tell maven to work in offline mode and it wont try to check for updates on the remote repo. cheers, javed On 5/15/06, Markus Reinhardt [EMAIL PROTECTED] wrote: Am Montag, den 15.05.2006, 11:20 +0200 schrieb Jörg Schaible: Geoffrey De Smet wrote on Monday, May 15, 2006 10:26 AM: Ibiblio is up, but the dns server of maven.org seems to be down. Brett Porter wrote: http://maven.apache.org/guides/mini/ guide-mirror-settings.html Yes, it's down. Unscheduled, and beyond our control, sorry. But, since the new plugin releases refer to artifacts only available in snapshots.maven.codehaus.org/maven2, our complete development comes to a sudden stop, because of the automated update. Please, make sure for such releases, that all artifacts are available at ibiblio (which is at least mirrored). Who do I to tell maven not to search for updates? Neither -o nor -npu switches help. All needed plugins (tomcat-maven-plugin:pom:1.0- SNAPSHOT) are located in my local repo. Markus Reinhardt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEaEpxTPqyj/tXZEMRAowGAKCfn8AEqNqeA/EVm66Fv53SO9PD6gCgtCzW gzcI00BTuqBtvCIYuKuP8BA= =lMx0 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repo down?
Can anyone clearly detail what I have to do to point ibiblio or another mirror instead of codehaus containing these snapshots mvn is attempting to download when I run mvn site? Answer the question as if I've no previous experience with maven Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transferring file org.apache.maven.doxia:doxia:pom:1.0-alpha-8 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://svn.apache.org/maven-snapshot-repository), snapshots (http://snapshots.maven.codehaus.org/maven2) -Mark On May 16, 2006, at 11:57 AM, Adam Leggett wrote: In hindsight, maven-proxy would of been worth setting up. Indeed. I was able to do this today in approx 15 minutes and point it to ibiblio. Despite http://maven-proxy.codehaus.org/ also being down. Now we all go via maven-proxy here. Isnt google cache a lovely thing :-) ? -Original Message- From: ben short [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 16, 2006 3:51 PM To: Maven Users List Subject: Re: repo down? In hindsight, maven-proxy would of been worth setting up. On 5/16/06, Mark Hansen [EMAIL PROTECTED] wrote: +1 !!! Is there anybody who can fix this problem with the repository? I've got a bunch of developers in India who have installed m2 and need to build our company's plugins. We are losing man-days of work because of this. Mark Diggory wrote: You can't if its the first time you've run maven, anyone trying to use maven for the first time can't get the proper plugins because its looking for Snapshots on codehaus. Seems if your going to do a full release of maven it would be wise to base it on full releases of the plugins in the mirrors, or at least a full release of maven and/or any plugin maintained and required by maven should be full released and often, then this sort of thing wouldn't happen. Look at Eclipse and the way they organize thier updates into integration, stable and release builds. For instance, EMF has a interim and stable update sites. This is one of the reasons I really pushed to have separate snapshot and release repositories at Apache, product stability. -Mark p.s. there was a comment I should set up a mirror or something crazy like that, it assumes I have some extensive knowledge of maven, which at this point with maven 2 I don't. While I understand you guys do allot of development and are focused on new features and bug fixes, it makes your product look bad to have single points of failure like this, I'm evaluating maven 2 for a project I'm now working on, this doesn't bode well in my evaluation. On May 16, 2006, at 8:25 AM, javed mandary wrote: You can use the -o flag , e.g mvn -o install this will tell maven to work in offline mode and it wont try to check for updates on the remote repo. cheers, javed On 5/15/06, Markus Reinhardt [EMAIL PROTECTED] wrote: Am Montag, den 15.05.2006, 11:20 +0200 schrieb Jörg Schaible: Geoffrey De Smet wrote on Monday, May 15, 2006 10:26 AM: Ibiblio is up, but the dns server of maven.org seems to be down. Brett Porter wrote: http://maven.apache.org/guides/mini/ guide-mirror-settings.html Yes, it's down. Unscheduled, and beyond our control, sorry. But, since the new plugin releases refer to artifacts only available in snapshots.maven.codehaus.org/maven2, our complete development comes to a sudden stop, because of the automated update. Please, make sure for such releases, that all artifacts are available at ibiblio (which is at least mirrored). Who do I to tell maven not to search for updates? Neither -o nor -npu switches help. All needed plugins (tomcat-maven-plugin:pom:1.0- SNAPSHOT) are located in my local repo. Markus Reinhardt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEaEpxTPqyj/tXZEMRAowGAKCfn8AEqNqeA/EVm66Fv53SO9PD6gCgtCzW gzcI00BTuqBtvCIYuKuP8BA= =lMx0 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] == = The contents of this email are intended for the named addresses and may contain confidential and/or privileged material. If received in error, please contact UPCO head office on +44(0)113 201 0600 and then delete the entire mail from your system. Unauthorised review, distribution, disclosure or other use of information could constitute a breach of confidence. Your co-operation in this matter is greatly appreciated. Every effort has been taken to ensure that this email and any attachments are virus-free. However, UPCO does not make any warranty to this effect, and is not liable for any damage done
Re: Doxia/site problems - FIXED
Thanks Brett, yes mvn site works as well. glad to see it up. (p.s. after a year or two of being away from Apache due to work, it looks like I'm going to have opportunities to get involved again in my new position) :-) -Mark On May 16, 2006, at 1:10 PM, Bob Arnott wrote: Brett Porter wrote: Hi, This should now be fixed. Please remove the following files from your local repository to correct the issue: org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-8/doxia-site- renderer-1.0-alpha-8.pom org/mortbay/jetty/project/6.0.0beta15/ project-6.0.0beta15.pom org/apache/maven/plugins/maven-site-plugin/2.0-beta-5/maven-site- plugin-2.0-beta-5.pom Top man Brett! My mvn deploy works now, thank you. Cheers, -- Bob Arnott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependency search engine?
Hi everyone, is there any effort to put together a dependency search engine that would allow one to search the maven repository for a particular dependency not knowing its group id or proper version to use. For instance, I've been using Google with limited success. http://www.google.com/search?hl=enlr=q=site%3Ahttp%3A%2F% 2Fibiblio.org%2Fmaven2%2F+servlet-api+jarbtnG=Search Seems as though there could be some very interesting statistics gathering done here... -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency search engine?
thank you, this is just what I needed. On May 16, 2006, at 3:18 PM, Wayne Fay wrote: Here are 2 such sites: http://www.mvnregistry.com http://mvnrepository.com Also, if the artifact you're looking for is in your local m2 repo, Jerome Lacoste posted a blog entry on how to search it for things: http://www.coffeebreaks.org/blogs/?p=47 Wayne On 5/16/06, Mark Diggory [EMAIL PROTECTED] wrote: Hi everyone, is there any effort to put together a dependency search engine that would allow one to search the maven repository for a particular dependency not knowing its group id or proper version to use. For instance, I've been using Google with limited success. http://www.google.com/search?hl=enlr=q=site%3Ahttp%3A%2F% 2Fibiblio.org%2Fmaven2%2F+servlet-api+jarbtnG=Search Seems as though there could be some very interesting statistics gathering done here... -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mojo jdepend plugin
I think I'm encountering another issues with codehaus being down. I'm trying to install the jdepend plugin, any tips on how to handle this with codehaus down? many thanks, Mark plugin groupIdorg.codehaus.mojo/groupId artifactIdjdepend-maven-plugin/artifactId /plugin
Cannot connect to codehaus?
I'm trying to build a project with the latest download of Maven and am encountering the following error. I see as well that codehaus.org is not up. Is there any way to get Maven site to generate without using codehaus? -Mark mdiggory$ mvn -e site + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building DSpace Core Library [INFO]task-segment: [site] [INFO] Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/ maven/doxia/doxia/1.0-alpha-8/doxia-1.0-alpha-8.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: null:doxia-site-renderer:jar:1.0-alpha-8 Reason: Cannot find parent: org.apache.maven.doxia:doxia for project: null:doxia-site-renderer:jar:1.0-alpha-8 [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.maven.doxia:doxia-site-renderer:jar': Cannot find parent: org.apache.maven.doxia:doxia for project: null:doxia-site- renderer:jar:1.0-alpha-8 org.apache.maven.doxia:doxia-site-renderer:jar:1.0-alpha-8 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://svn.apache.org/maven-snapshot-repository), snapshots (http://snapshots.maven.codehaus.org/maven2) Path to dependency: 1) org.apache.maven.plugins:maven-project-info-reports- plugin:maven-plugin:2.0 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports (DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports (DefaultLifecycleExecutor.java:637) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.maven.doxia:doxia-site-renderer:jar': Cannot find parent: org.apache.maven.doxia:doxia for project: null:doxia-site-renderer:jar:1.0-alpha-8 org.apache.maven.doxia:doxia-site-renderer:jar:1.0-alpha-8 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://svn.apache.org/maven-snapshot-repository), snapshots (http://snapshots.maven.codehaus.org/maven2) Path to dependency: 1) org.apache.maven.plugins:maven-project-info-reports- plugin:maven-plugin:2.0 at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse (DefaultArtifactCollector.java:297) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect (DefaultArtifactCollector.java:67) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:223) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:211) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi
