Git Product home page Git Product logo

p2-mirror-dev's Introduction

PDT Extension Group P2 mirror

Build Status

A mirror for various p2 repositories a.k.a eclipse updatesites to provide a centralized repository for all your PDT needs.

The current URL:

http://p2.pdt-extensions.org/

Contributing your updatesite

If you want to add your updatesite to the mirror follow these steps:

  1. Fork the repo
  2. Copy _empty.b3aggrcon and fill with new repository
  3. Add contributions tag to mirror.b3aggr
  4. Add your feature via b3 editor
  5. Send us a pull request

Building the repo

  1. Clone this repository
  2. Run mvn clean install
  3. This will result in a working p2 repository in mirror/final

p2-mirror-dev's People

Contributors

zulus avatar pulse00 avatar gossi avatar

Stargazers

George Birbilis avatar José Rigoni Jr avatar  avatar  avatar Atsuhiro Kubo avatar Michele Locati avatar Paul Verest avatar  avatar

Watchers

Atsuhiro Kubo avatar  avatar Sven Kiera avatar  avatar Stephan Hochdörfer avatar James Cloos avatar Michele Locati avatar C4Tom avatar heui avatar Stephan Kellermayr avatar Phong Nguyen avatar Anthony Maske avatar

Forkers

gossi

p2-mirror-dev's Issues

Update fails on http://p2-dev.pdt-extensions.org/ for PDT Extensions

An error occurred while collecting items to be installed
session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.core_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.core_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.core.ui_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.core.ui_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.repos_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.repos_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.repos.ui_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.repos.ui_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.semanticanalysis_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.semanticanalysis_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.semanticanalysis.ui_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.semanticanalysis.ui_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.server_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.server_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.server.ui_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/plugins/org.pdtextensions.server.ui_0.22.2.201701260348.jar
Artifact not found: http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/features/org.pdtextensions.feature_0.22.2.201701260348.jar.
http://dl.bintray.com/pulse00/pdt-extensions/nightly/0.0.6/features/org.pdtextensions.feature_0.22.2.201701260348.jar

PTI Tool with PDT 3.1.2

I'm not sure where should I add this error because PTI (CodeSniffer etc..) its not updated from 2 years.

I have this error after eclipse start:

Errors running builder 'Script Builder' on project 'mow'.

java.lang.NoSuchMethodError: org.eclipse.php.internal.debug.core.launching.PHPLaunchUtilities.getCommandLine(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Ljava/lang/String;)[Ljava/lang/String;
    at org.phpsrc.eclipse.pti.core.launching.PHPToolExecutableLauncher.launch(PHPToolExecutableLauncher.java:113)
    at org.phpsrc.eclipse.pti.core.launching.PHPToolExecutableLauncher.launch(PHPToolExecutableLauncher.java:60)
    at org.phpsrc.eclipse.pti.core.launching.PHPToolExecutableLauncher.launch(PHPToolExecutableLauncher.java:55)
    at org.phpsrc.eclipse.pti.core.launching.PHPToolLauncher.launch(PHPToolLauncher.java:164)
    at org.phpsrc.eclipse.pti.core.launching.PHPToolLauncher.launch(PHPToolLauncher.java:113)
    at org.phpsrc.eclipse.pti.validators.externalchecker.core.ExternalPHPCheckerDelegate.runValidator(ExternalPHPCheckerDelegate.java:99)
    at org.phpsrc.eclipse.pti.validators.externalchecker.core.ExternalSourceModuleWorker.runValidator(ExternalSourceModuleWorker.java:69)
    at org.eclipse.dltk.validators.core.SourceModuleValidatorWorker.runValidator(SourceModuleValidatorWorker.java:67)
    at org.eclipse.dltk.validators.core.AbstractValidatorWorker.validate(AbstractValidatorWorker.java:148)
    at org.eclipse.dltk.validators.core.AbstractValidatorWorker.doValidate(AbstractValidatorWorker.java:126)
    at org.eclipse.dltk.validators.core.SourceModuleValidatorWorker.validate(SourceModuleValidatorWorker.java:37)
    at org.eclipse.dltk.validators.core.ValidatorRuntime.executeSourceModuleValidators(ValidatorRuntime.java:448)
    at org.eclipse.dltk.validators.internal.core.ValidatorBuilder.build(ValidatorBuilder.java:50)
    at org.eclipse.dltk.internal.core.builder.ScriptBuilder.fullBuild(ScriptBuilder.java:449)
    at org.eclipse.dltk.internal.core.builder.ScriptBuilder.build(ScriptBuilder.java:156)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

Getter/Setter generation : Choose method name formatting (camelcase or underscores)

Before the last update, i was able to choose the method name formatting, in my case I have this :

class A {
  private $my_first_member;
  private $my_second_member;
}

Before the update, I could generate getters and setters like this :

class A {
  private $my_first_member;
  private $my_second_member;
  public function getMyFirstMember(){
    return $this->my_first_member;
  }
  public function setMyFirstMember($myFirstMember){
    $this->my_first_member = $myFirstMember;
  }
  public function getMySecondMember(){
    return $this->my_second_member;
  }
  public function setMySecondMember($mySecondMember){
    $this->my_second_member = $mySecondMember;
  }
}

That was great, because I could continue mapping my members into database fields automatically, and respect the public members naming convention.

Know it generates method names like this : getMy_first_member().

Can we have a feature to choose the naming convention ?

Thanks in advance

Smarty editor not properly associating with *.tpl files

Installed the Smarty Feature in Zend Studio 12.5 on several machines (Macs). On one machine the file association is correct but on the others the Preferences show that *.template and *.tpl files are associated with the Smarty Editor but double-clicking a *.tpl file opens an external program. Right-click -> Open With -> Smarty Editor works as expected but is a laborious way to open every *.tpl file.

Proposal: Show warning when type referenced in docBlock is not valid

It would be nice that the semantic analysis shows a warning when a Class referenced in @var or @return or @param is invalid.
For instance:

/**
 * @var MyClassName
 */
private $myProperty;

Should show a warning if MyClassName is not in the same namespace that the current class and was not included with a use statement.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.