John Casey wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-022/
Staging site:
http://maven.apache.org/shared/maven-common-artifact-filters-1.3/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubs
>>>
>>
>> That's what it does - it still fails if there are snapshots. It gives you
>> the option if it finds a snapshot to let you change that to a released
>> version.
>
> What's the use case here? You have a snapshot of log4j and there's a release
> version you can use?
>
> POM says 2.0-S
Brett Porter wrote:
However, I disagree with the default choice of updating the dependency to
another snapshot - since this is outside of the reactor it's a better practice
to pin to the release you just chose. I retained one exception for the use case
where it was a more recent snapshot than
On Sep 29, 2010, at 11:25 AM, Brett Porter wrote:
>
> On 29/09/2010, at 11:57 PM, Jason van Zyl wrote:
>
>>
>> On Sep 29, 2010, at 9:50 AM, Brett Porter wrote:
>>
>>> Hi,
>>>
>>> The release plugin has a mode where it can assist you in updating snapshot
>>> dependencies at release time. A l
On 29/09/2010, at 11:57 PM, Jason van Zyl wrote:
>
> On Sep 29, 2010, at 9:50 AM, Brett Porter wrote:
>
>> Hi,
>>
>> The release plugin has a mode where it can assist you in updating snapshot
>> dependencies at release time. A lot of this is better manipulated with the
>> versions plugin now
+1
2010/9/29 John Casey :
> Hi,
>
> *** NOTE ***
> This release depends on the pending 1.3 release of
> maven-common-artifact-filters. You will need BOTH of the staging
> repositories listed below in order to build the maven-assembly-plugin.
>
> We solved 92 issues:
> http://jira.codehaus.org/secu
+1
2010/9/29 John Casey :
> Hi,
>
> We solved 1 issue:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=15582
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=component+%3D+maven-commo
On Sep 29, 2010, at 9:50 AM, Brett Porter wrote:
> Hi,
>
> The release plugin has a mode where it can assist you in updating snapshot
> dependencies at release time. A lot of this is better manipulated with the
> versions plugin now, but it seems a useful feature to have at release time if
>
Hi,
The release plugin has a mode where it can assist you in updating snapshot
dependencies at release time. A lot of this is better manipulated with the
versions plugin now, but it seems a useful feature to have at release time if
you can.
The previous behaviour was a bit weird, though. It wo
Howdy,
As for [2], the nexus-indexer tries it's best to "recognize" (or guess is
maybe better) is an artifact an archetype or not, exactly because of that
mixup with packaging, etc. Considering all archetypes out there in central,
there is no "unique way" to decide... when an artifact is recognize
+1
-Lukas
John Casey wrote:
Hi,
*** NOTE ***
This release depends on the pending 1.3 release of
maven-common-artifact-filters. You will need BOTH of the staging
repositories listed below in order to build the maven-assembly-plugin.
We solved 92 issues:
http://jira.codehaus.org/secure/ReleaseN
11 matches
Mail list logo
