[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orekit Developers] Updated BUILDING.TXT

The only potential problem I've seen so far is that once you load it into Eclipse this way it adds a "plugin management" section and its own m2e plugin settings into the pom.  It doesn't seem to affect the execution of the script from the Maven command line.  If we add it to the pom.xml then it would make the Eclipse loading process even more straight forward.  How do you guys feels about that?


On Tue, Nov 19, 2013 at 4:39 AM, MAISONOBE Luc <luc.maisonobe@c-s.fr> wrote:
Hank Grabowski <hank@applieddefense.com> a écrit :

I'd like to request updating BUILDING.TXT to reflect a better way of
bootstrapping the Eclipse project.  I seriously struggled to get the JUnit
tests to recognize the resources folders, despite playing around with it
numerous times.  I finally scratched yet another attempt to configure it
and just imported the Maven pom file.  There was a warning on import but
running the "install" option on Maven worked and everything works right out
of the box even in a virgin git extracted repository.  It was a very simple
process as well.

I wasn't sure the correct way to submit this change.  I could submit new
language here, if you want to take my suggestion, or open up a new issue in
the tracker and submit it there.

If you can find a way to express it more appropriately, please go ahead. The relevant part in the current BUILDING.TXT file reads:

   set the source folders to orekit/src/main/java,
   orekit/src/main/resources, orekit/src/test/java,
   orekit/src/test/resources, orekit/src/tutorials in
   the source tab of the Configure Build Path dialog

It also missed the fact now rather than orekit/src/tutorials, it should have orekit/src/tutorials/java and orekit/src/tutorials/resources, just like test and main. I also have seen some version of eclipse show the "orekit" project name in the dialog while other versions did not display it and started directly at the "src" level.

If you intend to propose a text only for this part, you can send it here on the list, but if you want to rewrite more thoroughly the file, attaching a new version to the bug tracker is probably simpler to manage a complete file.


Hank Grabowski
Chief Technology Officer

10440 Little Patuxent Parkway, Suite 600

Columbia, MD 21044

(410) 715-0005 Office

(410) 715-0008 Fax

(301) 525-6219 Mobile


www.AppliedDefense.com <http://www.applieddefense.com/>

This message was sent using IMP, the Internet Messaging Program.