[nbdev] Re: Wrapper module enhancements.

  • From: Gregg Wonderly < >
  • To:
  • Cc: Ernie Rael < >
  • Subject: [nbdev] Re: Wrapper module enhancements.
  • Date: Thu, 28 Jun 2012 16:49:10 -0500

On 6/28/2012 4:32 PM, Ernie Rael wrote:
On 6/28/2012 2:06 PM, Gregg Wonderly wrote:
Okay, let me try and explain this better.  I have a project that has a whole
bunch of utility classes in it.  I have this placed in a particular directory
tree that is associated with all my work projects.

I have another project that is a netbeans module suite.  It includes a bunch
of modules, which are SPI and interface definitions for the suite.  The
utility project, above, is one of the modules I want to put in the suite.

That utility module also happens to be visible as an open source project that
people will download and build themselves.  I have no idea where they will put
that project.

I want the suite project's wrapper for this utility project, to be dynamic,
and I have no idea where they will put the utility project.

So, when I distribute this suite, I want the users to be able to just download
the utility project and load it into netbeans,

"load it into netbeans". Does that mean open it as a NetBeans project?

Yes, open the project in netbeans so that netbeans can see the project, by name. There might even need to be a "UUID" in the project definition to reference by, instead of name. Something as unique as a file path.

and then be able to built the suite.

Thus, the suite's wrapper module, has to have a dynamic link to this utility
project

"dynamic link". By project name? Without a reference to a path?There's nothing
that has to be done to indicate where the utility class is accessed by the
wrapper? Just open it in NetBeans. That doesn't sound right; seems like the 
user
has to do something to set the path, or otherwise indicate to the wrapper that
the downloaded utility project is where to get the jar.

There would be two properties. The project name/UUID, and then the relative path, in the referenced project, to it's build output.

so that it can be built, and the wrapper module can identity, to the suite,
how to get the wrapper jar.

The workaround I'm suggesting involves changing one line in the wrapper module
to set the install location (the dynamic link) of the utility project. It is
probably possible to have this build property come from somewhere else (for
example, can ant access the environment?)

I am trying to create a suite and a project type that would greatly simplify the task of building a module that the suite can use. My target audience are self taught developers who will not have any interest in messing with settings, over and over, trying to figure out why something can't be found.

The suite build process with wrappers is already too complicated. I need something that is as simple as saying "I want to create a module". I need the suite SPI and interfaces to just work, no matter where they are building things from.

Gregg


[nbdev] Wrapper module enhancements.

Gregg Wonderly 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Gregg Wonderly 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Ernie Rael 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Gregg Wonderly 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Ernie Rael 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Gregg Wonderly 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Ernie Rael 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Gregg Wonderly 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Ernie Rael 06/28/2012

[nbdev] Re: Wrapper module enhancements.

Gregg Wonderly 06/28/2012

Project Features

About this Project

www was started in November 2009, is owned by jpirek, and has 21 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20140418.2d69abc). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close