We have 2 files in there which I guess are just caused by default settings in
some IDE:
~/develop/java/apache/deltaspike$>grep -r "JBoss, Home of Professional Open
Source" *
deltaspike/modules/data/impl/src/test/resources/disabled/META-INF/apache-deltaspike.properties:#
JBoss, Home of Professional Open Source
deltaspike/modules/jsf/impl/src/test/resources/default/WEB-INF/faces-config.xml:
JBoss, Home of Professional Open Source
Both are basically empty templates or a simple file.
@Raphael, can you please change this to the standard ASF header? txs!
LieGrue,
strub
> Am 02.03.2015 um 08:39 schrieb Mark Struberg <[email protected]>:
>
> Hi!
>
> Gonna fix this.
> I’d also say we should call the release 1.3.0. There have been a bunch of
> feature enhancements.
> Will fix this and gonna roll the release.
>
> LieGrue,
> strub
>
>> Am 02.03.2015 um 00:00 schrieb Gerhard Petracek <[email protected]>:
>>
>> hi @ all,
>>
>> currently we are facing changes and issues with the release process (due to
>> the new root-pom).
>> #1 during the release process [1] it's now needed to confirm the version of
>>> every< module (minor, but something changed here)
>> #2 per >default< the resulting tag is deltaspike-root-[version] instead of
>> deltaspike-project-[version]
>> #3 during the prepare-step maven tries to interact with the original
>> repository (maven asks for the password which wasn't the case before)
>>
>> -> we need to resolve those topics, before we can continue.
>>
>> since the release is bocked anyway, we could think about the next version
>> number as well
>> (we could release v1.3.0 instead of v1.2.2, since the release will contain
>> new features).
>>
>> regards,
>> gerhard
>>
>> [1] http://deltaspike.apache.org/steps_for_a_release.html
>
