Re: proxied repositories -- plugin question
The one in the Dev Java Net repo looks like this: org.jvnet.jaxb2.maven2 maven-jaxb2-plugin 0.1 0.5 0.5 0.1 0.2 0.4 0.4.M1 0.4.M2 0.4.M3 0.5 20071215123957 The one in archiva looks like this: org.jvnet.jaxb2 maven2 maven-jaxb2-plugin 20071215123957 On Tue, 2008-01-29 at 13:51 -0700, Wendy Smoak wrote: > On Jan 29, 2008 1:44 PM, Eric Miles <[EMAIL PROTECTED]> wrote: > > Figured out my problem although not sure why it's NOT a problem when I > > don't use Archiva. This particular plugin (and no others) requires that > > I specify the version in order for the dependency to be downloaded. > > This isn't desirable as I'd like to have the upgrades to the plugins > > when they happen, however this is a workaround. > > > > Is this particular plugin deployed incorrectly? Is that why > > archiva/maven can not find the correct current version information? > > I'm curious, what does the maven-metadata.xml file look like through > Archiva? Does it match what you see in the remote repo? > > (If it's missing the 'latest' and/or 'release' elements for a plugin, > Maven will complain.) > > FWIW, specifying the plugin version is a best practice to help ensure > reproducible builds. >
Re: proxied repositories -- plugin question
On Jan 29, 2008 1:44 PM, Eric Miles <[EMAIL PROTECTED]> wrote: > Figured out my problem although not sure why it's NOT a problem when I > don't use Archiva. This particular plugin (and no others) requires that > I specify the version in order for the dependency to be downloaded. > This isn't desirable as I'd like to have the upgrades to the plugins > when they happen, however this is a workaround. > > Is this particular plugin deployed incorrectly? Is that why > archiva/maven can not find the correct current version information? I'm curious, what does the maven-metadata.xml file look like through Archiva? Does it match what you see in the remote repo? (If it's missing the 'latest' and/or 'release' elements for a plugin, Maven will complain.) FWIW, specifying the plugin version is a best practice to help ensure reproducible builds. -- Wendy
Re: proxied repositories -- plugin question
Figured out my problem although not sure why it's NOT a problem when I don't use Archiva. This particular plugin (and no others) requires that I specify the version in order for the dependency to be downloaded. This isn't desirable as I'd like to have the upgrades to the plugins when they happen, however this is a workaround. Is this particular plugin deployed incorrectly? Is that why archiva/maven can not find the correct current version information? Thanks! Eric On Tue, 2008-01-29 at 10:00 -0500, Eric Miles wrote: > I have a managed repository that I intend to use as a proxy for several > remote repositories. I'm doing a test and can't get the proxy to > resolve a plugin dependency to save my life. It will however resolve > regular dependencies to same remote repository. I am attempting to > proxy the Dev Java Net remote repoistory. > > Here is my pom: > > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > archiva-test > archiva-test > 0.0.1-SNAPSHOT > > > > org.j4j > j4j > 1.0 > > > javax.xml.bind > jaxb-api > 2.1 > compile > > > org.jtb > quickr > 0.8 > > > > > proxied > > http://myproxyserver/archiva/repository/proxied > > > > > > proxied > > http://myproxyserver/archiva/repository/proxied > > > > > > > true > src/main/resources > > > > > org.jvnet.jaxb2.maven2 > maven-jaxb2-plugin > > > > generate > > > > > > > **/*.xsd > > true > > > > > > > I have no problems resolving and proxying quickr and j4j dependencies, > but I get the following error for the jaxb2 maven plugin: > > $ mvn clean package > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - archiva-test:archiva-test:jar:0.0.1-SNAPSHOT > [INFO]task-segment: [clean, package] > [INFO] > > [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking > for updates from proxied > [INFO] artifact org.jvnet.jaxb2.maven2:maven-jaxb2-plugin: checking for > updates from proxied > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Tue Jan 29 09:38:40 EST 2008 > [INFO] Final Memory: 1M/254M > [INFO] > > > > Any suggestions? Thanks in advance. > > Eric
proxied repositories -- plugin question
I have a managed repository that I intend to use as a proxy for several remote repositories. I'm doing a test and can't get the proxy to resolve a plugin dependency to save my life. It will however resolve regular dependencies to same remote repository. I am attempting to proxy the Dev Java Net remote repoistory. Here is my pom: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 archiva-test archiva-test 0.0.1-SNAPSHOT org.j4j j4j 1.0 javax.xml.bind jaxb-api 2.1 compile org.jtb quickr 0.8 proxied http://myproxyserver/archiva/repository/proxied proxied http://myproxyserver/archiva/repository/proxied true src/main/resources org.jvnet.jaxb2.maven2 maven-jaxb2-plugin generate **/*.xsd true I have no problems resolving and proxying quickr and j4j dependencies, but I get the following error for the jaxb2 maven plugin: $ mvn clean package [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - archiva-test:archiva-test:jar:0.0.1-SNAPSHOT [INFO]task-segment: [clean, package] [INFO] [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from proxied [INFO] artifact org.jvnet.jaxb2.maven2:maven-jaxb2-plugin: checking for updates from proxied [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jan 29 09:38:40 EST 2008 [INFO] Final Memory: 1M/254M [INFO] Any suggestions? Thanks in advance. Eric
