Temporary block on trunk commits.

11 views
Skip to first unread message

Thomas O'Brien

unread,
Mar 26, 2010, 11:38:51 AM3/26/10
to Architect Developers
Hi all,

Recently a commit to svn has caused the history of all files under src
to be un-retrievable. For example, you can try:

$ svn blame http://power-architect.googlecode.com/svn/trunk/src/ca/sqlpower/architect/ArchitectSession.java
svn: Could not resolve path /trunk/src/ca/sqlpower/architect/
ArchitectSession.java for history

Until we get this issue resolved please commit under the branch temp-
for-history-error. Any changes made to this branch will be merged once
this issue has been resolved.

I will be posting updates to this thread as they happen. Please post
any problems you are having, including errors building Architect so
they can get resolved.

Thomas

Thomas O'Brien

unread,
Mar 26, 2010, 2:34:36 PM3/26/10
to Architect Developers
Revision 3401 contains a new build.xml file which should fix any
errors with compiling the classes generated by the library annotation
processor.

Thomas

On Mar 26, 11:38 am, "Thomas O'Brien" <thomasobrie...@gmail.com>
wrote:


> Hi all,
>
> Recently a commit to svn has caused the history of all files under src
> to be un-retrievable. For example, you can try:
>

> $ svn blamehttp://power-architect.googlecode.com/svn/trunk/src/ca/sqlpower/archi...

Thomas O'Brien

unread,
Mar 26, 2010, 6:03:04 PM3/26/10
to Architect Developers
Google has fixed this in their Subversion backend. (For reference
http://groups.google.com/group/google-code-hosting/browse_thread/thread/cfdf438baf935744.)

Everyone can once again commit to the trunk. I will monitor the branch
until Monday in case a commit was made around the time of this post.

Please note! The src/ca directory is now under src/main/java/ca so be
careful not to lose changes when updating/switching to head. There
will be some more changes to the structure of the project in terms of
the regress package and the resources (mainly jdbc_drivers) but the
history problem should be solved.

Thomas

Reply all
Reply to author
Forward
0 new messages