Skip to main content

Home/ Java Development/ Group items tagged svn

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Prajot G.

Installation Instructions - Eclipse Subversive - 0 views

www.eclipse.org/...installation-instructions.php

SVN

shared by Prajot G. on 24 Jul 12 - No Cached
  • d Eclipse is rebooted, Subversive automatically displays the dialog that shows Subversive SVN Connectors compatible with the installed version of the plug-in. Alternatively, you can install Subversive SVN Connectors from online and archived update sites for connectors. Visit Polarion.com, to get information about the available update sites.
  • Prajot G. on 24 Jul 12
     
    Eclipse SVN plug-in installation instructions
tubagus99

Solve 'svn : Working copy is too old (format 10, created by Subversion 1.6)' - Eli - 0 views

blog.elijaa.org/index.php

svn subversion java

shared by tubagus99 on 15 May 13 - No Cached
  • tubagus99 on 15 May 13
     
    "Solve 'svn : Working copy is too old (format 10, created by Subversion 1.6)'"
abuwipp

Subversive - SVN Team Provider | Eclipse Plugins, Bundles and Products - Eclipse Market... - 0 views

marketplace.eclipse.org/...subversive-svn-team-provider

subversive eclipse svn install

shared by abuwipp on 12 Mar 11 - No Cached
  • abuwipp on 12 Mar 11
     
    JavaHL is  platform-dependent
Hendy Irawan

logviewer - =Eclipse Log Viewer= - Google Project Hosting - 0 views

code.google.com/...logviewer

eclipse log viewer google project hosting

shared by Hendy Irawan on 01 Feb 12 - No Cached
  • Hendy Irawan on 01 Feb 12
     
    "Eclipse Plug-in for tailing log files and eclipse consoles (e.g. SVN, Java Stack Trace, CDT), including syntax coloring with either a regular expression or a word match. It allows you to have multiple logs open concurrently. "
Hendy Irawan

Buckminster Project - Eclipsepedia - 0 views

wiki.eclipse.org/Buckminster

project eclipsepedia buckminster eclipse build system management

shared by Hendy Irawan on 03 Jan 11 - No Cached
  • Hendy Irawan on 03 Jan 11
     
    " Jump to: navigation, search Welcome to our Wiki. This is the Wiki home page for the Buckminster Component Assembly project, an Eclipse Tools sub project. Buckminster is a component resolution & materialization framework. Its purpose is to get software components for you and materialize them in a context of choice, typically a workspace or file system. This applies whether you are looking at what's available on your local machine, within your development organization or in the public open source cloud. Buckminster reuses existing investments in a wide range of build and source management tools - Maven, ANT, CVS, SVN, PDE, etc. It removes ambiguity from component descriptions, enables component sharing and increases productiveness when applied in development, build, assembly and deploy scenarios. "
anonymous

Organize Projects - Google Web Toolkit - Google Code - 0 views

code.google.com/...evGuideOrganizingProjects.html

shared by anonymous on 14 Jan 11 - Cached
  • com.google.gwt.gears.Gears
    • anonymous
      anonymous on 14 Jan 11
       
      Gears.gwt.xml does not define andy entry point. It can only be inherits
  • two ways to approach loading them
  • nclude each module with a separate <script> tag
  • ...118 more annotations...
  • Create a top level module XML definition
  • Compile the top level module
  • the second approach will lead to much better end-user performance
  • each module has to be downloaded separately by the end-user's browser
  • each module will contain redundant copies of GWT library
  • conflict with each other during event handling
  • Linkers are divided into three categories, PRE, POST, and PRIMARY
  • one primary linker is run for a compilation
  • everal linkers are provided by Core.gwt.xml, which is automatically inherited by User.gwt.xml.
  • monolithic JavaScript file.
  • cross-site deployment model.
  • standard iframe-based
  • <add-linker name="xs" />
  • The GWT compiler
  • packaging its output with the Linker subsystem
  • responsible for the final packaging of the JavaScript code
  • providing a pluggable bootstrap mechanism
  • re-use an existing Java API for a GWT project,
  • <super-source>
  • "re-root" a source path
  • to emulate part of the JRE not implemented by GWT
  • tells the compiler to add all subfolders of com/example/myproject/jre/
  • to the source path
  • com/google/myproject/gwt/jre/java/util/UUID.java
  • most commonly used elements in the module XML file.
  • <inherits name="
  • herits all the settings from the specified module
  • <entry-point class=
  • Entry points are all compiled into a single codebase
  • when the onModuleLoad() of your first entry point finishes, the next entry point is called immediately.
  • Any number of entry-point classes can be added
  • <source path="
  • resources get copied into the output directory during a GWT compile.
  • client subpackage is implicitly added to the source path
  • <public path="path" />
  • treated as a publicly-accessible resource.
  • resources get copied into the output directory
  • the public subpackage is implicitly added to the public
  • <servlet
  • For RPC, this element loads a servlet class
  • mounted at the specified URL path
  • path=
    • anonymous
      anonymous on 14 Jan 11
       
      monting location
  • class="
    • anonymous
      anonymous on 14 Jan 11
       
      Which servlet class
  • URL path should be absolute
  • @RemoteServiceRelativePath attribute
  • you must configure a WEB-INF/web.xml in your war directory to load any servlets needed.
  • n development mode,
  • <script src="
  • external JavaScrip
  • <stylesheet src="
  • Extends the set of values
  • for an existing client property
  • <replace-with-class>
  • <generate-with-class>
  • <when-property-is
  • three different types of predicates are
  • <when-type-assignable
  • <when-type-is
  • <all>
  • <any>
  • <none>
  • GWT libraries are organized into modules
  • you want to inherit at least the User module
  • contains all the core GWT functionality
  • including the EntryPoint class
  • widgets and panels
  • History feature
  • Internationalization
  • DOM programming, and more
  • Low-level HTTP
  • Use the following syntax to cause an external JavaScript file to be loaded
  • before your module entry point is called.
  • as if you had included it explicitly using the HTML <script
  • loaded before your onModuleLoad() is called.
  • all included scripts will be loaded when your application starts, in the order in which they are declared.
  • associate external CSS files with your module
  • GWT.getModuleBaseURL() + "foo.css" in client code
  • module's public path
  • useful when
  • inheritance makes resource inclusion particularly convenient.
  • If you wish to create a reusable library that relies upon particular stylesheets or JavaScript files, you can be sure that clients
  • see the documentation for FileSet for a general overview
  • <public>
  • <super-source>
  • <source>
  • includes
  • excludes
  • defaultexcludes
  • casesensitive
  • By default, the patterns listed here are excluded.
  • defaultexcludes is true
  • <script src='myApp/myApp.nocache.js'></script>
  • <script> tags always block evaluation of the page
  • <img> tags do not block page evaluation
  • two simultaneous connections
  • The body.onload() event will only fire once all external resources are fetched, including images and frames.
  • GWT selection script
  • like a normal script tag
  • but the compiled script will be fetched asynchronously.
  • Parsing is blocked until externalScriptZero.js is done fetching and evaluating.
  • myApp/myApp.nocache.js completes
  • the compiled scrip
  • (<hashname>.cache.html
  • begins fetching in a hidden IFRAME (this is non-blocking).
  • onModuleLoad() is not called yet, as we're still waiting on externalScriptOne.js
  • body.onload() fires
  • onload='alert("w00t!")
    • anonymous
      anonymous on 14 Jan 11
       
      is the last line executed
  • put the GWT selection script as early as possible
  • because it won't block any other script requests
  • <img> tags are not guaranteed to be done loading when onModuleLoad() is called
  • <script> tags are guaranteed to be done loading when onModuleLoad() is called
  • multiple EntryPoints
  • will all be called in sequence as soon as that module (and the outer document) is ready
  • multiple GWT modules within the same page
  • each module's EntryPoint will be called as soon as both that module and the outer document is ready
  • EntryPoints are not guaranteed to fire at the same time
  • or in the same order
  • in which their selection scripts were specified in the host page
anonymous

untitled - 0 views

code.google.com/...DevGuideUiBinder.html

java TODO

shared by anonymous on 29 Dec 10 - Cached
  • initWidget(uiBinder.createAndBindUi(this));
    • anonymous
      anonymous on 29 Dec 10
       
      To inizialize the "menber variable" whith the widget object described in the XML view despription
  • uiBinder.createAndBindUi(this)
  • GWT compiler won't actually visit this URL to fetch the file, because a copy of it is baked into the compiler
  • ...15 more annotations...
  • @UiField have default visibility
  • UIObject
  • DivElement
  • If your factory method needs arguments, those will be required as attributes.
  • Every widget that is declared in a template is created by a call to GWT.create().
  • @UiConstructor annotation.
  • you can mark your own widgets with
  • CricketScores has no default (zero args) constructor
  • you can define a @UiFactory method on the UiBinder's owner
  • annotate a constructor of CricketScores with @UiConstructor.
  •   @UiFactory
  • public class UserDashboard extends Composite {  interface MyUiBinder extends UiBinder<Widget, UserDashboard> {}  private static MyUiBinder uiBinder = GWT.create(MyUiBinder.class);  public UserDashboard() {    initWidget(uiBinder.createAndBindUi(this));  }}
  • use several different XML templates for the same view
  • public interface Display
  • methods can be called to fill in attribute values
Hendy Irawan

Assembla project workspaces to accelerate software teams, with issue tracking, GIT, SVN... - 0 views

www.assembla.com/?affiliate=ceefour

project assembla software workspaces

shared by Hendy Irawan on 26 May 11 - No Cached
  • Hendy Irawan on 26 May 11
     
    "Assembla workspaces to accelerate software teams Ticketing and issue management, Subversion, Git, Mercurial, Wiki, and other collaboration tools to accelerate development. Unite your team with a single activity stream view. Free starter offers include free subversion, free git, standup/scrum reporting, and unlimited free services for public communities and open source projects. "
1 - 8 of 8
Showing 20▼ items per page