You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by David Van Couvering <da...@vancouvering.com> on 2007/06/27 00:22:46 UTC
NetBeans project metadata into Derby?
Having worked in NetBeans for a while, I have noticed that many code
bases are checked in with an associated NetBeans project directory.
This allows NetBeans users to quickly open up the project and start
using it within NetBeans.
I was thinking of doing the same thing for Derby. I am regularly having
to create the NetBeans project (each time I do a fresh pull or am
working in a separate sandbox).
Are there any reasons why this is not kosher?
Thanks,
David
Re: NetBeans project metadata into Derby?
Posted by David Van Couvering <da...@vancouvering.com>.
I think that will work. We could have nbproject-5.5, nbproject-6.0, etc.
On 6/29/07, Knut Anders Hatlen <Kn...@sun.com> wrote:
> David Van Couvering <da...@vancouvering.com> writes:
>
> > So, the message is, guaranteed compatibility from older to newer
> > version, but no guarantee from newer version to older version. And,
> > once you open a project with a newer version, it is auto-upgraded to
> > that new version's format.
>
> OK, so it sounds like there could be problems, like extra diffs, if
> people use different versions. What about adding a directory which
> contain project file templates instead? Then one could just do a "cp -r
> tools/templates/nbproject ." or something each time a new copy was
> checked out. That would allow users to do customizations without
> conflicting with the checked-in template. The same thing could be done
> for other IDEs as well.
>
> > On 6/28/07, David Van Couvering <da...@vancouvering.com> wrote:
> >> I didn't get any answer from the user community about about project
> >> file portability between versions, I"m going to try another channel...
> >>
> >> On 6/28/07, Knut Anders Hatlen <Kn...@sun.com> wrote:
> >> > David Van Couvering <da...@vancouvering.com> writes:
> >> >
> >> > > I don't know about the guaranteed compatibility between major
> >> > > versions, but I did notice that I could open a project in NB 5.5 that
> >> > > I created in NB 6, so things look pretty stable. But you're right,
> >> > > that's a concern. I'll ask around and see if I can find out how
> >> > > that's addressed, and get back to this list.
> >> > >
> >> > > All local changes are stored in a directory called 'private'. If you
> >> > > svn:ignore this directory, then what gets checked in is fully portable
> >> > > across user environments.
> >> >
> >> > Thanks for checking this out, David. It sounds OK to me. If it ever
> >> > becomes a problem, there's always the possibility of backing it out.
> >> >
> >> > --
> >> > Knut Anders
> >> >
> >>
>
> --
> Knut Anders
>
Re: NetBeans project metadata into Derby?
Posted by Julius Stroffek <Ju...@Sun.COM>.
Knut Anders Hatlen wrote:
> OK, so it sounds like there could be problems, like extra diffs, if
> people use different versions. What about adding a directory which
> contain project file templates instead? Then one could just do a "cp -r
> tools/templates/nbproject ." or something each time a new copy was
> checked out. That would allow users to do customizations without
> conflicting with the checked-in template. The same thing could be done
> for other IDEs as well.
>
>
+1, sounds good to me.
Re: NetBeans project metadata into Derby?
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
David Van Couvering <da...@vancouvering.com> writes:
> So, the message is, guaranteed compatibility from older to newer
> version, but no guarantee from newer version to older version. And,
> once you open a project with a newer version, it is auto-upgraded to
> that new version's format.
OK, so it sounds like there could be problems, like extra diffs, if
people use different versions. What about adding a directory which
contain project file templates instead? Then one could just do a "cp -r
tools/templates/nbproject ." or something each time a new copy was
checked out. That would allow users to do customizations without
conflicting with the checked-in template. The same thing could be done
for other IDEs as well.
> On 6/28/07, David Van Couvering <da...@vancouvering.com> wrote:
>> I didn't get any answer from the user community about about project
>> file portability between versions, I"m going to try another channel...
>>
>> On 6/28/07, Knut Anders Hatlen <Kn...@sun.com> wrote:
>> > David Van Couvering <da...@vancouvering.com> writes:
>> >
>> > > I don't know about the guaranteed compatibility between major
>> > > versions, but I did notice that I could open a project in NB 5.5 that
>> > > I created in NB 6, so things look pretty stable. But you're right,
>> > > that's a concern. I'll ask around and see if I can find out how
>> > > that's addressed, and get back to this list.
>> > >
>> > > All local changes are stored in a directory called 'private'. If you
>> > > svn:ignore this directory, then what gets checked in is fully portable
>> > > across user environments.
>> >
>> > Thanks for checking this out, David. It sounds OK to me. If it ever
>> > becomes a problem, there's always the possibility of backing it out.
>> >
>> > --
>> > Knut Anders
>> >
>>
--
Knut Anders
Re: NetBeans project metadata into Derby?
Posted by David Van Couvering <da...@vancouvering.com>.
So, the message is, guaranteed compatibility from older to newer
version, but no guarantee from newer version to older version. And,
once you open a project with a newer version, it is auto-upgraded to
that new version's format.
David
On 6/28/07, David Van Couvering <da...@vancouvering.com> wrote:
> I didn't get any answer from the user community about about project
> file portability between versions, I"m going to try another channel...
>
> On 6/28/07, Knut Anders Hatlen <Kn...@sun.com> wrote:
> > David Van Couvering <da...@vancouvering.com> writes:
> >
> > > I don't know about the guaranteed compatibility between major
> > > versions, but I did notice that I could open a project in NB 5.5 that
> > > I created in NB 6, so things look pretty stable. But you're right,
> > > that's a concern. I'll ask around and see if I can find out how
> > > that's addressed, and get back to this list.
> > >
> > > All local changes are stored in a directory called 'private'. If you
> > > svn:ignore this directory, then what gets checked in is fully portable
> > > across user environments.
> >
> > Thanks for checking this out, David. It sounds OK to me. If it ever
> > becomes a problem, there's always the possibility of backing it out.
> >
> > --
> > Knut Anders
> >
>
Re: NetBeans project metadata into Derby?
Posted by David Van Couvering <da...@vancouvering.com>.
I didn't get any answer from the user community about about project
file portability between versions, I"m going to try another channel...
On 6/28/07, Knut Anders Hatlen <Kn...@sun.com> wrote:
> David Van Couvering <da...@vancouvering.com> writes:
>
> > I don't know about the guaranteed compatibility between major
> > versions, but I did notice that I could open a project in NB 5.5 that
> > I created in NB 6, so things look pretty stable. But you're right,
> > that's a concern. I'll ask around and see if I can find out how
> > that's addressed, and get back to this list.
> >
> > All local changes are stored in a directory called 'private'. If you
> > svn:ignore this directory, then what gets checked in is fully portable
> > across user environments.
>
> Thanks for checking this out, David. It sounds OK to me. If it ever
> becomes a problem, there's always the possibility of backing it out.
>
> --
> Knut Anders
>
Re: NetBeans project metadata into Derby?
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
David Van Couvering <da...@vancouvering.com> writes:
> I don't know about the guaranteed compatibility between major
> versions, but I did notice that I could open a project in NB 5.5 that
> I created in NB 6, so things look pretty stable. But you're right,
> that's a concern. I'll ask around and see if I can find out how
> that's addressed, and get back to this list.
>
> All local changes are stored in a directory called 'private'. If you
> svn:ignore this directory, then what gets checked in is fully portable
> across user environments.
Thanks for checking this out, David. It sounds OK to me. If it ever
becomes a problem, there's always the possibility of backing it out.
--
Knut Anders
Re: NetBeans project metadata into Derby?
Posted by David Van Couvering <da...@vancouvering.com>.
I don't know about the guaranteed compatibility between major
versions, but I did notice that I could open a project in NB 5.5 that
I created in NB 6, so things look pretty stable. But you're right,
that's a concern. I'll ask around and see if I can find out how
that's addressed, and get back to this list.
All local changes are stored in a directory called 'private'. If you
svn:ignore this directory, then what gets checked in is fully portable
across user environments.
The entire NetBeans code base is a series of modules, with each module
being its own separate NB project. In all these cases the NB project
is checked into cvs, and I have been quite successful in opening these
projects.
David
On 6/27/07, Knut Anders Hatlen <Kn...@sun.com> wrote:
> David Van Couvering <da...@vancouvering.com> writes:
>
> > Having worked in NetBeans for a while, I have noticed that many code
> > bases are checked in with an associated NetBeans project
> > directory. This allows NetBeans users to quickly open up the project
> > and start using it within NetBeans.
> >
> > I was thinking of doing the same thing for Derby. I am regularly
> > having to create the NetBeans project (each time I do a fresh pull or
> > am working in a separate sandbox).
> >
> > Are there any reasons why this is not kosher?
>
> Does the project file format change between NetBeans versions? If it
> does, it could cause problems if developers use different versions.
>
> What about local changes to the project file? If a developer is not
> happy with the settings in the checked-in project file and customizes
> it, she always gets extra output from "svn diff" and "svn stat" and
> would have to edit the diffs before submitting them. Or are the project
> files fairly static?
>
> Another related matter I have been thinking about, is whether it would
> be OK to add the names of common project files and/or tag files to the
> svn:ignore property. I find it a bit annoying that they keep showing up
> when I run "svn stat" (yes, I know about "svn stat -q", but it also
> hides files I have added and forgotten to run "svn add" on).
>
> --
> Knut Anders
>
Re: NetBeans project metadata into Derby?
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
David Van Couvering <da...@vancouvering.com> writes:
> Having worked in NetBeans for a while, I have noticed that many code
> bases are checked in with an associated NetBeans project
> directory. This allows NetBeans users to quickly open up the project
> and start using it within NetBeans.
>
> I was thinking of doing the same thing for Derby. I am regularly
> having to create the NetBeans project (each time I do a fresh pull or
> am working in a separate sandbox).
>
> Are there any reasons why this is not kosher?
Does the project file format change between NetBeans versions? If it
does, it could cause problems if developers use different versions.
What about local changes to the project file? If a developer is not
happy with the settings in the checked-in project file and customizes
it, she always gets extra output from "svn diff" and "svn stat" and
would have to edit the diffs before submitting them. Or are the project
files fairly static?
Another related matter I have been thinking about, is whether it would
be OK to add the names of common project files and/or tag files to the
svn:ignore property. I find it a bit annoying that they keep showing up
when I run "svn stat" (yes, I know about "svn stat -q", but it also
hides files I have added and forgotten to run "svn add" on).
--
Knut Anders