[JBoss JIRA] (JBIDE-13175) Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13175?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13175:
------------------------------------------
JGit answers 2) when using
{code}
BranchTrackingStatus status = BranchTrackingStatus.of(repository, branchName);
{code}
BranchTrackingStatus may be queried in the following way:
{code}
/**
* @return number of commits that the local branch is ahead of the
* remote-tracking branch
*/
public int getAheadCount();
/**
* @return number of commits that the local branch is behind of the
* remote-tracking branch
*/
public int getBehindCount()
{code}
> Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13175
> URL: https://issues.jboss.org/browse/JBIDE-13175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha1
>
> Attachments: 1-local-change.png, no-local-changes.png, no_changes_yes.png
>
>
> # EXEC: launch *OpenShift Application* wizard and create a new application / import existing one
> # ASSERT: you get the OpenShift application imported to your workspace
> # EXEC: in *Servers* view, select the adapter for your OpenShift application and pick *Publish* from its context menu
> Result:
> The adapter tells you that there are no local changes. If you look at your local project you'll see in the git-decoration that the local git repo is ahead of 1 commit of the remote, so there is a local commit that could be pushed/published.
> !no-local-changes.png!
> Expected result:
> The adapter should tell you that there are local changes and ask you if you want to publish them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13175) Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13175?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13175:
------------------------------------------
OpenShift tooling currently's able to check for 1) but not for 2).
We need to implement 2)
> Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13175
> URL: https://issues.jboss.org/browse/JBIDE-13175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha1
>
> Attachments: 1-local-change.png, no-local-changes.png, no_changes_yes.png
>
>
> # EXEC: launch *OpenShift Application* wizard and create a new application / import existing one
> # ASSERT: you get the OpenShift application imported to your workspace
> # EXEC: in *Servers* view, select the adapter for your OpenShift application and pick *Publish* from its context menu
> Result:
> The adapter tells you that there are no local changes. If you look at your local project you'll see in the git-decoration that the local git repo is ahead of 1 commit of the remote, so there is a local commit that could be pushed/published.
> !no-local-changes.png!
> Expected result:
> The adapter should tell you that there are local changes and ask you if you want to publish them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBDS-2447) Issues to be resolved in SOA 5.0.3 Tooling
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2447?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2447:
------------------------------------
Len discovered this issue: "I have multiple runtimes installed. I create a new project and reference the SOA 5.2 (aka esb 4.10) runtime - and the project creation dialog/wizard tells me I have 4.12 "
My response:
The issue you've discovered really isn't a new one, but I have a better understanding of what's going on... So let me try to explain.
For each version of ESB, we have declared an explicit facet. In org.jboss.tools.esb.project.core, we have facets defined (4.2,4.3,4.4,4.5,4.6,4.7,4.9,4.10,4.11,4.12) and assign them to EAP runtime components (4.3,5.0,6.0) (which are specified in the AS tools plug-ins).
The "New ESB Project" wizard extends org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard and the first page extends org.eclipse.wst.web.ui.internal.wizards.DataModelFacetCreationWizardPage. We don't do any customizing to that page beyond telling it which facets (i.e. ESB) we want to use for the new project. (The fact that these are internal classes doesn't help.)
The first page is the one that gathers the runtimes (Target Runtime drop-down) and the facet versions (JBoss ESB Version drop-down). If I select a pre-defined runtime (let's say JBoss SOA-P 5.2 GA, which shipped with ESB 4.10), because of the way we have facets defined and associated with EAP runtimes, it automatically selects ESB version 4.12, because it's the highest supported ESB facet version associated with an EAP 5.x runtime. It does this by default.
So at this point, the user has to know what version of ESB they are working with and change the version drop-down accordingly. This selection in turn selects the "ESB Config Version" on the "Install ESB Facet" page later in the project wizard. If they leave the ESB version alone, the config version defaults to 1.3.1, which should work for ESB 4.11/4.12 but may cause issues going against ESB 4.10 which expects config version 1.3.0. (Len tested deploying an empty ESB project configured for 4.12 to SOA-P 5.2/ESB 4.10 and it seems to have worked, but will do more testing on this I'm sure).
Ultimately there's a usability nightmare in this particular combination of pages and settings that we'll need to address eventually. That said, this particular issue has been around as far back as I can see in the code.
Max says: "I suggest putting this issue in jira with this excellent write up and look for a solution in the next feature release of esb/soa tools - not something we should try fix in JBT 3.3.x/JBDS 5.x stream."
Follow up questions from Len:
"On this question:
'If they leave the ESB version alone, the config version defaults to 1.3.1, which should work for ESB 4.11/4.12 but may cause issues going against ESB 4.10 which expects config version 1.3.0.'
I haven't yet been able to create a problem with this - but I *think* users can run into trouble if they attempt to use a feature that was introduced in 1.3.1, but thy have specified 1.3.0 - But - they can always modify the schema setting."
> Issues to be resolved in SOA 5.0.3 Tooling
> ------------------------------------------
>
> Key: JBDS-2447
> URL: https://issues.jboss.org/browse/JBDS-2447
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.3.GA-SOA
> Reporter: Len DiMaggio
> Assignee: Douglas Palmer
> Fix For: 5.0.3.GA-SOA
>
>
> Issues to be resolved in SOA 5.0.3 Tooling*
> * This tooling is needed to support SOA-P 5.3.1 and will be certified with JBDS 5.0.2
> 1) ESB Issues
> https://issues.jboss.org/browse/JBDS-2444, https://bugzilla.redhat.com/show_bug.cgi?id=894120
> JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later
> https://issues.jboss.org/browse/JBIDE-13209
> Need to add ESB 4.12 option with constraints
> 2) EDS Issues - https://bugzilla.redhat.com/show_bug.cgi?id=893201
> https://bugzilla.redhat.com/show_bug.cgi?id=873834
> Provide the relational.xmd file which has the non-prepared extension property
> https://bugzilla.redhat.com/show_bug.cgi?id=893581
> (TEIIDDES-1255) Execution plan without executing the query
> https://bugzilla.redhat.com/show_bug.cgi?id=893583
> (TEIIDDES-1540) Non-UTF-8 Multi-byte characters imported from csv file are garbled
> Note: Related Issues Already Resolved in JBDS 5.0.2
> https://issues.jboss.org/browse/JBDS-2365
> ESB projects cannot be deployed using Server Add/Remove
> https://issues.jboss.org/browse/JBIDE-13328
> as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12
> https://issues.jboss.org/browse/JBDS-2394
> ESB projects cannot be deployed using Server Add/Remove
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBDS-2447) Issues to be resolved in SOA 5.0.3 Tooling
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2447?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2447:
------------------------------------
Example scenario:
New install of JBDS 5.0.2, install the ESB tooling, create a server runtime for SOA 5.2, and a corresponding ESB runtime of 4.10.
Then, reate a new ESB project - and the ESB runtime displayed in the wizard is 4.12, as this automatically defaults to the highest supported facet version on the runtime.
(From Brian)
For each version of ESB, we have declared an explicit facet. In org.jboss.tools.esb.project.core, we have facets defined (4.2,4.3,4.4,4.5,4.6,4.7,4.9,4.10,4.11,4.12) and assign them to EAP runtime components (4.3,5.0,6.0) (which are specified in the AS tools plug-ins). So every version of SOA-P based on EAP 4.3, 5.x, or 6.x supports every facet version we've defined thus far - up to 4.12
> Issues to be resolved in SOA 5.0.3 Tooling
> ------------------------------------------
>
> Key: JBDS-2447
> URL: https://issues.jboss.org/browse/JBDS-2447
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.3.GA-SOA
> Reporter: Len DiMaggio
> Assignee: Douglas Palmer
> Fix For: 5.0.3.GA-SOA
>
>
> Issues to be resolved in SOA 5.0.3 Tooling*
> * This tooling is needed to support SOA-P 5.3.1 and will be certified with JBDS 5.0.2
> 1) ESB Issues
> https://issues.jboss.org/browse/JBDS-2444, https://bugzilla.redhat.com/show_bug.cgi?id=894120
> JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later
> https://issues.jboss.org/browse/JBIDE-13209
> Need to add ESB 4.12 option with constraints
> 2) EDS Issues - https://bugzilla.redhat.com/show_bug.cgi?id=893201
> https://bugzilla.redhat.com/show_bug.cgi?id=873834
> Provide the relational.xmd file which has the non-prepared extension property
> https://bugzilla.redhat.com/show_bug.cgi?id=893581
> (TEIIDDES-1255) Execution plan without executing the query
> https://bugzilla.redhat.com/show_bug.cgi?id=893583
> (TEIIDDES-1540) Non-UTF-8 Multi-byte characters imported from csv file are garbled
> Note: Related Issues Already Resolved in JBDS 5.0.2
> https://issues.jboss.org/browse/JBDS-2365
> ESB projects cannot be deployed using Server Add/Remove
> https://issues.jboss.org/browse/JBIDE-13328
> as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12
> https://issues.jboss.org/browse/JBDS-2394
> ESB projects cannot be deployed using Server Add/Remove
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13382) 'Server Behaviour' title in Server Editor should use American spelling
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13382?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13382:
---------------------------------------------
Just to comment, we got not specific standard, so we should just align with content services for this.
> 'Server Behaviour' title in Server Editor should use American spelling
> ----------------------------------------------------------------------
>
> Key: JBIDE-13382
> URL: https://issues.jboss.org/browse/JBIDE-13382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.1.0.Alpha1
>
>
> One of the section titles on the Overview page of the Server Editor is misspelled: Server Behavi*our* should be Server Behavi*or*
> American spellings should be followed, as you have with Application Reload Behavi*or* on the same page.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13397) remove upper limit on m2e requirements in org.eclipse.tools.maven.* MANIFEST.MF files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13397?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13397:
------------------------------------
When I add both 0.16 and 0.15.3, it works.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl...
When I only add the 0.15.3 site, the install test that uses m2e 1.2 then tries to install JBT maven tools + JBT Central fails.
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stable_branch.director-install-tests.m2e.matrix/20/DownstreamSite=download.jboss.org%2Fjbosstools%2Fupdates%2Fnightly%2Fcore%2F3.3.indigo%2F,UpstreamSite=download.eclipse.org%2Ftechnology%2Fm2e%2Freleases%2F1.2%2F1.2.0.20120903-1050,eclipseBundleVersion=indigo.SR2,label=RHEL5_x86/console}
run.director:
[echo] Profile Name: epp.package.jee
[echo] Install Path: /qa/services/hudson/hudson_workspace/workspace/jbosstools-3.3_stable_branch.director-install-tests.m2e.matrix/DownstreamSite/download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/UpstreamSite/download.eclipse.org/technology/m2e/releases/1.2/1.2.0.20120903-1050/eclipseBundleVersion/indigo.SR2/label/RHEL5_x86/eclipse
[echo] Source Sites: http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/,htt...
[echo] IUS to Install:
[echo] org.jboss.tools.maven.feature.feature.group,org.jboss.tools.community.central.feature.feature.group
[p2.dir] Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product -application org.eclipse.equinox.p2.director -clean -consoleLog -flavor tooling -profile epp.package.jee -destination /qa/services/hudson/hudson_workspace/workspace/jbosstools-3.3_stable_branch.director-install-tests.m2e.matrix/DownstreamSite/download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/UpstreamSite/download.eclipse.org/technology/m2e/releases/1.2/1.2.0.20120903-1050/eclipseBundleVersion/indigo.SR2/label/RHEL5_x86/eclipse -bundlepool /qa/services/hudson/hudson_workspace/workspace/jbosstools-3.3_stable_branch.director-install-tests.m2e.matrix/DownstreamSite/download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/UpstreamSite/download.eclipse.org/technology/m2e/releases/1.2/1.2.0.20120903-1050/eclipseBundleVersion/indigo.SR2/label/RHEL5_x86/eclipse -installIU org.jboss.tools.maven.feature.feature.group,org.jboss.tools.community.central.feature.feature.group -metadataRepository http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/,htt... -artifactRepository http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/,htt... -profileProperties org.eclipse.update.install.features=true
[p2.dir]
[p2.dir] !ENTRY org.eclipse.osgi 4 0 2013-01-18 02:14:02.595
[p2.dir] !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-3.3_stable_branch.director-install-tests.m2e.matrix/DownstreamSite/download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/UpstreamSite/download.eclipse.org/technology/m2e/releases/1.2/1.2.0.20120903-1050/eclipseBundleVersion/indigo.SR2/label/RHEL5_x86/eclipse/configuration/org.eclipse.osgi
[p2.dir] Installing org.jboss.tools.maven.feature.feature.group 1.3.2.v20130112-0608-H143-Final.
[p2.dir] Installing org.jboss.tools.community.central.feature.feature.group 1.0.1.v20130112-0624-H128-Final.
[p2.dir] Installation failed.
[p2.dir]
[p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency.
[p2.dir] !MESSAGE Software being installed: JBoss Maven Integration 1.3.2.v20130112-0608-H143-Final (org.jboss.tools.maven.feature.feature.group 1.3.2.v20130112-0608-H143-Final)
[p2.dir] !MESSAGE Software currently installed: m2e - Maven Integration for Eclipse 1.2.0.20120903-1050 (org.eclipse.m2e.feature.feature.group 1.2.0.20120903-1050)
[p2.dir] !MESSAGE Only one of the following can be installed at once:
[p2.dir] !MESSAGE Maven / Nexus Indexer Bundle 1.0.200.20111228-1245 (org.eclipse.m2e.maven.indexer 1.0.200.20111228-1245)
[p2.dir] !MESSAGE Maven / Nexus Indexer Bundle 1.2.0.20120903-0645 (org.eclipse.m2e.maven.indexer 1.2.0.20120903-0645)
[p2.dir] !MESSAGE Cannot satisfy dependency:
[p2.dir] !MESSAGE From: Maven Integration for Eclipse 1.0.200.20111228-1245 (org.eclipse.m2e.core 1.0.200.20111228-1245)
[p2.dir] !MESSAGE To: bundle org.eclipse.m2e.maven.indexer [1.0.0,1.1.0)
[p2.dir] !MESSAGE Cannot satisfy dependency:
[p2.dir] !MESSAGE From: m2e - Maven Integration for Eclipse 1.2.0.20120903-1050 (org.eclipse.m2e.feature.feature.group 1.2.0.20120903-1050)
[p2.dir] !MESSAGE To: org.eclipse.m2e.maven.indexer [1.2.0.20120903-0645]
[p2.dir] Software being installed: JBoss Maven Integration 1.3.2.v20130ctor 4 1 2013-01-18 02:14:37.587
[p2.dir] !MESSAGE Cannot satisfy dependency:
[p2.dir] Software currently installed:02:14:37.588
[p2.dir] !MESSAGE From: JBoss Maven Core 1.3.2.v20130112-0608-H143-Final (org.jboss.tools.maven.core 1.3.2.v20130112-0608-H1 m2e - Maven Integration for Eclipse 1.2.0.20120903-1050 (org.eclipse.m2e.feature.feature.group 1.2.0.20120903-1050)
[p2.dir] Only one o43-Final)
[p2.dir] !MESSAGE To: bundle org.maven.ide.eclipse.wtp f the following can be installed at once:
[p2.dir] Maven / Nexus Indexer Bundle 1.0.200.20111228-1245 (org.eclipse.m2e.maven.indexer 1[0.13.0,0.16.0)
[p2.dir] !MESSAGE Cannot satisfy dependency:
[p2.dir] Maven / Nexus Indexer Bundle 1.2.0.20120903-0645 (org.eclipse.m2e.maven.indexer 1.2.0.20120903-0645)
[p2.dir] CaENTRY 2 org.eclipse.equinox.p2.director 4 0 2013-01-18 02:14:37.588
[p2.dir] !MESSAGE From: JBoss Maven Integration 1.3.2.v20130112-0608-nnot satisfy dependency:
[p2.dir] From: Maven Integration for Eclipse 1.0.200.20111228-1245 (org.eclipse.m2e.core 1.0.200.20111228-1245H143-Final (org.jboss.tools.maven.feature.feature.group 1.3.2.v20130112-0608-H143-Final)
[p2.dir] To: bundle org.eclipse.m2e.maven.indexer [1.0.0,1.1.0)
[p2.dir] Cannot satisfy dependency:
[p2.dir] From: m2e - Maven Integration for Eclipctor 4 0 2013-01-18 02:14:37.588
[p2.dir] !MESSAGE To: org.jboss.tools.maven.core [1.3.2.v20130112-0608-H143-Final]
[p2.dir] To: org.eclipse.m2e.maven.indexer [1.2.0.20se.equinox.p2.director 4 1 2013-01-18 02:14:37.589
[p2.dir] !MESSAGE Cannot satisfy dependency:
[p2.dir] Cannot satisfy dependency:
[p2.dir] From: JBoss Maven Core 1.3.2.v20130112-0608-H143-Final (org.jboss.tools.maven.core 1.or 4 0 2013-01-18 02:14:37.589
[p2.dir] !MESSAGE From: Maven Integration for Eclipse WTP 0.15.2.20120306-2040 (org.maven.ide.eclipse.wtp 3.2.v20130112-0608-H143-Final)
[p2.dir] To: bundle org.maven.ide.eclipse.wtp [0.13.0,0.16.0)
[p2.dir] Cannot satisfy dependency:
[p2.dir] From: JBoss 0.15.2.20120306-2040)
[p2.dir] !MESSAGE To: bundle org.eclipse.m2Maven Integration 1.3.2.v20130112-0608-H143-Final (org.jboss.tools.maven.feature.feature.group 1.3.2.v20130112-0608-H143-Final)
[p2.dir] e.core [1.0.0,1.2.0)
[p2.dir] !MESSAGE Cannot satisfy dependency: To: org.jboss.tools.maven.core [1.3.2.v20130112-0608-H143-Final]
[p2.dir] Cannot satisfy dependency:
[p2.dir] From: Maven Integration for Ecl
[p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2013-01-18 02:14:37.590
[p2.dir] !MESSAGE From: Maven Integration for Eclipse WTP 0.15.3ipse WTP 0.15.2.20120306-2040 (org.maven.ide.eclipse.wtp 0.15.2.20120306-2040)
[p2.dir] To: bundle org.eclipse.m2e.core [1.0.0,1.2.0)
[p2.dir] .20120830-0850 (org.maven.ide.eclipse.wtp 0.15.3.20120830-0850)
[p2.dir] Cannot satisfy dependency:
[p2.dir] From: Maven Integration for Eclipse WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp 0.15.3.2012:37.590
[p2.dir] !MESSAGE To: bundle org.sonatype.m2e.mavenarchiver 0.14.0
[p2.dir] To: bundle org.sonatype.m2e.mavenarchiver 0.14.0
[p2.dir] Cannot satisfy dependency:
[p2.dir] From: m2e connector for the mavenarc14:37.590
[p2.dir] !MESSAGE Cannot satisfy dependency:
[p2.dir] !MESSAGE Fhiver and pom properties 0.15.0.201109290002 (org.sonatype.m2e.mavenarchiver 0.15.0.201109290002)
[p2.dir] To: bundle org.eclipse.m2e.crom: m2e connector for the mavenarchiver and pom properties 0.15.0.201109290002 (org.sonatype.m2e.mavenarchiver 0.15.0.201109290ore [1.0.0,1.2.0)
{code}
> remove upper limit on m2e requirements in org.eclipse.tools.maven.* MANIFEST.MF files
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-13397
> URL: https://issues.jboss.org/browse/JBIDE-13397
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Marketplace, maven
> Affects Versions: 3.3.2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 3.3.2
>
> Attachments: JBIDE13397.patch.bundle-version-to-1.0.0.txt
>
>
> Looks like we need another fix here to make installation of org.jboss.tools.maven.* plugins possible when m2e > 1.1 is installed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months