It's fine to have your own repo with snapshots and needed things like ojb until is fixed in ibiblio, knowing that those things are temporal and avoiding a release depending on them, eg. removing that repo before making a relese and be sure that everything is fine.
For your custom jars you can upload them to your namespace in ibiblio (org.appfuse or any other of your domains) About xwork-optional.dev.java.nen the groupId should be net.java.dev.xwork-optional or an y other domain they own. Regards On 11/26/05, Matt Raible <[EMAIL PROTECTED]> wrote: > On 11/24/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > I don't think you should go down that path, as you will introduce > > confusion for your users. Poms in ibiblio have to be suitable for > > everybody, any customization needed can be added to your own pom as > > exclusions, overriding,... > > I agree that it's not the best solution, and I'd *love* to upload all > my dependencies to ibiblio, but I don't know if there's an issue with > some of them. For instance, here's a list of custom JARs/POMs I have > and why: > > OJB (http://static.appfuse.org/repository/ojb/db-ojb/1.0.3/), b/c the > POM hasn't been updated yet: > http://jira.codehaus.org/browse/MEV-231 > > Spring+XWork Integration > (http://static.appfuse.org/repository/opensymphony/spring-xwork-integration/1.0/), > b/c there was never a release. > > * Doh - now that I check, there is a release > (https://xwork-optional.dev.java.net/servlets/ProjectDocumentList?folderID=1425). > I'll create an upload request. I'll go with a groupId of > xwork-optional and artifactId of spring-xwork-integration. > > Tapestry Mock > (http://static.appfuse.org/repository/tapestry/tapestry-mock/3.0/), > this is a custom JAR I created from Tapestry's testing framework in > their CVS tree. It seems it would be inappropriate to create a JAR in > their namespace that's not part of their distribution. Maybe I could > create a request to upload this under the org.appfuse groupId? > > DWR (http://static.appfuse.org/repository/uk/ltd/getahead/dwr/1.0/), > b/c the POM hasn't been updated for M2 yet > (http://jira.codehaus.org/browse/MEV-232). > > Matt > > > > > On 11/24/05, Matt Raible <[EMAIL PROTECTED]> wrote: > > > It is possible to make ibiblio correct, I'm just looking for a > > > workaround in the meantime. ;-) > > > > > > I've been entering invalid POM bugs into JIRA as I see them (20+ so > > > far). However, there might be times where Maven developers and I don't > > > agree, and it'd be nice to customize the POMs when that happens. > > > Hopefully it won't happen that often. > > > > > > Matt > > > > > > On 11/24/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > > > Is it not possible to make ibibio correct or do you have special needs > > > > for > > > > your pom that others do not have? > > > > > > > > regards, > > > > > > > > Wim > > > > > > > > 2005/11/24, Matt Raible <[EMAIL PROTECTED]>: > > > > > > > > > > I've established my own repository for overriding POMs in ibiblio. > > > > > This seems to work great, but I still get a warning when M2 can't find > > > > > the JAR in my repo. It still goes to ibiblio and gets the correct > > > > > one, so I'd like to turn off the warning - especially since I'm only > > > > > overriding a few POMs and JARs. Developers will end up seeing a whole > > > > > bunch of errors like the following. > > > > > > > > > > > > > > > [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.pom > > > > > [artifact:dependencies] Transferring 0K > > > > > [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.jar > > > > > [artifact:dependencies] [WARNING] Unable to get resource from > > > > > repository > > > > > remote > > > > > (http://static.appfuse.org/repository) > > > > > [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.jar > > > > > [artifact:dependencies] Transferring 1141K > > > > > > > > > > Is it possible to turn off this warning? > > > > > > > > > > Thanks, > > > > > > > > > > Matt > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > --------------------------------------------------------------------- > 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]
