Sean Schofield schrieb:
Why would the information not be compatible. Isn't it just a list of
developers, mailings lists and misc reports for the website. My
thinking is that this stuff will work with any version.
I'm not sure that this will work with any version,
Lets come up with a good alternative then. I don't think the master
pom belongs in api either. First of all, that's not an intuitive
place to look for it. We saw this already with several of the
developers not realizing this was the parent pom. Also, this suffers
from the same criticism that you gave for maven/trunk/master-pom. If
you checkout an older version of tomahawk, the parent pom is out of
sync there as well.
I try to describe it with a possible release cycle.
First we should release commons. Commons has a parent ref to the master
pom in myfaces/api/trunk or any other pom. None release should have a
dependency to a unreleased version. How we can solve this?
I put all the related content of the master pom in the pom of common
define a version and remove the parent ref.
NOTE: the first release of commons has a dependency to
myfaces-api-1.1.1.jar (not any dependency to a unreleased version)
The next release whould be core. The core hasn't a dependency to any
unreleased version. Fine can release.
NOTE: the first release of commons and the core are really close together
Then I would release tomahawk. Tomahawk has a parent ref to the master
pom maybe this is an unreleased version this is not allowed ok put all
the related content to pom of tomahawk.
Now we don't have any ref to a real master pom.
This is the reason why I don't see any need for a master pom in a
different place. I don't want to copy all this stuff now. But this must
be done for a release.
The sandbox and the site are never released they can contain a ref to
any other pom. Sandbox should have a ref to tomahawk and the site to the
pom in the core.
A release mean a jar in a public maven repository.
The core, commons and tomahawk will have their own release cylces.
That is the plan (as soon as we finish up this maven business.)
Fine
I wanted to ask you about myfaces-core. With a snapshot repository
why can't we have a top level pom for api and impl?
The top leven pom for api and impl is in
myfaces/api/trunk
maybe we should rename the dir api to core.
Sean
Bernd
