Hello Mark! Your karma has changed!
We had to move the source around, a few years back, to allow us to work with Eclipse. I think it created a lot of confusion that we are still suffering from. After that I promised myself that if a new tool came along that would require us to move the source around my first reaction would be to consider the tool faulty since it is not configurable enough to allow our directory structure, then I would do a lot more examining and weighing the pros and cons before agreeing to such a change. For maven I have, in argouml/trunk/tools/maven/parentpom.xml (line 45 to 56 and line 150 http://argouml.tigris.org/source/browse/argouml/trunk/tools/maven/parentpom.xml?annotate=19543#id45) attempted to reconfigure maven to find source according to the argouml "standard". It seems to be working for the things I have managed to build using maven. /Linus 2011/8/9 Mark Fortner <[email protected]> > Hi Linus, > I'll restore the ant build. > > I'll be glad to help out with changing up the other projects -- although > I'm not sure I have checkin karma for the main argouml project. > > The main reason for moving the source trees around is that it reduces the > amount of configuration that you have to do. The primary problem I was > having with the current source tree is that resources were not being copied > into the target directory properly and I would end up with an unusable JAR > file. Instead of creating a "META-INF/services/**" it would create > "/services/**". After using maven for a couple of years, I've come to the > conclusion that using the default locations for things is definitely easier > than trying to shoehorn a non-standard directory structure into a maven > build. It's kinda like petting a cat backwards -- you can do it, but > neither you nor the cat will be happy. ;-) > > Mark > > > On Tue, Aug 9, 2011 at 5:34 AM, Linus Tolke Tigris <[email protected]>wrote: > >> Hello Mark! >> >> Since argoprint is now a part of the argouml release that uses the ant >> build that must still work for the release to work. >> >> I would prefer to move to maven in the same way for all argouml projects >> and not start in this end. Would you consider doing this on all argouml >> projects and not only the argoprint one? >> >> Why would you want to move the source trees? What is the problem with the >> source layout as described in >> http://argouml.tigris.org/wiki/Source_layout? >> >> /Linus >> >> 2011/8/6 Mark Fortner <[email protected]> >> >>> Does anyone have any objections if I completely mavenize ArgoPrint? The >>> reason I'm contemplating this is to make building it easier, minimize (or >>> remove altogether) the number of libraries stored in svn and to standardize >>> the directory structure. Here are some of the effects this would have: >>> >>> - The ant build-related artifacts and directories would be removed. >>> - The libraries would be removed >>> - The source and test trees would move >>> moved/reorganized/standardized >>> - The maven nature would be added to the Eclipse .project (meaning if >>> you wanted to build it with Eclipse you'd have to have the maven plugin). >>> >>> >>> Any feedback or suggestions about this is always welcome. >>> >>> Regards, >>> >>> Mark >>> >> >> > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2813174 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
