I don't have an answer, but I do have a question: I've seen this
bootstrap situation w/ internal repo's discussed before, and my
solution was to use a common (or bootstrap) parent pom as the parent
for all our project poms. For example:
ParentPom:
...
groupIdorg.mine/groupId
On 3/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Having developed a new archetype for developers to use internally to build
adaptors, I am also providing them with a pre-configured maven-2.0.2
installation that contains a profile (activated by default - see below
section from
