alternatively you can create your own repository using the nbm:populate-repository goal. It's fairly easy, just grab the netbeans zip or installation you want to build against and it will populate your local repository and if you specify a remote repository url, it will upload it as well.
Milos On 7/4/07, Sebastien Arbogast <[EMAIL PROTECTED]> wrote:
In fact it's not working for me because of the port. I'm in a corporate environment, behind a proxy that blocks everything except port 80. That would help if I can mirror your repository from my server since it is not behind the proxy. I don't know rsync, I'll see what it needs. 2007/7/4, Milos Kleint <[EMAIL PROTECTED]>: > > On 7/4/07, Sebastien Arbogast <[EMAIL PROTECTED]> wrote: > > OK, very interesting. But if I understand correctly, I'll still have to > > declare my dependencies manually, which can be very awkward if you look at > > this graph where dummy is exactly in the same position as my project: > > Yup. It's somewhat unfortunate but unavoidable given the different > concepts of maven and netbeans dependency management. Let's check this > scenario. > > module1 doesn't have any code by itself. It's a "library wrapper". > so in your case it can be spring. this module needs to include all the > libraries on runtime classpath of the module. > thus in the current 2.5 version of nbm-plugin, you need to declare > each dependency explicitly in the pom.xml or in the module descriptor. > pom.xml reasonably easier to do. > > module2 depends on module1. Here you only declare dependency on > module1. that generates the runtime module dependency as well and you > get everything on CP. > > I've experimented with automatic inclusion of transitive dependencies > quite a bit but was unable to avoid the situation where multiple > modules included the libraries on it's classpath. That results in > broken runtime module system in netbeans. > The older versions of nbm-plugin required each library/module > dependency to be declared in the src/main/nbm/module.xml module > descriptor however that was duplicating a lot of the metadata from the > pom. The current approach in 2.5 tries to simplify things, reduce > duplications and keep the build sane. > > The netbeans module dependencies are also transitive in the remote > repo, while the plugin and netbeans expects each dependency to be > declared. > I've added some code to the mevenide codebase that when running "mvn > dependency:analyze" goal within the IDE , lets you automatically add > direct dependencies on artifacts that are used for compilation. That > should at least partly automate the process. (Better tooling TBD in > the future I guess). > > > > Second thing, this repository > > ( http://208.44.201.216:18080/maven) seems to be offline so > > I can't get the sample platform project to build. By the way, from what I > > understand, this repository is hosted by you, right? If I'm right and if you > > need it, I have my own dedicated server in a data center, with plenty of > > bandwidth available so I would be happy to contribute by offering some > > hosting for this repository. > > > Not sure. I just checked and it worked for me. > yes, it's hosted by me. It's been reasonably reliable so far. I guess > you could mirror it via rsync? If you do, let me know, I'll update the > plugin's website wiht reference to your site as well. > > regards.. > > Milos > > > > > 2007/7/4, Milos Kleint <[EMAIL PROTECTED]>: > > > > > > check the [EMAIL PROTECTED] archive > > > http://archive.mevenide.codehaus.org/user > > > > > > Emilian Bold has gone through the same migration on that list a few > > > weeks ago. He plans to write some docs on the subject, not sure when > > > it gets released. > > > > > > A while back I have created an archetype for creating netbeans > > > platform based mutliproject setup. works with archetype-ng only (which > > > was not released yet) not with the current default > > > maven-archetype-plugin. > > > > > > http://jira.codehaus.org/browse/MNBMODULE-14 has a sample > > platform > > > project as attachment. > > > > > > the current mevenide version that is on autoupdate server for > > > netbeans 6.0 milestones and dailies has some additional support for > > > module development (eg. layer flies are browsable and netbeans file > > > templates work as well) > > > > > > Hope that helps. > > > > > > Milos > > > > > > On 7/4/07, Sebastien Arbogast < [EMAIL PROTECTED]> wrote: > > > > I'm trying to start up a Netbeans platform project. At first I've used > > > > Netbeans wizards to create the project and library wrappers. But now I'm > > > > fighting with the dependency management system because I'm using a lot > > of > > > > Maven dependencies: the backend to which my Netbeans rich client > > connects is > > > > built with Maven. I guess Maven NBM plugin is here to solve exactly that > > > > kind of problem but I don't have any idea how to move from my > > > > Netbeans-managed project to a Maven2-built one. > > > > > > > > Can someone help me get started? How should I lay out my project? > > > > > > > > -- > > > > Sébastien Arbogast > > > > > > > > http://www.sebastien-arbogast.com > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe from this list please visit: > > > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > > > > > -- > > > > Sébastien Arbogast > > > > http://www.sebastien-arbogast.com > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- Sébastien Arbogast http://www.sebastien-arbogast.com
--------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
