[JBoss JIRA] Created: (JBIDE-4127) "Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath
by Leiv Hellebo (JIRA)
"Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath
--------------------------------------------------------------------------------------
Key: JBIDE-4127
URL: https://jira.jboss.org/jira/browse/JBIDE-4127
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.0.0.GA
Environment: JBDS 2.0.GA
Seam 2.1.X
Reporter: Leiv Hellebo
The Add JSF-Capabilities dialog makes it possible to shoot oneself in the foot:
It will happily add jsf-facelets.jar with Implementation-Version: 1.1.11, even if the one mentioned in .classpath has Implementation-Version: 1.1.15.B1
AFAICS, when performing a redirect within a long-running conversation, this makes
"DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>> Begin re-initialization"
disappear from server.log, and needed context vars are not initialized.
I'd file this as an "Improvement", not a "Bug" if it was possible. You may want to say "PEBKAC" to this...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9268) Align versions across poms on each module
by Max Rydahl Andersen (JIRA)
Align versions across poms on each module
-----------------------------------------
Key: JBIDE-9268
URL: https://issues.jboss.org/browse/JBIDE-9268
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup, Build/Releng
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.M3
We recently aligned the pom's within each jboss tools module svn to have "natural parents" meaning the only pom within a module that refers the parent pom is the "root" one.
i.e. hibernatetools/pom.xml instead of *all* plugins and features inside the module.
That made updating parent pom's easy, now we should just get the pom versions aligned within the module to allow easy update of versions in that module without manual tweaking of files.
What this allows is that you can use commands like this:
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.4.0-SNAPSHOT
and tycho will take care of updating all pom/manifest/feature.xml/product defs for that module subdirectory.
(if the references are *outside* that directory then of course things won't be updated automatically)
The changes i'm planning will do two things:
1) Align all versions within one module (that is needed for the one command version update)
2) Remove all redundant <version> references when the parent reference is enough.
Please note, that if a module owner wish to manage individual plugin versions that is perfectly still doable
they just need to add the explicit <version> reference and cannot rely on the one command version update
to work automatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
by Magnus Mogren (JIRA)
Automatic detection of server ports cannot handle changing configuration from default
-------------------------------------------------------------------------------------
Key: JBIDE-8355
URL: https://issues.jboss.org/browse/JBIDE-8355
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
I create a new server for JBoss AS 6.0.
I select the "default" configuration in the "New server" dialog.
JNDI port is detected as 1099 as it should be.
Now i open the "Edit server runtime environment" dialog and change from "default" to "all" configuration.
I have edited the conf/bindingservice.beans\META-INF\bindings-jboss-beans.xml file to use JNDI port 11099 instead of 1099 for the "all" configuration.
Now the autodetected JNDI port is still 1099?
If i click the "Configure..." next to the auto detect checkbox and then "Edit XPath" i see that the root directory is still pointing to the default configuration.
If i click the browse button and try to change the root directory it does not take the change. It still points to the default directory the next time i open the "Edit XPath" dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9399) JBoss 7.1 not usable
by Juergen Zimmermann (JIRA)
JBoss 7.1 not usable
--------------------
Key: JBIDE-9399
URL: https://issues.jboss.org/browse/JBIDE-9399
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.3.0.M2
Environment: build 3203
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
JBoss 7.1 (snapshots) are not directly usable. When creating such a server, then a warning appears (screenshot will be attached). After the creating the "launch configuration properties" are wrong regarding the "Program arguments":
* --configuration=default
* instead of: -mp "c:/Software/jboss/modules" -logmodule org.jboss.logmanager -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone
It would be could if this issue could be fixed. Thank you.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months