Looks like something like this will actually work (so inline profiles
can override distributionManagement):
distributionManagement
!-- Null out inherited apache distribution repo by default --
repository
iddummy/id
nameDummy to avoid accidental deploys/name
url/url
On 8/29/06, Phil Steitz [EMAIL PROTECTED] wrote:
I have one more question / concern with the current setup.
Should we override the distributionManagement section to
null out the releases section ...
We've talked about this some on [EMAIL PROTECTED] IMO, we need to use a
staging repository
On 8/31/06, Phil Steitz [EMAIL PROTECTED] wrote:
Looks like something like this will actually work (so inline profiles
can override distributionManagement):
That looks great. A component can always override
distributionManagement if necessary, so this is still flexible.
How and where will
On 8/31/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 8/31/06, Phil Steitz [EMAIL PROTECTED] wrote:
Looks like something like this will actually work (so inline profiles
can override distributionManagement):
That looks great. A component can always override
distributionManagement if necessary,
I have one more question / concern with the current setup.
Currently, we are inheriting the distributionManagement config from
the apache POM. This seems good and reasonable, except that that
parent defines both apache.snapshots and apache.releases and points to
the ibiblio synched repo for
It's a valid point. Unfortunately, build profiles can't be used for
the distributionManagement section at the moment.
I believe the solution to this really needs to be server side
controls on the repository which we are definitely working on. I'm
not sure what we can do on the client side
On 8/29/06, Brett Porter [EMAIL PROTECTED] wrote:
It's a valid point. Unfortunately, build profiles can't be used for
the distributionManagement section at the moment.
Hmm...the introduction-to-profiles.html doc seems to suggest that if
you do it inline (in the POM), you can specify
It's either an error in the docs, or my memory is failing me :)
On 30/08/2006, at 1:40 PM, Phil Steitz wrote:
On 8/29/06, Brett Porter [EMAIL PROTECTED] wrote:
It's a valid point. Unfortunately, build profiles can't be used for
the distributionManagement section at the moment.
Hmm...the
On 8/27/06, Phil Steitz [EMAIL PROTECTED] wrote:
IIUC, we currently have an m2 pom hierarchy that goes
for sandbox components:
component - commons-sandbox - commons - jakarta
for proper components:
component - commons - jakarta
(though only scxml appears to have an m2 build and it does not
On 8/27/06, Phil Steitz [EMAIL PROTECTED] wrote:
I suggest that we make the following changes:
...
At the top of your pom hierarchy, you can inherit from
org.apache:apache, and you'll pick up the m2 snapshot repo both in
repositories and distributionManagement.
On 8/27/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 8/27/06, Phil Steitz [EMAIL PROTECTED] wrote:
I suggest that we make the following changes:
...
At the top of your pom hierarchy, you can inherit from
org.apache:apache, and you'll pick up the m2 snapshot repo both in
repositories and
11 matches
Mail list logo
