Ok- It seems like a good way forward is to assume usage of the maven
plugin within Eclipse. I think this is a reasonable way to do it and
will also keep us honest about being maven-agnostic. I entered a
comment accordingly in the ticket.
Karl
On Thu, Jul 14, 2011 at 10:04 AM, Farzad Valad wrot
I'm out of town, will resume Tue
Sent from my iPhone
On Jul 14, 2011, at 4:50 AM, Karl Wright wrote:
> I've created a ticket for this: CONNECTORS-223. If you could comment
> on the proposed plan before I start executing it, that would be great.
> I'll be happy to do all the needed tree rearran
I've created a ticket for this: CONNECTORS-223. If you could comment
on the proposed plan before I start executing it, that would be great.
I'll be happy to do all the needed tree rearrangement and build.xml
changes if, once again, you are willing to handle the maven pieces.
Thanks!
Karl
On Thu
Yes, it's feasible to move the tests around. The maven unit test
convention I understand, and it is straightforward to adhere to it,
but what should the structure be for the end-to-end tests? Right now
these are under the root-level "tests" directory, and there are tests
for various combinations
I also tried to import mcf into eclipse but it does not work in an easy way.
That's why I was looking for the maven integration.
It is really easy to import the modules using maven and the m2eclipse plugin
(Just import as maven project), but because of your project structure it is
currently not pos
I'm going to go ahead and open the ticket. Please attach your
proposed patch(es) to it. CONNECTORS-222.
I *would* like to avoid reorganizing the tree, except in a minor way.
Maven already forces a lot of cruft on us - we can't afford two
masters here.
Karl
On Wed, Jul 13, 2011 at 2:31 PM, Kar
Your proposal is then to change the structure of ManifoldCF to match
the hierarchy in your .zip file? If we did that, maven would no
longer work, and it might not be possible to get it to work. The ant
build system would require major revisions. The documentation and
book would all need changes
It is not as bad as it seems : ) The only extra step right now is
checking out the lcf source code. The projects I sent you are
essentially the eclipse settings you are looking for that would be
loaded into the repo. There are nothing in them beside eclipse settings
and links to the lcf sourc
Is there any way to provide a eclipse settings file that helps with
the project setup? Or is this an entirely manual process?
I am happy to open a Jira ticket to cover eclipse integration. It
*sounds* like what the patch should contain would be some files that
get checked into the source tree, a
So what is the verdict on the eclipse setup? Maybe we can work through
one example, like running the agent from eclipse, so I can fine tune the
setup procedure. I figured out how to link the sources into the eclipse
project without manual copying. You need two things, 1) check out the
existin
10 matches
Mail list logo
