ant elder wrote:
On 6/14/07, Frank Budinsky <[EMAIL PROTECTED]> wrote:
Hi,
I remember about a year ago discussing whether or not it is
acceptable/appropriate to check-in IDE specific files (e.g., Eclipse
.project files) into svn, and we decided to not do it. Does anyone
remember if this was re
I was assuming we would check in one "default" configuration. There's
nothing preventing people from running maven eclipse:eclipse or manually
changing them in their own environments. We wouldn't want people to
accidentally check their changes back in so we'd probably want them on the
svn:ignor
Where are you running the mvn eclipse command from? When I do it from the
top-level SDO folder all the projects get setup using inter project
dependencies (with the exception of sdo-api as thats outside in spec/sdo-api
right now but that will be fixed when its moved into the sdo folder)?
...ant
Agree with all that, plus the fact that you need to install maven and
check-out using the command line. If we had .project files, people could
check-out the projects they want "directly into Eclipse" and work with
them without ever needing mvn.
Frank.
"kelvin goodson" <[EMAIL PROTECTED]> wrote
Can we do anything with svn:externals properties or overlays to help with
this. Or maybe we could check in a standard set of patches that represent
adding eclipse stuff to projects? Users could then do an extract in one of
a set of standard patterns, and then apply a patch to put the IDE files i
Right thats the problem isn't it. If we check in the IDE files in we're
assuming one particular way of using the code. For the SCA project which is
quite big i've several different workspaces - one with every thing including
modules, samples and itest, another workspace just with modules, and anot
There's pain in the process, not huge, but irritating
first off there's the definition of the M2_REPO variable, not a huge
problem, especially if you stick to just one workspace. I tend to create
workspaces as and when I need them, and I can't see how to make my variable
definition cross multi
Sounds good to me, we'd just have to make some decisions about the nature
of the classpath entries. I would assume that for the api, lib, impl, tools
and plugins projects we would set up inter-project dependencies, but what
would we do about classpath entries for binary artifacts such as EMF? T
On 6/14/07, Frank Budinsky <[EMAIL PROTECTED]> wrote:
Hi,
I remember about a year ago discussing whether or not it is
acceptable/appropriate to check-in IDE specific files (e.g., Eclipse
.project files) into svn, and we decided to not do it. Does anyone
remember if this was really an Apache pol
Frank,
I'm of the opinion that anything that makes it easier for developers to
get to grips with our stuff, the better. Personally, having to to
create all the Eclipse stuff has been a pain, so doing this would save
me time and effort.
I agree with your sentiment that if others want to add
Hi,
I remember about a year ago discussing whether or not it is
acceptable/appropriate to check-in IDE specific files (e.g., Eclipse
.project files) into svn, and we decided to not do it. Does anyone
remember if this was really an Apache policy, or just a decision we made
for Tuscany? If the l
11 matches
Mail list logo
