Unfortunately the nbm:populate-repository goal that populates
deadlock.netbeans.org/maven2 repository isn't able to resolve module's
dependencies because it doens't know what the jar is in terms of
groupid/artifactid/version.
The workaround for beansbinding and also swinglayout and others is to
declare the module dependency
(org.netbeans.api:org-jdesktop-beansbinding) and also the actual
beans-binding jar as dependency (this one needs to have the scope
"provided" declared.
Regards
Milos
PS: In the current trunk of nbm-maven-plugin I improved the metadata
generation and the populate-repository goal can consult the nexus
index now and if found uses the correct ids, if not found put the jar
in org.netbeans.external groupid.
The deadlock repository won't be changed for the existing releases,
only for new ones. POssibly I might create a different repository with
new metadata.
On Sat, Oct 4, 2008 at 6:56 AM, Sidart Kurias <[EMAIL PROTECTED]> wrote:
> I wasn't sure if this is the right place to pist this. I had a question
> reagarding some of the jars being used with netbeans beansbinding and maven.
> Specifically the jar org.netbeans.api:org-jdesktop-beansbinding for release
> 6.1. This under the deadlock repository is one 1K in size and has little
> more than a Bundle.properties file. Am I missing something, am I supposed to
> be using the jar from somewhere else or someother jar to resolve the binding
> classses?
>
> Sid
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
