@Martijn: what is the correct way to release wicket-eclipse-settings
module/project ?
martin@martin-laptop:~/git/apache/wicket/wicket-eclipse-settings$ mvn
release:prepare
adds:
<scm>
<connection>scm:svn:
http://svn.apache.org/repos/asf/maven/pom/tags/wicket-eclipse-settings-2
</connection>
<developerConnection>scm:svn:
https://svn.apache.org/repos/asf/maven/pom/tags/wicket-eclipse-settings-2
</developerConnection>
<url>
http://svn.apache.org/viewvc/maven/pom/tags/wicket-eclipse-settings-2</url>
</scm>
in its pom.xml and fails with:
-----------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli)
on project wicket-eclipse-settings: Unable to commit files
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: E155007:
'/home/martin/git/apache/wicket/wicket-eclipse-settings/pom.xml' is not a
working copy
[ERROR] -> [Help 1]
[ERROR]
How did you release ver. 1?
On Thu, Apr 2, 2015 at 1:14 PM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:
> Thank you very much - then it can be released.
>
> Am 02.04.15 um 10:36 schrieb Emond Papegaaij:
>
> I've tested the settings, and they look fine. The compiler level is set
>> to 7
>> and formatting works as expected.
>>
>> Best regards,
>> Emond
>>
>> On Wednesday 01 April 2015 22:30:15 Tobias Soloschenko wrote:
>>
>>> I just gave some hints - you did all the stuff! ;-)
>>>
>>> I saw something about a new SNAPSHOT version of wicket-eclipse-setting
>>> and I
>>> also saw that it corrects the compiler level in the prefs - so yes two
>>> versions for JDK 6 and JDK 7 are needed - version 2-SNAPSHOT in the
>>> master
>>> branch has to be tested and released before the Wicket 7 Release, because
>>> Wicket 7 can't be released with SNAPSHOTS.
>>>
>>> wicket-eclipse-settings has to be "mvn install"ed to be tested with the
>>> SNAPSHOT - anyone who is able to do this except me (the plugin of the
>>> market place has to be installed) ?
>>>
>>> @Emond: maybe you?! Because you know the plugin and the wicket formatting
>>> rules?!
>>>
>>> kind regards
>>>
>>> Tobias
>>>
>>> Am 01.04.2015 um 15:06 schrieb andrea del bene <an.delb...@gmail.com>:
>>>>
>>>> Well, the release of Wicket 7 might be itself an April fools day joke
>>>> :).
>>>>
>>>> Going back to serious matters, with the fundamental help of Tobias, we
>>>> are
>>>> preparing a new module to integrate user guide generation into Maven
>>>> workflow. The work is in branch 'grails-maven-integration'. The code is
>>>> already working but I still need to modify some contents of the guide to
>>>> adapt them to Wicket 7. I've traced those issues that might have an
>>>> impact on the guide:
>>>>
>>>> * [WICKET-5577] - Generation of wicket ids with prefix / suffix
>>>> * [WICKET-5410] - All IXyzSettings are removed
>>>> * [WICKET-5708] - convertInput() to public
>>>> * [WICKET-5713] - Move /wicket.properties to
>>>> /META-INF/wicket/xyz.properties>
>>>>
>>>>> Due to an excessive workload currently at €dayjob until 9 april I am
>>>>> unable to perform releases or work on anything else than the
>>>>> conference I'm organizing.
>>>>>
>>>>> Things I'd like to accomplish before finalizing 7:
>>>>>
>>>>> - move the deprecated Wicket 6 Tree* to wicket stuff
>>>>> - run our application (migration to 7 is held back by conference)
>>>>> - complete the new site
>>>>>
>>>>> I've almost completed the migration for wicket 7 save for the Tree*
>>>>> stuff, and when that's completed I can try to run our application to
>>>>> see if there are any possible important stuff that should be fixed
>>>>> before finalizing 7.
>>>>>
>>>>> Completing the new site (http://dashorst.github.io/wicket-site/) is
>>>>> still something I have on my list of things to do, and it is in good
>>>>> shape currently. I'd like to publish that one at the moment of
>>>>> releasing wicket 7.
>>>>>
>>>> Pleeeeezz see my PR: https://github.com/dashorst/wicket-site/pulls
>>>>
>>>> Martijn
>>>>>
>>>>
>
