I am not sure about the current setup, so someone else will have to answer
that, but I think it would be very helpful to get some SNAPSHOT builds
deploying to m2-snapshot-repository or wherever they need to go. One thing
that comes to mind is that the Spring-OSGi builds could then pull down more
recent code to test against, etc.
One problem I know we will have is the pom-new-plugin.xml and
pom-old-plugin.xml files. I do Felix CI builds off of SVN changes and
deploy to my internal Maven repo, but I have some script workarounds to get
a proper pom.xml prior to the build execution.
If this becomes a plan I would be happy to get the poms cleaned up and help
set up a continuum build somewhere.
Chris
On 2/2/07, Steven E. Harris <[EMAIL PROTECTED]> wrote:
I've been tracking Felix's development via Subversion for a while,
building my own snapshots every few days. As more of our development
team starts leaning on Felix, I am faced with at least two choices:
o Modify the root Felix pom.xml file, changing its
distributionManagement element to point to my internal
repositories, so that I can deploy my own Felix builds there for
internal use.
o Add the "apache.snapshots" repository to my project's remote
repository set, and track the public Felix builds that way.
I like the second option, but I noticed that the most recent SNAPSHOT
(0.9.0-incubator-SNAPSHOT) was deployed on 22 December 2006. That
one's not too old yet, but it's hard to know when the next refresh
will come.
With that concern in mind, how often does the Felix team deploy a
SNAPSHOT build to this repository? What criteria triggers such a
deployment?
--
Steven E. Harris
