[jbosstools-issues] [JBoss JIRA] (JBIDE-17396) Unable to discover version of WF 8.1.0 patched build
Martin Malina (JIRA)
issues at jboss.org
Tue May 27 09:31:57 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-17396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Malina updated JBIDE-17396:
----------------------------------
Fix Version/s: 4.2.0.Beta3
(was: 4.2.0.Beta2)
Labels: (was: respin-a)
Rob, correct me if I'm wrong, but this one is for master (Beta3) and JBIDE-17397 is for Beta2 respin.
> Unable to discover version of WF 8.1.0 patched build
> -----------------------------------------------------
>
> Key: JBIDE-17396
> URL: https://issues.jboss.org/browse/JBIDE-17396
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> Creating a server/runtime out of a patch-build wildfly8.1.0.CR4 cannot correctly determine the version of the given home directory.
> The reason for this bug is that the class in charge of discovering a server version is looking for a jar that can properly give the versioning information. For wildfly, we are looking to introspect the jar modules/system/layers/org/jboss/as/server/main/*.jar. And we are looking for the manifest.mf property key: JBossAS-Release-Version
> Currently, trying to introspect this jar fails, because the jar is an invalid jar file.
> It must be recognized that there is now no safe way / agreed-upon API to determine the version of a given server installation when the server is stopped.
> There are options:
> 1) We respect the module structure / overlay layout and simply look for the correct module folder for "org.jboss.as.server", or
> 2) We agree to one single file that will be updated and hold the version information for a given project or product release.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
More information about the jbosstools-issues
mailing list