You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by De Smet Ringo <Ri...@staff.telenet.be> on 2008/04/29 11:30:25 UTC

Custom Maven plugin can't be resolved in 2.1 snapshot, works in 2.0.9

Hello,
 
In a Maven project, I have defined our company shared Maven 2 repository
in the repositories and pluginRepositories section of pom.xml. Our build
process relies on a few custom Maven 2 plugins that are correctly
deployed on our repository. The build works correctly with Maven 2.0.9,
but not with a 2.1 snapshot that I downloaded from the Q4E downloads
section.

Attached, you can find the transcript of a build of this (empty
top-level) project with both 2.0.9 and the 2.1 snapshot. Below are the
POM sections of repositories and pluginRepositories:

	<repositories>
		<repository>
			<releases>
				<enabled>true</enabled>
				<updatePolicy>always</updatePolicy>
				<checksumPolicy>ignore</checksumPolicy>
			</releases>
			<snapshots>
				<enabled>true</enabled>
				<updatePolicy>always</updatePolicy>
				<checksumPolicy>ignore</checksumPolicy>
			</snapshots>
			<id>telenet.repository</id>
			<name>telenet.repository</name>
	
<url>http://tsmdvlprs.dvp.corp.telenet.be/m2/repository</url>
			<layout>default</layout>
		</repository>
	</repositories>
	<pluginRepositories>
		<pluginRepository>
			<releases>
				<enabled>true</enabled>
				<updatePolicy>always</updatePolicy>
				<checksumPolicy>ignore</checksumPolicy>
			</releases>
			<snapshots>
				<enabled>true</enabled>
				<updatePolicy>always</updatePolicy>
				<checksumPolicy>ignore</checksumPolicy>
			</snapshots>
			<id>telenet.repository</id>
			<name>telenet.repository</name>
	
<url>http://tsmdvlprs.dvp.corp.telenet.be/m2/repository</url>
			<layout>default</layout>
		</pluginRepository>
	</pluginRepositories>

As a side note, before I tried to report this problem, I tried to build
the latest Maven 2.1 from SVN, but got a build error:

C:\Data\Private\maven-2.1\maven-workspace\src\main\java\org\apache\maven
\workspace\DefaultMavenWorkspaceStore.java:[3,-1] cannot access
org.codehaus.plexus.logging.LogEnabled
bad class file:
C:\Data\maven\repository\org\codehaus\plexus\plexus-container-default\1.
0-alpha-46-SNAPSHOT\plexus-container-default-1.0-alpha-46-SNAPSHOT.jar(o
rg/codehaus/plexus/logging/LogEnabled.class)
class file has wrong version 49.0, should be 48.0

I am using JDK 1.5.0_12, and tried both Maven 2.0.9 and the previous 2.1
snapshot to build the latest sources.
 
Ringo De Smet
 

*************************************************************

Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. 

This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents.

Ce courriel et les annexes �ventuelles peuvent contenir des informations confidentielles et/ou prot�g�es par des droits de propri�t� intellectuelle. Ce message est adress� exclusivement � son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou compl�te sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez re�u ce message par erreur, veuillez pr�venir l'exp�diteur du message et en d�truire le contenu.

*************************************************************