[JBoss JIRA] (JBIDE-10036) Forge and JAX-RS: Project configuration is not up-to-date with pom.xml. Run project configuration update
by Burr Sutter (Created) (JIRA)
Forge and JAX-RS: Project configuration is not up-to-date with pom.xml. Run project configuration update
--------------------------------------------------------------------------------------------------------
Key: JBIDE-10036
URL: https://issues.jboss.org/browse/JBIDE-10036
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Environment: 3.3.M4 (QA version)
Reporter: Burr Sutter
Attachments: Forge_JBossTools-3.png, Forge_JBossTools-4.png, Forge_JBossTools-5.png
Following this Forge "script"
new-project --named forgeProject1 --topLevelPackage com.burrsutter.forgeProject1
persistence setup --provider HIBERNATE --container JBOSS_AS7
I notice that the project is not refresh to show the additional generated files. So I right-click on the project and select Refresh from the context menu and I get a red x, opening up the Problems tab tells me that
"Project configuration is not up-to-date with pom.xml. Run project configuration update".
This message is a challenge - finding 'project configuration update' in the menu system is difficult. A new Maven user would not know that the right item is
Right-click on the project, Maven -> Update Project Configuration
This step should have happened automatically
After running Update Project Configuration, the next error is
"error: Attribute servlet-name references to javax.ws.rs.core.Application that is not a servlet"
What was thrown into web.xml
<servlet-mapping>
<servlet-name>javax.ws.rs.core.Application</servlet-name>
<url-pattern>/rest/*</url-pattern>
</servlet-mapping>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-12085) Make sure launching Forge creates a ForgeRuntimeProcss subclass of the default RuntimeProcess
by Koen Aers (JIRA)
Koen Aers created JBIDE-12085:
---------------------------------
Summary: Make sure launching Forge creates a ForgeRuntimeProcss subclass of the default RuntimeProcess
Key: JBIDE-12085
URL: https://issues.jboss.org/browse/JBIDE-12085
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Koen Aers
Assignee: Koen Aers
Fix For: 3.4.0.M1
- create ForgeRuntimeProcess class as subclass of RuntimeProcess
- override getProxies() so it returns null
- create a getForgeProxies() method that delegates to super.getProxies()
- create and contribute ForgeProcessFactory that creates ForgeRuntimeProcesses
- make sure that the process returned by the launch method in ForgeLaunchHelper always is a ForgeRuntimeProcess
- use the register='true' flag in launchConfiguration.launch() so that the process is always registered
- use the getForgeProxies() method in the AbstractForgeRuntime class instead of the getProxies method
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBDS-2176) Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2176?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2176 at 6/3/12 2:24 PM:
----------------------------------------------------------
Down to 4 major differences:
1.
JBDS installer from Tycho (left): org.eclipse.net4j.jms.api plugin is included.
JBDS installer from PDE (right): no such plugin included.
Also, the Tycho installer is missing the about_files/ folder and the about.html root file.
!jbds2176_orphans.png!
2.
Here's how bundles.info varies, showing the difference between jarred and unpacked plugins, and the addition of the additional org.eclipse.net4j.jms.api plugin:
!jbds2176_bundles.info.png!
3.
Config.ini is slightly different - PDE installer includes
{code}org.eclipse.update.reconcil=false{code}
This is because of PDE/Build's default configuration settings (http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.pde.doc.user...). Tycho does not set this default.
Do we need it? Given the help docs state the property is called "org.eclipse.update.reconcile", not ".reconcil", I would guess that this isn't actually doing anything.
!jbds2176_config.ini.png!
4.
jbdevstudio.ini is also different - PDE installer includes
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505{code}
whereas Tycho installer includes
{code}-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-1438.jar@1:start{code}
!jbds2176_jbdevstudio.ini.png!
was (Author: nickboldt):
JBDS installer from Tycho (left): org.eclipse.net4j.jms.api plugin is included.
JBDS installer from PDE (right):
no such plugin included.
Also, the Tycho installer is missing the about_files/ folder and the about.html root file.
!jbds2176_orphans.png!
Here's how bundles.info varies, showing the difference between jarred and unpacked plugins, and the addition of the additional org.eclipse.net4j.jms.api plugin:
!jbds2176_bundles.info.png!
Config.ini is slightly different - PDE installer includes {code}org.eclipse.update.reconcil=false{code}; tycho installer does not:
!jbds2176_config.ini.png!
jbdevstudio.ini is also different - PDE installer includes
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505{code}
whereas Tycho installer includes
{code}-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-1438.jar@1:start{code}
!jbds2176_jbdevstudio.ini.png!
> Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2176
> URL: https://issues.jboss.org/browse/JBDS-2176
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 5.0.0.CR1
>
> Attachments: jbds2176_bundles.info.png, jbds2176_config.ini.png, jbds2176_jbdevstudio.ini.png, jbds2176_orphans.png, lucene.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png
>
>
> Comparing the on-disk footprints for the two installers, I see some discrepancies.
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png!
> Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j
> Right: unpcked plugins
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png!
> Left: javax.servlet 3.0; no org.apache.lucene
> Right: no javax.servlet; org.apache.lucene 2.9.1
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png!
> Left: org.eclipse.jetty
> Right: no jetty
> !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png!
> Left: org.eclipse.mylyn.commons.workbench, org.jdom
> Right: no org.eclipse.mylyn.commons.workbench; no org.jdom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months