This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I have generated a Maven Web application, and inside my pom.xml I can see that a lot of the dependencies have groupId set to unknown.binary. What is the reason for this? Is it a bug? Should it be this way, and if yes, why? <dependencies> <dependency> <groupId>org.primefaces</groupId> <artifactId>primefaces</artifactId> <version>3.2</version> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>org.eclipse.persistence.jpa.modelgen</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>org.eclipse.persistence.asm</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>org.eclipse.persistence.antlr</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>org.eclipse.persistence.jpa</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>org.eclipse.persistence.core</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>org.eclipse.persistence.oracle</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>org.eclipse.persistence.moxy</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>unknown.binary</groupId> <artifactId>javax.persistence</artifactId> <version>SNAPSHOT</version> <scope>provided</scope> </dependency> <dependency> <groupId>javax</groupId> <artifactId>javaee-web-api</artifactId> <version>6.0</version> <scope>provided</scope> </dependency> </dependencies> According to Petr Jiricka this is an issue (regression since it used to work). I did *not* change the EclipseLink library in the library manager (Petr asked..).
As described on NetCAT, it is the responsibility of whatever code is adding these libraries to the project to make sure there are reasonable corresponding Maven artifacts available.
Could Netbeans provide some hints/tips in situations like this? I know the normal editor can provide tons of hints, but I think that what you've just described is something that Netbeans could try to help the user with in the pom. I'm a fairly experienced Maven user, and would probably sort out both groupId, artifactId and version myself if Netbeans couldn't help me, but for novice users I think Netbeans could provide some help:) (hint like "Try add repository, use http://jarfinder.com to figure out where the class is used, etc etc etc)
Well the IDE is only adding this kind of dependency as a last resort, when there is no other known way to find the right artifacts. From glancing at the list of JARs, it seems they have something to do JPA, but I am not clear on what specific IDE function triggered this change.
I'll add space in Eclipselink (JPA2.0) name so it will be first but Eclipselink from Gf should be created by plugin if I remeber right. Is it important to not have 'unknown.binary'?
> I'll add space in Eclipselink (JPA2.0) name so it will be first Sounds like a hack, we should have a more robust solution. Will this work in non-English locales? But as a quick fix it's ok. > Is it important to not have 'unknown.binary'? Yes.
(In reply to comment #4) > I'll add space in Eclipselink (JPA2.0) name so it will be first but Eclipselink > from Gf should be created by plugin if I remeber right. Can you describe the change that you are expecting the plugin to make in a bit more detail?
space is added already, gf issue is 'unknown.binary', can't say what should be done to avoid this case and if it's possible to avoid.
I think when GlassFish is creating the "EclipseLink from GlassFish" library, it needs to provide a "pom volume" which points to the corresponding pom files on the web. That should help.
Assigning to myself. Targeting after Tooling SDK will be finished.
Added to changeset for next release. We will use new library builder framework to generate EclipseLink library and add related maven information.
I just created new maven web project and added few classes with javax.persistence dependencies. pom.xml contains <dependencies> <dependency> <groupId>javax</groupId> <artifactId>javaee-web-api</artifactId> <version>6.0</version> <scope>provided</scope> </dependency> </dependencies> For me it looks like this issue is resolved in 7.3.1.