GitHub user fmarot opened a pull request:
https://github.com/apache/maven-site/pull/7
Corrected assumption regarding execution's configuration
Corrected a wrong assumption saying that specific plugin's execution's
configuration could not be used from the command line.
This used
So I am seeing conflicting requirements and I am unsure how we should
approach resolving them:
1. Seems perfectly reasonable to add some form of integrity details about
the *project's artifacts* into the PDT. Probably a SHA512 hash...
2. We could probably add the SHA512 hashes of dependencies...
Besides adding the original repository somewhere I would like to add the
file-extension.
Now you are required to translate the type to the extension based on the
ArtifactHandler, which is a waste of time in this case. During build it is
indeed good to use packaging, so you can control the plu
Or we say that repositories must be self-consistent and include a "sources"
metadata at the root.
If I resolve A from central and B from corp-proxy... B may list central' ID
as an aggregated source, in which case it doesn't matter if the artifact is
in both A and B, we can just take the artifact f
Am 09/28/16 um 19:27 schrieb Stephen Connolly:
> On Wednesday 28 September 2016, Christian Schulte wrote:
>
>> Am 09/28/16 um 08:25 schrieb Stephen Connolly:
>>> So if we provide a way to decentralise.
>>
>> We do already.
>>
>>>
>>> So now junit hosts their own artifacts, not central
>>
>> Or so
On Wednesday 28 September 2016, Christian Schulte wrote:
> Am 09/28/16 um 08:25 schrieb Stephen Connolly:
> > So if we provide a way to decentralise.
>
> We do already.
>
> >
> > So now junit hosts their own artifacts, not central
>
> Or some company hosts it at the same coordinates and I happen
Am 09/28/16 um 08:25 schrieb Stephen Connolly:
> So if we provide a way to decentralise.
We do already.
>
> So now junit hosts their own artifacts, not central
Or some company hosts it at the same coordinates and I happen to need to
add that repository to a project of mine.
> Now the absolute
I have started gathering together my proposals on how we can move Maven
forward under the
https://cwiki.apache.org/confluence/display/MAVEN/Requests+for+Comment page.
Hopefully we can use the wiki to actually drive discussion and
collaboration on the topics that concern us this way.
-Stephen
Stephen Connolly wrote:
> I am toying with having the format be xml.gz rather than xml
> OTOH transport GZ should be easy and makes the file easier for users > to
> inspect
>
> Thought?
If you mean by "transport GZ", serving the XML with "Content-Encoding:
gzip" by the repository manager, than
What happens if I want to use an in-house patch build of junit? I will not
have the same origin...
On Wednesday 28 September 2016, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
>
> On Wednesday 28 September 2016, Christian Schulte > wrote:
>
>> Am 09/28/16 um 04:48 schrieb Christi
10 matches
Mail list logo
