freemarker-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Dekany <ddek...@freemail.hu>
Subject Re: [VOTE] Release FreeMarker 2.3.24-rc01-incubating
Date Mon, 11 Jan 2016 19:05:51 GMT
Sure, I only ever push standard Maven artifacts (jar, source, javadoc)
to Nexus. For distributing non-Maven non-official artifacts there's
https://dist.apache.org/repos/dist/dev/.


-- 
Thanks,
 Daniel Dekany


Monday, January 11, 2016, 5:06:01 PM, Ralph Goers wrote:

> Actually, you can deploy SNAPSHOTs from a Jenkins job every day if
> you want to. They aren’t releases. I believe the only purpose that
> section serves is to let you verify that your settings are correct
> and that you have permission to deploy to the repository.
>
> Note that what you are deploying to the Nexus repository is what is
> going to go to Maven Central. What goes to Maven Central should not
> include the zip or tar.gz of the binaries and source you will be
> distributing on dist.apache.org.  With Log4j I end up deploying all
> of that to Nexus and then telling folks how to download it with
> wget. Once the vote passes I commit the distribution pieces into the
> distribution directory and delete them from Nexus before publishing the release in Nexus.
>
> Ralph
>
>> On Jan 8, 2016, at 2:37 AM, Daniel Dekany <ddekany@freemail.hu> wrote:
>> 
>> There were no further problems after I have realized that such
>> automatic version modification must happen there.
>> 
>> BTW, I'm not sure why the snapshot related steps aren't marked as
>> optional in the "Staging a release" guide. If someone wants to
>> understand what's going on, instead of just following the prescribed
>> steps, it can be confusing, especially without mentioning that the
>> "-SNAPSHOT" will be removed, and so you do not stage SNAPSHOT-s.
>> 
>> 
>> Friday, January 8, 2016, 8:42:53 AM, Sergio Fernández wrote:
>> 
>>> Well, that's described by the Maven Release plugin:
>>> 
>>> http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html
>>> 
>>> BTW, I always found that plugin a bit tricky, so some defaults are not the best,
for instance:
>>> 
>>> https://github.com/apache/marmotta/blob/develop/pom.xml#L208
>>> 
>>> So in a past project we've put together a detailed guide that may
>>> be relevant for you too:
>>> https://wiki.apache.org/marmotta/ReleaseProcess
>>> 
>>> I really find useful, in combination of pushChanges=false, the
>>> trick of using the local close as connections on release:prepare:
>>> -DconnectionUrl=scm:git:file://`pwd`/.git
>>> 
>>> Hope that helps.
>>> 
>>> 
>>> On Thu, Jan 7, 2016 at 9:16 PM, Daniel Dekany <ddekany@freemail.hu> wrote:
>>> Never mind, I have figured it out... "mvn release:prepare" removes the
>>> "-SNAPHOST" from the version, hence the documentation at ASF doesn't
>>> mention that such thing has happened after you have done the SNAPSHOT
>>> deployment. (A bit confusing IMO.)
>>> 
>>> 
>>> Thursday, January 7, 2016, 6:03:02 PM, Daniel Dekany wrote:
>>> 
>>>> I have fixed the noticed legal and packaging things (no actual change
>>>> in FreeMarker itself since the last vote), and almost called a new
>>>> voting, but I have some Maven doubts. I can deploy into the staging
>>>> repo, but I didn't dare to Close the staging repo because this I don't
>>>> understand in
>>>> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote:
>>>> "the project you want to stage must be a SNAPSHOT version". But if
>>>> it's 2.3.24-rc01-incubating-SNAPSHOT (as opposed to just
>>>> 2.3.24-rc01-incubating, which it is now), and the vote passes, then I
>>>> had to build and Maven-deploy a different artifact that's not a
>>>> SNAPSHOT and wasn't voted on. I don't think that's the intent. So, if
>>>> I just Close the staging repo, I would think that it doesn't go
>>>> anywhere "too public", not even if it's non-SNAPSHOT, only if I also
>>>> "Promote" it. But I don't know. So what artifact version should I use?
>>>> 
>>>> 
>>>> Otherwise, here's the new version - anybody spots something wrong with
>>>> it before the next voting?
>>>> 
>>>> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-rc01-incubating/
>>>> 
>>>> 2.3-gae commit hash: b968ffaf2b52225e57ec196aaa3ee7345fa0024d
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=b968ffaf2b52225e57ec196aaa3ee7345fa0024d
>>>> 
>>>> 2.3 commit hash: 9a4f598888c1eec85a0d7b9afb400626ec49f46e
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=9a4f598888c1eec85a0d7b9afb400626ec49f46e
>>>> 
>>>> 
>>>> Thursday, January 7, 2016, 5:18:20 PM, Sergio Fernández wrote:
>>>> 
>>>>> On Thu, Jan 7, 2016 at 4:12 PM, Daniel Dekany <ddekany@freemail.hu>
wrote:
>>>>>> 
>>>>>>> You'll need to to push the release to Maven central, so it's
better to
>>>>>> have
>>>>>>> it as soon as possible. I already requested it to INFRA, see
>>>>>>> https://issues.apache.org/jira/browse/INFRA-11045
>>>>>> 
>>>>>> Sorry if I was misunderstandable. I did that days ago, and in
>>>>>> principle we have it already.
>>>>>> 
>>>>> 
>>>>> OK, so I close that issue. No problem, thanks.
>>>>> 
>>>>> 
>>>> 
>>> 
>>> --
>>> Thanks,
>>> Daniel Dekany
>>> 
>>> 
>>> 
>>> 
>> 
>> -- 
>> Thanks,
>> Daniel Dekany
>> 
>> 
>
>
>


Mime
View raw message