Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] Testing single plugin export/deployment
Ok, these are the errors I'm getting... if anyone has a thought on how I need to massage my metadata so I can install these adjusted plugins with my new feature I would greatly appreciate it.  The feature's plugins causing the conflict are lml.da and lml.da.server but they're essentially the same as the version in the 5.0.5 branch.

Cannot complete the install because of a conflicting dependency.
  Software being installed: Pbs_cobalt_ibm 1.0.0.201201261405 (pbs_cobalt_ibm.feature.group 1.0.0.201201261405)
  Software currently installed: Eclipse IDE for Parallel Application Developers 1.4.1.20110911-0506 (epp.package.parallel 1.4.1.20110911-0506)
  Software currently installed: PTP Resource Manager for SLURM 5.0.4.201111121445 (org.eclipse.ptp.rm.slurm.feature.group 5.0.4.201111121445)
  Only one of the following can be installed at once: 
    PTP LML DA Server 2.0.0.201201261405 (org.eclipse.ptp.rm.lml.da.server 2.0.0.201201261405)
    PTP LML DA Server 2.0.0.201109141657 (org.eclipse.ptp.rm.lml.da.server 2.0.0.201109141657)
    PTP LML DA Server 2.0.0.201111121445 (org.eclipse.ptp.rm.lml.da.server 2.0.0.201111121445)
    PTP LML DA Server 2.0.0.201110141146 (org.eclipse.ptp.rm.lml.da.server 2.0.0.201110141146)
    PTP LML DA Server 1.0.0.201107131351 (org.eclipse.ptp.rm.lml.da.server 1.0.0.201107131351)
    PTP LML DA Server 1.0.0.201106140904 (org.eclipse.ptp.rm.lml.da.server 1.0.0.201106140904)
  Only one of the following can be installed at once: 
    PTP Resource Manager for SLURM 5.0.2.201109141657 (org.eclipse.ptp.rm.slurm.feature.jar 5.0.2.201109141657)
    PTP Resource Manager for SLURM 5.0.1.201107131351 (org.eclipse.ptp.rm.slurm.feature.jar 5.0.1.201107131351)
    PTP Resource Manager for SLURM 5.0.4.201111121445 (org.eclipse.ptp.rm.slurm.feature.jar 5.0.4.201111121445)
    PTP Resource Manager for SLURM 5.0.0.201106140904 (org.eclipse.ptp.rm.slurm.feature.jar 5.0.0.201106140904)
    PTP Resource Manager for SLURM 5.0.3.201110141146 (org.eclipse.ptp.rm.slurm.feature.jar 5.0.3.201110141146)
  Cannot satisfy dependency:
    From: Eclipse IDE for Parallel Application Developers 1.4.1.20110911-0506 (epp.package.parallel 1.4.1.20110911-0506)
    To: org.eclipse.epp.package.parallel.feature.feature.group [1.4.1.20110911-0506]
  Cannot satisfy dependency:
    From: EPP Parallel Feature 1.4.1.20110911-0506 (org.eclipse.epp.package.parallel.feature.feature.group 1.4.1.20110911-0506)
    To: org.eclipse.ptp.feature.group 0.0.0
  Cannot satisfy dependency:
    From: Parallel Tools Platform (PTP) End-User Runtime 5.0.0.201106140904 (org.eclipse.ptp.feature.group 5.0.0.201106140904)
    To: org.eclipse.ptp.rm.slurm.feature.group [5.0.0.201106140904]
  Cannot satisfy dependency:
    From: Parallel Tools Platform (PTP) End-User Runtime 5.0.1.201107131351 (org.eclipse.ptp.feature.group 5.0.1.201107131351)
    To: org.eclipse.ptp.rm.slurm.feature.group [5.0.1.201107131351]
  Cannot satisfy dependency:
    From: Parallel Tools Platform (PTP) End-User Runtime 5.0.2.201109141657 (org.eclipse.ptp.feature.group 5.0.2.201109141657)
    To: org.eclipse.ptp.rm.slurm.feature.group [5.0.2.201109141657]
  Cannot satisfy dependency:
    From: Parallel Tools Platform (PTP) End-User Runtime 5.0.3.201110141146 (org.eclipse.ptp.feature.group 5.0.3.201110141146)
    To: org.eclipse.ptp.rm.slurm.feature.group [5.0.3.201110141146]
  Cannot satisfy dependency:
    From: Parallel Tools Platform (PTP) End-User Runtime 5.0.4.201111121445 (org.eclipse.ptp.feature.group 5.0.4.201111121445)
    To: org.eclipse.ptp.rm.lml.feature.group [5.0.4.201111121445]
  Cannot satisfy dependency:
    From: PTP LML Support 5.0.4.201111121445 (org.eclipse.ptp.rm.lml.feature.group 5.0.4.201111121445)
    To: org.eclipse.ptp.rm.lml.da.server [2.0.0.201111121445]
  Cannot satisfy dependency:
    From: PTP Resource Manager for SLURM 5.0.0.201106140904 (org.eclipse.ptp.rm.slurm.feature.group 5.0.0.201106140904)
    To: org.eclipse.ptp.rm.slurm.feature.jar [5.0.0.201106140904]
  Cannot satisfy dependency:
    From: PTP Resource Manager for SLURM 5.0.1.201107131351 (org.eclipse.ptp.rm.slurm.feature.group 5.0.1.201107131351)
    To: org.eclipse.ptp.rm.slurm.feature.jar [5.0.1.201107131351]
  Cannot satisfy dependency:
    From: PTP Resource Manager for SLURM 5.0.2.201109141657 (org.eclipse.ptp.rm.slurm.feature.group 5.0.2.201109141657)
    To: org.eclipse.ptp.rm.slurm.feature.jar [5.0.2.201109141657]
  Cannot satisfy dependency:
    From: PTP Resource Manager for SLURM 5.0.3.201110141146 (org.eclipse.ptp.rm.slurm.feature.group 5.0.3.201110141146)
    To: org.eclipse.ptp.rm.slurm.feature.jar [5.0.3.201110141146]
  Cannot satisfy dependency:
    From: PTP Resource Manager for SLURM 5.0.4.201111121445 (org.eclipse.ptp.rm.slurm.feature.group 5.0.4.201111121445)
    To: org.eclipse.ptp.rm.slurm.feature.jar [5.0.4.201111121445]
  Cannot satisfy dependency:
    From: Pbs_cobalt_ibm 1.0.0.201201261405 (pbs_cobalt_ibm.feature.group 1.0.0.201201261405)
    To: org.eclipse.ptp.rm.lml.da.server [2.0.0.201201261405]


Thanks,
Wyatt

On Wed, Jan 25, 2012 at 6:16 PM, Beth Tibbitts <tibbitts@xxxxxxxxxx> wrote:

Wyatt, do you have a feature for your plugin?  
The new project wizard makes it easy to make one, even if you are using it only for your standalone testing as you describe.
Then you can use export>deployable features to create the update site (in a .zip file if you like).
And install that 'properly' i.e. with Help>install new software, and point to the update site you made.

Are you adding the date/timestamp qualifier to the plugin/feature version and forcing it to update (in that export>deployable features dialog there is a tab where you can blank it out, then it will reset to current date and time)?  If you have that qualifier and it's the current date and time, then the version number should trump the already installed ones.

If this doesn't fix it, i would also restart eclipse with -clean like Greg suggests.


...Beth

Beth Tibbitts
Eclipse Parallel Tools Platform  http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511

Inactive hide details for Greg Watson ---01/25/2012 08:04:12 PM---Wyatt, Dopping plugins into the plugins or dropins folders isGreg Watson ---01/25/2012 08:04:12 PM---Wyatt, Dopping plugins into the plugins or dropins folders is equivalent to installing the plugins.


    From:

Greg Watson <g.watson@xxxxxxxxxxxx>

    To:

Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>,

    Date:

01/25/2012 08:04 PM

    Subject:

Re: [ptp-dev] Testing single plugin export/deployment

    Sent by:

ptp-dev-bounces@xxxxxxxxxxx



Wyatt,

Dopping plugins into the plugins or dropins folders is equivalent to installing the plugins. This means that any conflict with existing plugins or other dependency problem will prevent them from being installed. I've had problems getting this to work also. You could check the error log or .log file to see if there are any messages. You can also try adding -clean -console -consoleLog to the eclipse command line.

The best way to get this to work is to create an archive update site and install using the update manager. Now that we're using maven, creating a local update site is not that difficult. If you'd like to try this approach, let me know.

Google "eclipse dropins" will give you some useful information also.

On Jan 25, 2012, at 3:18 PM, Wyatt Spear wrote:
    Specifically, our updated rm.lml.da.server isn't showing up, even when the original plugin is removed.  rm.lml.da is successfully overriding the installed plugin.  We're not sure what the difference is...

    =Wyatt

    On Tue, Jan 24, 2012 at 4:50 PM, Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:
      Greetings,

      We need to test our modified lml.da plugins on an actual eclipse installation rather than in a debug environment.  This means exporting the plugins and dropping them into the dropins or plugins folder of a real eclipse install.  When we do this with a new plugin (one not already present in the installation) it will show up.  If a version the plugin was already present as part of the PTP update site or the PTP package, then it will not override the original version so we can't test it out.  Is there any way we can force eclipse to recognize a new version of a PTP plugin that has already been installed?  Removing the older versions from the plugins folder doesn't work and we're not sure what else to try.

      Thanks,
      Wyatt

    _______________________________________________
    ptp-dev mailing list
    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev



_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


Back to the top