[JBoss JIRA] (JBIDE-18711) Cordova plugin addition and removal fails when config.xml is in a linked folder
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18711?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-18711:
--------------------------------------
I think this is probably a different issue with the config.xml editor. Can you actually open a separate one.
> Cordova plugin addition and removal fails when config.xml is in a linked folder
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18711
> URL: https://issues.jboss.org/browse/JBIDE-18711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Environment: Oracle JDK 1.8.0_05, Mac OS X Mavericks
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.2.1.CR1
>
>
> When config.xml is present in an Eclipse Linked folder (not in a symbolic link), then attempting to add or remove plugins (and possibly other operations on config.xml) fails with a spurious NullPointerException (without a stacktrace).
> This pretty much means that the Hybrid Mobile application project with a linked folder for 'www' is in a read-only state for plugin addition/removal. If any plugin should be added or removed, the linked folder must be dropped, converted to an ordinary folder (or symbolic link), and then re-created after modifications.
> To verify
> 1. create a new project
> 2. copy www folder to an alternate location
> 3. remove www folder
> 4.add www folder from alternate location as a linked folder (New Folder > Advanced> Link to alternate location)
> 5. add cordova plugins to the project. [Check they are added]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18837:
---------------------------------------
I didn't test it, but it looks like jbosstools.version property is going to get value below
{code}${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.${parsedVersion.incrementalVersion}.Alpha1{code}
because properties are immutable and set before plug-ins execution is taking place. Am i wrong?
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months