I also think that installing locally is somehow to be seen as a hack. And
though I do it myself on a regular basis while developing, I indeed never
see it as a sustainable place for my artifacts, only deploy is (and still
temporary for non releases).
Yes, I think we should rename that tag.
And if
+1
On 15 April 2014 07:14, Dennis Lundberg wrote:
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&version=20236&styleName=Html
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pi
Wouldn't be the solution to just remove the svn trunk & branches, and only
leave the tags in the last revision?
Or intermediately, leave the trunk path to be found, but remove anything
but that file "MOVED_TO_GIT"?
2014-04-16 22:31 GMT+02:00 Mirko Friedenhagen :
>
> +1 for Git and please includ
+1 for Git and please include the new repository location in the
MOVED_TO_GIT file as suggested by Dennis :-)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Wed, Apr 16, 2014
+1 (non-binding)
- Checked the SHA1 of the source zip
- Downloaded and unzipped source zip and ran "mvn clean verify
-Prun-its" successfully with Maven 3.2.1 and JDK 1.7.0_55
- Ran "mvn clean verify site site:stage" successfully with two pet projects.
Regards Mirko
--
http://illegalstateexception.b
Hi
No objections from me, but a request.
Please put a file in the root of the old svn repo called MOVED_TO_GIT or
something similar, so that it is clear that it has moved. I wasted some
time the other week trying to commit to plugin-testing before I realized
that the svn repo was read-only...
--
