> > >> >> (d) Is the repos.ops4j profile still required? If so, what for? >>> >> > Well, you can deploy to different targets.. we used to have sonatype > staging, sonatype snapshots, ops4j's own repo, ops4j's own snapshot repo. > Sure, the last two can be dropped. >
done (h) Does this version already include all the changes you were planning to >>> do to make the next Pax Runner release work more smoothly? If anything is >>> missing, I'm ready to help out... >>> >> >> Thank you very much, but except from your request for the m2e >> configuration everything should be included :-) Once this is in we can go >> ahead and release master-2.0.0. >> > > To recap, is master-2.0.0 the only (and flat) parent of ALL ops4j projects > ? > I recall to have the distinguishing pax-master to simplify pom managements > for both: pax projects (inherit from pax-master) and non pax projects > (inherit from ops4j-master). > I think it was about default naming conventions in pax projects as well as > some (maven-) site configuration. This may be obsolete, just keep in mind we > have a big Pax stack but also non Pax projects. Not sure if i missed > important bits of the discussion during my off time. > Feel free to take a look at the pax-master. If you remove the no longer relevant parts there is no need for this pom any longer. In addition I think the ops4j.master is general enough (and also good enough) to apply to the entire ops4j stack (including also non-pax-projects). Kind regards, Andreas
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
