You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Henrik Schmidt (JIRA)" <ji...@codehaus.org> on 2007/12/27 01:50:58 UTC
[jira] Created: (MRM-644) org.jvnet.jaxb2.maven2:maven-jaxb2-plugin
is not resolved correctly using Archiva as mirror
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly using Archiva as mirror
-------------------------------------------------------------------------------------------
Key: MRM-644
URL: http://jira.codehaus.org/browse/MRM-644
Project: Archiva
Issue Type: Bug
Affects Versions: 1.0
Environment: Maven version: 2.0.8
Java version: 1.6.0_03
OS name: "linux" version: "2.6.22-14-generic" arch: "i386" Family: "unix"
Reporter: Henrik Schmidt
Attachments: myproject.pom.xml, schema.xsd, settings.xml
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly with <version> tag omitted in pom.xml. Omitting the <version> tag works if Archiva is not used (Maven will just get the latest version).
Steps to reproduce:
Archiva application:
Unpack and run archiva
$ tar zxvf apache-archiva-1.0-bin.tar.gz
$ apache-archiva-1.0/bin/linux-x86-32/run.sh start
Navigate to http://localhost:8080/archiva
create Admin user and login
In Repositories (under Administration):
Add remote Maven 1 legacy repository
Identifier: maven-repository.dev.java.net
Name: Java.net Maven 1 Repository (legacy)
URL: http://download.java.net/maven/1
Type: Maven 1.x Repository
Add remote Maven 2 jfrog-plugins repository
Identifier: jfrog-plugins
Name: jFrog plugins
URL: http://www.jfrog.org/artifactory/plugins-releases
Type: Maven 2.x repository
In Proxy Connectors (under Administration)
Edit maven2-repository.dev.java.net proxy connector
Remove "jaxax/**" whitelist constraint and click Save Proxy Connector
Add Proxy Connectors
Managed Repository: internal
Remote Repository: maven-repository.dev.java.net
cache-failures: yes
releases: once
checksum: fix
snapshots: never
Managed Repository: internal
Remote Repository: jfrog-plugins
cache-failures: yes
releases: once
checksum: fix
snapshots: never
Client side:
Copy settings.xml to ~/.m2
$ cp settings.xml ~/.m2
Create sample project
$ mvn archetype:create -DgroupId=some.namespace -DartifactId=myproject
Overwrite pom.xml
$ cp myproject.pom.xml myproject/pom.xml
Add sample XML schema
$ mkdir myproject/src/main/resources
$ cp schema.xsd myproject/src/main/resources/
Run test
$ cd myproject
$ mvn test
This should fail with BUILD ERROR "The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid version could be found"
Workaround:
uncomment <version> tag in pom.xml and run test again
Now mvn test should succeed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-644) org.jvnet.jaxb2.maven2:maven-jaxb2-plugin
is not resolved correctly using Archiva as mirror
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-644:
-----------------------------
Fix Version/s: (was: 1.x)
1.0.x
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly using Archiva as mirror
> -------------------------------------------------------------------------------------------
>
> Key: MRM-644
> URL: http://jira.codehaus.org/browse/MRM-644
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Maven version: 2.0.8
> Java version: 1.6.0_03
> OS name: "linux" version: "2.6.22-14-generic" arch: "i386" Family: "unix"
> Reporter: Henrik Schmidt
> Fix For: 1.0.x
>
> Attachments: myproject.pom.xml, schema.xsd, settings.xml
>
>
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly with <version> tag omitted in pom.xml. Omitting the <version> tag works if Archiva is not used (Maven will just get the latest version).
> Steps to reproduce:
> Archiva application:
> Unpack and run archiva
> $ tar zxvf apache-archiva-1.0-bin.tar.gz
> $ apache-archiva-1.0/bin/linux-x86-32/run.sh start
> Navigate to http://localhost:8080/archiva
> create Admin user and login
> In Repositories (under Administration):
> Add remote Maven 1 legacy repository
> Identifier: maven-repository.dev.java.net
> Name: Java.net Maven 1 Repository (legacy)
> URL: http://download.java.net/maven/1
> Type: Maven 1.x Repository
> Add remote Maven 2 jfrog-plugins repository
> Identifier: jfrog-plugins
> Name: jFrog plugins
> URL: http://www.jfrog.org/artifactory/plugins-releases
> Type: Maven 2.x repository
> In Proxy Connectors (under Administration)
> Edit maven2-repository.dev.java.net proxy connector
> Remove "jaxax/**" whitelist constraint and click Save Proxy Connector
> Add Proxy Connectors
> Managed Repository: internal
> Remote Repository: maven-repository.dev.java.net
> cache-failures: yes
> releases: once
> checksum: fix
> snapshots: never
> Managed Repository: internal
> Remote Repository: jfrog-plugins
> cache-failures: yes
> releases: once
> checksum: fix
> snapshots: never
> Client side:
> Copy settings.xml to ~/.m2
> $ cp settings.xml ~/.m2
> Create sample project
> $ mvn archetype:create -DgroupId=some.namespace -DartifactId=myproject
> Overwrite pom.xml
> $ cp myproject.pom.xml myproject/pom.xml
> Add sample XML schema
> $ mkdir myproject/src/main/resources
> $ cp schema.xsd myproject/src/main/resources/
> Run test
> $ cd myproject
> $ mvn test
> This should fail with BUILD ERROR "The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid version could be found"
> Workaround:
> uncomment <version> tag in pom.xml and run test again
> Now mvn test should succeed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-644)
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly using
Archiva as mirror
Posted by "Johannes Tuchscherer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148564#action_148564 ]
Johannes Tuchscherer commented on MRM-644:
------------------------------------------
I do hit the same issue using Archiva 1.1.2 with the org.codehaus.mojo jab2-maven-plugin.
The maven-metadata xml files for the remote repositories look all good, but the maven-metadata-central.xml looks like the one of Lorant:
<metadata>
<groupId>org.codehaus</groupId>
<artifactId>mojo</artifactId>
<version>jab2-maven-plugin</version>
</metadata>
I always need to clean this up by hand to make it work.
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly using Archiva as mirror
> -------------------------------------------------------------------------------------------
>
> Key: MRM-644
> URL: http://jira.codehaus.org/browse/MRM-644
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Maven version: 2.0.8
> Java version: 1.6.0_03
> OS name: "linux" version: "2.6.22-14-generic" arch: "i386" Family: "unix"
> Reporter: Henrik Schmidt
> Fix For: 1.1.x
>
> Attachments: myproject.pom.xml, schema.xsd, settings.xml
>
>
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly with <version> tag omitted in pom.xml. Omitting the <version> tag works if Archiva is not used (Maven will just get the latest version).
> Steps to reproduce:
> Archiva application:
> Unpack and run archiva
> $ tar zxvf apache-archiva-1.0-bin.tar.gz
> $ apache-archiva-1.0/bin/linux-x86-32/run.sh start
> Navigate to http://localhost:8080/archiva
> create Admin user and login
> In Repositories (under Administration):
> Add remote Maven 1 legacy repository
> Identifier: maven-repository.dev.java.net
> Name: Java.net Maven 1 Repository (legacy)
> URL: http://download.java.net/maven/1
> Type: Maven 1.x Repository
> Add remote Maven 2 jfrog-plugins repository
> Identifier: jfrog-plugins
> Name: jFrog plugins
> URL: http://www.jfrog.org/artifactory/plugins-releases
> Type: Maven 2.x repository
> In Proxy Connectors (under Administration)
> Edit maven2-repository.dev.java.net proxy connector
> Remove "jaxax/**" whitelist constraint and click Save Proxy Connector
> Add Proxy Connectors
> Managed Repository: internal
> Remote Repository: maven-repository.dev.java.net
> cache-failures: yes
> releases: once
> checksum: fix
> snapshots: never
> Managed Repository: internal
> Remote Repository: jfrog-plugins
> cache-failures: yes
> releases: once
> checksum: fix
> snapshots: never
> Client side:
> Copy settings.xml to ~/.m2
> $ cp settings.xml ~/.m2
> Create sample project
> $ mvn archetype:create -DgroupId=some.namespace -DartifactId=myproject
> Overwrite pom.xml
> $ cp myproject.pom.xml myproject/pom.xml
> Add sample XML schema
> $ mkdir myproject/src/main/resources
> $ cp schema.xsd myproject/src/main/resources/
> Run test
> $ cd myproject
> $ mvn test
> This should fail with BUILD ERROR "The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid version could be found"
> Workaround:
> uncomment <version> tag in pom.xml and run test again
> Now mvn test should succeed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-644) org.jvnet.jaxb2.maven2:maven-jaxb2-plugin
is not resolved correctly using Archiva as mirror
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-644:
---------------------------------
Fix Version/s: 1.x
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly using Archiva as mirror
> -------------------------------------------------------------------------------------------
>
> Key: MRM-644
> URL: http://jira.codehaus.org/browse/MRM-644
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Maven version: 2.0.8
> Java version: 1.6.0_03
> OS name: "linux" version: "2.6.22-14-generic" arch: "i386" Family: "unix"
> Reporter: Henrik Schmidt
> Fix For: 1.x
>
> Attachments: myproject.pom.xml, schema.xsd, settings.xml
>
>
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly with <version> tag omitted in pom.xml. Omitting the <version> tag works if Archiva is not used (Maven will just get the latest version).
> Steps to reproduce:
> Archiva application:
> Unpack and run archiva
> $ tar zxvf apache-archiva-1.0-bin.tar.gz
> $ apache-archiva-1.0/bin/linux-x86-32/run.sh start
> Navigate to http://localhost:8080/archiva
> create Admin user and login
> In Repositories (under Administration):
> Add remote Maven 1 legacy repository
> Identifier: maven-repository.dev.java.net
> Name: Java.net Maven 1 Repository (legacy)
> URL: http://download.java.net/maven/1
> Type: Maven 1.x Repository
> Add remote Maven 2 jfrog-plugins repository
> Identifier: jfrog-plugins
> Name: jFrog plugins
> URL: http://www.jfrog.org/artifactory/plugins-releases
> Type: Maven 2.x repository
> In Proxy Connectors (under Administration)
> Edit maven2-repository.dev.java.net proxy connector
> Remove "jaxax/**" whitelist constraint and click Save Proxy Connector
> Add Proxy Connectors
> Managed Repository: internal
> Remote Repository: maven-repository.dev.java.net
> cache-failures: yes
> releases: once
> checksum: fix
> snapshots: never
> Managed Repository: internal
> Remote Repository: jfrog-plugins
> cache-failures: yes
> releases: once
> checksum: fix
> snapshots: never
> Client side:
> Copy settings.xml to ~/.m2
> $ cp settings.xml ~/.m2
> Create sample project
> $ mvn archetype:create -DgroupId=some.namespace -DartifactId=myproject
> Overwrite pom.xml
> $ cp myproject.pom.xml myproject/pom.xml
> Add sample XML schema
> $ mkdir myproject/src/main/resources
> $ cp schema.xsd myproject/src/main/resources/
> Run test
> $ cd myproject
> $ mvn test
> This should fail with BUILD ERROR "The plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid version could be found"
> Workaround:
> uncomment <version> tag in pom.xml and run test again
> Now mvn test should succeed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira