[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2484:
-----------------------------
Description:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 - JBDS-2486
* springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
* findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
* pmd/3.2.6 - nothing new as of 2013.02.28
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
Latest sites:
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
was:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 -
* springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
* findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
* pmd/3.2.6 - nothing new as of 2013.02.28
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
Latest sites:
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 - JBDS-2486
> * springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
> * findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
> * pmd/3.2.6 - nothing new as of 2013.02.28
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
> Latest sites:
> http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
> https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
--
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
12 years, 8 months
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2484:
-----------------------------
Description:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 -
* springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
* findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
* pmd/3.2.6 - nothing new as of 2013.02.28
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
Latest sites:
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
was:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 -
* springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 -
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
* findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
* pmd/3.2.6 - nothing new as of 2013.02.28
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
Latest sites:
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 -
> * springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 - JBDS-2485
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
> * findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
> * pmd/3.2.6 - nothing new as of 2013.02.28
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
> Latest sites:
> http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
> https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
--
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
12 years, 8 months
[JBoss JIRA] (JBDS-2484) 3rd party certification for JBDS 7.x (JBDS70_1211)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2484?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2484:
-----------------------------
Description:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
* gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 -
* springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 -
* testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
These are currently unchanged since December when we released JBDS 6.0.0:
* eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
* findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
* pmd/3.2.6 - nothing new as of 2013.02.28
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
Latest sites:
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
was:
For JBDS 7, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.0.6.v20120628 - JBIDE-13670, JBIDE-13682
* eclipsecs/5.6.0.201209221626
* findbugs/2.0.2.20121210
* gwt/3.1.0.v201208080121-rel-r42
* pmd/3.2.6
* springide/2.7.2.201109122348 - JBDS-2395
* subclipse/1.8.16_1.7.5.v1
* testng/6.7.0.20120825_1316 - JBDS-2415
Additionally:
* egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
Latest sites:
http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
> 3rd party certification for JBDS 7.x (JBDS70_1211)
> --------------------------------------------------
>
> Key: JBDS-2484
> URL: https://issues.jboss.org/browse/JBDS-2484
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.0.6.v20120628 --> 3.0.7.v20121218 - JBIDE-13670, JBIDE-13682
> * gwt/3.1.0.v201208080121-rel-r42 --> 3.2.0.v201302131858-rel-r42 -
> * springide/2.7.2.201109122348 --> 3.2.0.201301251408-M2 - JBDS-2395
> * subclipse/1.8.16_1.7.5.v1 --> 1.8.18_1.7.8.1 -
> * testng/6.7.0.20120825_1316 --> 6.8.0.20121120_1820 - JBDS-2415
> These are currently unchanged since December when we released JBDS 6.0.0:
> * eclipsecs/5.6.0.201209221626 - nothing new as of 2013.02.28
> * findbugs/2.0.2.20121210 - nothing new as of 2013.02.28
> * pmd/3.2.6 - nothing new as of 2013.02.28
> Additionally:
> * egit/2.3.1.201302201838-r - JBIDE-13629 (not included in Kepler M5, but will be in M6; not part of Central as this is included in TP / Core)
> Latest sites:
> http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.0/composi...
> https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.0/compositeAr...
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13588) Openshift tools in JBT 4 require org.eclipse.egit.core [1.2.0, 2.3.0), but the version of EGit in Juno SR2 is 2.3.0.201302130906
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13588?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13588:
------------------------------------
To bump features/plugins to a new version:
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.3-SNAPSHOT
> Openshift tools in JBT 4 require org.eclipse.egit.core [1.2.0,2.3.0), but the version of EGit in Juno SR2 is 2.3.0.201302130906
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13588
> URL: https://issues.jboss.org/browse/JBIDE-13588
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.1.Final
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Fix For: 4.0.1.Final
>
>
> Need to extend the upper bound in MANIFEST.MF and/or feature.xml files so Openshift tools in JBT 4 can depend on EGit <=2.3, not <2.3.
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--openshift/116/console}
> [ERROR] Software being installed: org.jboss.tools.openshift.egit.test 2.4.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.openshift.egit.core 2.4.0.Final-v20130218-1429-B116 requires 'bundle org.eclipse.egit.core [1.2.0,2.3.0)' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.openshift.egit.test 2.4.0.qualifier depends on: bundle org.jboss.tools.openshift.egit.core 1.0.0
> {code}
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13602) Backport to 4.0.x - Null Java EE Web Project Archetype
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13602:
---------------------------------------
tested on local build and could-not replicate the issue after PR is applied.
Pushed to jbosstools-4.0.x.
> Backport to 4.0.x - Null Java EE Web Project Archetype
> ------------------------------------------------------
>
> Key: JBIDE-13602
> URL: https://issues.jboss.org/browse/JBIDE-13602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Priority: Minor
> Labels: maven
> Fix For: 4.0.1.Final
>
>
> When trying to create a new Java EE Web Project, the following description is presented:
> {quote}
> This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1.
> This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.
> Project based on the *null:null:null* Maven archetype
> {quote}
> If I go forward with the creation of the project, I get the following error message:
> {quote}
> Failed to create project.
> Root cause: For artifact null:null:null:pom : The group id cannot be empty.
> {quote}
--
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
12 years, 8 months