[JBoss JIRA] (JBIDE-12854) JBoss Developer Framework Quickstarts - > in requirements
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-12854:
----------------------------------------
Summary: JBoss Developer Framework Quickstarts - > in requirements
Key: JBIDE-12854
URL: https://issues.jboss.org/browse/JBIDE-12854
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 4.0.0.Beta1
Reporter: Rastislav Wagner
Assignee: Snjezana Peco
Fix For: 4.0.0.CR1
There's a typo in requirements for examples:
m2e >=1.1.
m2e-wtp >=0.16.0.
(shows > instead of >)
Affected examples are:
Hello World JSF
Hello World JMS
Hello World Errai
Hello World OSGi
under JBoss Developer Framework Quickstarts
--
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, 4 months
[JBoss JIRA] (JBIDE-13007) Maven custom packaging types fail after version/coordinate change. Project files must be deleted and re-imported.
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created JBIDE-13007:
------------------------------------------
Summary: Maven custom packaging types fail after version/coordinate change. Project files must be deleted and re-imported.
Key: JBIDE-13007
URL: https://issues.jboss.org/browse/JBIDE-13007
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.0.0.Alpha2
Reporter: Lincoln Baxter III
Assignee: Fred Bricon
When using custom packaging types, assuming the packaging plugin is resolved correctly, the configuration works fine. However, after changing the packaging type coordinates, the plugin is no longer correctly configured, and the project must be completely deleted (eclipse .settings, .project/ and .classpath files) in order to correctly re-configure the project.
--
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, 4 months
[JBoss JIRA] (JBIDE-12608) Replace local.* properties and profiles by Maven mirroring
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-12608:
--------------------------------------
Summary: Replace local.* properties and profiles by Maven mirroring
Key: JBIDE-12608
URL: https://issues.jboss.org/browse/JBIDE-12608
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Affects Versions: 4.0.0.Alpha2
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
Currently, we deal with optimization for Jenkins by multiple local.* properties and local.* profiles.
Those properties and profiles are just used in order to replace repository URL.
Maven has the concept of mirroring for that, and without adding a profile, we can tell Maven to consume another URL for a given repo. Moreover, Tycho will support mirrors for repo in .target files starting from 0.16.0.
WE should move to the mirror approach since it keeps things clear and separate issues: pom describe build, mirror allow to override repo without any change.
Seems like Maven supports having 2 settings.xml files as input (one with -gs and one with -s), so no big difficulty here.
--
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, 4 months
[JBoss JIRA] (JBDS-2393) remove all refs to extras site
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2393:
--------------------------------
Summary: remove all refs to extras site
Key: JBDS-2393
URL: https://issues.jboss.org/browse/JBDS-2393
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite
Affects Versions: 6.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Minor
The following files in devstudio svn trunk need to be revised to no longer reference an extras/ site, if in fact we're going to obsolete it in favour of the Central composite site.
{quote}
./documentation/Release_Guide/2012_Release_JBDS_Staging_For_QE.txt
./devstudio.jboss.com/updates/6.0/central/core/compositeArtifacts.xml
./devstudio.jboss.com/updates/6.0/central/core/compositeContent.xml
./devstudio.jboss.com/updates/6.0-staging/central/core/compositeArtifacts.xml
./devstudio.jboss.com/updates/6.0-staging/central/core/compositeContent.xml
./devstudio.jboss.com/updates/6.0-staging/updatesites.xml
./devstudio.jboss.com/updates/6.0-staging/index.html
./devstudio.jboss.com/updates/6.0/index.html
./devstudio.jboss.com/updates/6.0/updatesites.xml
./product/features/com.jboss.jbds.product.feature.source/feature.xml
./product/site/associate.properties
./extras/site/associate.properties
./techpreview/features/com.jboss.jbds.byoe.feature/feature.xml
./techpreview/site/associate.properties
./product-soa/site/associate.properties
./qa/install-extras/jbds.properties
{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
13 years, 4 months
[JBoss JIRA] (JBIDE-12575) Problem with CDI validator
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12575:
-----------------------------------------
Summary: Problem with CDI validator
Key: JBIDE-12575
URL: https://issues.jboss.org/browse/JBIDE-12575
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 4.0.0.Alpha1
Reporter: Jaroslav Jankovič
Assignee: Alexey Kazakov
Fix For: 4.0.0.Alpha1
There is a problem to force CDI validator to work. In my case, I created simple dynamic web project without CDI support, added some bean with Multiple beans eligible case (message not present yet). Add CDI support into project. Expected validation messages won't appear - cleaning the project doesn't help either.
--
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, 4 months
[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2389:
--------------------------------
Summary: cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
Key: JBDS-2389
URL: https://issues.jboss.org/browse/JBDS-2389
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer, updatesite
Affects Versions: 6.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 6.0.0.CR2
Bare Juno JEE eclipse.ini:
{code}
$➔ cat eclipse/eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
{code}
or, for Eclipse Platform Binary:
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Xms40m
-Xmx384m
{code}
After installing JBDS BYOE:
{code}
$➔ cat eclipse/eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Xms512m
-Xmx1024m
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
{code}
After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini:
{code}
$➔ cat eclipse/jbdevstudio.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-product
com.jboss.jbds.product.product
-showsplash
platform:/base/plugins/com.jboss.jbds.product
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
-Xms512m
-Xmx1024m
-Dosgi.instance.area.default=(a)user.home/workspace
{code}
After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file:
{code}
$➔ cat eclipse/eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
-product
com.jboss.jbds.product.product
-showsplash
platform:/base/plugins/com.jboss.jbds.product
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
-Xms512m
-Xmx1024m
{code}
So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines
{code}
-product
com.jboss.jbds.product.product
-showsplash
platform:/base/plugins/com.jboss.jbds.product
{code}
and replace them with the following when JBDS is uninstalled:
{code}
-application
org.eclipse.ui.ide.workbench
-showsplash
org.eclipse.platform
{code}
Also need to know what happens if there are two -product directives... can we just
add (and later remove, when uninstalling) our product to the list, or must we replace
any existing -product entries with ours?
--
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, 4 months
[JBoss JIRA] (JBIDE-13121) Web XML Editor: Edit Small-Icon and Edit Large-Icon dialogs allow to select folder
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-13121:
-------------------------------------
Summary: Web XML Editor: Edit Small-Icon and Edit Large-Icon dialogs allow to select folder
Key: JBIDE-13121
URL: https://issues.jboss.org/browse/JBIDE-13121
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 4.0.0.CR1
Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121118-2035-B111.jar
Reporter: Daniel Azarov
Assignee: Alexey Kazakov
Priority: Minor
Test case:
EXECUTE:
1. Create JSF KickStart project
2. Open web.xml in Web XML Editor
3. Press "Browse" button next to "Small-Icon" or "Large-Icon" in Advanced section.
4. Select "META-INF" folder then press "OK" button
5. Save the file
5. Select "Source" tab
FAIL:
There is "small-icon references to "/META-INF/" that does not exist in web content" problem marker
--
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, 4 months
[JBoss JIRA] (JBIDE-12860) Jaxrs validation problems are not linked
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12860:
-----------------------------------------
Summary: Jaxrs validation problems are not linked
Key: JBIDE-12860
URL: https://issues.jboss.org/browse/JBIDE-12860
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 4.0.0.Beta1
Reporter: Jaroslav Jankovič
Assignee: Xavier Coulon
Fix For: 4.0.0.Beta1, 4.0.x
This case now fails:
STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
STEP: comment servlet definition in web.xml
ASSERT: problem marker in web.xml disappears
ASSERT: problem marker in application class disappears
FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 4 months