Re: [picocontainer-dev] build weirdness...

Mauro Talevi wrote:

> Jörg Schaible wrote:
>> 
>> OK, coming closer. Problem ist that the resources plugin is downloaded
>> from the configured apache snapshot repo, since it has not been entgered
>> with a fixed version in the pluginManagement section. Same apply for the
>> install plugin. Added to master POM now.
> 
> close but no cigar :-) IMO the problem lies in the jar plugin and is
> also related to http://jira.codehaus.org/browse/PICO-299
> 
> After fixing the jar plugin version to 2.0 I've been able to do a build
> with a blank local repo.    You can try it out by building trunk.

Not sure about this. I build still with M205 in the office (M206 was
seriously broken and M207+M208 drop under weird circumstances deps breaking
our build) and it might be that we use an older jar plugin anyway (must
have a look tomorrow), since the newer ones need newer Maven versions.

>> BTW: Did I already mention that Maven folks highly discourage to add
>> repositories to your POM? ;-)
> 
> It's a matter of debate actually.  If you put them in a profile in the
> settings.xml then you need to ensure that the profile is checked in and
> people activate it.

Might be the better option. In that case we're not slowed down using very
fresh versions, but for a release anything is required to be on central.

>> I noticed, that the POM for the jar-plugin could not be downloaded. I
>> commented out then all of those repository and pluginRepository
>> declarations ... et voilá. The build succeeds. So, the recommendation of
>> the Maven folks should be considered serioulsy...
>> 
>> I've checked in now a POM with the necessary mofigications, that allowed
>> me to build Pico again. Mauro, take  look.
>> 
> 
> Right - so that's the same conclusion I came to.  Something's wrong with
> the jar plugin, at least the latest version.

Maybe it was one from the snapshot repos ... ?!?

> 
>> BTW: IMHO the dep to paranamer in pico core is wrong. It should be
>> declared as provided, since the shade-plugin will hide all the classes
>> afterwards and it is no longer directly available to users of pico.
> 
> I don't think it gets shaded if it's declared as provided.

Have not tried it, but from the dependency PoV it is the only thing that
IMHO makes sence. It should definitely not be available as transitive
dependency to Pico users, because the shade-plugin ensures that the classes
are available (=provided, but differently as the original intention) for
Pico - but for Pico only.

- Jörg


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email