Hi
Default the jars will have SNAPHOST in the name but in the manifest the version is the date of today (the build date)
So I thought that missmatch will prevent Eclipse from loading the plugin.
Anyway issue I am trying to investigate is why my EJB and RAR projects gets this kind of error marker in the pom.xml
Description Resource Path Location Type Path must include project and resource name: / (org.apache.maven.plugins:maven-ejb-plugin:2.3:ejb:default-ejb:package) pom.xml /engine-ejb line 149 Maven Build Problem
The line looks like this:
<build> <plugins> <plugin> <!— line 149 —> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-ejb-plugin</artifactId> <configuration> <generateClient>true</generateClient> <archive> <manifestEntries> <Class-Path>. engine-api.jar</Class-Path> </manifestEntries> </archive> </configuration> </plugin>
The maven-ejb-plugin is otherwise configured in the root/super pom.xml
Thanks Lucas
Its been a while but p2 likely won't care about the qualifier during install, but you will need to update the repository to add the new jar - is there a reason you aren't simply using the whole build output?
Updating the jar is not as simple as it might appear - you will need to update the p2 repository to ensure the hashes match and remove the signature from the jar.
_______________________________________________ m2e-dev mailing list m2e-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-dev
--
![Oracle]()
Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 | Mobile: +46730946656
Oracle Communications Platform
ORACLE Sweden | Söder Mälarstrand 29, 6 tr | 118 25 Stockholm
Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
![Green Oracle]() |
Oracle is committed to developing practices and products that help protect the environment |
|