> I don't like the build dir. We should use a snapshot repository. If we > are using a snapshot repository we don't need a pom in build anymore.
How do you build everything at once? Are you saying you just build the projects you need one at a time? > A new version of the surefire plugin is available with forking support. > Forking is needed for the StateUtilsTestCases in common. > But the implementation of StateUtils contains some code for testing. > Code for testing in non test classes is very ugly. > We should change the test to a mocked version. I added a todo item to the wiki. Does someone want to volunteer? > An other problem is the MessageUtilsTest depends on the Message > resources in impl, but impl has a dependency to common. > Can we move(copy) the resources from impl to common? I volunteer for this one. > We don't have two high level POM's please use a snapshot repository!!! > You don't need to build all the stuff. The pom in build is only for > reactor and can be removed when we are using the snapshot repository. OK so you're saying the only reason for the build POM is to update the reactor so that the dependencies for a module (ex. tomahawk) are available to the tomahawk build. > The parent pom is fetched from the remote repository(snapshot) and > installed in the local repository. Interesting. I guess that could be better the build/pom.xml. Is Maven capable of downloading a parent pom from a snapshot repository? We would move the "common" parent stuff out of api/pom.xml and into this new parent pom right? How do we make a pom an artifact in Maven? Don't we still need a dir (like build) to store it? Is there another pom to publish the parent pom? > If you never change the version of the parent you don't get any new > information from the parent pom if has changed. (then you can delete the > parent ref) How are snapshot versions handled in m2? Ideally it would check the snapshot repository and use the newer snapshot if it is more recent then the one in your local repository. I'm still confused as to how snapshots work. Maybe someone could give me a good explanation. I find the maven site to have very little documentation on this, especially for maven2. > A version is only one line in the pom. Can we move this decision to a > release. If we decide tomahawk has his own version I add a version line > to the pom in tomahawk maybe I remove the parent ref (Then I have to > copy the inherited information from the parent pom). This is very simple. > > What i need is a discussion about reasonable artifact names and > directory names > > And we should talk about the process (updating the snapshots, nightly > build and continuum) > > And we should use the new site. Yes. Lots more to discuss here. > Bernd Sean
